One Control Library, Two Frameworks: The Series A Approach to ISO 27001 and SOC 2



Most Series A SaaS engineering teams need to demonstrate strong information security practices to customers, partners, and procurement teams. When they pursue ISO 27001 and SOC 2 separately, they may end up creating similar policies, collecting the same types of evidence, and assigning different owners to related controls.
A more efficient approach is to build a single, structured control library and map its evidence to the requirements of both frameworks.
At Folksoft, we approach compliance as an engineering discipline and act as a compliance co-founder for growing SaaS startups. This guide explains how to coordinate ISO 27001 and SOC 2, identify shared evidence, manage framework-specific requirements, and reduce unnecessary duplication.
Why ISO 27001 Can Support European Enterprise Sales
ISO 27001:2022 is an internationally recognised standard for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS).
For SaaS companies selling to European enterprises, ISO 27001 certification can provide useful evidence of a structured approach to information security. Some enterprise procurement teams request it as part of their supplier security assessments.
However, ISO 27001 certification is not a universal legal requirement for every SaaS company operating in Europe. Whether a buyer requests certification depends on its procurement policies, industry, risk assessment, and contractual requirements.
SOC 2 is a separate assurance framework based on the AICPA Trust Services Criteria. A SOC 2 examination is performed by an independent licensed CPA, while ISO 27001 certification is issued by a certification body following the relevant certification audit process.
These reports and certifications serve different purposes. A SOC 2 report may help demonstrate how controls address selected Trust Services Criteria, but it does not automatically replace ISO 27001 certification when a customer specifically requests an ISO certificate.
If European enterprise sales are part of your growth strategy, assess whether your target customers expect ISO 27001, SOC 2, or both. Build your compliance roadmap around actual customer requirements rather than assuming that one framework will satisfy every buyer.
Understanding the Control Overlap
ISO 27001:2022 Annex A contains 93 reference controls across four categories:
- Organisational controls: 37
- People controls: 8
- Physical controls: 14
- Technological controls: 34
SOC 2 uses five Trust Services Criteria categories:
- Security
- Availability
- Processing Integrity
- Confidentiality
- Privacy
The Security category is commonly included in SOC 2 examinations. Other categories are selected according to the organisation's services, commitments, and customer requirements.
The frameworks address several related information security areas, including:
Access management: Both frameworks address access-related risks. Evidence such as access policies, user access records, privileged access reviews, and authentication configurations may support relevant requirements under both frameworks.
Incident management: Incident response policies, incident records, escalation procedures, and post-incident reviews may provide useful evidence for both frameworks.
Logging and monitoring: System logs, monitoring configurations, alert records, and investigation records may support relevant requirements under both frameworks.
For example, consider a SaaS company that conducts quarterly user access reviews. The company maintains a list of active users, records the systems and permissions assigned to them, and obtains approval from the relevant managers. If inappropriate access is identified, the company records the corrective action and retains evidence that access was removed or updated.
The same access review records may support relevant access management requirements under ISO 27001 and applicable Security criteria under SOC 2. However, the company must map the evidence separately to the applicable requirements of each framework and confirm that it meets their respective expectations.
The requirements are not identical. There is no universally applicable overlap percentage between the two frameworks. The actual mapping depends on the company's ISMS scope, risk assessment, selected Annex A controls, and the Trust Services Criteria included in its SOC 2 examination.

Building One Control Library for Two Frameworks
Instead of managing separate evidence libraries, create one central control library that maps applicable requirements across both frameworks.
Each shared control should have:
- One clearly assigned control owner.
- A defined evidence source and collection process.
- A review schedule appropriate to the control.
- Mappings to the relevant ISO 27001 and SOC 2 requirements.
Begin with a gap analysis to identify three groups:
- Shared controls: Controls for which the same evidence may support requirements under both frameworks.
- ISO 27001-specific requirements: ISMS requirements and applicable controls that need additional attention.
- SOC 2-specific requirements: Requirements arising from the selected Trust Services Criteria that are not fully addressed by the ISO 27001 control implementation.
Define the ISMS scope carefully. It should reflect the organisation's information, systems, locations, services, and relevant business processes. A narrower scope is not automatically better; the scope must be appropriate to the organisation and its risks.
Once the mapping is complete, assign owners, document evidence requirements, and establish collection schedules. Where technically possible, automate evidence collection from cloud infrastructure, identity providers, ticketing systems, and change-management tools.
Automation can make evidence collection more consistent. However, it does not replace the need to review whether the collected evidence demonstrates that a control is operating effectively.
Coordinating the Audit Timelines
Pursuing both frameworks concurrently can help reduce repetitive evidence collection.
Before planning the SOC 2 timeline, understand the difference between its two report types:
- SOC 2 Type I: Evaluates the design of controls and whether they are suitably implemented as of a specific date.
- SOC 2 Type II: Evaluates both the design of controls and their operating effectiveness over a defined period.
For a Type II examination, the organisation must maintain relevant evidence throughout the examination period to demonstrate that controls operated effectively. A Type I examination focuses on the controls at a particular point in time rather than their operating effectiveness over an extended period.
For example, a company can begin defining its ISMS while preparing for a SOC 2 Type II observation period. It can identify shared controls, assign owners, and establish evidence collection processes before the observation period begins.
Evidence generated during this period may also support relevant ISO 27001 requirements, provided that it meets the applicable requirements and falls within the approved ISMS scope.
Before coordinating the timelines, establish the following:
- A unified control library with framework mappings.
- An approved ISMS scope.
- Clear ownership of shared controls.
- Evidence collection and review schedules.
- Separate readiness assessments for each framework.
- Audit plans coordinated with the relevant independent licensed CPA firm and certification body.
Concurrent preparation does not guarantee simultaneous completion. Audit schedules, organisational readiness, scope, control maturity, and the requirements of each assessment will affect the overall timeline.
Selecting the Right Compliance Partner
For a growing SaaS company, the right compliance partner should understand both frameworks and the practical challenges of implementing them with a small engineering team.
Evaluate potential partners based on the following criteria:
- Control mapping: Can they map applicable ISO 27001 controls to the selected SOC 2 Trust Services Criteria?
- Evidence collection: Can they help establish consistent evidence collection and review processes?
- Technical understanding: Can they work with your cloud infrastructure, identity systems, and development processes?
- Policy guidance: Can they help develop policies that reflect your actual operations?
- Audit coordination: Can they help you prepare for ISO 27001 certification audits and SOC 2 examinations without confusing the two processes?
- Scope management: Can they help define and maintain an appropriate ISMS scope?

At Folksoft, we act as a compliance co-founder for growing SaaS startups, providing hands-on guidance throughout their compliance journey. Each engagement includes a dedicated GRC analyst who helps with control mapping, evidence collection, policy development, and compliance preparation.
We also work with independent licensed CPA firms for SOC 2 examinations, helping companies prepare for independent assessments. For ISO 27001, we guide teams through the certification preparation process and help coordinate the necessary activities with the relevant certification body.
This approach helps engineering teams manage multiple compliance requirements with dedicated support while reducing unnecessary duplication.
Common Mistakes That Create Duplicate Work
1. Defining an Unclear ISMS Scope
An unclear or unnecessarily broad scope can increase implementation effort and create additional evidence requirements. Define the scope based on the organisation's services, information assets, systems, locations, and risks.
2. Treating Policies as Proof of Implementation
A written policy does not automatically demonstrate that a control is operating effectively. Auditors may also require records showing that the organisation follows the documented process.
For example, an access review policy should be supported by completed access reviews and evidence of any necessary follow-up actions.
3. Assigning Separate Owners to Shared Controls
When related controls have different owners across the two programmes, responsibilities can become fragmented. Assign clear ownership and coordinate responsibilities for shared controls.
4. Collecting Evidence Only Before Audits
Manually collecting evidence at audit deadlines can be time-consuming and error-prone. Establish regular collection and review processes so that relevant evidence is available when required.
Frequently Asked Questions
Can we pursue ISO 27001 and SOC 2 simultaneously?
Yes. Organisations can prepare for both frameworks concurrently. A shared control library can help reduce duplicate work, but the requirements of each framework must still be assessed separately.
How long does ISO 27001 certification take for a Series A SaaS company?
The timeline depends on the organisation's existing security practices, ISMS scope, control maturity, internal resources, and certification body availability.
Six to twelve months can be used as an indicative planning estimate for some organisations, but it is not a guaranteed certification timeline. Companies with mature controls may progress faster, while organisations with significant gaps or broader scopes may require more time.
Which requirements are not fully covered by both frameworks?
The frameworks have different structures and purposes. ISO 27001 includes ISMS requirements covering areas such as organisational context, risk assessment, management review, internal audits, and continual improvement. SOC 2 focuses on the applicable Trust Services Criteria selected for the examination.
A framework mapping and gap analysis should identify requirements that need separate treatment based on the organisation's specific scope.

Build One Coordinated Compliance Programme
Running ISO 27001 and SOC 2 as separate projects can lead to repeated evidence collection and fragmented ownership. A coordinated programme can help your team manage shared controls more efficiently while addressing the requirements unique to each framework.
Start with a gap analysis, define the ISMS scope, map the relevant controls, and establish clear evidence ownership before beginning the audit preparation process.
At Folksoft, we help growing SaaS startups manage SOC 2 and ISO 27001 requirements through dedicated GRC guidance, hands-on support, and access to independent licensed CPA firms for SOC 2 examinations.
As your compliance co-founder, we help simplify compliance preparation so your team can focus on building and growing the business.
Planning for ISO 27001 certification and SOC 2 attestation? Start your journey with Folksoft.
Sources
- System and Organization Controls Suite of Services – AICPA
- Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy. AICPA.
- ISO 27001, International Organization for Standardization.
- Folksoft SOC 2 Compliance
- Folksoft ISO 27001 Compliance
- Folksoft SOC 2 Cost Calculator
- Folksoft ISO 27001 Cost Calculator

