Currency

Live Control State — current, not last quarter's audit

Security posture that updates itself, so the picture reflects what is true now — not what was self-reported at the last assessment cycle.

Testify maintains a Live Control State per company per control — always current — fed continuously by four sources: assessments, incidents, remediations, and audited manual overrides. The result is a posture that reflects what is true now, not what was self-reported at the last audit.

Four inputs, one current register

Assessments establish the baseline; remediations move controls forward; audited manual overrides capture reality with a receipt; and incidents degrade the affected controls automatically. No stale dashboards, no manual sync.

Incidents treated as systemic control failures

Creating an incident automatically degrades the affected controls via a MITRE ATT&CK → CIS mapping, and root-cause analysis compares the at-incident state to the current state. A breach is treated as a systemic control failure rather than an isolated event — the "informed by real incident data" half of evidence-backed efficacy.

Every change leaves a receipt

Every state change writes an immutable record with source, user, timestamp, and justification, and uploaded evidence carries a tamper-evident SHA-256 hash. The method is inspectable; nothing moves without a receipt.

Frequently asked questions

How is Live Control State different from an annual assessment?

An annual assessment is a point-in-time snapshot that goes stale between cycles. Live Control State is always current — continuously updated from assessments, incidents, remediations, and audited overrides — so posture reflects what is true now.

What happens to controls when an incident is logged?

Creating an incident automatically degrades the affected controls via a MITRE ATT&CK to CIS mapping, and root-cause analysis compares the at-incident state to the current state. Breaches are treated as systemic control failures, not isolated events.

Is every change auditable?

Yes. Every control-state change writes an immutable record with source, user, timestamp, and justification, and evidence uploads carry a tamper-evident SHA-256 hash re-verified on download.

See it on your portfolio

Testify is accepting early customers. Portfolio Directors and Operating Partners get priority access to a guided walkthrough.