Deployment-Based Scanning


Jit offers the option to trigger runtime scanning tools when a new code deployment is detected. Scanning runtime environments every time a deployment occurs reduces the chances of security issues finding their way onto runtime environments.

Deployment-based scanning is available for the following security requirements—


  1. Deployment via Github actions Jit deployment scanning currently only supports deployments via Github actions. Support for more deployment services is coming soon. In order to use deployment scanning, a deployment job must be included in the Github actions workflow. Jit looks for the environments:<name> tag in the workflow YAML to determine if a deployment has occurred and will look for the environment name to know which runtime environment to scan. Learn more about deployments with Github actions.
name: 'Deploy to staging'

      - dev
      - main
      - main
    environment: staging
    runs-on: ubuntu-latest
      - uses: actions/checkout@v2
  1. Slack integration is required to enable deployment scanning.

Configuring deployment scanning

When activating one of the supported security controls, set the trigger in the control configuration to Scan on deployment:

Under Environment name enter the environment defined in the deployment YAML on Github actions. Jit needs an exact match between the environment name defined on Jit and on Github Actions to trigger a scan.

Note - Environment names are global. When you change it in any control configuration, it will change on all controls.

Slack notifications

Jit requires an active Slack integration to enable deployment scanning. You can configure Slack via the Integrations page or when configuring a security control that supports deployment scanning.

When a deployment scan detects findings, it will report them in two places:

  1. The pipelines page, under a Deployment pipeline.
  2. A Slack notification, sent to the selected channel under Deployments in the Slack integration configuration: