Control map
Which artefacts Sentinelleai actually holds against named compliance controls, and what each one stops short of proving.
What people come here for
Compliance Frameworks
Maps controls to frameworks such as SOC 2 Type II, and keeps the few controls whose evidence covers a period separate from the majority that are only ever point-in-time.
Full definition →Risk Register
Collects risks from the mechanisms that actually carry them, grades each by the rigor of the decision behind it, and flags the ones nobody has given a review date.
Full definition →Remediation Tracking
Every finding carries an owner and a due date, and a fix counts as verified only after a fresh run has re-read the code — not when somebody ticked it.
Full definition →Policy as Code
Policies written as machine-checked rules — which actuators are armed, service-level targets by severity, whether the required evidence exists — resolved against the live environment instead of against a document.
Full definition →Business Continuity
The continuity and recovery artefacts an assessor asks for, held in the same evidence chain as everything else here.
Full definition →Everything else in this surface
Each name opens its own one-line definition in the capability catalogue.
What this does not do
This is a control map, not a certification. Nothing on it makes anyone compliant, and the guide states which controls it cannot cover at all.
Everything this product does not do →