What Is CMMC Compliance? A Complete Guide

A well-built SOC 2 runbook is the difference between a finding and a clean opinion. It converts the abstract language of a control into a sequence of actions someone actually performed, in a verifiable order, with a paper trail attached. Auditors do not fail companies for having incidents. They fail them for not being able to prove how those incidents were handled. This guide shows you how to build a runbook that holds up under scrutiny — covering what a SOC 2 runbook is, what makes it audit-ready, how it differs from a playbook, the components every runbook should include, the control areas where runbooks are expected, and how to keep them current between annual examinations. What Is a SOC 2 Runbook? A SOC 2 runbook is a documented, repeatable procedure that operationalises a specific SOC 2 control. Where a policy states what must happen and why, a runbook states exactly how: the trigger, the steps, the people, the systems touched, the evidence captured, and the sign-off that closes it out. Runbooks live closest to the engineers and operations staff actually doing the work. They are the layer auditors care about most because they are where the control either operates or fails. A well-written runbook turns a control objective into something testable, traceable, and survivable across staff turnover. SOC 2 Runbook vs. SOC 2 Playbook: Key Differences The terms get used interchangeably, but they describe two different artefacts. The cleanest distinction is scope and audience. Dimension Runbook Playbook Scope One specific procedure Multi-step strategy across functions Audience Engineers, on-call responders, operations teams Leadership, legal, communications, incident response coordinators Detail Level Commands, queries, exact tooling Decisions, escalation paths, stakeholder roles Example Isolating an affected EC2 instance using a documented AWS CLI command Coordinating a ransomware response across legal, PR, and law enforcement Length Short, tactical, and scannable Longer, narrative, and decision-oriented A mature SOC 2 programme uses both. The playbook frames the response. The runbook executes pieces of it. Why SOC 2 Auditors Expect Runbooks The AICPA’s Trust Services Criteria describe what auditors test, but at the level of objectives, not procedures. CC7.3 says you must respond to security incidents. It does not tell you how. The runbook is your answer to how. Auditors are looking for two things when they evaluate a control: that it was designed appropriately, and that it operated effectively across the audit period. Runbooks are how you show both. The document itself is the design. The completed runbook artefacts (tickets, logs, sign-offs, post-mortems) are the operating evidence. Which SOC 2 Trust Services Criteria Require Runbook Documentation Every Common Criteria area benefits from runbooks, but the strongest expectation sits in CC6 (logical and physical access), CC7 (system operations, including incident detection and response), CC8 (change management), and CC9 (risk mitigation, vendor management, and BCP/DR). For a deeper look at how these criteria are structured and what auditors are actually testing, the Trust Services Criteria breakdown is worth reading before you start mapping your runbooks. If your scope includes the Availability criteria, A1.2 and A1.3 will require runbooks for failover, restoration, and capacity management. Confidentiality and Privacy add data handling and retention runbooks on top. If you are still determining which criteria apply to your organisation, a structured gap analysis is the most reliable starting point. Why Your Organization Needs a SOC 2 Runbook The common failure pattern is not the absence of policies. It is the absence of a credible bridge between the policy and what people actually do at 2am during an incident. How Runbooks Demonstrate Control Effectiveness to Auditors Auditors sample. For a Type II report covering twelve months, they will pull a population of incidents, changes, access reviews, or vendor onboardings, and trace a sample of them end to end. Without runbooks, that trace usually breaks. Engineers describe what they did from memory, ticket histories are inconsistent, and the auditor has no baseline to test against. With runbooks, the auditor compares the documented steps to what actually happened in the artefacts. If the runbook says approval is required, the ticket should show it. If it says evidence must be retained for ninety days, the log should be there. The runbook turns a subjective conversation into an objective trace. Runbooks as Evidence: Avoiding the Audit Evidence Trap A specific failure mode is what practitioners call the evidence trap: the control exists, the team is doing the right thing, but nothing was captured at the time. Three months later, the SIEM has rotated the logs, the on-call engineer has left, and the only record is a Slack thread no one can find. Runbooks prevent this when they make evidence capture a step in the procedure itself, not an afterthought. A line in the runbook that reads export the relevant CloudTrail entries to the incident folder before remediation is what stands between you and a qualified opinion. Pro Tip: Build evidence capture into the runbook as a numbered step, not a footer note. Auditors test what is written. If “save the screenshot” is step 7, it gets done. If it is buried in a paragraph at the bottom, it usually does not. SOC 2 Type I vs. Type II: How Runbooks Support Each A SOC 2 Type I report assesses the design of controls at a single point in time. For Type I, the runbook itself, together with the policies it references, is most of what auditors need. Type II is a different beast. It tests operating effectiveness over a period (typically six to twelve months), and that is where runbooks earn their keep. Each completed run produces evidence: a ticket, a log entry, a screenshot, a signed approval. Over twelve months those artefacts become the case for control effectiveness. Without runbooks, evidence collection is reactive and full of gaps. With them, it is a byproduct of normal work. For a fuller picture of what to expect across both report types, the SOC 2 compliance checklist is a useful companion to this guide.   Core Components

SOC 2 compliance is a critical trust signal for organizations handling sensitive data. Unlike ISO standards, SOC 2 reports are private attestations issued by licensed CPA firms, making verification essential.  To verify a SOC 2 report, you need to review the auditor’s opinion, audit period, report type, scope, and any control exceptions, then confirm the auditor’s AICPA registration and request a bridge letter if the report is outdated. In today’s cybersecurity-driven business environment, SOC 2 compliance has become one of the most recognized trust signals in the industry. Whether you are a SaaS provider handling customer data or an enterprise evaluating third-party vendors, a SOC 2 report plays a central role in proving that security controls are properly designed and operating effectively. Verifying a SOC 2 report, however, is not as simple as checking a public registry. Unlike ISO 27001, SOC 2 is not a public certification. Despite being regulated by the AICPA, there is no central database or government portal where you can confirm a company’s compliance status. Instead, SOC 2 is a private attestation report, issued by an independent CPA firm. That makes verification a matter of careful review and disciplined due diligence. If you want to understand how SOC 2 stacks up against other frameworks, our breakdown of ISO 27001 vs SOC 2 is a good place to start. This guide explains how to properly verify a SOC 2 report, what to watch for, and how expert partners like Axipro help organizations achieve and maintain SOC 2 compliance so their reports hold up to real scrutiny. Why Verifying a SOC 2 Report Matters SOC 2 reports are widely used across vendor risk management, enterprise procurement decisions, security questionnaires, and customer trust and sales cycles. Because SOC 2 reports are private and shareable only under NDA, verification responsibility falls entirely on the recipient. Accepting an outdated, poorly scoped, or improperly audited SOC 2 report can expose your organization to serious security and compliance risks. According to IBM’s Cost of a Data Breach Report, the average cost of a data breach continues to climb year over year, and third-party vendor relationships remain one of the most common attack vectors. Treating SOC 2 verification as a formality is not just sloppy governance; it is a liability. Knowing how to verify a SOC 2 report, and working with the right compliance experts, is not optional. It is essential. Step 1: Thoroughly Review the SOC 2 Report Key Sections Once a company provides its SOC 2 report (typically under a Non-Disclosure Agreement), your first step is a structured internal review. There are five areas you must examine closely. The Auditor’s Opinion is the single most critical section of the report. The opinion should be Unqualified (also called Unmodified). A Qualified, Adverse, or Disclaimer opinion is a major red flag and should immediately prompt further questions. An unqualified opinion means the auditor found no material issues with how controls were designed or operated during the audit period. The Report Period and Date tell you whether the report is still relevant. SOC 2 reports are generally considered valid for 12 months. Confirm the exact audit period, for example, October 1, 2024 to September 30, 2025, and flag anything older than that as potentially unreliable without additional assurance documentation. The Report Type is equally important. A SOC 2 Type I assesses whether controls were properly designed at a single point in time. A SOC 2 Type II evaluates whether those controls actually operated effectively over a defined period, typically six to twelve months. For most enterprise customers, SOC 2 Type II is the expected standard, and anything less should be treated with appropriate skepticism. The Scope of Services, found in the System Description section, must explicitly include the product or service you are evaluating. A SOC 2 report that does not cover the relevant system offers limited assurance, regardless of how clean the auditor’s opinion is. Exceptions and Control Failures in the testing results section deserve careful attention. Look for exceptions, failed controls, or deviations from expected behavior. Not all exceptions are disqualifying, but you need to assess whether they represent a material risk to your data or operations. If the report contains a significant number of exceptions or a pattern of failures in critical areas, that is a conversation worth having with the vendor before proceeding. If you want a structured checklist to guide this review process internally, we have put one together here. Step 2: Verify the Auditor’s Credibility A SOC 2 report is only as trustworthy as the CPA firm that issued it. This step is non-negotiable. The auditor must be a licensed CPA firm authorized to perform SOC engagements under the standards set by the American Institute of Certified Public Accountants (AICPA). The AICPA is the governing body for SOC reporting, and any firm issuing these reports must be formally registered with them. Beyond registration, AICPA requires CPA firms to undergo periodic peer reviews to ensure quality and professional standards are maintained. You can check a firm’s peer review standing directly through the AICPA peer review database or verify their status through the relevant state board of accountancy. This is a free, publicly accessible check that takes minutes, and skipping it is a mistake. An unlicensed or non-peer-reviewed firm issuing a SOC 2 report is not just a compliance risk, it is a sign the report may not be worth the paper it is written on. Axipro works closely with reputable, AICPA-registered audit firms, helping clients select the right auditor and ensuring the engagement meets all professional and regulatory expectations from the start. Step 3: Request a Bridge Letter When There Is a Coverage Gap SOC 2 reports cover a defined period. If the most recent report ended several months ago and the next audit is still in progress, you are operating in a coverage gap, a window of time where you have no formal attestation of current control effectiveness. In this situation, you should request a Bridge Letter, sometimes