An IT company has successfully achieved ISO 27001 certification, implemented security policies and established access management procedures. However, when negotiating a new contract, the client requests a SOC 2 report. Does the company need to go through the entire process again from scratch? In most cases, the existing system allows much of the work already completed to be reused. The key is to clarify the client's requirements first and identify what additional evidence is needed.
Quick Answers to Key Questions (FAQ)
Does ISO 27001 Certification Automatically Replace a SOC 2 Report?
No, it does not. ISO 27001 establishes requirements for an organisation-wide Information Security Management System (ISMS). SOC 2 is an independent auditor's report on the controls of a specific system or service, assessed against AICPA Trust Services Criteria and issued by a licensed CPA firm. For clients, the scope of the service, applicable criteria categories, report type and auditor's opinion are crucial. Therefore, ISO 27001 certification does not automatically replace a SOC 2 report.
Is SOC 2 Type I Required Before Type II?
No, completing Type I before Type II is not mandatory. Type I assesses the system description and the suitability of control design as at a specific date, whereas Type II also examines the operating effectiveness of those controls over a defined period (typically six months or longer). If a client requires Type II, a Type I report will only be acceptable as an interim solution with the client's written agreement.
How Much of the Work Completed for ISO 27001 Can Be Reused?
An existing ISO 27001 management system may already address up to 60–70% of SOC 2 requirements. Risk registers, security policies, access management procedures, incident response processes and change management procedures provide a strong foundation. However, the key challenge is to provide not only the policies themselves but also accumulated evidence (logs, tickets and approvals) demonstrating that the controls have actually operated throughout the period under examination.
ISO 27001 vs SOC 2: Key Differences for Businesses
Parameter | ISO 27001 | SOC 2 |
Document Type | International management system standard (certification) | Auditor's report on controls assessed against AICPA criteria |
Audit Focus | Information Security Management System (ISMS), risk management and processes | A specific service, product or cloud infrastructure |
Who Conducts the Audit | Certification Body | Independent, licensed CPA firm |
Outcome | Certificate of conformity with the standard | Detailed audit report containing the auditor's opinion |
Important point: For example, an ISO 27001 certificate may cover software development, while the client requires assurance relating to the operation of a cloud platform (SaaS). In this case, the issue also lies in a mismatch between the audit scopes. |
What to Clarify with the Client Before Commissioning an Audit
Before commissioning an audit or engaging consultants, ask the client's security team to clarify the following requirements in writing:
- Report type: Which report is required — Type I (as at a specific date) or Type II (covering a defined period)?
- Audit scope: Which product, infrastructure and legal entity must be included in the assessment?
- Trust Services Criteria categories: Which categories need to be included (Security is mandatory, while Availability, Confidentiality, Processing Integrity and Privacy are included as required)
- Deadlines and reporting period: By what date is the report required, and what audit period must it cover (for Type II)
- Temporary alternatives: Would the client temporarily accept ISO 27001 certification, a security questionnaire (such as CAIQ or SIG) and an approved SOC 2 readiness plan
Which Documents and Evidence Can Be Reused from ISO 27001
The transition from ISO 27001 to SOC 2 should begin by mapping existing controls against the applicable SOC 2 criteria. The following can provide a solid foundation:
- Core documentation: Risk registers, security policies, access management procedures, incident response procedures, supplier assessments and change management procedures.
- Existing evidence: Access provisioning and revocation requests, access review results, release approvals, backup restoration test reports and employee training records.
Practical advice: A useful working tool is a control mapping table: [SOC 2 Criterion] → [Existing Control] → [Control Owner] → [Frequency] → [Evidence] → [Outstanding Actions]. This helps assess the amount of additional preparation required and avoids unnecessarily rewriting procedures that are already working effectively. |
What Else Needs to Be Reviewed and Improved
However, having a policy in place does not necessarily prove that it is being followed. Documents and records must relate to the service under examination, be up to date and cover the required period:
- System Description: Check whether the system, data flows, infrastructure, third-party service providers and allocation of responsibilities are accurately described.
- Alignment Between Commitments and Actual Practices: Compare public commitments made to clients with the controls actually in place. For example, is the stated recovery procedure supported by documented test results
- Continuous Evidence Collection: Common gaps often relate to the regular execution of procedures and the retention of supporting evidence. Access reviews may have been carried out, but without records identifying the reviewer, the date and the decisions made. Evidence must not be created retrospectively to misrepresent past activities. Instead, the process for recording and documenting actions should be improved going forward.
SOC 2 Preparation: Kazakhstan and the Wider Region
For companies in Kazakhstan, Uzbekistan, Georgia and Kyrgyzstan, it is advisable to start by understanding the client's specific requirements.
A useful first step is to conduct a Gap Analysis of existing controls. When contacting ISO Cert Hub, the objective can be defined as identifying what is already covered by the existing management system, what supporting evidence is missing and what improvements are required.
The outcome should be a clear action plan with assigned responsibilities, deadlines and an agreed audit scope. This allows the investment already made in ISO 27001 to serve as a foundation for further preparation, while giving management a clear understanding of the work involved before making commitments to the client.
