Building a Unified Control Framework Across SOC 2 and ISO 27001

How to map one control library to both audits and cut duplicate work.

Cover illustration for “Building a Unified Control Framework Across SOC 2 and ISO 27001”
Written by
Compliance Primer Editors
Published
November 19, 2026
Reading time
9 min read
Sources cited
8 sources ↓
  • The default organizational behavior: treat each framework as its own workstream, assign separate owners, collect separate evidence, run separate audits
  • What that default costs in practice: companies running compliance as a separate workstream from security operations spend 40%+ of their compliance budget on duplicate evidence collection across overlapping frameworks
  • Audit fatigue is real and cumulative: two separate observation windows, two sets of auditor requests, two documentation cycles — each drawing on the same underlying controls
  • The demand pressure making this untenable: 81% of organizations had a current or planned ISO 27001 certification in 2025, up from 67% in 2024 — most of these organizations also carry SOC 2 obligations, so dual compliance is now the norm, not the exception
  • Regulatory overlay tightening the timeline: the ISO/IEC 27001:2013 transition window closed October 31, 2025 — all 2013 certificates have now expired or been withdrawn, forcing organizations onto ISO/IEC 27001:2022 whether or not they planned for it
  • NIS2 adds external pressure: as of March 2026, 21 of 27 EU member states had transposed NIS2 into national law, with active enforcement, fines reaching €10 million or 2% of worldwide turnover for essential entities, and personal liability on management — organizations already juggling SOC 2 and ISO 27001 now face a third compliance vector that a unified architecture can absorb more cleanly than two siloed programs
  • The argument this section makes: the inefficiency is structural, not a matter of effort — parallel programs are inefficient by design, and the fix is architectural

What the two frameworks actually share at the control level, and what each adds on top

  • Structural differences that shape how each framework is governed, not what security work gets done
    • SOC 2: auditor's opinion on controls; U.S. market currency; no public certificate; renewed annually via CPA attestation; organizations choose which Trust Services Criteria to include beyond mandatory Security
    • ISO 27001:2022: formal certificate from accredited registrar; valid 3 years with annual surveillance audits; publicly searchable and displayable; 93 controls in four themes — Organizational, People, Physical, Technological — reorganized from 114 controls in 14 categories, with 11 new controls added
    • ISO 27001:2022 also added controls for cybersecurity threat intelligence, cloud security, and data masking and data leakage prevention — making it more directly useful as a shared foundation than the 2013 version
    • Visibility asymmetry: ISO 27001 certificates can appear on a website and in marketing materials; SOC 2 reports cannot — the two credentials serve overlapping but distinct buyer audiences, which is why enterprise customers ask for both
  • The Confidentiality TSC appears in 64.4% of SOC 2 Type II reports and the Availability TSC in 75.3% — not every organization selects every TSC, so the shared control layer needs to account for the specific criteria in scope
  • The actual shared control domains — access control, change management, incident response, risk assessment, vendor management, encryption, logging, and awareness training — are core to both; the differences are in structure, documentation format, and governance mechanism, not in the underlying security work
  • What each framework adds that the other does not cover in the same way
    • ISO 27001 adds: formal ISMS scope documentation, Statement of Applicability, management review cadence, internal audit program, corrective action tracking
    • SOC 2 adds: Trust Services Criteria framing, observation-period evidence (Type II), CPA attestation language, and the flexibility to include or exclude TSCs based on service commitments
  • Key implication: the differences are real but mostly additive — a shared control library covers the common ground, and each framework's unique requirements are a relatively thin layer on top

The quantified overlap case: how much shared evidence a unified architecture actually produces

  • The overlap figures come from different vantage points and should be presented together, not collapsed into a single number
    • An AICPA mapping spreadsheet puts requirement overlap at roughly 80%
    • A-LIGN's 2025 benchmark report found that roughly 43% of SOC 2 evidence can also satisfy ISO 27001 requirements — a more conservative evidence-reuse figure
    • Practitioner consensus: the on-record overlap is 70%; in day-to-day audit practice it runs closer to 90%
    • A 60–70% overlap figure is the floor cited in combined certification guides, with dual certification achievable in 30–36 weeks versus 48 weeks sequentially when controls are mapped from the start
    • Writer's framing task: the range (43% to 90%) reflects different measurement units — evidence artifacts vs. requirement text vs. audit findings — not contradiction; a unified architecture captures value across the entire range
  • What the overlap translates to in effort and cost reduction
    • Mapping has cut audit preparation time by roughly half and reduced internal effort by about 75% in documented cases per Konfirmity's multi-thousand-audit dataset
    • A unified gap assessment done simultaneously saves 30–40% compared to running two separate assessments
    • Bundle pricing for dual certification saves 20–35% versus two independent audit engagements
  • The cost of not mapping: companies running compliance as a separate workstream spend 40%+ of their compliance budget on duplicate evidence collection — the overlap figures above represent recoverable waste, not theoretical efficiency
  • This section's payoff: the overlap is large enough that a shared control library is not a compromise — it is the higher-fidelity approach, because it forces explicit mapping rather than leaving connections implicit and unmaintained

Building the shared control library: the architecture of a unified framework in practice

  • The foundational decision: build the ISO 27001 ISMS first, because it provides the most complete structural foundation — then map each policy, control, and process to the relevant SOC 2 Trust Services Criteria as it is built, not retroactively
  • The Statement of Applicability doubles as a control matrix for both frameworks — one document, two purposes; this is the architectural hinge that makes the shared library work
  • The shared control layer for most software and technology organizations includes at minimum
    • Asset inventory and classification
    • Logical access control — authentication, authorization, quarterly access reviews
    • IAM implementation: SSO and MFA as baseline
    • Centralized logging with alerts for privileged actions
    • Encryption standards: AES-256 at rest, TLS 1.3 in transit, defined key rotation
    • Vulnerability management program
    • Change management with documented approvals
    • Incident response playbooks with testing logs
    • Backup and recovery with defined RTO/RPO and tested DR runbooks
    • Supplier/vendor inventory, data mapping, risk ratings, and signed contracts
    • Secure development practices
    • Risk assessment and management process
    • Awareness training program
  • How the control library entry is structured: each control record should carry its ISO 27001:2022 Annex A reference, the mapped SOC 2 TSC criteria (e.g., CC6.1, CC7.2), the evidence artifact(s) that satisfy both, the owner, review frequency, and audit-trail location
  • What "framework-specific" controls look like in this architecture: they are not separate programs — they are additional fields or attributes on a shared record
    • ISO-specific additions: ISMS scope document, SoA justifications for excluded controls, internal audit schedule, management review minutes, corrective action log
    • SOC 2-specific additions: TSC mapping per selected criteria, operating-effectiveness evidence spanning the observation window, CPA-ready artifact packaging
  • Single evidence set principle: every artifact is collected once, tagged to all applicable control references, and stored in a single location — auditors for either framework are pointed to the same repository, not a framework-specific subset
  • Common failure mode to flag for the writer: building the ISO ISMS fully, then attempting to retrofit SOC 2 mapping — this recreates the duplication problem at the documentation layer even when the controls themselves are shared

Running the gap analysis simultaneously across both frameworks

  • The unified gap assessment is months 1–2 of a recommended sequencing; its output is a single roadmap, not two separate ones
  • What the assessment maps
    • Current-state controls against both ISO 27001:2022 Annex A and the selected SOC 2 TSCs simultaneously
    • Shared gaps: controls absent from both frameworks' requirements that a single remediation closes
    • ISO-specific gaps: ISMS management system requirements (clauses 4–10) that have no SOC 2 equivalent — these are typically documentation and governance gaps, not technical control gaps
    • SOC 2-specific gaps: Trust Services Criteria that are in scope but lack operating evidence for the intended observation period
  • The remediation sequence logic: fix shared gaps first (highest ROI per hour of effort), then ISO-specific governance gaps (required for certification), then SOC 2 observation-period evidence collection (time-bound by audit schedule)
  • Savings from simultaneous assessment: 30–40% compared to running two separate assessments — the gap is not trivial because most shared-control gaps would be discovered and remediated twice in a sequential approach
  • Practical output format: a prioritized control inventory with three columns — shared remediation, ISO-only, SOC 2-only — so teams can sequence work without losing visibility into why each item is on the list
  • What to do with controls that appear in one framework's language but not the other's: map them to the closest equivalent before declaring a gap — many apparent gaps resolve on inspection once the mapping is explicit
  • Practitioner consensus on sequencing: ISO 27001 ISMS first, then SOC 2 audit — because the ISMS provides the policy and process foundation that makes SOC 2 evidence collection straightforward
  • Full sequencing in phases
    • Months 1–2: unified gap assessment and roadmap
    • Months 2–8: build the ISMS, simultaneously mapping each policy and control to SOC 2 TSCs as it is finalized
    • Following the ISO 27001 audit: SOC 2 Type II observation period can overlap with or immediately follow the ISO audit — because controls are already implemented and documented, the SOC 2 audit is primarily an evidence collection and reporting exercise
  • Timeline benchmarks to give the writer concrete anchors
    • ISO 27001 first-time certification typically lands at 6–12 months for organizations starting from scratch
    • SOC 2 Type II with AI-powered compliance platforms: some specialist auditors now complete the process in 6–8 months total
    • For SaaS startups targeting SOC 2 Type I only: timeline can be compressed to 3–4 months and $10,000–$25,000 using AI tools for policy generation and gap tracking
    • Dual certification pursued together: 30–36 weeks versus 48 weeks sequentially — the time savings compound because the observation period and ISMS build overlap
  • What drives variance in timelines: starting maturity, in-scope TSC count, organization size, and whether a compliance automation platform is in use
  • The audit coordination point: align the ISO 27001 certification body and the SOC 2 CPA firm early — shared scheduling reduces the number of auditor-request cycles and allows a single evidence repository to serve both
  • Bundle pricing benefit: dual certification saves 20–35% versus two independent audit engagements — factor this into the business case for pursuing both simultaneously

Sustaining the unified framework: keeping a single evidence set current across both audit cycles

  • The maintenance challenge: SOC 2 renews annually; ISO 27001 has annual surveillance audits plus a full recertification every 3 years — two different cadences against the same control library
  • The single evidence set must be structured so both audit cadences can draw from it without requiring separate preparation cycles
    • Continuous evidence collection, not point-in-time collection: access reviews, change approvals, incident logs, and vendor risk ratings should be collected as operations produce them, not assembled ahead of each audit
    • Control record versioning: when a control changes (new tool, new process, new owner), both framework mappings update simultaneously — a change in one is not a change in one framework
    • Observation window management for SOC 2 Type II: the 12-month default observation period must be supported by artifacts collected throughout — a unified evidence system makes this automatic if controls are instrumented correctly from the start
  • Internal audit program (an ISO 27001 clause requirement) doubles as a pre-audit readiness check for SOC 2: the same internal audit findings that feed the ISO corrective action log can identify SOC 2 control gaps before the external auditor does
  • Management review cadence (ISO 27001 requirement) provides a governance moment to review both frameworks' control status — one meeting, two compliance programs reviewed
  • Tooling that supports this: Vanta, Drata, and Secureframe are among the leading compliance-automation platforms as of April 2026 — they connect to cloud providers, identity providers, ticketing systems, and HR systems and continuously collect evidence against a control framework; their strength is rapid time-to-readiness for SOC 2 and ISO 27001
  • Tooling limitation to note honestly: these platforms' AI-specific control coverage for ISO 42001 and the AI Act is still maturing as of April 2026; most of their 42001 modules launched in late 2024/2025

Methodology & sources

  1. Unified control frameworks: Simplifying multi-standard compliance in 2025

    Supported the single shared control library approach and the case for duplicate-evidence waste across frameworks.

  2. ISO 27001 Mapping To SOC 2: A Walkthrough with Templates (2026) | Konfirmity

    Provided the mapping approach and the audit-preparation and internal-effort reduction figures.

  3. SOC 2 Controls Mapped To ISO 27002: A 2026 Guide for Busy Teams | Konfirmity

    Informed the control-level mapping of SOC 2 criteria to ISO controls and the shared control layer list.

  4. ISO 27001 vs SOC 2: Key Differences & Comparison Guide

    Covered structural differences such as certificates versus attestation reports and the ISO 2022 control reorganization.

  5. SOC 2 vs. ISO 27001: differences, similarities and standards mapping

    Contributed the standards mapping and the overlap figures between the two frameworks.

  6. A Unified Approach to SOC 2, ISO 27001 & HIPAA in 2026

    Supported the unified approach and the dual-certification timeline and sequencing.

  7. ISO 27001 vs. SOC 2: Understanding the Differences

    Informed the comparison of what each framework adds and how ISO and SOC 2 governance differ.

  8. https://pentagoninfosec.com/blog/soc2-type2-iso27001-compliance-overlap

    Informed the discussion of Type II overlap with ISO 27001 and the practitioner overlap percentages.

Compliance Primer Editors