Register objects
Creates and updates on systems, controls, evidence, policies, and tasks.
Platform · Audit trail
Who changed the register is part of the register.
Controls, evidence, policies, and tasks are only useful if you can reconstruct how they got that way. ReadyComply logs the change. Impersonated Authio sessions cannot open evidence.
Why it exists
An examiner will ask how a control got to implemented.
If the answer is “someone clicked it last week,” that is not a program. The trail records the actor, the action, and the time on the objects in the workspace.
In the workspace
What the trail covers.
Attributed to Authio
The session is project-bound. You know which organization and which user.
Impersonation stop
Support impersonation cannot open compliance evidence. The trail is not a backdoor.
Not an audit opinion
A log is not a SOC 2 report. It is the record you hand a firm so they are not guessing.
How it fits
Prep is the register plus the trail.
When you hire a CPA, they will sample. You will need to show the control, the evidence, the policy text, and that changes were not silent. That is this page’s job.
Also in ReadyComply
The trail is only as good as the objects.
Controls
Scope SOC 2, ISO 27001, HIPAA, and GDPR families to each system. Track status, owner, and why something is out of scope.
Evidence
File what you have against a control. Manual upload or a read-only connector.
Policies
Versioned drafts next to the controls they support. Know which text is current.
Keep the register current. The trail follows.
Sign in. Make a real change. That is the first event worth having.
Sign in