Skip to main content

ScanCompletionHook

ScanCompletionHooks are Custom Resource Definitions (CRD's) used to define custom behavior which should be run after a scan has been completed.

For more detailed explanations on how a new hook can be integrated, see the hooks section in the contribution part of our docs.

Specification (Spec)#

Type (Required)#

The type field can be either ReadOnly or ReadAndWrite.

ReadOnly hooks only have read rights on the findings and the raw scan reports (e.g. XML output from nmap). These are usually used to export the findings into a external system like "Elasticsearch" or "DefectDojo" or to send out notifications to chats like "Slack". ReadOnly hooks are executed in parallel to speed up their runtime.

ReadAndWrite hooks have the ability to update both the findings and raw scan reports. This can be used to attach additional metadata to the findings by comparing the findings to external inventory systems or APIs of cloud providers.

Priority (Optional)#

The priority field helps determine the execution order of the hook. Hooks with a higher priority will be scheduled before hooks with a lower priority. By default, hooks are given a priority of 0. Hooks with equal priority are scheduled according to the default schedule:

  1. Run ReadAndWrite hooks one by one (undefined order).
  2. Once all ReadAndWrite hooks are completed, ReadOnly hooks are scheduled in parallel.

The following diagram shows an example run:

                                 Priority 2                                          Priority 1                    Priority 0    +-------------------------------------------------------------------+     +----------------------+      +----------------------+    |    +--------------+       +--------------+       +--------------+ |     |    +--------------+  |      |    +--------------+  |     | -> | ReadAndWrite |------>| ReadAndWrite |------>|   ReadOnly   | |     | -> |   ReadOnly   |  | ---> | -> | ReadAndWrite |  |    |    +--------------+       +--------------+  |    +--------------+ |     |    +--------------+  |      |    +--------------+  |--> |                                             |                     | --> |                      |      +----------------------+    |                                             |    +--------------+ |     |    +--------------+  |    |                                             +--->|   ReadOnly   | |     | -> |   ReadOnly   |  |    |                                                  +--------------+ |     |    +--------------+  |    +-------------------------------------------------------------------+     +----------------------+

Image (Required)#

The image field contains a container image reference for the image supposed to run as the hook.

ImagePullSecrets (Optional)#

The imagePullSecrets field can be used to specify pull secrets used to access the hooks image from a private registry.

ImagePullPolicy (Optional)#

The imagePullPolicy field can be used to specify under which circumstances the images should be pulled from the registry. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. See the Kubernetes docs for more information.

Env (Optional)#

The env field can be used to specify env variables and to mount secrets into containers.

Volumes (Optional)#

volumes lets you specify Kubernetes volumes that you want to use and make available to the hook. Similarly to env, it can be used to pass data into a container. It has to be combined with volumeMounts to be useful (see below).

VolumeMounts (Optional)#

volumeMounts let you specify where you want the previously-created volumes to be mounted inside the container. It has the same API as the volumeMounts property on Kubernetes pods.

Affinity and Tolerations (optional)#

affinity and tolerations can be used to control which nodes the parser is executed on. The values should be set via Helm values (during install) or by specifying affinity and/or tolerations in the Scan specification.

ServiceAccountName (Optional)#

The serviceAccountName field can be used to specify a custom ServiceAccount to use for the Kubernetes Job running the hook. Should only be used if your hook needs specific RBAC Access. Otherwise the hook is run using a scan-completion-hook service account.

The service account should have at least get rights on scans.execution.securecodebox.io, and get & patch on scans.execution.securecodebox.io/status so that the hooks can work correctly.

TTLSecondsAfterFinished (Optional)#

ttlSecondsAfterFinished can be used to automatically delete the completed Kubernetes job used to run the hook. This sets the ttlSecondsAfterFinished field on the created job. This requires your cluster to have the TTLAfterFinished feature gate enabled in your cluster.

Example#

apiVersion: execution.securecodebox.io/v1kind: ScanCompletionHookmetadata:  name: elastic-persistence-hookspec:  type: ReadOnly  priority: 2  image: docker.io/securecodebox/persistence-elastic:latest  imagePullSecrets:  - name: image-pull-secret  serviceAccountName: elastic-persistence  env:  - name: ELASTICSEARCH_ADDRESS    value: https://data.chase.securecodebox.io  - name: ELASTICSEARCH_USERNAME    valueFrom:      secretKeyRef:        key: username        name: elastic-persistence-credentials  - name: ELASTICSEARCH_PASSWORD    valueFrom:      secretKeyRef:        key: password        name: elastic-persistence-credentials  ttlSecondsAfterFinished: 60