Tool integration

Pulumi Policy integration guide

Policy as code for Pulumi infrastructure using CrossGuard

Get a Free API Key

Integrate Pulumi CrossGuard Policy with Vulnesis. Enforce security and compliance policies on Pulumi infrastructure deployments and export violation findings for Vulnesis.

TypeScript / Python / Go (Pulumi IaC)CLI toolJSON

How Vulnesis compares: better together

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

Pulumi Policy is strongest at its core category and also carries features in Cloud Security & CSPM, just as Vulnesis spans categories.

CapabilityVulnesisPulumi Policy
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✗
IaC / misconfiguration✓ Terraform, k8s, CloudFormation✓ Core: CrossGuard Policy Packs enforce security/cost/tagging/compliance guardrails during pulumi preview and up
Secret scanning✓ 1,000+ rules, source + binary + git history✗
Cloud / CSPM✓ Cloud-posture findings, compliance tab~ Audit mode continuously scans live infrastructure discovered via Insights (incl. non-Pulumi/manual resources) for violations: CSPM-adjacent, though tied to the Pulumi policy model
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 Pulumi Policy does well

Where Vulnesis adds to it: Pulumi CrossGuard is a strong IaC policy-as-code engine with real compliance-framework packs and a live audit mode, but its universe is infrastructure configuration. Vulnesis brings native code and supply-chain scanning (SAST, SCA across 40+ ecosystems, container, secrets, malware/package firewall, SBOM) that CrossGuard has no engine for, and ingests CrossGuard policy violations into one deduped, exploit-intel-prioritised queue with versioned VEX, autofix and SSVC, better together, Vulnesis sits above CrossGuard's IaC guardrails.

No migration, no rip-and-replace. Pulumi Policy 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 Pulumi Policy results in Vulnesis

Upload Pulumi Policy 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.

Pulumi Policy documentation ↗

Wire Pulumi Policy into your CI/CD pipeline →