Four governance domains. One evidence layer. How assessors verify that infrastructure changes, recovery tests, integrity monitoring, and supply chain assurance leave cryptographic proof.
Audience: Notified Bodies, conformity assessment bodies, C3PAOs, third-party auditors, certification body leads. Proficiency: Expert. Time: 12 minutes.
Most organizations can describe their infrastructure governance policies. Fewer can prove those policies were followed for a specific change, a specific recovery test, or a specific supply chain event.
The gap is not in policy. It is in evidence. When an assessor asks "show me proof that your last disaster recovery test completed all four phases before you declared success," the typical answer is a spreadsheet with manual timestamps and a sign-off email. When they ask "prove this patch went through staging before production," the answer is a ticket with status transitions.
Neither of these is independently verifiable. Neither is tamper-evident. Neither proves sequence or completeness.
SWT3 witness anchors close this gap. Each governance decision, each phase completion, each test result mints a cryptographic receipt. These receipts are organized into hierarchical Merkle trees that prove temporal ordering: Phase 2 cannot exist without Phase 1. The tree root is independently timestamped via RFC 3161, creating evidence that is verifiable without trusting the organization that produced it.
Independent verification without trust. Every witness receipt is Ed25519-signed by a resolvable DID (did:web:sovereign.tenova.io) and rolled into a daily Merkle tree with an RFC 3161 timestamp. The assessor can recompute any fingerprint, walk any inclusion proof, and verify any signature without access to the organization's systems. The evidence is self-proving.
Assessor note
This guide maps infrastructure governance to SWT3 procedures and regulatory requirements. It does not prescribe how organizations should implement their governance. SWT3 is a witness layer: it records what happened, it does not decide what should happen.
Infrastructure governance evidence falls into four domains. Each domain has distinct regulatory drivers, distinct evidence requirements, and distinct failure modes that assessors encounter during conformity assessment.
| Domain | Core Question | Primary Procedures | Evidence Type |
|---|---|---|---|
| Change Management | Did this change follow governance gates before reaching production? | CM-3.1, AI-DRIFT.1, AI-DRIFT.2, AI-FREEZE.1 | Phase-gated Merkle tree |
| Disaster Recovery | Did this DR test complete all phases successfully? | CP-4.1, AI-ROBUST.1, AI-ASSESS.1, AI-RECOMM.1 | Phase-gated Merkle tree |
| Integrity Monitoring | Can you prove system integrity was continuously monitored? | SI-7.1, SI-7.2, AI-DRIFT.1, AI-DRIFT.2 | Continuous witness chain |
| Supply Chain | Can you prove component provenance and trust verification? | AI-SUPPLY.1, AI-SBOM.1, AI-HW.1, AI-TRUST.1 | Per-component attestation |
A change management pipeline witnessed by SWT3 produces a Merkle tree with one branch per phase. The assessor can verify that each phase completed before the next began, and that drift thresholds were respected at each gate.
release-v2.14.0). This identifies the Merkle tree./api/v1/merkle/gate endpoint returns whether all required milestones were satisfied before the gate opened.AI-DRIFT.1 witness anchor should show drift score below the organization's stated threshold.AI-FREEZE.1 anchor should precede the production rollout anchor in the tree.Assessor note
The most common finding: organizations skip the canary phase under time pressure. If the Merkle tree has leaves in Phase 0 (test) and Phase 3 (production) but nothing in Phase 2 (canary), that is a nonconformity against Art.17 QMS requirements.
DORA Art.8 note
For financial entities, the ICT risk management framework must include change management procedures (Art.8(4)). The structure root for each deployment can be included in the entity's ICT risk management report submitted to competent authorities. The drift attestations between phases prove that impact assessment occurred before production deployment, not after.
A DR test witnessed by SWT3 produces a phase-gated Merkle tree covering backup, restore, validation, and cutover. Each phase contains milestones with specific evidence leaves.
dr-test-q4-2026). One tree per test execution.AI-ROBUST.1 anchor with service count and success rate.AI-ASSESS.1 anchor comparing DR environment to production baseline. Look for functional parity percentage.AI-RECOMM.1 anchor with validator count and RTO attestation. This leaf must be the last in the tree (temporal ordering).Assessor note
Request both PASS and FAIL anchors. A DR test that never fails is suspicious. Legitimate DR programs generate FAIL verdicts when RTO is exceeded or services fail to restore. The absence of any FAIL history across multiple test cycles is itself a finding worth investigating.
EU AI Act Annex VI note
During conformity assessment of high-risk AI systems, the NB evaluates whether the provider's risk management system (Art.9) includes tested resilience measures. The DR test structure root is a single artifact the assessment team can verify independently. Resolve the DID, check the Ed25519 signature, walk the phase proofs. No reliance on the provider's internal systems required.
Continuous integrity monitoring produces a chain of witness anchors over time, not a single tree. The assessor verifies that the chain has no gaps longer than the organization's stated monitoring interval.
Assessor note
Integrity monitoring evidence is the easiest domain to verify at scale. Query the witness ledger for procedure IDs SI-7.1 and AI-DRIFT.1, sort by timestamp, and check for gaps. The daily Merkle rollup at /api/v1/merkle provides a per-day summary: if a day has zero leaves for integrity procedures, that is a gap.
Supply chain governance produces per-component attestations. Each hardware component, software dependency, and AI model has its own provenance record.
suppliers_assessed and suppliers_compliant factors.Assessor note
Supply chain evidence is the most framework-dense domain. AI-SBOM.1 alone maps to 11 regulatory frameworks. When assessing EU AI Act compliance, cross-reference the SBOM attestation against Art.60(a) registration database requirements and the G7 AI-SBOM minimum elements.
The following table maps infrastructure governance domains to specific regulatory articles. This is the reference for scoping a conformity assessment.
| Framework | Change Mgmt | DR Testing | Integrity | Supply Chain |
|---|---|---|---|---|
| EU AI Act | Art.17(1)(d) | Art.9(2)(a) | Art.15(1) | Art.60(a) |
| ISO 42001 | Cl.8.1 | A.6.2.6 | A.6.2.3 | A.6.2.5 |
| EU Machinery Reg | Art.18 | Annex III 1.2.1 | Art.18 | Art.10(2) |
| DORA | Art.8(4) | Art.11(6) | Art.9(2) | Art.28 |
| NIST 800-53 | CM-3 | CP-4 | SI-7 | SA-12 |
| CMMC v2.0 | CM.L2-3.4.3 | CP.L2-3.6.3 | SI.L2-3.14.6 | SA.L2-3.13.11 |
| SR 11-7 | IV.A | IV.C | III.B | V.B |
| NIS 2 | Art.21(2)(e) | Art.21(2)(c) | Art.21(2)(d) | Art.21(2)(d) |
All SWT3 witness anchors are independently verifiable. The assessor does not need to trust the organization's systems to confirm the evidence.
SWT3-{TIER}-{PROVIDER}-{UCT}-{PROCEDURE}-{VERDICT}-{EPOCH}-{SHA256_12}. Parse and validate structure.SHA256("WITNESS:{tenant}:{procedure}:{fa}:{fb}:{fc}:{ts_ms}").hex()[:12] and compare against the anchor's hash suffix./api/v1/merkle/proof?fingerprint=xxx. Walk the proof to the daily root.did:web:sovereign.tenova.io. The public key is in the DID document at /.well-known/did.json.Public verification tool: sovereign.tenova.io/verify accepts any SWT3 anchor for client-side verification. No account required. The verification runs entirely in the browser.
A suggested protocol for assessing infrastructure governance evidence during conformity assessment.
Questions or feedback: support@tenovaai.com