Prove & Operate

Prove it stayed built

Go-live is the middle of the project, not the end. Panaptico keeps the blueprint pointed at live state forever after — detecting drift, proposing bounded remediations, and assembling evidence that every control still holds.

Posture

The blueprint is a living contract

Every implementation ends with a blueprint — the intended shape of the world after rollout. Panaptico keeps pointing that blueprint at reality. When they diverge, you hear about it before auditors do.

LivePosture Overview· Enterprise-Wide
Updated 48s ago

Blueprint Coverage

98.4%

of 148,291 assets reconciled

Drift Events (7d)

37

12 auto-resolved · 4 open

Control Assertions

1,204

across 41 frameworks

Last Reconcile

48s ago

continuous · 2.1s median

Reconcile cadence · Last 24h

2,048 runs · 2.1s median

ReconcileDrift detected
1

Continuous, not scheduled

Reconciliation runs every few seconds against every connected source. You find out about drift in seconds, not next quarter's audit.

2

Coverage you can point at

Every asset in the blueprint has a coverage state. You see exactly which ones are being watched and by which source.

3

Noise-suppressed signal

Drift that's expected (change windows, approved waves) is folded in automatically. What surfaces is what actually needs attention.

Detect

Drift, triaged and explained

Every drift event is grounded in at least two sources. Severity isn't a vibes call — it's derived from blueprint intent, blast radius, and which controls the asset participates in.

37 Drift Events· rolling 7 days
All sourcesSeverity: All
IDAssetKindDriftSeveritySourcesDetected
d-7841prod-api-gateway-01Network

Security group 0.0.0.0/0 on port 22 — blueprint requires bastion only

· 99%
Critical
AWS
Wiz
2m ago
d-7839hr-okta-app-204Access

9 users granted admin outside IAM change window

· 96%
High
Okta
Workday
11m ago
d-7835tp1dist-01Config

Terraform state drift — manual resize of i-0de42 to r6i.4xl

· 100%
High
Terraform
AWS
24m ago
d-7828ops-db-cluster-03Compliance

Backup retention 7d — SOC2 CC7.3 requires 30d

· 100%
Critical
AWS
Vanta
41m ago
d-7824sso-group-finance-adminsAccess

Group membership drift — 2 identities not in source-of-truth

· 94%
Medium
Entra ID
Workday
1h ago

Showing 5 of 37 · grouped by asset

Every row is two-sourced. No single-source drift alerts.

1

Grounded in multiple sources

Every drift event is corroborated by at least two connectors. A single API blip never pages oncall.

2

Severity derived from graph

Blast radius isn't guessed — it's computed from the live dependency graph. Critical means critical in your environment.

3

Context ready for triage

Click into a row and the blueprint diff, change history, and the last approved wave load together — no tab-hopping.

Evidence

The audit assembles itself

Every reconciliation run produces immutable evidence — API snapshots, config diffs, approvals, screenshots, logs — each tied to the control it satisfies. When audit season comes, you export a bundle, not a prayer.

Evidence Vault· 1,204 artifacts · immutable
API snapshot4.2 KB

IAM policy GetAccountPasswordPolicy

CC6.1 · Logical access

SOC 2 Type II

AWS IAM
2026-04-22 14:08
Config diff18.6 KB

terraform plan — prod/us-east-1

CC8.1 · Change management

SOC 2 Type II

Terraform
2026-04-22 14:05
Approval record2.1 KB

CHG-00482 — Rolling upgrade Wave 2

CC8.1 · Change approval

ISO 27001 A.12.1.2

ServiceNow
2026-04-22 13:41
Screenshot1.3 MB

Backup retention — 30d attested

CC7.3 · System monitoring

SOC 2 Type II

AWS Backup
2026-04-22 13:02
Log7.8 KB

MFA enforcement — last 24h

164.312(d) · Auth

HIPAA

Okta
2026-04-22 12:55
API snapshot912 B

CloudTrail retention config

CC7.2 · Logging

PCI DSS 10.5.3

CloudTrail
2026-04-22 12:30
1

Tied to controls, not folders

Every artifact carries its control mapping at capture time. An auditor can trace any assertion back to its source in one click.

2

Immutable by design

Evidence is hashed, signed, and append-only. The record of what was true at 14:08 is the same record you export next March.

3

Generated, not chased

Evidence is a byproduct of reconciliation, not a deliverable. Nobody is taking screenshots. Nothing waits on a sprint.

Control

Frameworks, mapped to live state

Controls are assertions about the graph. Panaptico checks the assertion every reconcile, attaches the evidence that proves it, and tells you the minute it starts to fail.

SOC 2 Type II

Enterprise

97%

62/64

CC6.1

Logical access controls

148Covered

CC7.2

System monitoring

92Covered

CC7.3

Incident response

41Partial

CC8.1

Change management

204Covered

ISO 27001

Enterprise

93%

106/114

A.9.2

User access management

87Covered

A.12.1

Operational procedures

63Covered

A.12.4

Logging and monitoring

29Partial

A.18.1

Compliance

4Gap

HIPAA

HR + Benefits

94%

51/54

164.308(a)(1)

Security mgmt process

71Covered

164.312(a)(1)

Access control

112Covered

164.312(b)

Audit controls

38Partial
1

One graph, many frameworks

The same assertions satisfy SOC 2, ISO, HIPAA, PCI, FedRAMP. You model the environment once — the control mapping is just a projection.

2

Gaps with remediation context

Where there's a gap, the next step is already scoped: which assets, which blueprint change, which playbook. Not a Jira ticket.

3

Coverage that moves with reality

Add a region? Launch a new service? Controls re-assert automatically. Scope creep doesn't mean audit debt.

Close the loop

Drift gets resolved the way it got detected

Remediation is not a parallel universe. It's the same engine that built the system, in miniature: bounded change, approved wave, dry-run, apply, evidence. The loop doesn't stop.

BlueprintLIVING CONTRACTMonitorcontinuous reconcileDetecttwo-source corroborationProposebounded remediationApproveCAB + policy gateReconcilelive graph updatesEvidencecontrol re-asserted
Active event

d-7841 — prod-api-gateway-01

Security group 0.0.0.0/0 on port 22 · detected 2m ago

Monitor

Reconciled 48s ago · AWS + Wiz

Detect

Two sources confirm · severity CRITICAL

Propose

Revert SG → bastion-only · ready

Approve

CAB pending · policy gate OK

Reconcile

Dry-run queued · wave-scoped

Evidence

CC6.1 + A.9.2 re-assertion

1

Same engine, miniature scope

Remediation reuses the Plan & Execute pipeline. If you trust the implementation, you trust the fix.

2

Bounded even under pressure

Emergency fixes still run through wave scoping and dry-run. Speed doesn't cost governance.

3

The loop is the product

Every resolved drift hardens the blueprint. The longer you run Panaptico, the less drift you see in the first place.

Operate

A live record of what's true now

Panaptico is the single place to answer "what changed, when, why, and did it still satisfy the controls?" — for the life of the system, not just the rollout.

Reconcile Activity
6 events · last 2h
Reconciled 148,291 assets across 14 sources
48s ago
Drift resolved — i-0de42 rolled back to r6i.2xl
3m ago
New drift — prod-api-gateway-01 · SG open 0.0.0.0/0:22
2m ago
Control CC8.1 re-asserted — CHG-00482 closed clean
14m ago
Evidence bundle exported — SOC 2 Q1 package, 874 artifacts
1h ago
Blueprint updated — new region us-west-2 onboarded
2h ago

Go-live is the start of the contract

Panaptico keeps the blueprint honest — quietly, continuously, and with the receipts every auditor and engineer already wish they had.