Compliance Control Mapper

Look up how one control area maps across SOC 2, ISO 27001, NIST 800-53, and PCI-DSS.

Compliance frameworks overlap far more than they differ. Access review, encryption at rest and logging appear in all of them under different names and numbers. Seeing the mapping is what stops an organisation running three separate audit programmes for one set of controls.

How to use it

  1. Pick a control area.
  2. Read how each framework expresses that control.

What to take away

Implement once, evidence many times

One well-run access review can satisfy SOC 2, ISO 27001 and several others simultaneously — provided the evidence is captured in a form each auditor accepts.

Compliant is not secure

Frameworks set a floor, and they are deliberately technology-neutral. Passing an audit means you met the floor, not that you would survive a determined attacker.

Auditors ask for evidence, not intentions

A written policy nobody follows fails. Tickets, logs, signed approvals and dated screenshots are what actually pass.

Frequently asked questions

What is the difference between SOC 2 and ISO 27001?

SOC 2 is a US attestation report on controls against the Trust Services Criteria, produced by an auditor for your customers. ISO 27001 is an international certification of a management system. Customers ask for whichever their market expects.

Which framework should a small company start with?

Usually whichever your customers are asking for — that is the one blocking deals. If nobody is asking yet, the CIS Controls give the most security per unit of effort.

Can one control satisfy several frameworks?

Yes, and that is the entire point of mapping. The work is in collecting evidence in a form that every auditor accepts.

Where this fits in the course

This security tool pairs with Path 23 — GRC & Compliance — see all 26 learning paths.

It runs entirely in your browser: nothing is uploaded, no account is needed, and it is free.

Related

Browse all 32 security tools →