🛡 Stage 08 · Secure & govern

Proving compliance

How unified security findings map to CIS, SOC 2, ISO 27001 and PCI — and turn into auditor-ready, exportable evidence instead of a spreadsheet scramble.

1Scan 2Unify 3Risk graph 4Map controls 5Posture 6Evidence PDF
01

One findings model

Heavy scanners (Trivy, Grype, gitleaks, checkov, kube-bench and more) run in a sidecar and feed a single unified findings store. Code, containers, infra, secrets and runtime all land in one place — no more reconciling five dashboards.

02

Risk graph & attack paths

Findings are folded into a resource graph — software, images, infra, cloud and credentials as nodes; runs-on, exposes and depends-on as edges. Resolve traverses the graph to find real attack paths and produces one graph-aware risk score per product.

03

Control mapping in code

The unified findings map onto CIS, SOC 2, ISO 27001 and PCI control families deterministically, in code — each control fails on matching open findings at or above its severity gate. Posture is the share of passing controls, graded A–F. No per-row hand-tagging.

04

Exportable evidence

Export a branded posture report per framework as a PDF — the artefact auditors actually ask for. A continuous sweep surfaces new critical/high findings, opens tickets and snapshots posture over time, so compliance is a living state, not a once-a-year panic.

resolve · security
Security cockpit (CNAPP)
See it for real

Walk through it on your own project.

We’ll scope your build in one meeting and show this lifecycle running against it, live.

Start a project → All guides