A snapshot at one date.
Assesses control design at a specified date. It can be an interim step when customers need evidence before a Type II period is complete.
The date is agreed with the practitioner.SOC 2 is an independent report on how a service organisation protects customer systems and information. Explore your first timeline, understand what the report means, and find your next step.
From readiness to report
Your indicative Type II delivery
Share your organisation’s details for a proposal based on your scope, readiness and reporting needs.
A tailored response, based on your organisation. No published price.
A planning scenario, not a promised audit date. This model assumes a three-month Type II review period and one month for final review/reporting, plus one preparation month where needed. Readiness, available evidence, your customer’s requirements and the independent practitioner determine the actual schedule. A GRC tool does not automatically shorten the audit.
Your organisation. Your scope.
Tell us who you are and what needs to be covered. Your planning scenario is shown below. Include any additional requirements in your request.
Open the request form in a new tabSOC 2 helps service organisations explain how they protect the systems and information their customers rely on.
An independent practitioner examines the system and controls within an agreed scope. The resulting report helps customers assess the risks of working with you.
For a SaaS company, cloud provider or outsourced service business, that evidence can support procurement and supplier reviews. Its value comes from what the report covers and what the examination found.
Evidence for a decision. No guarantee of perfect security.
SOC 2 uses the AICPA’s Trust Services Criteria. Your risks and service commitments shape the controls within the system being examined. It is not a universal checklist or a software badge.
Security is the foundation of a SOC 2 examination. Controls address risks such as inappropriate access, unauthorised changes and security incidents.
For example: access approvals, multi-factor authentication, monitoring and incident response.
Additional categories depend on your service commitments and the agreed scope.
Framework reference: AICPA — SOC suite of services ↗
Both report types address the system description and the design of controls. Type II also examines whether the controls operated effectively throughout a specified period.
Assesses control design at a specified date. It can be an interim step when customers need evidence before a Type II period is complete.
The date is agreed with the practitioner.Also examines operating effectiveness across the reporting period. Evidence must demonstrate that controls worked during that period.
The period depends on your requirements and engagement.| Approach | Primary focus | Typical output |
|---|---|---|
| SOC 2 | Controls relevant to the applicable Trust Services Criteria | Independent assurance report |
| ISO/IEC 27001 | An information security management system | Certification, if pursued successfully |
| SOC 1 / ISAE 3402 | Controls relevant to customers’ financial reporting | Independent assurance report under the relevant standard |
These address different assurance needs. Existing controls can overlap; one report or certificate does not automatically replace another. ISO reference ↗
You do not need every answer today. You need to know what the customer expects, which service is in scope and who owns the work.
Ask your customer which report type, system, criteria and period they need. Check their deadline before committing to one.
Identify your services, data, people, suppliers and controls. A readiness review helps establish what needs to change and which evidence is missing.
Put controls into operation and retain evidence. A GRC tool can help organise the work; it does not replace accountability or the independent examination.
Confirm the scope, reporting route and timing with a qualified practitioner. Review the resulting opinion, tests and any exceptions before sharing the report.
A UK service can serve customers anywhere. Those customers still need to understand the systems, controls and assurance behind it.
SOC 2 offers a recognised reporting approach for those conversations. Acceptance depends on the buyer’s requirements, the practitioner and the report’s scope. It is not a worldwide licence or a substitute for local obligations.
This index is a discovery starting point: find organisations and explore their stated reporting information, then request current evidence directly.
Explore the organisation index ↗A directory entry is not validation of a report, accreditation or proof of current compliance. Check the original report, dates, scope and opinion.
About this platform ↗Start with the question you have now. Each answer explains the decision it affects.
Understand the report before you buy a tool, promise a date or agree an audit scope.
Explore your timeline ↑SOC 2 is an independent examination of a service organisation’s system and controls against applicable Trust Services Criteria. The report describes the scope and includes the practitioner’s opinion. It helps customers evaluate the service provider.
The formal output is an assurance report, rather than a general security certificate. People often search for “SOC 2 certification”, but the report’s scope, type, period, opinion and exceptions are what buyers need to assess.
Organisations that provide services involving customer systems or data may be asked for one, particularly in SaaS, cloud and outsourced technology. Start with customer and contractual requirements; company size alone does not determine the need.
SOC 2 is not a general statutory requirement for every UK business. Customers may make it a contractual or procurement condition. It does not by itself establish compliance with UK GDPR or other applicable obligations.
Security, availability, processing integrity, confidentiality and privacy. Security forms the foundation. Additional categories are selected to reflect the service commitments and system requirements within scope.
Preparation, the Type II reporting period and final examination work all affect delivery. A ready organisation and one with significant gaps will need different plans. The calculator offers an illustrative scenario, not an agreed audit date.
The proposal depends on scope, complexity, locations, report type, categories, readiness and available evidence. Separate preparation, software and independent examination costs when comparing proposals. Use the calculator first, then share organisation details to request tailored pricing.
Yes. A focused service and manageable scope can make the work practical for a small organisation. You still need accountable owners, appropriate controls and sufficient evidence. Check that customer demand justifies the effort.
No. Type I can provide an earlier snapshot, but it is not a universal prerequisite. Choose the route with your practitioner and customer, considering deadlines, readiness and the required reporting period.
Examples include access reviews, change records, incident handling, staff onboarding, risk assessments and supplier oversight. The evidence required depends on your system and controls. For Type II, evidence needs to support operation over the agreed period.
No. A tool can help manage controls, gather evidence and track tasks. Your team remains responsible for the system and controls. A qualified independent practitioner performs the examination and issues the opinion.
No. ISO/IEC 27001 addresses an information security management system; SOC 2 examines a defined system and controls against applicable Trust Services Criteria. Their work can overlap. Ask which output your customer actually needs.
SOC 1 addresses controls relevant to user entities’ financial reporting. SOC 2 focuses on applicable Trust Services Criteria. ISAE 3402 also addresses financial-reporting-related service organisation controls; it is not interchangeable with SOC 2.
A licensed, independent CPA performs a SOC 2 examination under the AICPA Attestation Standards. Check credentials, relevant experience and independence. Readiness consultants and software providers do not automatically have authority to issue the report.
A report covers a specified date or period. It is not a perpetual statement about current controls. Customers often request updated reports; agree a reporting cadence and address any gap between the covered period and the review date.
SOC 2 reports are generally intended for specified, informed users and may be shared through a controlled process. Ask the organisation for its current report and access conditions. SOC 3 is a separate general-use reporting option.
No. A listing is a discovery aid. Request the actual report and assess its scope, dates, practitioner, opinion and exceptions. Absence from this directory does not prove that an organisation lacks a report.
SOC stands for System and Organization Controls, the AICPA’s official US name. SOC 2 focuses on controls relevant to security, availability, processing integrity, confidentiality and privacy. This UK guide uses British English; the official framework name retains its original spelling.
No. SOC 2 evaluates controls within an agreed system and scope. UK GDPR creates separate data protection obligations. A report can support supplier due diligence, but you must still assess lawful processing, contracts, international transfers and other applicable requirements.
Confirm your customer’s request and the service in scope. Identify a responsible owner, review readiness and discuss the reporting route with a practitioner. Use the calculator above to explore a first timeline before requesting a tailored proposal.
This guide explains the reporting concepts; your engagement’s criteria and professional standards govern the examination.
AICPA: SOC reporting resources ↗AICPA: SOC 2 description criteria ↗ISO: ISO/IEC 27001 ↗Updated 15 November 2026 · SOC 2® is an AICPA trademark.