SOC 2, run as a programme. Not a scramble.
A plan, an owner for every control, evidence an auditor accepts.
SOC 2 Type II programme
Project plan with milestones; progress fills as work completesMilestones
Controls by domain7 of 11
Open tasks2 of 17
Enterprise buyers ask for the report before they sign.
SOC 2 is an independent attestation, from a CPA firm, on how a service organisation protects customer data. It is how a vendor proves it, instead of promising it.
The report is a gate
Many buyers will not onboard a vendor until they have read its report.
Questionnaires repeat
The same security questions arrive from every buyer. A standing programme answers them once.
Renewal is annual
A Type II report covers a period, so the work continues after the first report.
From scoping to a clean report, one continuous plan.
Seven stages, with the same plan and the same people from the first day to renewal.
- 01
Scope
Choose the system, the criteria and the report type.
A plan built from the SOC 2 framework - 02
Assess gaps
Compare what you do today with what the criteria expect.
Gaps recorded against each control - 03
Remediate
Close the gaps, write the policies, name the owners.
Tasks with owners and due dates - 04Type II observation window
Operate
Run the controls and keep evidence as you go.
Evidence linked to every control - 05
Fieldwork
Your auditor tests controls and samples evidence.
A shared workspace for the auditor - 06
Report
An independent CPA firm issues the SOC 2 report.
Issued by your auditor, not by us - 07
Maintain
Stay ready between audits and renew each period.
Review cadence and standards watch
Every criterion, accounted for.
Security is mandatory. Add Availability, Processing integrity, Confidentiality or Privacy when your customers' needs call for them. Your plan carries whichever you choose.
- SecurityCC1 to CC9 · Always in scope
- AvailabilityA1 · Uptime and recovery
- Processing integrityPI1 · Complete, accurate, timely
- ConfidentialityC1 · Protected as agreed
- PrivacyP1 to P8 · Personal information
From criterion to control to evidence.
The common criteria for Security, and how each is carried in your plan. Additional criteria follow the same pattern when they are in scope.
Shape your SOC 2 plan in three choices.
A quick view of where to start. A named expert refines it with you in the first conversation.
See your SOC 2 programme on screen.
The same screens your compliance lead, your control owners and your auditor would use.
Programme overview
Orion Bank Ltd, all frameworksFramework progress
Controls by status
Risk heat map
Upcoming
Standards watch
Swipe the screen sideways to see all of it.
Programme dashboard. Framework progress, risk heat map, upcoming milestones and standards updates for the whole programme.
How a control becomes evidence an auditor accepts.
Auditors sample evidence. Your programme should make every sample easy to find, verified and tied to a criterion.
- 1Control assignedEvery control has an owner and a review date.
- 2Task raisedThe owner sees what to provide, and by when.
- 3Evidence addedDocuments and records attach to the control.
- 4ReviewedA reviewer verifies it before the auditor sees it.
- 5MappedEvidence links to the criteria it supports.
- 6SharedThe auditor works in an isolated, shared workspace.
Two reports. One programme underneath.
Enterprise buyers usually prefer Type II. Many teams start with Type I to reach a first report sooner, and run the same plan into Type II.
A flagship engagement, not a login.
Software carries the plan. People carry you through it.
- 01
Readiness assessment
A gap assessment against the criteria in scope, with a prioritised plan.
- 02
Programme set-up
Your SOC 2 plan, owners and policies configured alongside your team.
- 03
Operating cadence
Regular reviews of evidence and open tasks with your named expert.
- 04
Auditor liaison
Help organising fieldwork and answering evidence requests with your auditor.
- 05
Renewal planning
A plan for the next period, updated for any change to the criteria.
Facing the DPDPA as well?
Many teams carry both. Consent, rights requests and data mapping sit in CyberMetric DPDPA, next to the same evidence habits you build for SOC 2.
CyberMetric DPDPA
Consent, data principal rights, data discovery and lineage.
Explore CyberMetric DPDPA →Where to next?
Pick a path. Each one takes a minute or two, and ends with a clear answer.
- ✓Explore
- 2Self-check
- 3Talk to us
See your SOC 2 plan, before you commit.
Tell us a little and we will arrange a conversation with the people who build and support it.
What we will cover
- Your customers' requirements and your timeline
- Which criteria are in scope
- A walkthrough of a SOC 2 plan, risk and evidence
- A clear next step, with no obligation
Helpful to bring
- The systems in scope
- Any customer requests for a SOC 2 report
- Your target date for the report
Need the certificate or report for your vendor review? Ask us.
