SOC 2 vs ISO 27001 Mapping: Crosswalk, Gaps and Evidence Reuse
Published on
February 9, 2026
/
updated on
November 20, 2026

The 33 SOC 2 common criteria mapped series by series to ISO/IEC 27001:2022 clauses and Annex A, the gaps, and a 6-step crosswalk method.
Most technical SOC 2 controls have a home in Annex A of ISO/IEC 27001:2022, and the governance criteria give you a start on clauses 4 to 10, whose management-system records are new work. An ISO-certified team owes SOC 2 a system description and, for a Type 2 report, a tested period.
An enterprise customer's security questionnaire asks for your ISO/IEC 27001 certificate. If you run a SaaS or managed service with international clients and built your security program for SOC 2, use a SOC 2 vs ISO 27001 mapping to see what transfers before you budget.
ISO 27001 and SOC 2 look interchangeable because both cover information security, but SOC 2 ends in a CPA's report on one system and ISO/IEC 27001 in a certificate for a management system. Treat one as the other, and the gap surfaces at the first audit of the framework you did not build for.
How SOC 2 Criteria and ISO 27001 Controls Are Structured
SOC 2 measures one system against a fixed set of criteria, while ISO/IEC 27001 certifies a management system and lets your own risks decide which controls apply. That difference sets the limit of any one-to-one crosswalk:
- SOC 2: the American Institute of Certified Public Accountants (AICPA) describes it, in its October 2026 news release proposing updated criteria, as "an examination performed by a licensed, independent CPA under the AICPA Attestation Standards." The result is an attestation report. The examination is measured against the Trust Services Criteria (TSC), whose 33 common criteria, CC1.1 to CC9.2, sit in nine series.
- ISO/IEC 27001:2022: the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) publish it jointly as an International Standard for information security management systems. Clauses 4 to 10 set the requirements for managing information security through an information security management system (ISMS), and Annex A references the controls of ISO/IEC 27002:2022.
The common criteria cover security on their own: for security, the TSC say "no additional control activity criteria are needed." Each of the other four categories adds criteria on top of them. In 2016, the AICPA document that holds the criteria (TSP section 100) still carried the title Trust Services Principles and Criteria, so a customer who asks about your trust service principles means the five Trust Services Criteria categories. The acronym changed in 2017, when the AICPA redefined SOC as system and organization controls; before that, SOC referred to service organization controls.
On the ISO side, ISO/IEC 27002:2022 groups the Annex A controls into four themes: organizational controls, people controls, physical controls, and technological controls. You compare the controls your risk treatment needs with that reference set and record the outcome in a Statement of Applicability.
Figure 1 sets the two structures side by side.

Is There an Official AICPA Mapping of SOC 2 to ISO 27001?
Yes. The AICPA publishes Mapping: 2017 Trust Services Criteria to ISO 27001, a spreadsheet that "compares the requirements of ISO 27001 to the relevant categories within" the 2017 criteria, including the March 2020 updates, although its resource page dates it May 4, 2018. The download is "Reserved for AICPA & CIMA Members."
ISO published ISO/IEC 27001:2022 on October 25, 2022, and the International Accreditation Forum's transition requirements for ISO/IEC 27001:2022 made 2013-based certifications "expire or be withdrawn at the end of the transition period," which ended on October 31, 2025. The AICPA resource page names the standard only as "ISO 27001," with no edition year, so check the rows against the 2022 numbering before you reuse them.
These references help when you build or check a crosswalk:
- The AICPA spreadsheet: criteria to ISO 27001 requirements, for members.
- NIST's crosswalk: the SP 800-53 Rev. 5 to ISO/IEC 27001:2022 crosswalk, a free spreadsheet NIST posted on November 13, 2023. It relates NIST controls, not SOC 2 criteria, to ISO clause and Annex A numbers.
- ISO's free preview: the iso.org pages of ISO/IEC 27001:2022 and ISO/IEC 27002:2022 show each document's table of contents, with the clause and control titles. The control text stays in the paid standard: ISO notes that "Only informative sections of the standard are publicly available."
Treat any crosswalk as a starting point: NIST warns that its mappings "are not always one-to-one and may not be completely equivalent."
On October 28, 2026, the AICPA proposed revised SOC 2 criteria that would consolidate duplicative concepts, remove some criteria, and add new ones; comments are open through January 15, 2027. If approved, the proposed 2027 SOC 2 Trust Services Criteria would apply to engagements beginning on or after December 31, 2027, with early adoption permitted. The exposure drafts need a free AICPA account, and a crosswalk built on the current criteria will need a review against the final text.
SOC 2 to ISO 27001 Mapping: Common Criteria Against ISO 27001:2022
CC1 to CC5 are where the management-system clauses of ISO/IEC 27001:2022 come in, while CC6 to CC9 land almost entirely on its Annex A controls. The first five series follow the COSO internal control principles and describe how the organization governs itself; the last four describe what it does to its systems.
Common Criteria CC1 to CC9
Table 1 maps each common criteria series to the ISO/IEC 27001:2022 clauses and Annex A controls it overlaps, and the records that one run of a control can give both audits.
Table 1. SOC 2 common criteria series mapped to ISO/IEC 27001:2022
| CC series | What the criteria ask | ISO/IEC 27001:2022 clauses | Annex A controls | Records that serve both |
|---|---|---|---|---|
| CC1 Control environment | Integrity and ethical values, oversight, structures and authorities, competent people, accountability | 5.1, 5.3, 7.2 | A.5.2, A.5.4, A.6.1, A.6.3, A.6.4 | Security roles and reporting lines, background check records, training records |
| CC2 Communication and information | Quality information for internal control, internal and external communication | 7.4, 7.5 | A.5.1, A.5.14, A.6.8 | Published policies, policy acknowledgments, notices to customers |
| CC3 Risk assessment | Objectives, risk identification and analysis, changes that could affect internal control | 6.1.2, 8.2 | A.5.7 | One risk register with its method, ratings, and owners |
| CC4 Monitoring of controls | Ongoing and separate evaluations, communication of deficiencies | 9.1, 9.2, 9.3, 10.2 | A.5.35, A.5.36 | Monitoring evaluations and deficiency logs, a start for the ISO internal audit and management review |
| CC5 Control activities | Control activities that mitigate risk, general controls over technology, policies and procedures | 6.1.3, 8.3 | A.5.1, A.5.3, A.5.37 | Policies, procedures, and the risk treatment decisions behind the Statement of Applicability |
| CC6 Logical and physical access controls | Access security, registration and removal of users, least privilege, physical access, protected transmission | Mainly Annex A | A.5.15 to A.5.18, A.7.2, A.8.2, A.8.5, A.8.24 | Access reviews, provisioning and removal tickets, authentication settings, badge logs |
| CC7 System operations | Detection of vulnerabilities and anomalies, incident evaluation, response, and recovery | 8.1 | A.5.24 to A.5.28, A.8.8, A.8.9, A.8.16 | Scan reports, alert tickets, incident records, post-incident reviews |
| CC8 Change management | Authorizing, designing, testing, approving, and implementing changes | 8.1 | A.8.25, A.8.29, A.8.32 | Change tickets with approvals and test results |
| CC9 Risk mitigation | Risks from business disruption, and from vendors and business partners | 6.1.3 | A.5.19 to A.5.23, A.5.29, A.5.30 | Vendor risk reviews, cloud security reviews of providers, continuity plans and test results |
Sources: TSC (1); ISO/IEC 27001:2022 and 27002:2022 previews (3, 5); NIST crosswalk (6); read November 2026.
Note. The mapping is ours, built from the criterion text and ISO's published clause and control titles. NIST's crosswalk supplies only the ISO/IEC 27001:2022 clause and Annex A numbering; it maps NIST SP 800-53 controls, not SOC 2 criteria. An assessor may place a control differently.
The access criteria show the overlap control by control. CC6.2 asks the entity to register and authorize users before it issues credentials, and CC6.3 asks it to grant and remove access by role, "giving consideration to the concepts of least privilege and segregation of duties." Annex A answers with A.5.16 identity management, A.5.18 access rights, and A.8.5 secure authentication, so one quarterly access review can serve as evidence for both.
Availability, Confidentiality, Processing Integrity, and Privacy
The four optional categories map less evenly than the common criteria:
- Availability: A1.1 to A1.3 cover capacity, environmental protections, data backup, recovery infrastructure, and tests of recovery plans. Annex A meets them with A.5.29 information security during disruption, A.5.30 ICT readiness for business continuity, and A.8.14 redundancy of information processing facilities.
- Confidentiality: C1.1 and C1.2 ask the entity to identify, keep, and dispose of confidential information. A.6.6 confidentiality or non-disclosure agreements, A.8.10 information deletion, and A.8.12 data leakage prevention give your data security records an ISO home.
- Processing integrity: PI1.1 to PI1.5 ask whether system processing is "complete, valid, accurate, timely, and authorized." This is the loosest fit. The nearest Annex A controls, A.8.26 application security requirements and A.8.29 security testing in development and acceptance, are written about security, so expect to keep processing controls of your own.
- Privacy: the privacy criteria, P1.1 to P8.1, follow personal information from notice through collection, use, retention, disclosure, and disposal; the TSC apply confidentiality to various types of sensitive information and privacy only to personal information. Annex A's matching control is A.5.34 privacy and protection of PII. For a management system built around data privacy, ISO publishes ISO/IEC 27701:2025, which it says can be used alone as an independent management system standard.
SOC 2 Mapping to ISO 27001: What Carries Over and What You Still Build
The technical controls and their evidence carry over wherever the SOC 2 system and the ISMS scope cover the same services. The management system around those controls is the part you still build.
What Carries Over
Access, operations, change, incident, and vendor controls built for CC6 to CC9 can go into the Statement of Applicability as implemented Annex A controls, with the evidence you already collect. Your SOC 2 risk management under CC3 is a start as well. ISO/IEC 27001 gives the information security risk assessment two clauses of its own: 6.1.2 under planning and 8.2 under operation, and turns the result into risk treatment under 6.1.3 and 8.3. The task is to show that your risk treatment selected the security controls you already run.
What ISO 27001 Adds
ISO/IEC 27001:2022 sets out requirements for the assessment and treatment of information security risks tailored to the needs of the organization as part of the ISMS. For a company that holds only a SOC 2 report, its clauses add seven pieces of work. Your CC3 to CC5 records give you a start on several of them, but each one becomes ISMS work under its own clause:
- ISMS scope (clause 4.3): the boundaries of the management system, which need not match the system your SOC 2 report describes.
- Information security objectives (6.2): the objectives and the plans to achieve them.
- Risk assessment and risk treatment method (6.1.2, 6.1.3): how you assess risks and decide how to treat each one.
- Statement of Applicability (6.1.3): the record of your comparison with the Annex A reference set.
- Internal audits (9.2): audits of the ISMS that you run or commission before the certification body arrives.
- Management review (9.3): top management's review of the ISMS, with defined inputs and results.
- Nonconformity and corrective action (10.2): how you record what audits find and fix it.
Budget the seven as new work, and reuse your control evidence wherever the two scopes match.
What an ISO 27001-Certified Team Still Needs for SOC 2
In an ISO 27001 to SOC 2 mapping, the first place to check already names your certificate. A point of focus for CC4.1 says management uses a variety of different types of ongoing and separate evaluations. Its examples are penetration testing, independent certification made against established specifications (for example, ISO certifications) and internal audit assessments.
The certificate counts as monitoring evidence, but the CPA still evaluates your controls against the criteria and, in a Type 2, tests whether they operated effectively. Four parts of a SOC 2 have no ISO counterpart:
- A system description: service organization management prepares it using the AICPA's description criteria for SOC 2 reports, and the service auditor evaluates it alongside the service organization's controls.
- A scope drawn around the system your customers use: the boundary follows the service in the report, and it may be narrower or wider than your ISMS scope.
- Categories beyond security: the four optional categories, each with its own criteria.
- A Type 2 period: a type 2 examination adds whether the controls operated effectively over the period the report covers. The evidence section below shows how to date records for it.
Your ISO records then work as SOC 2 evidence for the organization's internal controls: the risk register for CC3, the Statement of Applicability and procedures for CC5, and internal audit reports and management review minutes for CC4.
How to Build a SOC 2 and ISO 27001 Crosswalk, Step by Step
Build the crosswalk as one control catalog with owners and evidence, then map each control to both frameworks. Figure 2 lays the steps out in order.

Step 1: Align the SOC 2 System and the ISMS Scope
Start with the audit scope, because every control mapped outside the shared scope needs a second answer. Settle five questions before you map anything:
- Which services are in scope for your customer commitments?
- What environments run them: cloud accounts, networks, endpoints?
- Who operates, secures, and supports the in-scope system?
- Do any third parties affect the service?
- Where do the in-scope data flows run, from customer data to operational logs?
Write the answers into one scope statement that marks what each audit covers.
Step 2: Inventory Controls With Owners, Frequency, and Evidence
List every control once, in your own words, with the person who owns it, how often it runs, and the record it leaves. Write each one as a statement an auditor can test, such as "access to production is reviewed every quarter and the system owner signs off on the review." The owner and evidence fields are the evidence map that Step 5 and Table 2 build on.
Step 3: Merge the Risk Assessments Into One Register
Keep one risk register that serves CC3 and ISO clauses 6.1.2 and 8.2. Rate each risk once, link it to the controls that treat it, and let the same register feed the Statement of Applicability. Two registers make it easy for the same risk to carry two ratings.
Step 4: Map Each Control Both Ways
Tag each control with the TSC criteria and the ISO clauses or Annex A controls it supports. Record the ISO 27001 mapping to SOC 2 in the same row as the TSC tags, so one control carries both references. A control tagged on only one side shows where the other framework needs work, and Table 1 above gives the series-level starting points.
Step 5: Turn Gaps Into a Remediation Backlog With Owners
Every criterion or Annex A control without a tagged control is a gap. Your gap analysis becomes a backlog: give each gap a remediation owner, a due date, and the evidence that will close it. For a SOC 2 holder, the list holds the management-system work described above. An ISO-certified team's list holds the SOC 2 parts with no ISO counterpart.
Step 6: Review the Crosswalk When a Framework or System Changes
Rerun the mapping when a framework or your system changes. The AICPA's proposed 2027 criteria are the next known change, so plan a review once the final text is out. Between changes, continuous monitoring of the catalog, such as a quarterly check that owners and evidence are current, keeps the crosswalk usable for ongoing compliance.
What a SOC 2 and ISO 27001 Mapping Spreadsheet Should Contain
Keep the ISO 27001 vs SOC 2 mapping spreadsheet at one row per control, with the 10 columns in Table 2.
Table 2. Columns of a SOC 2 and ISO 27001 mapping spreadsheet
| Column | What it holds |
|---|---|
| Control ID | Your own identifier, used in both audits |
| Control statement | What the control does, written as a testable sentence |
| Owner | The person who runs the control and answers for it |
| Frequency | How often it runs: per event, daily, quarterly, or yearly |
| TSC criteria | Every criterion the control supports, such as CC6.2 |
| ISO clause or Annex A control | Every clause or control it supports, such as A.5.18 |
| Statement of Applicability (SoA) status | Applicable or excluded, with the justification |
| Evidence artifact | The record the control leaves and where it is stored |
| Period covered | The dates the evidence covers |
| Gap and remediation owner | Open gaps, who closes them, and by when |
Sources: our column set, with criterion and control numbers from the TSC (1) and ISO/IEC 27002:2022 (5); read November 2026.
If someone on your team has AICPA member access, the AICPA spreadsheet described above can seed the criteria side; the columns stay the same.
A file in Excel works while one person maintains it. Once several owners edit it, keep a dated version of every change, or move the catalog into a tool that records who changed what and when.
Reusing One Evidence Record in Both Audits
One evidence record can serve both audits when it is tagged with every criterion and control it supports and dated inside the SOC 2 period. A Type 2 report covers the design and operating effectiveness of controls over the period it names. An ISO certification audit reviews records of the ISMS in operation. A record from inside the SOC 2 period can answer both, because the same security controls are under test.
These records serve both audits:
- Access reviews: CC6.2 and CC6.3 on one side, A.5.18 access rights on the other.
- Change tickets: CC8.1 and A.8.32 change management, with approval and test evidence.
- Incident records: CC7.3 to CC7.5 and A.5.24 to A.5.28, from the evaluation of security breaches and other incidents through lessons learned.
- Test and scan reports: CC4.1 and CC7.1, and A.8.8 management of technical vulnerabilities.
Penetration test results and vulnerability scans count on both sides. A CC4.1 point of focus lists penetration testing among the ongoing and separate evaluations, and the point of focus for CC7.1 expects vulnerability scans "on a periodic basis and after any significant change in the environment." On the ISO side, the same reports feed A.8.8. Date each report and keep it with the remediation that followed, since the pair shows both auditors how the controls that protect customer data performed.
A compliance tool helps when it keeps a time-stamped history of each record, because evidence of control effectiveness needs a date. A folder of screenshots may not show when a piece of evidence was produced.
Running SOC 2 and ISO 27001 Audits on One Calendar
Run both on one calendar by placing the SOC 2 period so that the evidence it produces also serves the ISO audit dates. Your customers' requests decide which framework comes first, our SOC 2 vs ISO 27001 comparison covers that choice and the other key differences.
The ISO side runs on a fixed cycle set by ISO/IEC 17021-1, the standard for certification bodies:
- Initial certification audit: it shall be conducted in two stages, and to achieve certification you then need the certification body's decision.
- Surveillance audits: they come "at least once a calendar year, except in recertification years."
- Recertification audit: it follows in the third year, before the certificate expires.
The whole cycle is covered in our post on the ISO 27001 certification process.
Both are external audits run by different parties: a licensed CPA firm examines the SOC 2 system, and a certification body audits the ISMS. If your SOC 2 Type 2 period spans a year, schedule the ISO surveillance audit inside it, so one compliance process produces the records both audits use.
Three things drive the time and cost of adding ISO 27001 when a SOC 2 program already runs. The first is the management-system layer you still build, from the ISMS scope to management review. The second is the gap between your SOC 2 controls and the Annex A controls you select. The third is the certification audit cycle above. Evidence your SOC 2 program already produces cuts the work wherever the two scopes match.
Adding HITRUST, NIST CSF, and Other Frameworks to the Same Crosswalk
A third framework becomes one more column in the same catalog, and a published crosswalk gives you the starting map for it. HITRUST builds that mapping into its own framework: the Introduction to the HITRUST CSF v11.9.0 says the CSF's core structure is based on ISO/IEC 27001 and 27002 and that it integrates 71 authoritative sources. The list includes ISO/IEC 27001:2022 as well as the AICPA's Trust Services Criteria (TSP section 100).
Start the extra column from one of these:
- HITRUST CSF: its control requirements carry a documented mapping to their authoritative sources, so your SOC 2 and ISO tags give you a starting point for its requirements.
- NIST CSF 2.0: NIST's OLIR catalog lists crosswalks of ISO/IEC 27001:2022 to CSF 2.0, submitted by outside developers rather than by NIST or ISO.
- SP 800-53: NIST's free crosswalk, listed above with the AICPA spreadsheet, relates its control catalog to ISO/IEC 27001:2022 numbers.
Keeping multiple frameworks in one catalog means each new one, whether a law such as the GDPR or one of the security standards above, costs a column and a gap list, while the evidence process stays the same. The compliance frameworks still differ in what they test, so check each new column against that framework's own requirements before you rely on it.
Common Mistakes When Mapping SOC 2 and ISO 27001
Avoid these seven mistakes when you map the two frameworks:
- Scope drift: the SOC 2 system and the ISMS cover different services, so every control outside the shared scope needs two answers.
- Treating ISO as SOC 2 plus a few controls: as a compliance standard, ISO/IEC 27001 makes the management system itself a requirement, and ISO states that leaving out any of clauses 4 to 10 is not acceptable when an organization claims conformity.
- Mapping to 2013 Annex A numbers: certifications to ISO/IEC 27001:2013 had to end with the International Accreditation Forum's transition on October 31, 2025, so a crosswalk that still cites 2013 control numbers maps to a withdrawn edition.
- Policy statements in place of controls: security practices that exist only on paper leave no evidence of operational effectiveness: an auditor can read the policy but finds no record that the control ran.
- Evidence with no date or version: a record with no date cannot be placed inside the SOC 2 period or the ISO audit cycle, so it serves neither audit.
- One owner for the whole crosswalk: when that person leaves, nobody updates the mapping; give each control's row to its control owner.
- A spreadsheet nobody maintains: the catalog goes stale after the first framework or system change unless a review is on the calendar (Step 6).
Prepare for SOC 2 and ISO 27001 With CyberCrest
We prepare companies for both frameworks from one control catalog. Prepare for certification with our ISO 27001 compliance services: gap assessment and remediation support. The certificate itself is issued by an accredited certification body independent of CyberCrest. On the SOC 2 side, we run readiness and gap assessments against the criteria in scope and review your evidence before the examination begins. Talk to us about mapping your controls before your next audit period starts.
Sources
- AICPA & CIMA, TSP section 100, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (With Revised Points of Focus, 2022). https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022
- AICPA & CIMA, DC section 200, 2018 Description Criteria for a Description of a Service Organization's System in a SOC 2 Report (With Revised Implementation Guidance, 2022). https://assets.ctfassets.net/rb9cdnjh59cm/1vCduR1U2OnhIvFFaDBjMv/836050054707e9afb65adeb30d2e95d8/92317096_dc_section_200_clean_version.pdf
- ISO, ISO/IEC 27001:2022, Information security, cybersecurity and privacy protection: Information security management systems: Requirements (standard page and public preview). https://www.iso.org/standard/27001
- International Accreditation Forum, IAF MD 26:2023, Transition Requirements for ISO/IEC 27001:2022, Issue 2. https://iaf.nu/iaf_system/uploads/documents/IAF_MD26_Issue_2_15012023.pdf
- ISO, ISO/IEC 27002:2022, Information security, cybersecurity and privacy protection: Information security controls (standard page and public preview). https://www.iso.org/standard/75652.html
- NIST, SP 800-53 Rev. 5 to ISO/IEC 27001:2022 crosswalk, OLIR informative reference 155 (posted November 13, 2023). https://csrc.nist.gov/projects/olir/informative-reference-catalog/details?referenceId=155
- Journal of Accountancy, Explaining the 3 faces of SOC (June 2016). https://www.journalofaccountancy.com/newsletters/2016/jun/3-face-of-soc/
- AICPA & CIMA, AICPA System and Organization Controls communications guidelines (May 28, 2019). https://www.aicpa-cima.com/resources/article/aicpa-system-and-organization-controls-communications-guidelines
- AICPA & CIMA, Mapping: 2017 Trust Services Criteria to ISO 27001 (May 4, 2018). https://www.aicpa-cima.com/resources/download/mapping-2017-trust-services-criteria-to-iso-27001
- AICPA & CIMA, AICPA Proposes Update of SOC 2 Trust Services Criteria to Enhance the Relevance, Usability and Value of CPAs' Reports (October 28, 2026). https://www.aicpa-cima.com/news/article/aicpa-proposes-update-of-soc-2-r-trust-services-criteria-to-enhance-the-relevance-usability-and-value-of-cpas-reports
- AICPA & CIMA, AICPA Exposure Drafts: Proposed 2027 SOC 2 Trust Services Criteria and Description Criteria (October 26, 2026). https://www.aicpa-cima.com/resources/download/aicpa-exposure-drafts-proposed-2027-soc-2-trust-services-criteria-and-description-criteria
- ISO, ISO/IEC 27701:2025, Privacy information management systems: Requirements and guidance. https://www.iso.org/standard/27701
- International Accreditation Service, ISO/IEC 17021-1:2015, Section 9: Process Requirements (as published by IAS). https://www.iasonline.org/wp-content/uploads/2021/02/17021-1-2015-Section-9.pdf
- HITRUST, Introduction to the HITRUST CSF, Version 11.9.0. https://hitrustalliance.net/hubfs/CSF/CSF%20v11.9/Introduction%20to%20HITRUST%20CSF%20v11.9.0.pdf
- NIST, Online Informative References (OLIR) catalog. https://csrc.nist.gov/projects/olir/informative-reference-catalog
- EUR-Lex, Regulation (EU) 2016/679 (General Data Protection Regulation), Article 32. https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- FedRAMP, Consolidated Rules for 2026: Rev5 Control Guidance. https://www.fedramp.gov/2026/providers/rev5/controls/


FAQ
Can one crosswalk cover ISO 27001, SOC 2, and GDPR?
For security, yes. Article 32 of the GDPR requires technical and organizational security measures appropriate to the risk, including, as appropriate, encryption, restoring access to personal data after an incident, and regular testing. An approved certification mechanism may help demonstrate compliance with it. Those measures for safeguarding data map onto your catalog. Data protection duties such as a lawful basis for processing need regulatory compliance work no security crosswalk covers.
Is ISO 27001 still relevant?
Yes. ISO/IEC 27001:2022 is the current edition, published in October 2022, and ISO added Amendment 1:2024 on climate action changes. Certifications to the 2013 edition had to expire or be withdrawn by October 31, 2025, under the International Accreditation Forum's transition rules. ISO advises citing the full edition, for example "certified to ISO/IEC 27001:2022," so check which edition a supplier's certificate names.
Can I leverage my existing SOC 2 or ISO 27001 work for FedRAMP?
Partly. FedRAMP Rev5 uses controls from NIST Special Publication 800-53 Revision 5, so start from NIST's free crosswalk, which relates SP 800-53 controls to ISO clause and Annex A numbers. Your ISO and SOC 2 evidence can then support the matching controls, while FedRAMP's own baseline and assessment decide what you need.
Can one checklist cover both SOC 2 and ISO 27001?
One checklist with both sets of tags can cover the controls: access, operations, change, incidents, and vendors. It cannot cover the management system. ISO/IEC 27001 adds seven pieces of management-system work that a SOC 2 checklist does not cover in full, and the section on what ISO 27001 adds lists each one with its clause number.
How to automate SOC 2 and ISO 27001 compliance?
Automate evidence collection and leave the judgments to people. Security compliance tools can pull access lists, change tickets, and scan results on a schedule and tag each record with its criteria and Annex A controls, which keeps evidence flowing between audits for continuous compliance. Risk decisions and the Statement of Applicability stay with your team. The CPA and the certification body still test the controls themselves.
Is ISO 27001 equivalent to SOC 2?
No. An ISO/IEC 27001 audit can end in formal certification of a management system by a certification body, while a SOC 2 ends in an attestation report from an independent auditor, a CPA, on one system. For a mapping, a control can satisfy both, but neither result substitutes for the other: the TSC mention ISO certification only as one example of an ongoing or separate evaluation, in a point of focus for CC4.1.











