The report every enterprise buyer already trusts.
SOC 2 is the shared language of B2B trust. One independent CPA opinion tells a buyer's security team how you protect their data, so the review that used to stall a deal can move.
SOC 2 Compliance: Requirements, Process and Automation
SOC 2 is an AICPA reporting framework in which a licensed CPA firm examines a service organization's controls against the Trust Services Criteria. A Type 1 report covers control design at one date. A Type 2 report also tests how controls operated over a period, usually 3 to 12 months. Providers use it to show how they protect customer data.
Carbon helps software development teams build SOC 2 evidence into the way they already ship, whether they build a product that is in scope of a SOC 2 examination or work inside an organization pursuing one.
/01 · Overview
At a glance
| Full name | System and Organization Controls (SOC) 2 report, an examination against the AICPA Trust Services Criteria |
|---|---|
| Also known as | SOC 2 compliance, SOC 2 report, SOC 2 attestation, SOC 2 audit, SOC 2 Type 1, SOC 2 Type 2 (Type II). Often called "SOC 2 certification", though no certificate is issued. |
| Issuing body | American Institute of Certified Public Accountants (AICPA) |
| Framework type | Attestation report |
| Variants | Type 1 (design at one date) and Type 2 (operation over a period) |
| Mandatory? | No. It is voluntary under law, but customers and contracts often require it. |
| Geography | Used worldwide; developed in the United States |
| Applies to | Service organizations that store, process or transmit customer data, such as SaaS, cloud, data-processing and managed-service providers |
| Current version | 2017 Trust Services Criteria, revised points of focus, 2022 |
| Assessment method | Examination by a licensed CPA firm. Type 1 tests design at one date; Type 2 tests design and operating effectiveness over a period. |
| Renewal or reassessment | Annual |
| Official source | AICPA: 2017 Trust Services Criteria (with revised points of focus, 2022) |
/02 · Carbon by HardStack.AI
How Carbon supports SOC 2
Carbon helps software development teams turn the way they build and ship into SOC 2 evidence. It connects to the tools your team already uses, guides people through auditor-tested control structures, and keeps every record mapped to the criteria it supports. AI speeds the work; your people decide, and a licensed CPA firm performs the examination.
Who Carbon supports
/A · In-scope product
Teams building an in-scope product
If your product or platform sits inside the boundary of a SOC 2 examination, Carbon shows engineers which changes, access and operations records auditors will sample, and keeps those records complete from the first day.
/B · Organization pursuing SOC 2
Teams inside an organization pursuing SOC 2
If your company is pursuing a Type 1 or Type 2 report, Carbon gives engineering, security and compliance leads a shared view of controls, owners and evidence, built on the tools you already use rather than replacing them.
10 / 13
SOC 2 control areas automated or assisted
For a Type 1 report, Carbon helps you document control design and have evidence ready for the examination date. For a Type 2 report, it keeps evidence flowing across the whole observation period, so populations and samples are ready when fieldwork starts. Carbon works with your existing tools and documents instead of replacing them. Areas that depend on judgment, such as governance, processing integrity and privacy, stay with your people.
What Carbon does not do
- Carbon does not perform the examination or issue a SOC 2 report. Only a licensed CPA firm can do that.
- Carbon does not make management decisions, such as scope, risk acceptance or which criteria to include.
- People-based controls, such as board oversight and staff completing training, still need people to act.
- Coverage depends on your tools. Where Carbon has no connection, evidence is uploaded manually.
- Using Carbon does not guarantee an unmodified opinion.
/03 · Definition
What is SOC 2?
SOC 2 is an independent examination report from a licensed CPA firm. It evaluates whether a service organization's controls meet the AICPA Trust Services Criteria, either at one date (Type 1) or throughout a review period, usually 3 to 12 months (Type 2). Security is mandatory; availability, processing integrity, confidentiality and privacy are optional.
SOC 2 belongs to the AICPA's System and Organization Controls suite. It has no fixed control list. The Trust Services Criteria describe outcomes, each company designs its own controls, and the auditor tests those controls against management's written description of the system. Type 2 reports are the ones most enterprise buyers ask for, because they show that controls kept working over time. SOC 2 reports are restricted-use documents, shared with customers and prospects under NDA rather than published.
There is no SOC 2 certificate and no pass mark. "SOC 2 compliant" means a CPA firm issued a report with an unmodified (clean) opinion on your system and period. Exceptions can still appear in a clean report. Qualified, adverse and disclaimer opinions signal bigger problems.
/04 · Scope
Who needs SOC 2?
Service organizations that handle customer data need SOC 2 when customers ask for independent proof of their controls. That includes SaaS, cloud and managed-service providers, and the software development teams inside them, because engineering processes such as code review, change approval and access control are tested in the examination.
You likely need SOC 2 if
- Your engineering team builds or runs a product that is in scope of a SOC 2 examination and must show that changes, releases and access follow controlled processes.
- Enterprise customers request a SOC 2 report in security questionnaires, RFPs or contracts.
- You host, process or store customer data as a SaaS, cloud, data or managed-service provider.
- You serve regulated buyers, such as fintech or healthcare companies, who must review their vendors.
- Your organization is pursuing a Type 1 or Type 2 report and engineering must supply much of the evidence.
You likely do not need SOC 2 if
- You do not handle customer data and no customer has asked for third-party assurance.
- You sell only to consumers, and no business buyer reviews your vendor security.
- Your buyers require a different standard, such as ISO 27001 or FedRAMP, and have not asked for SOC 2.
- You are pre-product and no contract or buyer requires an independent report yet.
If you do not comply: SOC 2 is not a law, so there is no regulatory penalty. The cost is commercial: stalled enterprise deals, long security questionnaires, failed vendor reviews, and contracts that require a current report. A qualified or adverse opinion can have similar effects.
/05 · Criteria
SOC 2 requirements
SOC 2 has no fixed control list. The AICPA Trust Services Criteria define what must be achieved: 33 common criteria (CC1 to CC9) for Security, plus optional criteria for availability, processing integrity, confidentiality and privacy. Your controls must meet them, and for a Type 2 report they must operate consistently through the review period.
| Family or domain | What it covers | Example requirement | Carbon support |
|---|---|---|---|
| CC1 Control Environment | Governance, integrity, oversight, accountability and competence | Management sets a code of conduct, assigns security responsibility, and screens new hires | Manual |
| CC2 Communication and Information | How security information is produced and shared inside and outside the company | Publish security responsibilities to staff and customers; keep a current system description | Assisted |
| CC3 Risk Assessment | Identifying and analyzing risks to objectives, including fraud and change | Complete and document a risk assessment at least annually | Assisted |
| CC4 Monitoring Activities | Ongoing and separate evaluations of whether controls work | Review control performance and report deficiencies to management | Automated |
| CC5 Control Activities | Policies and procedures that put controls into effect | Approve and review security policies on a set schedule | Assisted |
| CC6 Logical and Physical Access | Restricting access to systems, data and facilities | Enforce MFA, review user access quarterly, remove access when staff leave | Automated |
| CC7 System Operations | Detecting and responding to vulnerabilities, anomalies and incidents | Scan for vulnerabilities, monitor logs, and follow an incident response plan | Assisted |
| CC8 Change Management | Authorizing, testing and deploying changes to the system | Require approval and review before any production deployment | Automated |
| CC9 Risk Mitigation | Business disruption and vendor risk | Assess critical vendors and review their SOC reports annually | Assisted |
| A1 Availability (optional) | Capacity, backup and recovery to meet uptime commitments | Test backup restoration and disaster recovery | Assisted |
| PI1 Processing Integrity (optional) | Processing is complete, valid, accurate and timely | Validate inputs and reconcile outputs against commitments | Manual |
| C1 Confidentiality (optional) | Identifying, protecting and disposing of confidential information | Encrypt confidential data and delete it per retention commitments | Assisted |
| P1–P8 Privacy (optional) | Notice, consent, collection, use, retention, disclosure, access and quality of personal information | Publish a privacy notice and honor access and deletion requests | Manual |
/06 · Type 1 vs Type 2
SOC 2 types and levels
SOC 2 comes in two report types. A Type 1 report tests whether controls are suitably designed at a single date. A Type 2 report tests design and operating effectiveness over an observation period of 3 to 12 months. Type 2 gives buyers stronger assurance, so most enterprise customers ask for it.
| Option | What it proves | Period covered | Typical timeline | Best when |
|---|---|---|---|---|
| SOC 2 Type 1 | Controls are suitably designed as of a specific date | One point in time | About 3 to 6 months | You need a report quickly, controls are new, or a deal needs interim assurance |
| SOC 2 Type 2 | Controls are suitably designed and operated effectively across the period | 3 to 12 months; the AICPA sets no minimum, and 3 months is the practical floor | About 6 to 12 months | Enterprise buyers require it, or your controls already run consistently |
Many teams start with Type 1 and move to Type 2 once controls have run for a few months. Others go straight to Type 2 to avoid paying for two examinations. Either path uses the same criteria and the same controls. Type 1 audit fees are commonly quoted at about $5,000 to $25,000 and Type 2 at about $7,000 to $50,000.
/07 · Process
How to get SOC 2 compliant
Getting SOC 2 compliant means scoping your system, closing control gaps, and passing a CPA firm's examination. For Type 1 that examination covers one date. For Type 2 your controls first run through an observation period of 3 to 12 months. Most teams complete the full Type 2 path in 6 to 12 months.
-
/01
Scope the system
Define the in-scope product, infrastructure and people, and choose the Trust Services Criteria. Security is required.
-
/02
Choose Type 1 or Type 2 and select a CPA firm
Decide the report type, engage a licensed CPA firm, and agree the audit period and fee.
-
/03
Run a readiness assessment
Compare your controls to CC1–CC9 and list gaps, including gaps in your development process.
-
/04
Remediate gaps
Write policies, enforce MFA, access reviews and change approvals, and set up logging, scanning and vendor reviews.
-
/05
Operate controls through the observation period
Type 2 only. Run every control on schedule and keep evidence for the full window.
-
/06
Complete auditor fieldwork
Provide populations and samples and answer auditor questions.
-
/07
Review and receive the report
Review the draft, sign management's assertion, and receive the final report.
-
/08
Renew every year
Start the next period so coverage has no gap.
/08 · Time and cost
SOC 2 timeline and effort
A first SOC 2 Type 1 report typically takes about 3 to 6 months, and a first Type 2 report about 6 to 12 months, though some sources report longer when remediation is heavy. The Type 2 observation period is the longest phase: 3 to 12 months, with 3 to 6 months common for a first report. The AICPA sets no minimum, but auditors treat 3 months as a practical floor.
| Phase | Typical duration |
|---|---|
| Preparation, readiness and remediation | 1–3 months (up to 4–6 months if gaps are large) |
| Observation period (Type 2 only) | 3–12 months |
| Auditor fieldwork | 2–6 weeks |
| Report drafting and issuance | 2–6 weeks |
| Total, first Type 1 report | About 3–6 months |
| Total, first Type 2 report | About 6–12 months |
What moves the timeline most
- Readiness on day one. Missing MFA, policies or logging add weeks of remediation before the observation period can start.
- Observation period length. 3, 6, 9 or 12 months is a choice you make with your auditor.
- Criteria in scope. Each optional category adds controls and evidence.
- System complexity. Multiple products, cloud accounts or deployment pipelines enlarge the populations auditors sample.
- Evidence process. Manual screenshots and spreadsheets slow fieldwork, while integrations speed it.
- Auditor availability. CPA firms book fieldwork windows in advance.
- Team capacity. Control owners need time each quarter for access reviews and testing.
Published estimates vary widely and come from vendors and audit firms, not the AICPA. Typical CPA audit fees are about $5,000 to $25,000 for Type 1 and $7,000 to $50,000 for Type 2, and all-in first-year Type 2 programs run about $30,000 to $150,000. Renewal audits typically cost about 70% to 90% of the first audit fee.
/09 · For engineering teams
SOC 2 and the software development lifecycle
SOC 2 does not prescribe a development methodology, but its change management and system operations criteria test how work moves from idea to production. Auditors sample pull requests, approvals, test results, deployments and incident records, so engineering teams produce much of the evidence.
| SDLC stage | What SOC 2 expects | Evidence it produces | How Carbon helps |
|---|---|---|---|
| Plan and design | Risks to the system are assessed (CC3), and design and security requirements are considered before building | Risk assessment, design review records, tickets linking requirements to work | Interviews the team against the control structure to document risk and design decisions, then maps the records to the criteria |
| Code and review | Changes are authorized, reviewed and tested before they are implemented (CC8.1) | Pull requests with reviewer approvals, branch protection settings, commit history | Connects to source control to collect approvals and flags changes that lack them |
| Build and test | Testing happens before release (CC8.1) | CI run results, test reports, security scan results | Pulls CI and scan results into the evidence set for each release |
| Release and deploy | Deployments are authorized and documented, and emergency changes follow a defined process (CC8.1) | Deployment logs, release approvals, emergency change records | Builds the population of production changes an auditor samples and links each to its approvals |
| Operate and monitor | Vulnerabilities are found and fixed, systems are monitored (CC7.1–CC7.2), and access is controlled and reviewed (CC6) | Vulnerability scan results and remediation, monitoring alerts, quarterly access reviews, MFA settings | Collects scan and access evidence on schedule and tracks open findings |
| Respond and recover | Incidents are evaluated, handled and reviewed (CC7.3–CC7.5); backups and recovery are tested if Availability is in scope (A1.2–A1.3) | Incident tickets with post-incident reviews, restore test results | Assists with incident records and test evidence |
| Vendors and dependencies | Third-party and vendor risk is assessed and monitored (CC9.2) | Vendor inventory, vendor risk reviews, vendors' SOC reports | Tracks the vendor list and review dates and prompts owners when reviews are due |
The 2022 revision of the points of focus added guidance on secure software development. Points of focus are guidance for designing and evaluating controls, not required controls, and the criteria themselves did not change.
/10 · What auditors sample
SOC 2 evidence and documentation
SOC 2 evidence is proof that each control operated, and for Type 2 that it operated throughout the observation period. Auditors first request populations, such as every new hire or deployment, then select samples to test. Records must span the full window, so evidence collection should start on day one.
| Evidence | Type | Carbon support |
|---|---|---|
| System description | Document | Assisted |
| Management's assertion | Signed document | Manual |
| Security policies and procedures | Document | Assisted |
| Risk assessment | Document | Assisted |
| User list, new-hire and leaver populations | System export | Automated |
| Provisioning and offboarding tickets (sampled) | Tickets | Automated |
| Quarterly access review records | Review record | Automated |
| MFA and SSO configuration | System setting | Automated |
| Change records: pull requests, approvals, deploy logs | Tickets and logs | Automated |
| Vulnerability scans and penetration test report | Report | Automated |
| Incident records and response test | Records | Assisted |
| Backup and disaster recovery test results | Test record | Assisted |
| Vendor inventory and vendor SOC reports | List and reports | Assisted |
| Security training and background-check records | HR records | Automated |
| Management and board meeting minutes | Document | Manual |
/11 · Exceptions
Common SOC 2 mistakes
The most common SOC 2 exceptions come from access management, change management and missing evidence, not from missing policies. Auditors sample across the whole period, so one skipped quarterly access review or one unapproved deployment becomes a documented exception.
-
/01
Starting the observation period too early
The window opens before controls work, so early failures are in scope.
Run a readiness assessment and close gaps first. -
/02
Late or missed access reviews and offboarding
Reviews and removals depend on someone remembering.
Schedule reviews on fixed dates and trigger removal from the HR system. -
/03
Changes deployed without approval
The merge or deploy happens before review is recorded.
Enforce approvals with branch protection and ticket links. -
/04
Evidence collected only at the end
Records are rebuilt at fieldwork, and gaps cannot be fixed.
Collect evidence continuously from day one. -
/05
System description that no longer matches reality
Tools or architecture change mid-period without an update.
Update the description whenever a significant change ships. -
/06
Adding criteria no customer needs
Teams add Privacy or Availability by default, which multiplies controls.
Start with Security, and add categories only when customers rely on them.
/12 · Comparison
SOC 2 vs related frameworks
SOC 2 is an attestation report on your controls, ISO 27001 is a certification of a management system, FedRAMP is a government authorization, and HIPAA is a law. Many controls carry over between them, so one program can support several, but meeting one does not satisfy another.
| Attribute | SOC 2 | ISO 27001 | FedRAMP | HIPAA |
|---|---|---|---|---|
| Purpose | Assurance that controls are designed, and for Type 2 operating, effectively | Certified information security management system | Authorization to sell cloud services to U.S. federal agencies | Legal protection of health information |
| Who it applies to | Service organizations | Any organization | Cloud service providers serving federal agencies | Covered entities and their business associates |
| Assessor | Licensed CPA firm | Accredited certification body | Independent third-party assessment organization (3PAO) | No formal certification; enforced by regulators |
| Renewal | Annual | Three-year certificate with annual surveillance audits | Annual assessment and continuous monitoring | Ongoing risk analysis and review |
| Control overlap with SOC 2 | — | High: published estimates range from about 40% to over 90% depending on method | Partial: NIST SP 800-53 is more prescriptive; the AICPA publishes a crosswalk | Partial: shared safeguards, different legal duties |
/13 · Readiness
SOC 2 checklist
Use this checklist to check SOC 2 readiness for your software development team before the observation period starts. Every item maps to one or more Trust Services Criteria and produces evidence an auditor can sample.
- Define the in-scope system, its boundaries and its services.
- Choose the Trust Services Criteria: Security, plus any optional category customers require.
- Decide on Type 1, Type 2, or Type 1 first, and engage a licensed CPA firm.
- Run a readiness assessment against CC1 to CC9.
- Approve and communicate information security policies.
- Complete and document a risk assessment.
- Enforce MFA or SSO and least-privilege access to code, cloud and production.
- Schedule quarterly access reviews and same-day offboarding.
- Require pull request approval, review and passing tests before every production change.
- Record each deployment and define an emergency change procedure.
- Turn on logging, monitoring and vulnerability scanning, and commission a penetration test.
- Test your incident response plan and your backup and recovery process.
- Inventory critical vendors and open-source dependencies, and collect vendor SOC reports.
- Run security awareness training and background checks for staff.
- Draft the system description and management's assertion, and start evidence collection on day one of the observation period.
/14 · Questions
SOC 2 FAQ
What is SOC 2?
SOC 2 is an independent audit report from a licensed CPA firm. It tests whether a service organization's controls meet the AICPA Trust Services Criteria, either at one date (Type 1) or over a review period of usually 3 to 12 months (Type 2). Customers use the report to judge how a vendor protects their data.
Who needs SOC 2?
Any service organization that stores, processes or transmits customer data can pursue SOC 2, and most who do are SaaS, cloud, data and managed-service providers. It is usually driven by customers: enterprise buyers, regulated companies and partners ask for the report during vendor security reviews, so the software teams that build the product supply much of the evidence.
Is SOC 2 mandatory or voluntary?
SOC 2 is voluntary. No law or regulator requires it. In practice it is often a commercial requirement, because enterprise customers and contracts ask for a current report before they buy or renew. The AICPA publishes the criteria, but each service organization decides whether to be examined.
How long does SOC 2 take?
A first SOC 2 Type 1 report typically takes about 3 to 6 months. A first Type 2 report takes about 6 to 12 months, covering 1 to 3 months of preparation, an observation period of 3 to 12 months, 2 to 6 weeks of fieldwork, and 2 to 6 weeks to issue the report. Heavy remediation can push it past 12 months.
What does SOC 2 cost?
Published estimates vary widely. Vendors commonly cite $5,000 to $25,000 for a Type 1 audit fee and $7,000 to $50,000 for Type 2, with $30,000 to $150,000 for a full first-year Type 2 program including tooling, readiness and remediation. Renewal audits typically cost about 70% to 90% of the first audit fee. Treat these as vendor-reported ranges, not quotes.
How often do you renew SOC 2?
SOC 2 is renewed annually. A report covers a past date or period, and customers generally expect a new report every 12 months. Many organizations choose 12-month observation periods after their first Type 2 report so coverage has no gaps. If a gap occurs, customers may ask for a bridge letter from management.
What is the difference between SOC 2 Type 1 and Type 2?
A SOC 2 Type 1 report tests whether controls are suitably designed at a single point in time. A Type 2 report tests design and operating effectiveness across an observation period of 3 to 12 months. Type 2 gives buyers stronger assurance, which is why most enterprise customers ask for it.
What evidence do auditors ask for in a SOC 2 audit?
Auditors request populations, then samples. Typical evidence includes policies, the system description, access and offboarding records, quarterly access reviews, MFA settings, change tickets with approvals, vulnerability scans, incident records, vendor reviews, and training and background-check records. For Type 2 it must be drawn from across the whole observation period rather than only its final weeks.
How does SOC 2 apply to software development?
SOC 2 has no development methodology, but its change management and system operations criteria test how code reaches production. Auditors sample pull requests, reviewer approvals, test results, deployment records, vulnerability remediation and incident handling. The 2022 revised points of focus also added guidance on secure software development, which serves as guidance rather than required controls.
Can SOC 2 be automated?
Partly. Software can collect access lists, configuration settings, change records and scan results continuously, which covers much of the evidence an audit samples. It cannot replace the CPA firm's examination, management's decisions, or people-based controls such as risk acceptance and governance. Automation reduces missed evidence, a common cause of exceptions.
How does Carbon support SOC 2 teams?
Carbon connects to the tools software teams already use, interviews people against auditor-tested control structures, and maps evidence to the criteria it supports. It automates or assists with 10 of 13 control areas, but it does not perform the examination. Only a licensed CPA firm can issue a SOC 2 report.
Where is the official SOC 2 documentation?
The AICPA publishes the 2017 Trust Services Criteria with revised points of focus (2022) as TSP Section 100. The criteria document is a free download that requires registration on the AICPA and CIMA website. The AICPA also publishes the SOC 2 description criteria and an attestation guide for auditors.
Can I skip Type 1 and go straight to Type 2?
Yes. Nothing requires a Type 1 report first. Some teams start with Type 1 to get a report sooner and learn the process, then move to Type 2. Others begin their Type 2 observation period right after readiness work to avoid paying for two examinations. Both paths use the same criteria and controls.
How long is a SOC 2 Type 2 observation period?
The observation period is the span of time a Type 2 report covers, and auditors test controls across it. The AICPA sets no minimum, but 3 months is the practical floor and 6 or 12 months are common. First reports often use 3 to 6 months; mature programs tend to use 12.
Which Trust Services Criteria should I include?
Security is required in every SOC 2 report. Add availability, processing integrity, confidentiality or privacy only when your customers rely on those commitments. More criteria means more controls, more evidence and a higher audit fee, so many teams start with Security alone or Security plus one addition.
/15 · Version history
What changed in SOC 2
-
Revised points of focus
The AICPA revised the points of focus to address newer technology, threats and secure software development, without changing any criterion. Points of focus are guidance, not required controls.
-
2017 Trust Services Criteria
The criteria were reorganized and aligned with the COSO 2013 internal control framework, and points of focus were added to each criterion.
-
SOC 2 introduced
The AICPA introduced SOC 2 reporting as a successor to SAS 70, built for cloud and technology service organizations.
/16 · References
Sources and further reading
- 2017 Trust Services Criteria (with revised points of focus, 2022), AICPA & CIMA. Accessed Nov 15, 2026.
- AICPA revises guidance on applying its Trust Services Criteria and SOC 2 Description Criteria (To the Point 2022-13), EY. Accessed Nov 15, 2026.
- Everything You Need to Know About the Revised Points of Focus for the SOC 2 Trust Services Criteria, Drata. Accessed Nov 15, 2026.
- 2024 SOC 2 updates and considerations, Forvis Mazars. Accessed Nov 15, 2026.
- SOC 2 compliance timeline: How long does it really take?, Scrut. Accessed Nov 15, 2026.
- SOC 2 Trust Services Criteria, TCSA. Accessed Nov 15, 2026.
- SOC 2 opinions and exceptions, TCSA. Accessed Nov 15, 2026.
- SOC 2 Certification Cost in 2026, Bright Defense. Accessed Nov 15, 2026.
- SOC 2 audit cost in 2026, soc2auditors.org. Accessed Nov 15, 2026.
- SOC 2 Type 2 population and sampling guide, Strike Graph. Accessed Nov 15, 2026.
- Most Common Exceptions Found During a SOC 2 Audit, Bastion. Accessed Nov 15, 2026.
- SOC 2: Service Organization Control 2, arc42 Quality Model. Accessed Nov 15, 2026.
Carbon by HardStack.AI
Building software under SOC 2?
See how Carbon turns your SDLC into SOC 2 evidence.