Tool integration

Gatekeeper Integration Guide

OPA-powered Kubernetes admission controller for runtime policy enforcement and compliance auditing

Get a Free API Key

Integrate OPA Gatekeeper with Vulnetix. Deploy Gatekeeper to your Kubernetes cluster, export audit violations as JSON, and upload policy findings to Vulnetix.

SaaS platformJSON

Run Gatekeeper in CI

Scan on every push and upload the report as a workflow artifact:

- name: Export Gatekeeper violations
  run: |
    kubectl get constraints -A -o json       | jq '[.items[] | {constraint: .metadata.name, violations: (.status.violations // [])}]'       > gatekeeper-violations.json

- name: Upload to Vulnetix
  run: vulnetix upload --file gatekeeper-violations.json

How Vulnetix compares: better together

Vulnetix does not replace Gatekeeper. Keep running it. Vulnetix sits on top of Gatekeeper (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.

Gatekeeper is strongest at its core category and also carries features in IaC & Cloud Configuration, Container & Image Scanning, just as Vulnetix spans categories.

CapabilityVulnetixGatekeeper
Security coverage
SAST (static code analysis)Built-in rules + Semgrep augmentation
SCA / dependencies40+ ecosystems, transitive graph
DAST (dynamic testing)~ Ingests DAST results; no native dynamic engine
Container & imageImage CVEs, base image, Dockerfile~ Via external data providers (Ratify/JFrog) it can gate on image signature verification and vuln metadata; does not scan images itself
IaC / misconfigurationTerraform, k8s, CloudFormation~ Enforces misconfiguration/security constraints on Kubernetes manifests at admission and via periodic audit
Secret scanning1,000+ rules, source + binary + git history
Cloud / CSPMCloud-posture findings, compliance tab
Mobile (MAST)~ Ingests mobile scanner output; no native mobile engine
License complianceSPDX, copyleft/AGPL/SSPL policy
SBOM generationCycloneDX 1.7 + SPDX 2.3, cosign-signable
Malware / supply-chainDe-duplicated corpus + install-time firewall (25+ registries)
Network / infra vuln~ Ingests network scanner output; no native network scanner
FuzzingIngests fuzzing crashes; no native fuzzer
Pentest / bug bountyIngests pentest/bug-bounty findings; not a testing service
The Vulnetix orchestration layer
Cross-scanner dedup & one queue (ASPM)Correlates every scanner into one prioritised queue with ownership routing
Exploit-intel prioritisationEPSS, CISA KEV, Coalition ESS, CWSS, Vulnetix LEV
Reachability analysisTree-sitter + CVEAffected; direct/transitive/semantic
Versioned VEX + audit trailImmutable OpenVEX/CycloneDX, cosign-signable
Safe Harbour autofixResolves + applies the nearest safe version
End-of-life policyFlags/blocks past-EOL runtimes & packages
SSVC / risk-based policySSVC v2 + CISA/FedRAMP/Essential-8 presets

✓ full · ~ partial · ✗ not covered

What Gatekeeper does well

Where Vulnetix adds to it: Gatekeeper enforces runtime/admission policy on a Kubernetes cluster; it is not a vulnerability scanner and relies on external providers for image/vuln data. Vulnetix runs the SCA/container/IaC/secrets scanning and produces the exploit-prioritised, deduplicated findings, VEX and SSVC decisions that such an admission gate can consume. They layer together. Vulnetix scores and attests risk, Gatekeeper can enforce the resulting policy at deploy time, without either replacing the other.

No migration, no rip-and-replace. Gatekeeper keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.

Centralise Gatekeeper results in Vulnetix

Upload Gatekeeper JSON output to the Vulnetix platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.

Gatekeeper documentation ↗  ·  Source repository ↗

Wire Gatekeeper into your CI/CD pipeline →