Guide12 October 2026

Compliance Mapping Explained: Turning Security Findings Into Audit Evidence

Compliance Mapping Explained: Turning Security Findings Into Audit Evidence

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.

Mapping one finding to several frameworks at once means you don't repeat the exercise for each one.

Common use cases

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:

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.

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 →