
Compliance Mapping Explained: Turning Security Findings Into Audit Evidence
A security scan and a compliance audit speak different languages. The scan says "missing Strict-Transport-Security header". The auditor asks "how do you protect data in transit, and can you show me?" Someone has to translate between the two, and that someone is usually a person with a spreadsheet and a free afternoon that turns into three.
Compliance mapping automates the translation.
What compliance mapping is
Every framework, whether SOC 2, ISO 27001, NIS2, DORA, PCI DSS or LGPD, is a list of controls: things an organisation is expected to do or demonstrate. Compliance mapping links each technical finding to the control or requirement it is relevant to.
So instead of one flat list of issues, you get two useful views. What is wrong, and which obligations that touches.
Why it matters
Findings without context are hard to prioritise for compliance. A missing header, an expired certificate and an exposed admin path all sound like "security hygiene". Mapped to controls, you see that they land on transport security, certificate management and access control, which is how an audit is organised.
It saves the translation work. Evidence gathering is one of the most time-consuming parts of any audit. If your scan output is already labelled by control, you are attaching evidence, not rewriting it.
It shows gaps early. If several findings all map to the same control, that control is probably not meeting the standard, and you'd rather learn that before the auditor does.
It supports continuous compliance. Audits are point-in-time. Regulations increasingly expect ongoing assurance. A mapped scan that runs regularly builds a record over time.
Why several frameworks
Different customers and regulators ask for different things.
- SOC 2 and ISO 27001 are the usual asks from enterprise customers and procurement teams.
- NIS2 applies to many organisations operating in the EU in sectors considered important or essential.
- DORA applies to financial entities in the EU and their ICT providers.
- LGPD is Brazil's data protection law.
- PCI DSS applies to anyone who handles payment card data. It is not a law or a self-assessed framework, and it is assessed by qualified assessors.
Mapping one finding to several frameworks at once means you don't repeat the exercise for each one.
Common use cases
- Preparing for an audit. Pull mapped evidence for the technical controls a scan can observe.
- Answering customer security questionnaires. "Do you test for vulnerabilities regularly? Show evidence." A mapped report is a concrete reply.
- Vendor risk reviews. If you sell to larger companies, their reviewers think in frameworks. Speaking their language shortens the process.
- Agencies and consultants. Handing a client a report organised by the framework they care about is more useful than a generic scan.
- Tracking progress. Fix findings, re-scan and watch the number of controls with evidence change.
- Payment pages. PCI DSS v4.0 introduced requirements around scripts running on payment pages (6.4.3 and 11.6.1). Decloak's third-party script and integrity checks map onto those directly. We wrote that up in PCI DSS mapping is live.
How Decloak does it
Compliance mapping is a Pro feature. It works as a labelling exercise on top of the scan we already run. Each of our finding categories, roughly 40 of them, is tagged with the specific control or requirement it relates to, for each supported framework. There is no separate scan and no extra step.
The six frameworks are SOC 2, ISO 27001, NIS2, DORA, LGPD and PCI DSS v4.0.
Where you see it:
- On the report. A Compliance Mapping section with a tab for each framework, showing the controls that scan produced evidence for.
- On your scoreboards. A Compliance Controls tile, account-wide and per domain, counts the distinct controls with evidence across all frameworks, with PCI DSS as its own bar.
- In the evidence package. The mapped output goes into the bundle you can hand to an auditor. See what's inside an evidence package.
Because the frameworks are driven from one lookup table rather than hardcoded in each screen, adding a new one shows up everywhere at once. That is how NIS2, DORA and PCI DSS each arrived without new interface work. See also compliance mapping now covers NIS2 and DORA.
What it is not
Please read this part.
- It is an indicative mapping, not a certification. Decloak does not audit you, and a mapped report is not an attestation that you comply with anything.
- A scan only sees what is observable from outside. Policies, staff training, access reviews, vendor contracts and internal processes are outside what a website scan can check. Most frameworks are mostly about those.
- Granularity varies. SOC 2, ISO 27001 and PCI DSS map to specific controls. NIS2 and DORA are broader by nature, so their mappings are coarser.
- PCI DSS is assessed by a qualified assessor. Our mapping helps you prepare and gather evidence. It doesn't replace the assessment.
Used honestly, it is a head start: the technical evidence, already sorted the way an auditor thinks. It is not a shortcut around the audit.
Getting started
Run a scan, open the Compliance Mapping section of the report and pick the framework you care about. Free scans show the findings. Pro adds the mapping, along with the evidence package.
See which controls your scan touches. Explore Decloak's features →