Skip to content
English
  • There are no suggestions because the search field is empty.

SOC 2 Foundations Quick Start Guide

What You Need to Get Started - Getting Audit Ready with Sensiba

Before You Begin

Before we can hand your engagement over to our audit team, there are a few foundational steps that need to be completed within your Compliance Automation Platform.

This guide walks you through the key requirements to ensure your platform is appropriately configured and ready for audit. It also outlines what to expect once your audit begins and how we can support you in demonstrating your SOC 2 progress to customers and prospects.

What do we need from you before your audit can begin?

To ensure a smooth handover and avoid unnecessary delays, please make sure you have completed the following:

  • Platform configuration and audit scope: Your key systems are connected, your audit scope is defined, and your in-scope personnel and devices are correctly configured.
  • Policies published and approved: Your information security policies have been created or uploaded, published within your platform, and approved. Required personnel should have been assigned their policies and completed any necessary acknowledgements.
  • Risk management: You have made a start on your risk register, including documenting identified risks, assigning owners and recording relevant mitigation plans.
  • Vendor management: Your critical third-party vendors have been added to your platform, with initial risk assessments or reviews completed where applicable.
  • Continuous Monitoring: Configure and review your platform's automated monitoring checks to ensure key controls are operating effectively and any identified issues are investigated.
  • Device Compliance: Integrate your device management solution (MDM) or endpoint monitoring agent to verify that in-scope devices meet your organisation's security requirements.
  • Control framework reviewed: You have downloaded and reviewed the applicable Sensiba control framework for your platform.
  • Auditor access granted: Our audit team has been provided with the necessary access to your Compliance Automation Platform.

Once these steps are completed, please notify your Client Success Specialist so we can progress your engagement to our audit team.

You do not need to have every control fully implemented or every evidence item completed before handover. However, your platform should be sufficiently configured, with the foundational activities above underway, so that our auditors can begin their review.

Connecting your key systems

Where applicable, we recommend connecting the following systems to your Compliance Automation Platform:

  • Cloud Providers (e.g. AWS, Azure, Google Cloud)
  • Databases (e.g. MongoDB Atlas)
  • Version Control (e.g. GitHub, GitLab, Bitbucket)
  • Identity Provider (IdP) (e.g. Microsoft Entra ID, Okta, Google Workspace)
  • Mobile Device Management (MDM) (e.g. Kandji, Jamf, Intune)

Defining your audit scope

Ensure your platform accurately reflects the systems and environments that fall within your SOC 2 audit scope.

  • In-scope: Production systems, databases containing sensitive data, and any infrastructure processing customer information.
  • Out-of-scope: Development, testing and sandbox environments, where they do not form part of your production environment or audit scope.

💡Tip: Always confirm that your in-scope inventory covers all production systems and sensitive data and nothing unnecessary.


2. Review Your Applicable Control Framework

Each Compliance Automation Platform includes a comprehensive library of default controls. However, not all of these controls are required for your SOC 2 audit with us.

Please note:

  • Your audit only requires a subset of the default controls available within your platform.
  • Approximately 50 controls are applicable to the Security, Availability, and Confidentiality Trust Services Criteria.
  • While our control frameworks also include Processing Integrity and Privacy, these criteria are not included in your audit scope by default unless specifically agreed.
  • Any controls or evidence that are not applicable to your audit can be safely excluded or descoped in accordance with the control framework provided below.

Please download the control framework for your Compliance Automation Platform:

📥 Please click the relevant link below to download the applicable control framework that applies to your specific platform:

  • Sensiba's Vanta SOC 2 Control Framework here.

  • Sensiba's Drata SOC 2 Control Framework here.

    • Please note that Drata introduced changes to its control framework for clients onboarded to the platform after 7 May 2025. As a result, there may be slight differences in the applicable control framework depending on your onboarding date.

      To make this easier to navigate, we've included two separate columns within the framework to help you identify and reference the controls applicable to your organisation.

      For further details on Drata's changes, please refer to their SOC 2 updates article.

💡 Helpful tips for interpreting the Control Framework

Each Control Framework contains two tabs:

  • Combined Control Matrix - Outlines how the controls will be presented in Section IIII of your final audit report. This is useful for understanding how your controls will be structured and reported.
  • Combined Criteria Analysis - Lists the unique controls included in the framework, along with their corresponding SOC 2 Trust Services Criteria mapping.

Understanding the SOC 2 Trust Services Criteria abbreviations

The Combined Criteria Analysis tab uses the following abbreviations to identify which Trust Services Criteria each control maps to:

Trust Services Criteria Abbreviation
Security (Common Criteria) CC
Availability A
Confidentiality C
Privacy P
Processing Integrity PI

3. Grant Auditor Access

Granting auditor access early allows our team to review your environment, provide guidance, identify any gaps, and help you become audit-ready as efficiently as possible.

Please follow the instructions below for your applicable Compliance Automation Platform:

Once auditor access has been granted, please notify your Client Success Specialist so we can support your audit preparation.


4. What to Expect Once Your Audit Begins

As part of your SOC 2 audit, your Lead Auditor will ask you to complete a scoping task through Sensiba Workspace.

Sensiba Workspace is our internal audit tool, which works alongside your Compliance Automation Platform to support the audit process.

Once your Lead Auditor has been introduced, they will provide instructions and assign you the General & SOC 2 Scoping Task through Sensiba Workspace.

This task helps define the boundaries of your audit and forms the basis of your final report. It allows your auditor to confirm exactly which systems, services and other relevant areas are included within your audit scope.

Important: This task is not required before your engagement can be handed over from our Customer Success team to the audit team. Your auditor will request that you complete it as part of the audit process, typically during the initial stages of the engagement


5. Demonstrating Your SOC 2 Progress to Customers & Prospects

We understand that achieving SOC 2 compliance can be an important requirement for your customers and prospects, particularly when responding to security questionnaires, procurement requirements or requests for evidence of your compliance progress.

If you need to demonstrate that your SOC 2 audit is underway before your final report is issued, Sensiba can assist with the following:

Confirmation of Engagement Letter

We can provide a Confirmation of Engagement Letter confirming that your organisation has formally engaged Sensiba to undertake a SOC 2 audit.

This can be shared with prospective or existing customers as confirmation that your SOC 2 audit is in progress.

If you require a confirmation letter, please reach out to your Client Success Specialist.

SOC 2 Type 2 Coverage Gap Communications

If you are completing a SOC 2 Type 2 audit and there is a gap in your compliance coverage (for example, where your previous Type 1 or Type 2 report or coverage period has ended before your new Type 2 report is available), we can provide a suggested communication template to help explain your current compliance position.

Please note that this communication must be issued directly by your organisation and on your company's behalf, rather than by Sensiba. It should accurately reflect your current compliance status and coverage period.

If you require assistance with communicating a coverage gap to your customers or prospects, please reach out to your Client Success Specialist.


Ready to Get Started?

Once your platform is appropriately configured, your foundational compliance activities are underway, your control framework has been reviewed and auditor access has been granted, please notify your Client Success Specialist.

Our team will coordinate the handover to your assigned audit team so we can get your SOC 2 audit underway.