Security
See what protects the OS, what needs attention, and which actions an admin can take.
Review each source with its date, scope and result. Failed or refused readings stay visible.
Access to the OS
Who can sign in and what they can reach.
Evidence neededAccess checks and active sessions.
Keys & secrets
Keeps exposed credentials from going unnoticed.
Evidence neededLatest scan and scanner availability.
Data protection
Keeps records within the right permissions.
Evidence neededDatabase access rules and permissions.
Release checks
Confirms the tested version is the one people use.
Evidence neededTest results and proof of the version in use.
Evidence & recent activity
Access checks, history and tool evidence are independent readings. Each needs its own source, date, scope and result. One successful read cannot clear another failed source.
Urgent findings come first, with the responsible role and permitted next step. Uninstalled tools, unsafe permissions, disabled protection, failed readings and refusals stay visible.
How evidence determines state
Verified: fresh evidence passes. Needs attention: evidence is incomplete or stale. Failed: a measured protection failure. Unassessed: no evidence loaded. No green state is inferred from missing data.
Admin tools & limits
Sign a person out everywhere · Shut or open an eligible door · Run the secret scan · Export this audit · Review rotation prerequisites.
Availability comes from tool evidence: Live / Built, not yet used / Not built. Key rotation is not built. Sign-in cannot be shut. Existing confirmations and admin permission checks remain required. Never show secret values.