CI/CD security gates

CI/CD integration lets you run SecNxt as a security gate in your build pipeline, so risky code can be flagged or blocked before it merges or ships.

It moves security 'left', catching issues at the cheapest possible moment.

You create a CI token and call the SecNxt security-gate endpoint from your pipeline (GitHub Actions, Jenkins, CircleCI and similar).

The gate returns a pass/fail result your pipeline can act on, based on the policy you set.

1. 1Open the CI/CD card in Integrations and create a CI token.
2. 2Copy the snippet for your CI system (GitHub Actions, Jenkins, CircleCI).
3. 3Add it to your pipeline configuration.
4. 4Run a build and confirm the gate reports results.

• Failing a build when a new critical vulnerability is introduced.
• Enforcing a security baseline on every pull request.

• Keep CI tokens secret — store them in your CI system's secret store, never in code.
• Start in a warn-only mode, then tighten the gate once the team is used to it.

Which CI systems are supported?

Any system that can make an HTTP call — ready-made snippets are provided for GitHub Actions, Jenkins and CircleCI.