Framework overlap

Does SOC 2 cover ISO 27001:2022?

You hold SOC 2 and have been told to do ISO 27001:2022. Here is how much overlaps, control by control.

27% of ISO 27001:2022 you already have

SOC 2 already covers about 27% of ISO 27001:2022, leaving 38 of 52 controls as genuinely new work.

Already covered 0 Likely covered 14 New work 38

No control in SOC 2 maps directly to one in ISO 27001:2022. Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in SOC 2 reaches these. This is the list to scope.

5.1
Policies for information secu- Control
5.10
Acceptable use of information Control
5.11
Return of assets Control
5.12
Classification of information Control
5.13
Labelling of information Control
5.14
Information transfer Control
5.16
Identity management Control
5.17
Authentication information Control
5.18
Access rights Control
5.20
Addressing information security Control
5.21
Managing information security Control
5.22
Monitoring, review and change Control
5.25
Assessment and decision on in- Control
5.26
Response to information security Control
5.27
Learning from information se- Control
5.28
Collection of evidence Control
5.30
ICT readiness for business con- Control
5.31
Legal, statutory, regulatory and Control
5.32
Intellectual property rights Control
5.33
Protection of records Control
5.34
Privacy and protection of person- Control
5.35
Independent review of informa- Control
5.36
Compliance with policies, rules Control
5.37
Documented operating proce- Control
5.4
Management responsibilities Control
5.5
Contact with authorities Control
5.6
Contact with special interest Control
5.7
Threat intelligence Control
5.9
Inventory of information and Control
6.1
Screening Control
6.2
Terms and conditions of em- Control
6.4
Disciplinary process Control
6.5
Responsibilities after termination Control
6.7
Remote working Control
7.2
Physical entry Control
7.3
Securing offices, rooms and fa- Control
7.4
Physical security monitoring Control
9.2.2
Internal audit programme
Show the 14 you already have
5.15
Access control Control
5.19
Information security in supplier Control
5.2
Information security roles and Control
5.23
Information security for use of Control
5.24
Information security incident Control
5.29
Information security during Control
5.3
Segregation of duties Control
5.8
Information security in project Control
6.3
Information security awareness, Control
6.6
Confidentiality or non-disclosure Control
6.8
Information security event re- Control
7.1
Physical security perimeters Control
9.3.2
Management review inputs
9.3.3
Management review results

How this is calculated

Already covered means a mapping runs from a control in SOC 2 to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition