





A readiness assessment compares what you do today with what SOC 2 expects and gives you a prioritized list of gaps to close before the audit. It is not part of the formal examination and it produces no report or opinion. Its value is finding problems while they are still private.
It is a structured review of your scope, controls, policies, evidence and ownership against the criteria you chose.
It is not an audit. Nobody issues an opinion, and passing a readiness review does not guarantee a clean report.
It is most useful after your controls are designed and before an observation window or audit date is set.
Your own team. Fast and low cost, and builds internal knowledge, but it can miss blind spots.
An outside adviser. Brings fresh judgment and experience with what auditors expect.
Your audit firm, if it offers readiness services. Ask how the firm maintains independence between advisory work and the examination, since the same firm will later give an opinion on your controls.
Confirm scope and criteria. Confirm the services, systems, locations and Trust Services categories, and write down your service commitments.
Build an inventory. List assets, applications, data stores, people, vendors and subservice organizations in scope.
Map existing controls. Match each criterion to the control you already run, and note where none exists.
Test design. For each control, ask whether it would meet the criterion if it ran as written.
Test operation. Pull real evidence, such as access approvals, change tickets, training records and vendor reviews, to see whether the control actually ran.
Rate and prioritize gaps. Rank by audit impact and effort, assign an owner and a date to each.
Remediate and retest. Fix, produce the evidence and check again.
Decide the path. Choose Type 1 or Type 2, the window start date and the audit firm timing.
With Cstream: controls and control tests show pass and fail results from the start, so your gap list builds itself instead of beginning in a spreadsheet. Test Insights in Observe Pod turns failures into a live remediation worklist for engineers, and Projects assign tasks with due dates while tracking audit readiness as work completes.
Area | Questions | Evidence to check |
Governance | Does every control have an owner? Is management oversight documented? | Org chart, roles, meeting records |
Policies | Are policies current, approved and acknowledged by staff? | Policy versions, approvals, acknowledgment records |
Risk | Is there a documented risk assessment with owners and treatments? | Risk register, review dates |
Access | Is access approved, reviewed and removed on time? Is multi-factor authentication enforced? | Access lists, review records, offboarding records |
Operations | Are vulnerabilities found and fixed? Are incidents logged and reviewed? | Scan results, tickets, incident records |
Change | Are changes reviewed, tested and approved before release? | Change tickets, code review records |
Vendors | Do we know which vendors touch customer data, and have we reviewed them? | Vendor list, review records |
People | Is training completed and tracked? Are onboarding and offboarding steps followed? | Training records, checklists |
Resilience | Have we tested incident response and recovery plans? | Exercise records, outcomes |
Rating | What it looks like | What to do |
High | A control the criteria clearly call for is missing or not operating, such as no approved policies or no access removal process | Fix before the audit or window starts |
Medium | A control exists but evidence is incomplete or inconsistent | Fix evidence and ownership, then retest |
Low | Wording, documentation or minor process improvements | Schedule alongside normal work |
A gap list with owners, dates and ratings
A remediation plan in priority order
A list of evidence you can already produce for each control
A go or no-go view on audit timing
With Cstream: Launch Pad is a go-live readiness workspace that validates business and technology operations before launch, confirming that requirements, policies, vendors, controls, onboarding and monitoring are in place. It is a useful pattern when you want a new product or service to reach customers already compliance-ready.
Cstream is the trusted GRC platform that supports startups through every stage of the SOC 2 journey, from planning and control implementation to audit preparation and ongoing compliance. Cstream keeps one data model for IT operations and compliance, so the assets, people, vendors, policies and control test results you use every day are the same ones that support your audit.
Cstream's SOC 2 capabilities include key features supporting preparation and audit, such as:
Cstream works directly with your audit firm to keep reviews moving. Multi-framework Mapping also lets the same controls support ISO 27001, HIPAA and other frameworks later.
Schedule a demo to see how Cstream supports your SOC 2 journey.

