Skip to main content

Finding Post Processing

License Apache-2.0GitHub release (latest SemVer)OWASP Lab ProjectArtifact HUBGitHub Repo starsMastodon Follower

What is "Finding Post Processing" Hook about?

Installing the Finding Post Processing hook will add a ReadAndWrite Hook to your namespace, which can be used to add or update fields from your findings meeting specified conditions.


The finding-post-processing chart can be deployed via helm:

# Install HelmChart (use -n to configure another namespace)
helm upgrade --install finding-post-processing oci://


Kubernetes: >=v1.11.0-0

Additional Chart Configurations

Rule Configuration

The rules can be defined in the values of the HelmChart. The syntax and semantic for these rules are quite similar to CascadingRules (See: secureCodeBox | CascadingRules)

To define rules you will have to provide the rules field with one or more matches elements. Each machtes defines one Rule. For example:

- matches:
- category: "Open Port"
port: 23
state: open
severity: "high"
description: "Telnet is bad"

This rule will match all findings with an open port on 23 and override the severity for this finding with high as well as providing a new description Telnet is bad!.


Within the matches you will have to provide anyOf and override. In the anyOf contains one or more conditions to be met by the finding to match the rule. Notice that only one of these elements needs to match the finding for the rule to match.


The override field specifies the desired fields and values that need to be updated or added if the rule is matching.


hook.affinityobject{}Optional affinity settings that control how the hook job is scheduled (see:
hook.envlist[]Optional environment variables mapped into the hook (see:
hook.extraVolumeMountslist[]Optional VolumeMounts mapped into the hook (see:
hook.extraVolumeslist[]Optional Volumes mapped into the hook (see:
hook.image.repositorystring""Hook image repository
hook.image.tagstringdefaults to the charts versionThe image Tag defaults to the charts version if not defined.
hook.labelsobject{}Add Kubernetes Labels to the hook definition
hook.priorityint0Hook priority. Higher priority Hooks are guaranteed to execute before low priority Hooks.
hook.resourcesobject{ requests: { cpu: "200m", memory: "100Mi" }, limits: { cpu: "400m", memory: "200Mi" } }Optional resources lets you control resource limits and requests for the hook container. See
hook.tolerationslist[]Optional tolerations settings that control how the hook job is scheduled (see:
hook.ttlSecondsAfterFinishedstringnilSeconds after which the kubernetes job for the hook will be deleted. Requires the Kubernetes TTLAfterFinished controller:
imagePullSecretslist[]Define imagePullSecrets when a private registry is used (see:



Code of secureCodeBox is licensed under the Apache License 2.0.