Skip to main content


title: Notification Hook category: hook type: integration state: roadmap usecase: 'Publishes Scan Summary to MS Teams, Slack and others.' custom_edit_url: >-


Installing the Notification hook will add a ReadOnly Hook to your namespace.

helm upgrade --install nwh ./hooks/notification-hook/ --values /path/to/your/values"

The values.yaml you need depends on the notification type you want to use. Please take a look at the documentation for each type (e.g. for slack see Configuration of a Slack Notification)

Available Notifier

Configuration of a Notification

The general configuration of a notification looks something like this

  - name: slack
    type: slack
    template: slack-messageCard
    skipNotificationOnZeroFinding: true
      - matches:
            - category: "Open Port"
    endPoint: "SOME_ENV"

  - name: SOME_ENV
        secret: some-secret
        key: some-key

The Notification Hook enables you to define multiple so called notificationChannels. A notificationChannel defines the Notification to a specific platform (e.g. Slack or Teams).

The name is used to for debugging failing notifications. it can be a string of you choice.

The type specifies the type of the notification (in this example slack). See Available Notifier.

The template field defines the name of a Nunjucks template to send to your notification channel. These templates are usually tied to their notification channel (slack templates will not work for teams). The template slack-messageCard is provided by default. Notice that for the name of the template we chose to omit the file type. The template slack-messageCard will point to slack-messageCard.njk in the filesystem of the hook.

The skipNotificationOnZeroFindings if set to true will cause the notifier when there were no findings. This can happen when the scan did not identify any or if all findings were filtered out using rules. Defaults to false if not set. You can use skipNotificationOnZeroFindings to only send out notification for non duplicate findings, e.g. by combining the DefectDojo hook with this one and filtering out the duplicate attribute in the rules.

The endPoint specifies where the notification has to go to. To protect the actual endPoint (e.g. a webhook url) this should point to an env name defined under env For slack this would be your webhook URL to slack.

To define conditions when a notification should be created you can use rules. If no rules are specified, this hook will assume that you always want to be notified.

Under env you have to define additional information needed for your templates such as the actual endpoint. env will be mapped to the env implementation of Kubernetes. This means that you can define key-value pairs as well as providing envs via secrets (See Define Environment Variables for a Container | Kubernetes).

Rule Configuration

The rules can be defined in the values of the Chart. 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

This Rule will match all Findings with an open port on 23.


Within the matches you will have to provide anyOf 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.

Configuration of a Slack Notification

To configure a Slack notification set the type to slack and the endPoint to point to your env containing your Webhook URL to slack. You can use one of the following default templates:

  • slack-messageCard: Sends a message with a summary listing the number of findings per category and severity.
  • slack-individual-findings-with-defectdojo: Sends a message with a list of all findings with a link to the finding in DefectDojo. Will only work correctly if the DefectDojo hook is installed in the same namespace.

Configuration of a Slack App Notification

The slack-app notifier is an alternate way to send notifications to slack using the slack api directly rather then using webhooks. Use slack-app over the normal slack if you want to send notifications into different slack channels on a per scan basis.

Slack App Configuration

To set it up, you'll need to create a new slack app at and add the chat:write "Bot Token Scope" to it on the "OAuth & Permissions" tab. Then add the bot to your workspace, this will give you the access token (should begin with a xoxb-).

To configure a Slack notification set the type to slack-app and reference the secret via the SLACK_APP_TOKEN env var.

Example Config

  - name: slack
    type: slack-app
    template: slack-messageCard
    rules: []

  # you can create the secret via: kubectl create secret generic slack-app-token --from-literal="token=xoxb-..."
        name: slack-app-token
        key: token
  # configures which channel the messages are send to if the scan doesn't specify a channel
    value: "#example-channel"

Supported Notification Channels

The slack-app notifier supports the same message templates as the slack notifier. See slack for the supported message types.

Scan / Channel Config

You can configure to which channel the message is sent to by setting the to the channel the message should be sent to, the following example will send its notifications to the #juice-shop-dev channel in the slack workspace of the configured token.

Note: The channel needs to have the app you've create invited to it. Otherwise the app will not be permitted to write to it.

apiVersion: ""
kind: Scan
  name: "nmap-juice-shop"
  annotations: "#juice-shop-dev"
  scanType: "nmap"
    - juice-shop.default.svc

Configuration Of An Email Notification

To configure an email notification set the type to email and the endPoint to point to your env containing your target email address. You can use one of the following default templates:

  • email: Sends a email with a summary listing the number of findings per category and severity.

Additional to this configuration you will have to provide a special smtp configuration URL. This config reflects the transporter configuration of nodemailer (See nodemailer | SMTP Transport). This configuration needs to be specified under env in the values yaml. The identifier for this config has to be SMTP_CONFIG. A basic configuration could look like this:

  - name: email
    type: email
    template: email
    rules: []
    endPoint: ""
  - name: SMTP_CONFIG
    value: "smtp://user:pass@smtp.domain.tld/"

To provide a custom from field for your email you can specify EMAIL_FROM under env. For example:

  - name: SMTP_CONFIG
    value: "smtp://user:pass@smtp.domain.tld/"
  - name: EMAIL_FROM
    value: secureCodeBox

Custom Message Templates

CAUTION: Nunjucks templates allow code to be injected! Use templates from trusted sources only!

The Notification Hook enables you to write your own message templates if the templates provided by default are not sufficient. Templates for this hook are written using the Nunjucks templating engine.

To fill your template with data we provide the following objects.

findingsAn array of the findings matching your rules (See [FindingsecureCodeBox](
scanAn Object containing information about the scan that triggered the notification (See [ScansecureCodeBox](
argscontains process.env (See: [process.envnodejs]( you can use this to access data defined in env of the values.yaml

Chart Configuration

hook.image.repositorystring""Hook image repository
hook.image.tagstringdefaults to the charts versionImage tag
hook.ttlSecondsAfterFinishedstringnilseconds after which the kubernetes job for the hook will be deleted. Requires the Kubernetes TTLAfterFinished controller:
notificationChannels[0].rules[0].matches.anyOf[0].categorystring"Open Port"