Governance evidence
Use for control statements that cite ISO/IEC 42001 clause 6.3 change management, EU AI Act Articles 62–75, and SOC 2 trust service criteria.
Think of IT infrastructure as the plumbing and electricity of the digital world. Just like a building needs foundations, wiring, and pipes before anyone can live in it, every app, website, and digital service needs infrastructure to run.
Controls stack visual kit
Reusable icons and a telemetry-to-audit diagram aligned to our fundamentals and operational guides.
Use for control statements that cite ISO/IEC 42001 clause 6.3 change management, EU AI Act Articles 62–75, and SOC 2 trust service criteria.
Pair with SBOM, provenance, and intake guidance that references SPDX or CycloneDX formats, SLSA Level 3 attestations, and NIST SSDF tasks PS.3/PO.4.
Highlight logging of prompts, responses, refusal rates, and safety filters alongside adversarial evaluation suites from NIST AI RMF playbooks or UK AISI guidance.
Use for incident response and assurance artefacts that must meet OMB M-24-10 24-hour notifications, CIRCIA’s 72-hour clocks, and serious-incident duties under the EU AI Act.
Let’s break this down into pieces you can actually picture:
Here’s the thing: when infrastructure works, nobody notices. It’s invisible. But when it fails...
There’s no “best” choice—only the right choice for your situation. A startup might go all-cloud for speed. A bank might stay on-prem for control. Most organisations mix and match. The important thing is understanding the trade-offs.