Azure Pipelines

OX Security integrates with Azure Pipelines to scan builds for vulnerabilities during the CI/CD process. Azure Pipelines integration is ideal for streamlined security embedded directly into the CI/CD process.

Prerequisites

• Docker support: Ensure your Azure agents can run Docker containers and execute docker run.

Required environment variables

Variable	Description
OX_API_KEY	The OX Security integration key.

Optional environment variables

Variable	Description
OX_OVERRIDE_BLOCKING	Set to true to override job failure caused by blocking issues.
OX_TIMEOUT	Maximum duration of the scan, in minutes.
OX_FAIL_ON_TIMEOUT	Set to true to fail the job if a scan times out.
OX_FAIL_ON_ERROR	Set to true to fail the job if a system or network error occurs.

Advanced environment variables

Variable	Description
OX_DISABLE_SSL_VALIDATION	Set to true to disable SSL certificate validation for self-signed certificates in on-premise environments.
CF_ACCESS_CLIENT_ID	Sent as the CF-Access-Client-Id request header on requests to the OX API. Set this only when your OX deployment sits behind an access proxy that requires service-token headers, such as Cloudflare Access.
CF_ACCESS_CLIENT_SECRET	Sent as the CF-Access-Client-Secret request header on requests to the OX API. Use together with CF_ACCESS_CLIENT_ID.

Integration example (azure-pipelines.yml)

pool:
  vmImage: ubuntu-latest

variables:
  - group: "OX"

stages:
  - stage: OX Security Scan
    jobs:
      - job: OX
        displayName: Run OX Security Scan
        steps:
          - script: |
              docker run \
                -e OX_API_KEY=$(OX_API_KEY) \
                --env-file <(env | grep 'SYSTEM_\|BUILD_') \
                oxsecurity/ox-block-mode:latest