The differentiator

“Are our endpoints hardened right now, and can you prove it?”

That is the board question. Hardening Proof is the single-screen answer. A CISO opens it in front of an auditor and walks out in ten seconds with a defensible answer — posture, proof, and action, in one place.

The Hardening Proof screen: 97% posture score across 247 of 254 controls, 23 drift events in the last 30 days, a 94-second mean time to remediate, 98% auto-remediated, a stacked drift timeline, a control-families rollup for CIS, NIST, PCI, DPDP and ISO 27001, and a live signed-receipts table.

Screen anatomy

Seven data points. One story an auditor can take unedited.

Every value on the screen traces back to a service that already exists. Nothing here is a mock-up of a promise — it is the promise, rendered.

97%

Posture score

Applied controls across the selected tenants — 247 of 254 scored controls. Refreshes every 15 minutes. Carries a delta versus the prior window, never a bare percentage.

23

Drift events, 30 days

Every configuration change the Drift Detector caught in the window. Live over websocket — a new event slides into the timeline as it happens.

94s

Mean time to remediate

Average from drift detected to control restored, drawn from the Playbook Execution Log. Down from 6 minutes 12 seconds the prior window.

98%

Auto-remediation rate

Share of drift closed with no human in the loop. The remaining fraction escalates to a playbook awaiting a condition or a human decision — never a silent failure.

Drift timeline

Green is restored. Amber is investigating. Red is open.

A stacked bar per day for the window. Every segment is clickable and drills to the filtered receipts below. The story a board wants is the colour balance: mostly green, and shrinking amber.

Control families

Ranked by framework, applied over total.

CIS Level 1
58 / 58
CIS Level 2
42 / 44
NIST 800-53 (Mod)
71 / 73
ISO 27001 Annex A
14 / 16

Live receipts

The single most important table on the screen.

Each row is a signed audit entry — timestamp, asset, control, what drifted, the playbook that fixed it, and the status. Exportable as JSON or PDF. This is the receipt that turns proof into a story.

07 Jul 21:14:03srv-prod-04 · CIS 5.4.1 SSH root login · PermitRootLogin yes → PB-021 set to ‘no’● Restored
07 Jul 20:48:22wk-mkt-118 · CIS 1.7.2 firewall default · disabled inbound rule → PB-003 rule re-enabled● Restored
07 Jul 19:33:57srv-db-02 · NIST AC-2 inactive account · svc-legacy 91d idle → PB-014 account disabled● Restored
every row signed · x-zelarsoar-audit-signature · immutable object storage, 7-year DPDP retention

Empty state, when it happens: “No drift detected in the selected window. Every scored control is currently applied.” A green tick still carries a last-verified time — there are no ticks without timestamps on this screen.

Discipline

What this screen will never show.

A policy PDF as evidence

This screen is the proof. The PDF is the promise. We do not confuse the two.

A green tick without a timestamp

Every green state carries a last-verified time. "Applied" means "applied as of a moment you can point to."

A vendor logo

The screen belongs to the customer in front of the auditor, not to us.

A chart without a headline finding

Every chart title states the finding, not the metric name. The board reads findings, not axes.

Open this screen on your infrastructure, in front of your evaluator.

Two hours. Your board question. If the answer is not one screen, ten seconds, and a signed receipt, you leave with a written scorecard instead.