SOC 2 Readiness: Trust Services Criteria, Type 1 and Type 2

How SOC 2 readiness is planned in practice: report structure, Trust Services Criteria, the Type 1–Type 2 difference, overlap with ISO 27001, the control matrix and the observation period.
Technical summary
Technology
AICPA SOC 2, Trust Services Criteria (TSC), SSAE 18, ISO/IEC 27001:2022, ITGC
Topic
The SOC 2 reporting framework and readiness process
Level
Intermediate–advanced
Prerequisites
  • The service and system boundaries defined
  • Basic IT general controls (access, change, operations) in operation
In this article7 sections

When selling software or managed services to a US-based customer, the same question comes up at some point in the purchasing process: “Do you have a SOC 2 report?” An ISO 27001 certified company often reads this as “one more certificate” and underestimates the preparation. That’s where the mistake starts. SOC 2’s structure, evidence expectations and timeline are different. Below we explain the report structure, the Trust Services Criteria categories, the difference between Type 1 and Type 2, and how a company coming from ISO 27001 should plan its preparation.

What is SOC 2, and who asks for it?

SOC 2 is an assurance report defined by the American Institute of Certified Public Accountants (AICPA). It contains an independent auditor’s opinion that a service organization’s controls over a specific system are suitably designed against the Trust Services Criteria and, in Type 2, also operate effectively. The audit is carried out by a licensed CPA firm under the attestation standards of SSAE 18.

The request usually comes from enterprise customers of SaaS providers, companies buying data center or managed services, and organizations working with suppliers that process customer data. The report has restricted distribution; it’s usually shared with the customer under a confidentiality agreement.

A SOC 2 report typically consists of these sections:

  • Independent auditor’s report: The auditor’s opinion; the reason if it’s a qualified opinion.
  • Management assertion: Company management’s assertion about the accuracy of the system description and the controls.
  • System description: The service, infrastructure, software, people, processes and data; subservice organizations and complementary user entity controls (CUEC).
  • Criteria, controls and test results: Each control, the test the auditor applied and the result; exceptions, if any.

Trust Services Criteria categories

The Trust Services Criteria consist of five categories. Security is mandatory in every report. The others are a scoping decision.

Category Focus When is it included in scope?
Security (common criteria) Protection against unauthorized access and damage Always
Availability Committed availability If there’s an SLA or availability commitment
Processing Integrity Processing being complete, accurate and timely If the service performs processing/calculation on behalf of the customer
Confidentiality Protection of information designated as confidential If there’s a contractual confidentiality commitment
Privacy Collection, use, retention and disposal of personal data If there’s a personal data processing commitment, especially where data is collected directly from individuals

The common criteria of the Security category are grouped as CC1–CC9: control environment (CC1), communication and information (CC2), risk assessment (CC3), monitoring activities (CC4), control activities (CC5), logical and physical access (CC6), system operations (CC7), change management (CC8) and risk mitigation (CC9). The first five groups follow the components of the COSO internal control framework. That’s why SOC 2 puts more weight on governance and the control environment than ISO 27001; technical teams struggle most with CC1 and CC2 evidence during preparation.

The difference between Type 1 and Type 2

Feature Type 1 Type 2
Time covered A specific date A period (observation period)
Subject of the opinion Suitable design of controls Design and operating effectiveness throughout the period
Test method Walkthrough, design review Operating test with a sample from the period
Value to customers Initial assurance Usually the report expected

The standard doesn’t impose a single length for the Type 2 observation period. In practice, a shorter period is common for the first report and a twelve-month period in later years; set the length together with the audit firm and customer expectations. If there’s a gap between the report’s end date and the customer’s request date, company management, not the audit firm, issues a “bridge letter” stating that no significant changes occurred during that interval.

The logic of operating effectiveness testing is explained in detail in the control effectiveness testing guide. In Type 2 preparation, running the same test in-house beforehand is the cheapest way to see early the exceptions the auditor will find.

Overlap table with ISO 27001

Most of an ISO 27001 certified company’s controls are reused in SOC 2. The difference lies in how controls are defined and how they’re evidenced.

SOC 2 area ISO/IEC 27001:2022 equivalent Difference to watch
CC1 Control environment Clause 5, Annex A 6.1–6.4 Board oversight and ethical rules need more explicit evidence
CC3 Risk assessment Clauses 6.1, 8.2 Fraud risk must be assessed separately
CC6 Access Annex A 5.15–5.18, 8.2, 8.5 Each joiner/leaver and review is tested by sampling
CC7 Operations and incidents Annex A 5.24–5.28, 8.15, 8.16 Records showing monitoring alerts were handled are expected
CC8 Change Annex A 8.32 Approval and test evidence is sought for every change
CC9 Risk mitigation Annex A 5.19–5.22, 5.30 SOC reports of subservice organizations must be reviewed

The practical difference: an ISO 27001 certification audit verifies with examples that the management system works; SOC 2 Type 2 takes a defined sample for each control and reports exceptions one by one. That’s why control definitions in the SoA usually aren’t precise enough for SOC 2. Where the Statement of Applicability says “access rights are reviewed periodically”, a SOC 2 control must include frequency, owner and timeframe, such as “production database access is reviewed every three months by the system owner, and permissions to be removed are removed within ten working days”. The word “periodically” can’t be tested.

Readiness assessment steps

  1. System and boundary definition: Which service does the report cover? Which applications, databases, cloud accounts, locations and teams are inside? Limiting scope to the service provided to the customer is the first decision that sets the workload. A mistake you may come across is opening the scope as “the whole company” and then drowning during the observation period.
  2. Category selection: In addition to Security, decide the other categories based on commitments in contracts.
  3. Subservice organizations: For parties such as the cloud provider, data center and identity provider, decide on the carve-out or inclusive method. Carve-out is common; in that case, the annual review of the provider’s own SOC report becomes a control.
  4. Control matrix: Write one or more controls for each criterion: control statement, owner, frequency, automated/manual, evidence. The evidence matrix method is used directly here.
  5. Gap analysis: For each control in the matrix, answer two questions: is there a design, and does it produce evidence? For access, change and operations controls, the ITGC structure is a good starting skeleton.
  6. Remediation: Set up missing controls before the observation period starts and run at least one cycle.
  7. Complementary user entity controls: List what the customer must do on its own side (for example managing its own users’ access); these go in the system description.

Observation period and evidence collection

From the moment the observation period starts, every run of every control produces evidence and can’t be fixed afterwards. A missed quarterly access review shows up as an exception in the report. There’s no going back. That’s why, before the period starts, this preparation for IT security compliance must be complete:

  • A schedule and reminder for every periodic control (ticketing system or calendar task).
  • A central repository for evidence, with restricted access and version history.
  • A written description of how population lists (joiners, leavers, changes, incidents) are pulled from systems.
  • A monthly internal check: the second line looks at whether that month’s evidence is complete.
  • Assessing the scope impact of system changes made during the period (a new cloud account, a new application).

At the end of the period, the auditor asks for populations, selects samples and requests evidence. If evidence was collected regularly throughout the period, this stage is short; if evidence is being searched for retrospectively, it takes weeks and gaps come out then. If exceptions turn up, management’s response can be added to the report. This response should clearly explain the root cause and the action taken; that’s the only way the customer interprets the exception in the report correctly.

For preparing the control matrix and system description, our SOC 2 readiness and IT control documentation work, and for setting up access, change and operations controls, our IT general controls (ITGC) work can be the starting point.

Frequently asked questions

Is SOC 2 a certification?

No. SOC 2 is an assurance report issued by an independent audit firm (a CPA firm licensed in the US) on the controls of a specific system. It isn’t a pass/fail certificate; the opinion, exceptions and test results are in the report, and readers assess them for themselves.

Can you start directly with Type 2?

Yes. If controls are already mature and producing evidence, it’s possible to skip the Type 1 step and start the observation period. If there’s uncertainty in control design, a Type 1 or at least a formal readiness assessment prevents exceptions piling up during the observation period.

Does an ISO 27001 certificate replace SOC 2?

It depends on the customer. Some customers accept ISO 27001; others specifically ask for a SOC 2 Type 2 report. The two frameworks overlap to a large extent; but because SOC 2 reports test results control by control, it’s a different kind of assurance the customer can present to its own auditor.

Which Trust Services Criteria categories should we choose?

Security (the common criteria) is mandatory in every SOC 2 report. The others are chosen based on customer commitments: Availability if there’s an availability commitment via an SLA, Confidentiality if the confidentiality of customer data is assured by contract, and so on. Including a category you haven’t committed to increases workload for nothing.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles