Whitesec ID
Customer Assurance

SOC 2 Type 2 Readiness

Enterprise customers are asking for your SOC 2 report. Get the controls and evidence ready before the auditor arrives.

  • SOC 2 Type 2
  • Trust Services Criteria
  • Gap Assessment
  • Evidence Collection

A SOC 2 Type 2 report is an independent attestation that a service provider's security controls are designed properly and operated effectively over a defined period. It is issued by a licensed CPA firm, not by us. Our job is to get your organization ready: map the gaps against the AICPA Trust Services Criteria, implement controls, collect evidence throughout the observation period, and stand beside you during the audit.

What you receive

  • Gap assessment report against the Trust Services Criteria
  • Audit-ready security policies and procedures
  • Control matrix mapped to SOC 2 criteria
  • Draft system description
  • Evidence calendar and checklist for the observation period
  • Support until the auditor's report is issued
Context & Urgency

Why this matters now

In enterprise procurement, the security questionnaire increasingly ends with a request for one document: a SOC 2 report. SaaS, cloud, and data service providers without one often stall at due diligence.

  • A SOC 2 report replaces the long questionnaire

    Prospects, especially multinationals, use an independent auditor's report to skip hundreds of security questions. Without one, every deal means a new questionnaire.

  • Type 2 demands controls that run, not just controls on paper

    Auditors sample across the whole observation period. A control that only started before the audit, or leaves no evidence, shows up as an exception in the report.

  • The observation start date sets the timeline

    The observation period cannot be back-dated. The sooner controls are ready, the sooner the clock starts and the report can be issued.

Signs your organisation needs this

  • A prospect asks for a SOC 2 report before signing the contract
  • Engineering and security time is consumed by repeated security questionnaires
  • Access, code change, and backup controls run, but there is no tidy evidence
  • It is unclear which criteria categories and systems belong in scope

Any one of these is reason enough to start the conversation early.

Scope

What we cover

  • Scoping

    Define the systems, services, and criteria categories (Security, Availability, Processing Integrity, Confidentiality, Privacy) that match your customer commitments.

  • Gap Assessment

    Assess existing controls against the Trust Services Criteria and produce a prioritized list of gaps to close.

  • Policies & Controls

    Draft and implement policies, procedures, and technical controls: access, change management, logging, encryption, vendors, and backup.

  • System Description

    Write an accurate system description covering boundaries, components, complementary user entity controls, and subservice organizations.

  • Continuous Evidence Collection

    Run an evidence cadence through the observation period so audit samples are always available and consistent.

  • Audit Support

    Help select an auditor, respond to sample requests, and follow up on findings until the report is issued.

How We Work

Clear stages, with no surprises along the way

Every stage has agreed deliverables, so progress is never in question.

  1. 01

    Scoping

    Agree on systems, criteria categories, and the observation period with management.

  2. 02

    Gap Assessment

    Map current controls to the criteria and measure readiness.

  3. 03

    Remediation

    Close the gaps: policies, configuration, and workflows that stick.

  4. 04

    Readiness Review

    Internal dry run before the observation period starts, so controls are already operating.

  5. 05

    Observation Period

    Controls run and evidence is collected on a routine throughout the period.

  6. 06

    Audit & Report

    Support the CPA auditor's fieldwork until the SOC 2 Type 2 report is issued.

Reference Basis

The standards and regulations we work from

Every recommendation traces back to the references below and can be verified independently.

  • Trust Services Criteria (AICPA)The Security, Availability, Processing Integrity, Confidentiality, and Privacy criteria auditors assess.
  • SOC 2 Description Criteria (DC 200)Guidance on what the accompanying system description should contain.
  • SSAE 18 (AT-C 105 and 205)The attestation standards CPA firms follow in SOC 2 engagements.
  • ISO/IEC 27001:2022The information security management framework that overlaps heavily with SOC 2 controls.
  • Law No. 27 of 2022Indonesia's personal data protection law, relevant when the Privacy category is in scope.

Success indicators

Agreed upfront so the work is judged objectively rather than by impression.

  • Percentage of controls with complete evidence per period
  • Number of open gaps from the gap assessment
  • Time to provide evidence when the auditor requests a sample
  • Number of exceptions in control testing
Glossary

Terms that come up in these discussions

The vocabulary you will meet in documents, reports, and conversations with auditors.

SOC 2 Type 2
An attestation report on the design and operating effectiveness of a service provider's controls over a defined observation period.
Trust Services Criteria
AICPA criteria in five categories that auditors test against: Security, Availability, Processing Integrity, Confidentiality, and Privacy.
Observation Period
The span of time, typically three to twelve months, over which the auditor tests whether controls operate consistently.
System Description
Management's account of the system, its boundaries, components, and the controls the report covers, including subservice organizations.
Frequently Asked

The questions we hear most

Still unanswered? Send your question and our team will reply on a working day.

Ready to build stronger security?

Talk your organisation's needs through with our team. Free, and without obligation.