Security is something you build every day, and proof is how everyone else gets to see it. That is what SOC 2 is for. A SOC 2 report puts your efforts on display: an independent report from a licensed CPA firm that shows your customers and prospects, in one trusted place, that you protect their data at rest, in transit, and in everyday use, and that the controls behind that protection work as described. It gives them a clear reason to trust you with their data, and it gives you a way to be recognized for the work you’re already doing.
The proof itself is made of everyday habits. When access is reviewed every quarter, every code change is approved before it ships, and every alert gets a response, those habits leave a trail behind them: dated records, complete lists, and a steady line of evidence that each control kept working from the first day of your review period to the last. Put that trail in front of your CPA firm and the conversation changes. Your word is backed by records, and the records speak for themselves.
This is why SOC 2 success rests so heavily on evidence. Every review, approval, and response your team completes becomes a building block, and together they show a company that watches its own controls continuously instead of reconstructing the story at audit time. Teams that treat evidence as part of daily work arrive at fieldwork prepared and assured, because the proof already exists.
databrackets is a SOC 2 readiness partner, and we wrote this blog because we believe the best-prepared companies are the best-informed ones. We’ve spent over 15 years helping organizations meet demanding security standards, and we’ve worked alongside CPA firms long enough to know what they ask for and what makes a record acceptable. This blog walks you through the landscape of SOC 2 Requirements and supports your team as you prepare. Our aim is to help you prove that you’re running a genuinely secure company and that you’ve earned the trust your customers and prospects place in you.
What Are SOC 2 Requirements?
SOC 2 Requirements are a checklist of goals. The AICPA, the body behind the SOC framework has defined what a service organization’s controls must achieve, and every SOC 2 report is measured against those goals. They are fixed. Neither you nor your CPA firm can rewrite them.
What the checklist doesn’t fix is the path. The criteria don’t prescribe specific controls, so you design how each control operates, and your CPA firm tests what you describe. Your task is to put controls in place that meet each goal, configure your systems, so those controls operate as described, and show your CPA firm the proof.
This isn’t a regulatory exercise, and SOC 2 is not a law. It is the benchmark customers name when a SOC 2 report appears in an RFP or a security review.
Goals, controls, and evidence
Every SOC 2 report rests on three layers:
- Criteria: the AICPA’s fixed goals.
- Controls: the policies, processes, and system configurations you choose to meet them.
- Evidence: the records showing those controls operate. This is what your CPA firm tests.
Good evidence is a by-product of security practiced from the start, not something assembled for the examination. What you receive at the end is a report, not a certificate: your CPA firm describes what it tested and what it found, and your evidence determines how convincing that report is. Our blog on how to read a SOC 2 report shows how the results are laid out.
The goals come from the Trust Services Criteria (TSC)
The AICPA’s Assurance Services Executive Committee developed the Trust Services Criteria (TSC), the standard CPA firms use to evaluate controls over the security, availability, processing integrity, confidentiality, and privacy of information and systems. The current version is the 2017 Trust Services Criteria with points of focus revised in 2022 (see Sources). They can apply to a whole company or to a narrower slice, such as a division, unit, or function, so defining your scope is an early and important decision.
The framework runs from broad to specific:
- Categories. There are five: Security, Availability, Processing Integrity, Confidentiality, and Privacy.
- Criteria. The categories contain 61 criteria. Each has a code, such as CC6.1 or A1.2, where the letters identify the family. You will meet these codes in readiness work, in documentation, and in your CPA firm’s requests.
- Points of focus. Under each criterion, these describe characteristics a well-designed control often has.
Category | Code | Criteria | In every SOC 2 report? |
Security (the common criteria) | CC | 33 | Yes |
Availability | A | 3 | Optional |
Processing Integrity | PI | 5 | Optional |
Confidentiality | C | 2 | Optional |
Privacy | P | 18 | Optional |
How fixed are the goals? Security is in every report. The other categories are included based on your service and what your customers rely on you for, and once a category is included, all of its criteria apply. The one exception is a criterion that genuinely doesn’t apply to your service, which your system description states along with the reason. Your CPA firm then measures your controls against two things: the criteria, and the commitments you make to customers, which your system description spells out.
Beneath each criterion sit the points of focus. They’re guidance, not requirements. The AICPA is clear that you don’t have to address every one, and you can tailor them or add your own. CPA firms use points of focus as a lens, so reading them helps you predict which questions will come.
In 2022, the AICPA revised the points of focus, not the criteria. The update added technical detail, reflected the growth of privacy regulation and data retention concerns, and clarified which privacy considerations fall to data controllers and which to data processors. The goals didn’t move, so controls built to earlier guidance generally don’t need to start over, though you should expect more specific questions.
Security: the foundation of every report
Of all SOC 2 Requirements, Security is the only one in every report. It’s about protecting information and systems from unauthorized access, exposure, and damage. Its 33 criteria are the common criteria, and they sit beneath every other category. Include Availability or Privacy and you build on Security, never replace it.
Group | Criteria | What it covers | Evidence Example |
CC1 | 5 | The control environment. The people and governance side of security: defined roles, accountability, oversight, and a workforce that is vetted and trained | Code of conduct and handbook acknowledgments, background checks for new hires, security awareness training completion records |
CC2 | 3 | Communication and information | Policies acknowledged by staff |
CC3 | 4 | Risk assessment | A completed risk assessment, with remediation plans for identified risks |
CC4 | 2 | Monitoring activities | Internal control monitoring, evaluations, and corrective action tracking |
CC5 | 3 | Control activities | Policies reviewed annually, assigned control owners |
CC6 | 8 | Logical and physical access | Access request and approval records, role-based and administrator access, encryption, password requirements, anti-virus and patching, records showing departed users’ access was removed |
CC7 | 5 | System operations | Vulnerability scans, penetration testing, an incident response plan, records of how anomalous activity is detected and addressed, tabletop exercise records |
CC8 | 1 | Change management | Code review and testing documentation, how segregation of duties is maintained, the emergency change process |
CC9 | 2 | Risk mitigation | A vendor inventory with risk classification, reviews of vendors’ SOC reports, disaster recovery testing |
The first five groups come from COSO, an internal-control framework used well beyond technology, and describe how the organization is run. The last four are the technical day-to-day.
CC4 is where continuous monitoring lives. It asks management to evaluate whether controls are present and functioning, through ongoing checks, separate periodic reviews, or a mix of both. The points of focus name penetration tests and vulnerability scans among the methods. No criterion requires a penetration test, but many CPA firms and customers expect one, which is why we cover it in Pen Testing for SOC 2. The records of your own checks are evidence in their own right.
Later in this blog, we show how CPA firms group their evidence requests, which follows a different order.
Where data privacy fits
When Privacy is in scope, the 2022 revisions add privacy-related points of focus to the Security criteria, so privacy considerations appear within the Security groups as well as in the Privacy category. The Privacy category, covered below, goes further for organizations that handle personal information.
Four categories that prove what you promise
Beyond Security, SOC 2 Requirements include four categories that address specific promises a service makes. Which additional categories belong in your report depends on your industry, your service, and what your customers rely on you for. Each brings its own criteria, controls, and evidence, and once a category is included, it applies in full.
- Availability (3 criteria). For services that promise uptime, recovery targets, or reliable access that customers depend on. The criteria cover managing capacity, protecting infrastructure and maintaining backup and recovery capability, and testing recovery plans. A backup is only proven once you’ve restored from it.
- Processing Integrity (5 criteria). For services that process data or transactions for customers, such as financial services, e-commerce, or data reporting platforms. The criteria follow data from input to output: what is processed, and whether inputs, processing, outputs, and stored data are complete, valid, accurate, timely, and authorized.
- Confidentiality (2 criteria). For services that hold information that customers or contracts designate as confidential. The criteria ask you to identify that information, protect it through its life, and dispose of it properly.
- Privacy (18 criteria). For services that collect, use, or store personal information about individuals. It follows that information through eight themes: notice, choice and consent, collection, use and retention and disposal, access and correction, disclosure and breach notification, accuracy, and monitoring and enforcement. Your CPA firm tests your controls against these criteria.
If you process personal information on behalf of customers, as many SaaS companies do, the points of focus now indicate which privacy considerations belong to the data controller and which to the processor. Confirm your scope with your CPA firm early.
Confidentiality and Privacy are easy to confuse. Confidentiality covers any information your agreements say must be protected. Privacy covers only personal information about individuals, and goes further into how you collect, use, and share it. For example, a SaaS company that offers project management and CRM platforms would likely include Confidentiality but not Privacy if it does not collect personal information directly from individuals.
Choosing your categories
Your categories should mirror your commitments.
- Start with Security. Every report includes it.
- Read what customers ask for in contracts, security questionnaires, and RFPs.
- Match categories to commitments. Uptime promises point to Availability, contractual confidentiality terms to Confidentiality, and so on.
From Goals to Proof
Here’s how the layers come together in practice. Each row starts with a goal from the criteria, shows one way a company might meet it, and shows the evidence that results:
Goal (criterion) | Example control | Example evidence |
Access is limited to authorized people and removed when no longer appropriate (CC6) | Accounts are removed promptly after departure, and system owners review access quarterly | Departure records matched against removal dates, plus dated, signed review records |
Changes are authorized, tested, and approved before release (CC8) | Peer review and approval are required before code reaches production | A complete list of production releases for the period, with approval and testing records for each change your CPA firm selects |
Incidents are identified and responded to (CC7) | A documented response process, with practice exercises | Incident tickets from detection to closure, and records of practice exercises |
Recovery plans are tested (A1, if Availability is in scope) | Restores from backup are tested on a regular schedule | Dated restore-test logs showing the results |
Notice the pattern. Each piece of evidence is dated, complete, and traceable to a control. Your CPA firm usually chooses which items to examine from the complete lists you provide, so the aim is to keep everything in order, not to prepare a few examples.
Every criterion in your scope needs controls, and every control leaves a trail. That’s the thread through the rest of this blog, and it’s where an experienced readiness partner can add the most value. Our blog on the role of a SOC 2 readiness partner explains what that support looks like. Next, we’ll look at the evidence behind SOC 2 Requirements, starting with the difference between documentation and evidence, and what makes a record acceptable to your CPA firm.
Documentation and Evidence: Two Halves of the Same Proof
SOC 2 Requirements ask for two kinds of proof, and they work as a pair.
- Documentation states what you do: how your controls are designed and who owns them.
- Evidence shows that you did it: the records your controls produce while they run. Documentation is the design. Evidence is the operation.
This maps onto the two report types. A Type 1 report looks at whether your controls are suitably designed on a single date. A Type 2 report adds operating effectiveness over a period, so your CPA firm also needs dated records from across that period. Step 4 of our SOC 2 Roadmap covers how to choose between them, and our SOC 2 Examination FAQs answer common questions about each.
The documentation your CPA firm reads first
The documentation side of SOC 2 Requirements starts with policies and procedures, which our SOC 2 readiness services help organizations write and maintain.
Before your auditor tests a single control, they read to understand what you’ve built and what you’ve promised. The first documents they open set the tone for the entire engagement, so it pays to have them ready, consistent, and current.
The engagement letter and scope definition
This sets the report type (Type 1 or Type 2), the audit period, and which Trust Services Criteria apply. Security is always required. Availability, Confidentiality, Processing Integrity, and Privacy are added based on your commitments to customers.
Your system description
This is the narrative that defines your service: the product, infrastructure, software, people, data flows, boundaries, and any subservice providers such as hosting or payment vendors. Everything the auditor tests traces back to this document, so it must match reality. A system description that says one thing while your environment does another is one of the fastest ways to create findings.
Foundational context
Expect requests for an org chart, network and data flow diagrams, an asset inventory, a vendor list, and your risk assessment. These show the auditor how your environment fits together and whether you’ve identified your own risks.
Your policy set
Start with the Information Security Policy, then the supporting policies: access control, change management, incident response, vendor management, business continuity and disaster recovery, data classification and retention, and HR onboarding and offboarding. Auditors check for four things: each policy is approved, version-controlled, reviewed at least annually, and communicated to employees.
The control matrix and evidence request list
Your controls are mapped to the criteria, and the auditor sends a “Prepared By Client” (PBC) list of evidence they expect. Asking for this list early is one of the best ways to understand how your firm works.
Additionally, the Trust Services Criteria don’t name a required set, but these are the documents CPA firms most commonly ask to see:
Document | What it establishes | Typically supports |
Information security policy | Your security objectives, governance, and management’s commitment | CC1, CC2, CC5 |
Risk assessment procedure | How risks are identified, rated, and treated, the focus of a security risk assessment | CC3 |
Access control policy | How access is requested, approved, reviewed, and removed | CC6 |
Change management policy | How changes are authorized, tested, approved, and released, including emergency changes | CC8 |
Incident response plan | Roles, severity levels, communication, and post-incident review | CC7 |
Vendor management policy | How vendors are assessed, monitored, and offboarded, supported by vendor risk assessments | CC9 |
Business continuity and disaster recovery plans | Recovery priorities, procedures, and testing | CC9, A1 |
Onboarding and offboarding procedures | Screening, security awareness training, and access at hire and departure. All employees should read the employee handbook and acknowledge it. | CC1, CC6 |
Your list will vary with your service and the categories in your report.
CPA firms commonly ask whether policies are reviewed annually. The criteria don’t prescribe specific controls, so you design how each control operates, and your CPA firm tests what you describe.
Your CPA firm looks for three qualities in each document. It exists as a formal, approved document. It accurately describes how your team works. And it is reviewed on a set schedule, typically annually, with a version history. Specificity matters too: a document should be detailed enough that each control can be checked against it.
The two documents management writes
Two documents in your SOC 2 report come from management, not from your CPA firm.
1) The system description
It tells report users what your system is and how your controls operate. The AICPA’s description criteria (DC 200) set nine items it must cover:
- The services you provide
- Your principal service commitments and system requirements
- The components of the system: infrastructure, software, people, procedures, and data
- Identified system incidents
- The applicable criteria and the controls that meet them
- Complementary user entity controls, which are what customers must do on their side
- Subservice organizations, and whether they’re included or carved out
- Any criteria that aren’t relevant, with the reasons
- For a Type 2, significant changes during the period.
2) Management’s assertion
This is a signed statement that the description is fairly presented and that your controls were suitably designed and, for a Type 2, operated effectively. At the end of the engagement, management also signs a representation letter. The AICPA’s illustrative SOC 2 report shows how the assertion, description, auditor’s report, and test results fit together, and our blog on how to read a SOC 2 report walks through each section of a finished report.
Because your CPA firm tests the controls your description claims, the description works as a commitment. Describe what you operate today, in the detail you can evidence. Preparing these documents is a core part of the work a SOC 2 readiness partner does alongside your team.
What documentation can’t show, and what evidence adds
Documentation can’t show that a control ran. For those details, your CPA firm looks at evidence such as system-generated reports (user access listings, transaction logs, ticket exports, and configuration reports), spreadsheets, and screenshots from the system itself.
Your CPA firm looks for four kinds of evidence:
- Configuration evidence. The settings that enforce a control, such as MFA required for all users, encryption enabled, or branch protection requiring review before code is merged.
- Activity records. The tickets, logs, approvals, and sign-offs your controls generate as they run.
- Complete lists. Every occurrence of an event in the period: all new hires, departures, production releases, or incidents. Your CPA firm builds its selection from these.
- Traced samples. Specific items your CPA firm picks from those lists and follows end to end, from request to approval to completion.
Here’s how a documented statement turns into evidence:
What your documentation says | What the evidence shows |
Employees complete security awareness training within 30 days of hire and annually | A training completion report with dates, matched against start dates from HR |
A risk assessment is performed annually and approved by management | A dated risk assessment, a risk register with owners and treatment decisions, and management sign-off |
Vendors that handle customer data are reviewed before onboarding and annually | A vendor inventory with risk tiers, completed reviews, and records of vendors’ SOC reports being reviewed |
Vulnerabilities found through scans and penetration testing are remediated within defined timelines | Scan results, a penetration test report, and remediation tickets showing detection and closure dates against those timelines (see Pen Testing for SOC 2) |
Policies are reviewed annually | Version history with dated approvals |
One story, told three ways
Your policies, your system description, and your records should tell the same story. When a policy says what the team does, the description says the same, and the records confirm it; your CPA firm’s work is straightforward. Three practices keep them aligned:
- Version your policies with dated approvals, so its clear which version applied when.
- Update the description when your system or controls change.
- Review each document on the schedule it states.
Documentation sets the standard, and evidence shows you met it. Next, we’ll look at what makes a record acceptable to your CPA firm, and how it holds up across the evidence behind SOC 2 Requirements.
What Makes your SOC 2 Evidence Audit-Ready
Meeting SOC 2 Requirements depends on records your CPA firm can rely on. AICPA guidance requires your CPA firm to obtain sufficient, appropriate evidence for each conclusion it reaches, and your CPA firm judges whether a given record meets that bar.
Complete and accurate information
Many of the records your CPA firm tests are reports that you generate: a list of employees, a list of production releases, an export of alerts. CPA firms call this information produced by the entity, or IPE. Your CPA firm builds its selections from these lists and evaluates whether they can be relied on. The AICPA’s SOC 2 guide (see Sources), updated in 2022, strengthened its guidance on the completeness and accuracy of this information, so expect it to receive close attention.
Completeness and accuracy are separate questions. Completeness asks whether anything is missing: does the list include every in-scope user, change, or event? Accuracy asks whether the details are right: do the names, dates, and statuses match what the system recorded? A list can pass one test and not the other.
Five practices make this straightforward:
- Generate lists from the system of record, not from memory or a manually maintained spreadsheet.
- Document how each report is produced: the source system, the query or filters, the date range, and who ran it and when.
- Reconcile the counts. The number of records in the console should equal the number of rows in the export, and key reports should tie back to their source.
- Keep exports unaltered. Opening a file and saving it again can remove the details that made it reliable. If you need to filter, document what you filtered, why, and how completeness was maintained.
- Treat the logic behind key reports as controlled. If a query or report setting changes during the period, record the change.
Reliable lists also keep fieldwork efficient, because weaknesses in completeness or accuracy lead to additional testing.
Screenshots, exports, and history
Screenshots are common and useful, but each form of evidence answers a different question:
Form | What it shows well | Strengthen it by |
System export or report | Records and events as the system captured them, with a generated timestamp | Keeping it unaltered, and noting the source, the run time, and any filters |
Screenshot | The visible state at the moment of capture | Including the system clock and the full URL or tenant identifier, and capturing the whole relevant screen |
Evidence from the whole review period
SOC 2 Requirements for a Type 2 report ask for evidence that the control operated across the review period, which for a first report commonly runs six to twelve months. Two points follow:
- Spread matters. CPA firms spread their samples across the period, so every month needs records.
- Records made at the time are the strongest. Evidence assembled afterward describes the present, not the period. Systems that generate records during normal work, such as tickets, logs, and approvals, produce the most reliable trail.
Following one change from start to finish
Consider a single production change. The ticket records the request and the reason. The review shows approval from someone authorized to give it. The test result is attached. The deployment record shows the release time and an identifier for the change. Because these pieces link to one another through shared identifiers, your CPA firm can follow the change from request to release without anyone needing to explain it.
The same pattern works for a departure. An identifier from your HR system can connect the termination record to the access removal in your identity provider, with a timestamp at each step.
Building this in from the start
Evidence is easier to gather as controls operate than to reconstruct afterward, which is why a SOC 2 readiness partner can help before the review period begins. Our readiness clients’ evidence lives in a structured format on our dbACE platform, which the CPA firm they choose can access.
Next, we’ll look at how your CPA firm tests evidence, from the procedures it uses to the way it selects samples. That is where the evidence practices above come together.
How Your CPA Firm Tests Your Controls
Once your evidence is in order, testing becomes predictable. Understanding the sequence, the procedures, and the logic behind sampling lets your team prepare with confidence. This section explains how an examination moves from walkthroughs to results, what each testing procedure involves, and how your CPA firm decides what to examine when it tests your controls against SOC 2 Requirements.
How a SOC 2 examination unfolds
Most examinations follow five stages:
- Kickoff and information requests. Your CPA firm confirms scope, timing, and contacts, then sends its requests.
- Walkthroughs. Control owners walk your CPA firm through how each control works.
- Populations and selection. Your CPA firm requests complete lists of events for the review period and selects the items it will examine.
- Testing. Each selected item is traced through the control, with follow-up questions as needed.
- Reporting. Your CPA firm documents its results, and management reviews the draft and signs a representation letter.
The four testing procedures
Your CPA firm uses four procedures, often in combination:
Procedure | What your CPA firm does | Example |
Inquiry | Asks knowledgeable people how a control works | Asking the engineering lead how code changes are approved |
Observation | Watches a process or condition as it happens | Watching an access review take place, or confirming that a login is refused without the right permissions |
Inspection | Examines records, documents, and settings | Reviewing change tickets, approvals, logs, and configuration exports |
Reperformance | Independently repeats the control and compares the result | Re-running a comparison of active accounts against the HR departure list and checking that the results match |
Inquiry is part of every examination, but it can’t carry a conclusion on its own. AICPA guidance, set out in its SOC 2 guide, is clear that inquiry alone does not provide sufficient, appropriate evidence of operating effectiveness, so your CPA firm pairs it with another procedure. Reperformance is typically used when the other procedures don’t provide enough assurance.
How your CPA firm decides what to examine
A CPA firm starts with a population; the complete list of times a control operated during the period and then selects a sample from it. There is no fixed sample size. The CPA firm decides, based on how often the control operates, the risk, the population, and the deviations it can tolerate. Higher-risk controls tend to receive larger samples.
You won’t know in advance which items will be selected, so every record from the period needs to be ready. How a control operates shapes what gets examined:
Control type | Example | Population | What your CPA firm typically examines |
Point in time | Encryption enabled on production databases | The setting, and its history across the period | Configuration evidence plus configuration history |
Periodic | Quarterly access review | Each review in the period | The records of each review |
Event-driven | Production changes, new hires, departures | Every event in the period | A selection of events, each traced from start to finish |
An annual control has a single occurrence, so your CPA firm examines it every time.
For each selected item, your CPA firm checks the specific attributes the control promises: that approval came before deployment, that a review took place within its stated timeframe, or that every in-scope system was covered.
When an item doesn’t meet the control
If a selected item doesn’t meet the control as written, your CPA firm records a deviation. The report presents the outcome as an exception: a description of the control tested, what was found, and how often.
An exception doesn’t end an engagement. A few minor exceptions rarely sink a report, but serious problems can lead to a modified opinion. What matters is their frequency, their scope, and their relevance to the services you provide. Management can add a response explaining the cause and the remediation. That response is management’s own statement, not a test result, so it adds context without changing what the test found.
How results appear in your report
In a Type 2 report, the tests-of-controls section pairs each criterion and control with the procedures your CPA firm performed and the result, which is typically “no exceptions noted” or a description of what was found. Wording and layout vary by CPA firm. A Type 1 report lists controls without tests, because it covers design only. The AICPA’s illustrative SOC 2 report (see Sources) shows a Type 2 layout, including the tests of controls and their results.
Preparing with confidence
Two practices help your team approach testing with confidence:
- Know where each list comes from. Be ready to show how each population was generated, as covered in the previous section.
- Provide complete lists and let your CPA firm choose the items. Because your CPA firm makes its own selections, having every record from the period ready is the surest approach.
Maintain consistent security controls and supporting evidence. Ensure that security controls operate consistently throughout the audit period and that relevant supporting evidence is maintained and readily available to demonstrate their ongoing effectiveness. As a SOC 2 readiness partner, we run a readiness assessment ahead of the examination, so you can see how your controls hold up to this kind of testing before your CPA firm begins
Next, we’ll walk through the evidence behind SOC 2 Requirements, control area by control area.
The Evidence Your CPA Firm Asks For, Area by Area
In the first section, we laid out the common criteria in the AICPA’s own order, CC1 through CC9. We did that because this order mirrors the Trust Services Criteria and the tests-of-controls section of your report, so it works as a checklist of goals: every criterion your controls must meet, each with a code you can trace.
Requests by your CPA firm, however, rarely arrive in that order. CPA firms commonly organize them by what your teams actually do: hiring people, removing their access, approving changes, responding to incidents. That is the point where SOC 2 Requirements turn into work for your teams.
The two views overlap rather than match one to one, so each area below lists its criteria codes. Wording and order vary from one CPA firm to the next, and your own list will follow your system description.
Governance and people
Criteria: CC1, CC2, CC5.3
What your CPA firm asks about | Evidence that answers it |
Who owns and oversees security | Your information security governance structure, and records that those charged with governance receive information about security |
Whether policies are current and approved | Records that policies are reviewed annually |
Whether people know their responsibilities | Handbook and code of conduct acknowledgments |
Whether people are trained | Security awareness training records |
New hires
Criteria: CC1.1, CC1.4, CC6.2
What your CPA firm asks about | Evidence that answers it |
Screening | Background check completion records |
Commitments | A signed code of conduct and handbook acknowledgment |
Training | Training completion records |
Access | Access request tickets and approvals |
Departures
Criteria: CC6.2, CC6.3
What your CPA firm asks about | Evidence that answers it |
Access removed on time | Access removal requests, and user lists showing the account was removed or disabled in a timely manner |
The most useful check you can run yourself is the gap between each person’s last day and the removal timestamp. If a gap appears, the process is broken. If a contractor can reach production or customer data, include contractors in these records too.
Logical access and access reviews
Criteria: CC6.1, CC6.3, CC6.6, CC6.7, CC6.8
What your CPA firm asks about | Evidence that answers it |
Role-based access | An export of user-to-role and group assignments, plus approvals for permissions beyond a standard role |
Privileged access | A list of administrator and production accounts with the reason each exists |
Strong authentication | Identity provider settings showing MFA is required, not optional |
Data protection | Encryption settings for data stores and backups, minimum password requirements, malware protection, and patch status |
Periodic reviews | Dated review records showing the reviewer, the accounts examined, the decisions made, and the removals that followed |
Two details raise confidence: MFA that users can’t decline, and access reviews that show decisions and follow-through rather than a list that was generated and signed.
Risk management and continuity
Criteria: CC3.1 to CC3.4, CC4.1 to CC4.2, CC9.1
What your CPA firm asks about | Evidence that answers it |
A completed risk assessment | A dated assessment tied to your service commitments, a risk register with owners, ratings, and treatment decisions, and management sign-off. |
Follow-through on risks | Remediation plans and records of risks treated or formally accepted |
Reassessment after significant change | Risk review records for new products, major architecture changes, and critical vendors |
Checks on your own controls | Records such as monitoring results, owner reviews, and a deficiency log tracked to closure |
Continuity | A business continuity plan with an owner and review date, and dated recovery test records where recovery is tested |
Continuous monitoring shows up in this area. Records showing that you check your controls between examinations are evidence in their own right.
Change management
Criteria: CC8.1
What your CPA firm asks about | Evidence that answers it |
Review and testing | Pull request or ticket records with the reviewer, approval, and test results |
Segregation of duties | Branch protection or approval settings that prevent a person from approving their own change |
Completeness | A list of every production deployment in the period, each linked to its commit, approved change, and timestamp |
Urgent changes | The emergency change procedure and emergency change tickets with after-the-fact review |
A documented emergency path, treated as a controlled exception with its own review, keeps urgent fixes from looking like gaps.
Vulnerability management and monitoring
Criteria: CC7.1, CC7.2, CC4.1
What your CPA firm asks about | Evidence that answers it |
Regular scanning | Dated scan reports from across the period showing what each scan covered |
Independent testing | A penetration test report with scope, dates, and findings, plus confirmation that fixes were retested. Our blog to Pen Testing for SOC 2 explains what CPA firms expect |
Findings fixed on schedule | Remediation tickets with open date, owner, and close date, or a signed risk acceptance, with follow-up scans showing fixes cleared |
Monitoring in place | Alert rules, alerts that fired with acknowledgment and triage notes, and log retention that reaches back to the start of the review period. |
Check coverage early. A new cloud account or service that was never connected to monitoring is an easy gap to prevent.
Incident response
Criteria: CC7.3, CC7.4, CC7.5
What your CPA firm asks about | Evidence that answers it |
A defined plan | An incident response plan with roles, severity levels, and communication steps, with a review date |
Detection | How anomalous activity is detected and addressed, from alert rules to triage records |
Practice | Tabletop exercise records with the scenario, participants, findings, and resulting plan updates |
Real events | Incident tickets showing detection, containment, recovery, and closure times, with post-incident reviews and corrective actions. |
Record the work where a record is created. An incident resolved in a chat thread, with no ticket, is hard to show.
Vendor management
Criteria: CC9.2, CC3.2
What your CPA firm asks about | Evidence that answers it |
Knowing your vendors | A vendor inventory with risk tier, owner, and the data each vendor receives |
Assessing them | Review records with the date, reviewer, report period covered, and conclusion, plus current SOC 2 reports for critical vendors. |
Monitoring them | Evidence that key vendors are reviewed at least annually |
Offboarding them | Records showing access revoked and data returned or deleted when a vendor leaves. |
Make the inventory a gate in onboarding, so every vendor is reviewed before it receives customer data, and check that each SOC 2 report you hold covers a recent period.
Availability, Confidentiality, Processing Integrity, and Privacy
Where these categories are in your report, SOC 2 Requirements add their own criteria, and your CPA firm will request evidence against them:
Category | What your CPA firm typically asks for | Criteria |
Availability | Capacity and uptime monitoring, backup configuration and job history, and dated restore or failover test records | A1.1 to A1.3 |
Confidentiality | Data classification and handling rules, a retention schedule, and deletion records, including deletions confirmed by vendors | C1.1 to C1.2 |
Processing Integrity | Input validation rules, test results for processing logic before release, and exception handling records | PI1.1 to PI1.5 |
Privacy | Privacy notice versions, consent records, logs of individual requests and response times, retention and deletion records, and vendor privacy terms | P1 to P8 |
Because requests arrive by area, naming one owner for each area, and one source system for each owner, keeps an examination running smoothly. Mapping areas to owners and systems is a core part of a SOC 2 readiness assessment.
Next, we’ll look at the routines that keep the evidence for each of these areas flowing all year.
How to Keep Your Evidence Flowing All Year
Evidence is easiest to manage when your routines already produce it. Criterion CC4 in the Trust Services Criteria asks management to evaluate whether controls are present and functioning. A routine that checks your controls between examinations is the practical form of that goal.
Start with owners and a schedule
Assign each control an owner and a schedule. Ensure there is an owner for each category of evidence that stays manual. Sticking to the frequency as agreed upon in your policies by your organization and what is required for the control, is critical.
Settle three details early:
- whether quarters follow the calendar or fiscal year
- how due dates are set
- who covers for an owner who is away
Match your control frequency to your controls
Common control frequencies for SOC 2 compliance are illustrated below. The AICPA Trust Services Criteria do not prescribe specific controls or their operating frequencies. Organizations define how their controls operate, while the independent CPA firm evaluates their design and operating effectiveness.
Maintaining evidence according to the established control frequency helps demonstrate consistent control operation throughout the SOC 2 Type II reporting period and supports independent auditor testing.
Control Frequency | Typical controls | What to keep |
As work happens | Access requests, production changes, hires, departures, alert handling, incidents | The complete list of events from the source system, with each item’s records |
Monthly | Vulnerability scans and review of open findings, and the control check-in | Dated scan reports, remediation tickets, and a record of each review |
Quarterly | User access reviews, and risk or vendor reviews where your policy sets them | A dated record of each review showing the reviewer, the scope, the decisions, and the follow-through |
Annually | Risk assessment, policy review, security awareness training, penetration test, tabletop exercise, recovery test, and vendor reviews for critical vendors | Dated, approved records of each, with the remediation that followed |
Protect your original records
Keep original exports and limit who can change them.
Build a control-to-evidence map
One living tracker keeps owners and evidence connected. For each control, record the criterion it supports, the owner, the source system, the evidence it produces, how often it is collected, where it is stored, when it was last collected, and its status. Add a line for any exception and its fix. The map mirrors the way CPA firms group their requests, which is why the previous section was organized by area.
Store the records in a structured repository with consistent naming. Limit who can edit it, and keep a record of changes, so your CPA firm can rely on what it sees.
Review monthly
A short monthly check-in catches missed tasks. Record what you fix and when.
Rehearse before the review period begins
Before the period opens, run each recurring control once as if it had started. Generate the complete population for a trial window, confirm that each list reconciles to its source system, and check that every owner can complete their control on schedule. Confirm that the control wording matches how the work is actually done. Fix what the rehearsal reveals while there is still time to adjust.
Use automation with intention
Automation can collect evidence from integrated systems, centralize artifacts, and coordinate requests, which saves real effort. CPA firms also point out what it cannot do: judge whether evidence is complete, representative, or appropriate for the control being tested. Integrations can also capture a single point in time instead of the full period. Four practices help:
- Confirm coverage. Check that integrations reach every in-scope cloud account, repository, and user population, and document anything excluded.
- Align the controls. Match the controls in your platform to the wording in your system description, not to a generic template.
- Name owners for manual evidence. Some evidence usually stays manual, such as HR populations, vendor reviews, and incident narratives.
- Reconcile regularly. Compare platform coverage with your in-scope controls at least quarterly, not only before the examination.
When something changes or slips
Systems and controls change during a review period. When they do, update the control wording and the system description. If a review runs late or a record is missing, complete the work, fix the cause, and record the fix.
Carrying the routine into renewal
Because the next review period begins as soon as the last one ends, the routine you build here carries straight into renewal. Ongoing support and monitoring is one of the tasks a SOC 2 readiness partner performs, alongside the internal audit mentioned earlier.
Next, we’ll look at the evidence pitfalls we see most often, and how to avoid them.
Common Evidence Pitfalls and How to Avoid Them
Many difficulties in meeting SOC 2 Requirements come from the records, not from the controls behind them. A control can run exactly as designed and still be hard to show if its records are late, incomplete, or hard to trace. The good news is that these pitfalls are predictable. Here are the ones that appear most often, grouped by where they arise.
Timing and history
Watch for | What helps |
Evidence gathered late, covering only part of the review period | Collect records as work happens, and use the monthly review to flag any record that covers only part of the period |
Records created after the fact | Prefer records your systems generate at the time of the activity, because reconstructed records describe the present, not the period |
A control that runs on a different cadence than its policy states | Set cadences your team can sustain, and update the policy if a cadence changes |
History that is not retained | Check retention settings early, since some platforms keep only a rolling window, and make sure logs reach back to the start of the period |
Reliability of records
Watch for | What helps |
Undated or context-free screenshots | Capture the system clock, the full URL or tenant identifier, and the logged-in user |
Lists that have not been reconciled | Match record counts to the source system, and document how each list was produced. The AICPA’s SOC 2 guide gives this topic close attention |
Exports that were edited or re-saved | Keep exports unaltered, and document any filtering and why it was needed |
Evidence that doesn’t match the control | Match each record to the wording of the control. If a control calls for a documented review, a raw log alone does not show it |
Reviews that show attendance but not content | Record the reviewer, the scope, the decisions made, and the follow-through |
Ownership and process
Watch for | What helps |
Controls with no named owner | Assign an owner to every control and to each category of manual evidence |
Policies that describe a different organization | Write policies from how work is actually done, and review them against practice on the schedule they state |
Samples chosen in advance | Provide complete lists, and let your CPA firm select the items |
Scope and coverage
Watch for | What helps |
New systems or accounts outside monitoring and inventory | Reconcile your system inventory with log sources and integrations whenever something new is provisioned |
Integrations that collect only part of the picture | Document what each integration includes and excludes, and confirm that it retains history for the full period |
Testing scope that doesn’t match the system description | Align the scope with the description. Our Pen Testing for SOC 2 blog explains how |
Contractors outside HR records | Include contractors who can reach production or customer data in training, acknowledgment, and offboarding records |
Vendors onboarded without review, or reports that are out of date | Criterion CC9.2 expects you to manage the risks that vendors and partners bring. |
Next, we’ll look at how to choose a readiness partner, and what to ask about evidence before you decide.
Choosing a Readiness Partner Who Strengthens Your Evidence
A SOC 2 report is only as strong as the work behind it, and that work involves two kinds of professionals: a readiness partner who prepares you, and a CPA firm that examines you. Choosing both well is one of the most practical ways to meet SOC 2 Requirements with confidence.
What a thorough SOC 2 readiness engagement covers
At databrackets, a SOC 2 readiness engagement moves through eight steps, from determining the Trust Services Criteria for your industry to sharing access to your evidence with your CPA firm so that effort is not duplicated. Along the way, you receive:
Deliverable | What it provides |
Gap analysis report | An overview of current security protocols and the areas that need improvement |
Penetration testing reports | An in-depth assessment of vulnerabilities |
Compliance and security assessment reports | A comprehensive evaluation across your environment |
Guidance on acceptable evidence documents | Direction that streamlines the process |
Updated policies and procedures | Documents that address policy and procedural requirements |
Security technology consulting | Support implementing any missing technical controls |
Customized user training | The knowledge staff need to maintain security standards |
Support for the management assertion | Help completing management’s assertion for the SOC 2 report |
Final readiness report | A summary of your preparedness for a SOC 2 Type 2 examination |
Once your SOC 2 examination begins, your readiness partner can stay involved: facilitating communication with the CPA firm, assisting with the system description, furnishing evidence for controls, helping collect sample evidence, conducting walkthroughs, joining interviews, and addressing open questions. Our SOC 2 Evidence FAQ page covers what counts as evidence, what each control area requires, how long to retain it, and what happens when it is missing.
Well-prepared organizations are better positioned for a successful SOC 2 examination. With the right readiness partner, the right CPA firm, and the evidence routine described earlier in this blog, your SOC 2 Requirements become a program you can run with confidence all year.
Frequently Asked Questions
Is SOC 2 a certification?
No. SOC 2 is an attestation. A licensed CPA firm issues a report that describes what it tested and what it found, and no certificate is issued.
What counts as SOC 2 evidence?
SOC 2 evidence is the documentation that demonstrates a control was in place and operating as intended during the review period. It is what your CPA firm tests. It can include system-generated reports such as user access listings, logs, ticket exports, and configuration reports, as well as spreadsheets and screenshots from the system itself.
What is the difference between documentation and evidence?
Documentation states what you do: how your controls are designed and who owns them. Evidence shows that you did it: the records your controls produce while they run. A Type 1 report looks at whether your controls are suitably designed at a single date. A Type 2 report adds operating effectiveness over a period, so your CPA firm also needs dated records from across that period.
What evidence does a Type 2 report need?
Your CPA firm needs evidence that each control operated across the whole review period, which for a first report commonly runs six to twelve months. CPA firms spread their samples across the period, so every month needs records. Records made at the time are the strongest, because evidence assembled afterward describes the present, not the period.
What is information produced by the entity (IPE)?
IPE is a report you generate for your CPA firm, such as a list of employees, a list of production releases, or an export of alerts. CPA firms evaluate whether these lists are complete and accurate before relying on them. Generating each list from the system of record, documenting how it was produced, reconciling the counts, and keeping exports unaltered all help.
Does my CPA firm test every record?
No. Your CPA firm starts with a population, the complete list of times a control operated during the period and selects a sample from it. There is no fixed sample size. Your CPA firm decides, based on how often the control operates, the risk, the population, and the deviations it can tolerate. You won’t know in advance which items will be selected, so every record from the period needs to be ready.
What happens if a record is missing or a control didn’t operate?
A record you can’t produce may be treated as an exception, even if the control ran, because a CPA firm can’t support a conclusion with a verbal claim alone. The report describes the exception and how often it occurred. A few minor exceptions rarely sink a report, but serious problems can lead to a modified opinion. Management can add a response explaining the cause and the fix.
Does SOC 2 require a penetration test?
No criterion requires a penetration test, but many CPA firms and customers expect one. The points of focus under CC4 name penetration tests and vulnerability scans among the ways to evaluate controls. Our Pen Testing for SOC 2 blog explains what auditors expect, including testing at least annually.
Can software collect all of my evidence?
Automation can collect evidence from integrated systems, centralize artifacts, and coordinate requests. CPA firms also point out that it cannot judge whether evidence is complete, representative, or appropriate for the control being tested. Check that integrations reach every in-scope account and population, match the controls in your platform to your system description, name owners for evidence that stays manual, and reconcile coverage at least quarterly.
How do I choose a CPA firm?
The Journal of Accountancy advises looking into the firm’s size, capacity, and client experience; checking qualifications, experience, and peer review outcomes; understanding the scope, the sampling, and how independence is protected; and weighing whether the promised speed, simplicity, or price sounds too good. Our SOC 2 Auditor Selection FAQ page adds seven questions to ask before you sign.
Key Takeaways
- SOC 2 Requirements are fixed goals set by the AICPA. The controls that meet them, and the evidence that proves they operate, are yours.
- Security is in every report. Add Availability, Processing Integrity, Confidentiality, or Privacy only when your commitments justify them.
- Documentation shows how your controls are designed. Evidence shows they operated. A Type 2 report needs dated records from across the whole review period.
- Lists you generate for your CPA firm must be complete and accurate. Produce them from the system of record, document how, reconcile the counts, and keep exports unaltered.
- Your CPA firm tests by population and sample, with no fixed sample size. You won’t know which items it will select, so keep every record ready.
- CPA firms commonly group evidence requests by what your teams do: new hires, departures, access, risk, change, vulnerabilities, incidents, and vendors.
- Software can collect evidence, but it can’t judge whether the evidence is complete. Name owners for manual evidence and reconcile coverage regularly.
- Choose your readiness partner and your CPA firm with care. Ask about scope, sampling, independence, and peer review.
Summary
SOC 2 rewards teams whose everyday work leaves a trail. The AICPA fixes the goals, you design the controls, and your records show those controls operated. That is why SOC 2 Requirements come down to evidence that is dated, complete, and traceable to the control it supports.
Start with the documentation your CPA firm reads first, produce the lists it will sample straight from your systems, and keep records across the full review period. Choose a readiness partner and a CPA firm that tailor their work to your system. Do that, and your evidence will be ready long before fieldwork begins.
How databrackets can help you with your SOC 2 requirements
databrackets is an authorized and accredited FedRAMP 3PAO with ISO/IEC 17020:2012 accreditation from A2LA. We are also an authorized certifying body for ISO 27001 and an authorized C3PAO for CMMC.
For over 15 years, we have been helping organizations achieve compliance or certification with the most rigorous cybersecurity and data privacy standards, including NIST SP 800-53, NIST SP 800-171, NIST Cybersecurity Framework, ISO 27001, SOC 2, CMMC, HIPAA, and GDPR.
Services for SOC 2
databrackets guides you through your SOC 2 journey as your readiness partner. We work alongside licensed CPA firms, so your CPA firm performs the examination and issues the report while we prepare your organization. You can bring your own CPA firm, or we can work with our CPA partners.
Here is how we support you:
- Gap analysis and readiness assessment: We assess your controls against the criteria you select, identify gaps, and develop a plan of action.
- Policies and documentation: We provide updated policies and procedures, and support for completing your management assertion.
- Evidence: We give you guidance on acceptable evidence documents. Our readiness clients’ evidence lives in a structured format on our dbACE platform, which the CPA firm they choose can access.
- Penetration testing: Our penetration testing services produce the third-party pen test reports your CPA firm looks for.
- Staff training: We provide customized user training so your staff can maintain security standards.
- CPA coordination: We facilitate communication with your CPA firm, furnish evidence for controls, help collect sample evidence, conduct walkthroughs, and join interviews.
Ready to start? Connect with an expert or explore our SOC 2 readiness services.
Sources
AICPA publications
Some of these sources may be paid, and some may be available to AICPA members.
- 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (With Revised Points of Focus — 2022)
- 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)
- SOC 2® Reporting on an Examination of Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy (SOC 2 guide)
- Illustrative SOC 2® Report with Description and Assertion
- Ethics Staff Insights: Business arrangements with SOC tool providers, AICPA, April 2026
- Promises of ‘fast and easy’ threaten SOC credibility, Journal of Accountancy, February 2026
- AICPA guides peer reviewers to address SOC 2 risks, Journal of Accountancy, May 2026
Srini Kolathur
Co-Author: Aditi Salhotra
Manager – Digital Marketing and Business Development
Aditi is a Digital Marketing and Business Development Professional at databrackets.com. She is a strong advocate of good cyber hygiene and is proud of the company’s mission to safeguard organizations from cyber threats and ensure their business continuity in adverse situations.