SOC 2 requirements in the library
The Trust Services Criteria are seeded and linked to controls, ready to switch on.
A SOC 2 Type 2 report looks at how controls worked over months, so the hard part is keeping proof current the whole time. Purplecop GRC keeps controls, policies and evidence together as the period runs, instead of reconstructing them at the end.
What changes when the audit period runs on Purplecop.
The criteria, the controls and the proof live together, so the period is never rebuilt from memory.
The Trust Services Criteria are seeded and linked to controls, ready to switch on.
A control shared across frameworks is created once in the library, not rebuilt for each one. The work you do for SOC 2 counts toward everything else you hold.
Start from a ready-made policy, not a blank page. Each one is tagged to the frameworks it supports and goes through review in the same place.
External auditors get read-only access enforced on the server, across four roles from Lead Auditor to Observer — with one exception: they can raise a correction request when a requirement is not met.
Corrective actions run through a tracked workflow with 5-Whys and fishbone analysis, ageing buckets and three escalation tiers.
The whole GRC estate in one product: frameworks, controls, policies, evidence, risk and audit on one control library.
The team that runs your engagement works inside the same system, so the work they do stays with you.
Also on the platform
Onboard, assess, score and continuously monitor every vendor in one workflow.
Asset discovery, network monitoring and the audit log in one module, so every asset’s data lives in one place.
Live phishing campaigns with per-user risk scores, run entirely in-house.
Role-based security awareness training for every employee, tracked to completion.
A directory of the people in scope for training, policy sign-off and access reviews.
Role-based access control with granular permissions, on a least-privilege model.
No. A SOC 2 report is issued by an independent CPA firm. Purplecop GRC holds the controls and evidence they examine.
Type 1 looks at how controls are designed at a point in time. Type 2 looks at how they operated over a period, which is why keeping proof current matters.
Every control that serves both frameworks is created once and counts for both.
It scales with how much you integrate: the more connectors you turn on, the more evidence is collected automatically, saving up to 70% of the time you used to spend preparing for each audit window.
We will walk the product against your scope and show you what runs on day one and what needs configuring.