Integrate OPA Gatekeeper with Vulnesis. Deploy Gatekeeper to your Kubernetes cluster, export audit violations as JSON, and upload policy findings to Vulnesis.
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 Vulnesis
run: vulnetix upload --file gatekeeper-violations.json
How Vulnesis compares: better together
Vulnesis does not replace Gatekeeper. Keep running it. Vulnesis 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 Vulnesis spans categories.
| Capability | Vulnesis | Gatekeeper |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image 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 / misconfiguration | ✓ Terraform, k8s, CloudFormation | ~ Enforces misconfiguration/security constraints on Kubernetes manifests at admission and via periodic audit |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ✗ |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✗ |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25 registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ✗ |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✗ |
| The Vulnesis orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✗ |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV | ✗ |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ✗ |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ✗ |
| End-of-life policy | ✓ Flags/blocks past-EOL runtimes & packages | ✗ |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What Gatekeeper does well
- OPA-powered Kubernetes admission controller that enforces policy at the API server, blocking non-compliant resources at admission time
- Audit controller periodically re-scans existing cluster resources against active constraints and records violations in each Constraint's status for compliance reporting
- Constraint Templates plus a substantial reusable policy library make policy authoring and sharing Kubernetes-native
- Extensible via external data providers (e.g. Ratify, JFrog) to pull image verification and vulnerability metadata into admission decisions
Where Vulnesis 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. Vulnesis 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. Vulnesis 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; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.
Centralise Gatekeeper results in Vulnesis
Upload Gatekeeper JSON output to the Vulnesis 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.