Starter families
SOC 2, ISO 27001, HIPAA, and GDPR families instantiated per system so you are not inventing the catalog from a blank page.
Platform · Controls
Map the criteria to the systems you actually run.
ReadyComply instantiates starter families for SOC 2, ISO 27001, HIPAA, and GDPR per system. You record status, ownership, and why a control is out of scope. It never marks a control passing on its own.
Why it exists
A control without a system is a slogan.
SOC 2, ISO 27001, HIPAA, and GDPR are not a generic checklist you stamp on the company. They apply to a system boundary. ReadyComply binds each instance to an organization and a named system, with a unique record per template — no silent duplicates.
In the workspace
What you can do today.
Status that a human sets
Not started, in progress, implemented, needs attention, or not applicable. The product does not auto-pass.
Owner and statement
Who is accountable, how the control operates here, and why it is out of scope if it is.
One record per template
Organization + system + template is unique. Re-importing the family does not clone the register.
Evidence and work
The register has to agree with itself.
A control that is implemented still needs evidence. A gap still needs an owner. From a control you file artifacts and open remediation without leaving the workspace.
Also in ReadyComply
Keep the rest of the register in view.
Start with the systems in scope. Then assign owners.
Sign in. Name the first system. Instantiate the starter family before you write a policy.
Sign in