GitHub Actions
OX Security integrates with GitHub Actions to detect vulnerabilities in your code or container images during CI/CD builds.
The OX GitHub Action runs a full security scan, covering secrets, SAST, SCA, IaC, and more, on every push or pull request, and evaluates the results against your defined security policies. If a blocking issue is detected, the workflow will fail unless overridden.
You can configure global or repository-specific policies in the OX platform to determine enforcement behavior.
This integration is highly customizable and supports any event trigger supported by GitHub Actions.
When using pull request or push triggers in GitHub Actions, scans run automatically without needing manual webhook setup.
Prerequisites
A GitHub repository connected to your OX application.
A valid OX Security API key stored as
OX_API_KEYin your repository secrets.
Required environment variables
ox_api_key
Optional environment variables
ox_override_blocking
Set to true to override blocking issues and allow the workflow to succeed.
ox_timeout
Maximum scan duration in minutes. Defaults to 20.
ox_fail_on_timeout
Set to true to fail the job if the scan times out.
ox_fail_on_error
Set to true to fail the job when network or system errors occur.
Advanced environment variables
ox_disable_ssl_validation
Set to true to disable SSL certificate validation (useful for self-signed or internal endpoints).
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 (.github/workflows/scan.yml)
Last updated