Integrate Falco with Vulnetix. Deploy Falco as a runtime security monitor in Docker or Kubernetes to detect anomalous syscalls and policy violations. Export JSON alerts for upload to Vulnetix.
Install & scan
$ # Docker (privileged) docker run --rm -it --privileged -v /var/run/docker.sock:/host/var/run/docker.sock -v /dev:/host/dev -v /proc:/host/proc:ro falcosecurity/falco:latest # Kubernetes via Helm (recommended) helm repo add falcosecurity https://falcosecurity.github.io/charts helm install falco falcosecurity/falco --namespace falco --create-namespace --set falco.json_output=true $ # Enable JSON output falco --option "json_output=true" 2>&1 | tee falco-alerts.json
Run Falco Security in CI
Scan on every push and upload the report as a workflow artifact:
- name: Start Falco
run: |
docker run -d --name falco --privileged -v /var/run/docker.sock:/host/var/run/docker.sock -v /dev:/host/dev -v /proc:/host/proc:ro falcosecurity/falco:latest falco --option "json_output=true" 2>/tmp/falco-alerts.json
- name: Run integration tests
run: ./run_tests.sh
- name: Collect Falco alerts
run: docker exec falco cat /tmp/falco-alerts.json > falco-alerts.json || true
- name: Upload to Vulnetix
run: vulnetix upload --file falco-alerts.json
How Vulnetix compares: better together
Vulnetix does not replace Falco Security. Keep running it. Vulnetix sits on top of Falco Security (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Falco Security is strongest at its core category and also carries features in Cloud Security & CSPM, Network & Vulnerability Scanners, just as Vulnetix spans categories.
| Capability | Vulnetix | Falco Security |
|---|---|---|
| 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 | ✓ Core: runtime threat detection for containers, K8s and Linux hosts via syscalls/eBPF |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ~ Cloud runtime detection via plugins (CloudTrail/K8s audit logs), powers Sysdig agentless CDR |
| 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) | ~ Out-of-the-box rules alert on malicious activity and CVE exploitation at runtime |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ~ Detects unexpected network connections; Talon can enforce network policies via Cilium APIs |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests 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 prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnetix 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 | ~ Falco Talon no-code response engine auto-reacts (terminate, delete, network policy, Lambda) |
| 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 Falco Security does well
- CNCF-graduated real-time runtime threat detection via eBPF/kernel syscall monitoring, detects intrusions, privilege escalation and anomalous behavior as they happen
- Rich Kubernetes and container context on every alert (pod, namespace, process, command line, user) with a customizable rule engine
- Growing plugin ecosystem (K8s audit logs, cloud logs) and Falco Talon no-code response engine for real-time terminate/network-policy/Lambda actions
- Low overhead suitable for production nodes: community benchmarks typically cite roughly 1-5% CPU with the eBPF driver
Where Vulnetix adds to it: Falco is a runtime detection engine, not a vulnerability scanner. Vulnetix does not run Falco's syscall monitoring or replace its live threat detection. Vulnetix ingests and orchestrates its alert/finding output for consolidation and prioritisation, and covers the entire pre-runtime scanning surface (SAST, SCA, IaC, container image, secrets, SBOM, malware/package-firewall) plus dedup, exploit-intel, VEX, autofix, EOL and SSVC that Falco does not address.
No migration, no rip-and-replace. Falco Security keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise Falco Security results in Vulnetix
Upload Falco Security 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.