01 · Execution risk
AI wants to execute
Agents, tools, and automated workflows create irreversible actions, transfers, deployments, data access, without a deterministic gate.
Governance > Regulatory mapping
TrigGuard provides execution authorization, evidence generation, and audit-ready controls aligned to major governance and compliance frameworks.
Section 1
AI systems want to execute. Regulators require accountability, traceability, control, and auditability. TrigGuard is the authorization checkpoint before irreversible actions.
01 · Execution risk
Agents, tools, and automated workflows create irreversible actions, transfers, deployments, data access, without a deterministic gate.
02 · Regulatory pressure
EU AI Act, DORA, NIS2, and sector rules demand pre-execution governance, logging, and evidence, not post-hoc explanations.
03 · Control point
Permit, deny, or silence before execution. Signed receipts prove what happened, offline verifiable, audit-ready.
Section 2
One control layer spans multiple frameworks. Frameworks define requirements; TrigGuard enforces controls; evidence proves alignment.
EU AI Act · UK GDPR · DORA · NIS2 · ISO/IEC 27001 · SOC 2 · SR 11-7 · PRA SS1/23
TrigGuard Control Layer
Authorization · Audit · Receipts · Evidence
Compliance Outcomes
Section 3
Active mappings across UK, EU, and global regulatory requirements, with TrigGuard controls tied to each framework.
| Framework | Coverage | Key controls | Status | Mapping |
|---|---|---|---|---|
| EU AI Act | High-risk AI obligations: risk management, governance, transparency, and logging. | Authorization, Receipts, Audit trail | Mapped | View mapping → |
| UK GDPR | Lawful processing, data minimization, security, and accountability for AI operations. | Privacy, Minimization, Evidence | Mapped | View mapping → |
| DORA | Operational resilience, ICT risk controls, incident reporting, third-party governance. | Fail-closed, Risk controls, Logging | Mapped | View mapping → |
| NIS2 | Cybersecurity risk management, supply chain safeguards, incident notification. | Execution controls, Supply chain, Audit | Mapped | View mapping → |
| ISO/IEC 27001 | Information security management system controls and evidence management. | ISMS, Encryption, Key mgmt | Mapped | View mapping → |
| SOC 2 | Security, availability, processing integrity, confidentiality, and privacy criteria. | Processing integrity, Availability, Privacy | Mapped | View mapping → |
| SR 11-7 | Model risk management expectations for financial institutions. | Model risk, Pre-execution, Governance | Mapped | View mapping → |
| PRA SS1/23 | Operational resilience policy statement for banks and insurers. | Resilience, Authorization, Evidence | Mapped | View mapping → |
Section 4
Every authorization decision produces verifiable artifacts, the evidence procurement and audit teams need.
{
"receipt_id": "rcpt_8f3a2b1c",
"decision": "PERMIT",
"action": "transfer_funds",
"policy_version": "pol_v12.4",
"timestamp": "2026-05-14T09:41:22Z",
"signature": "ed25519:7k2m…"
}
2026-05-14 09:41:22 UTC
agent: payments-agent-03
action: transfer_funds
amount: 50000 GBP
decision: PERMIT
policy: pol_v12.4 §4.2
receipt: rcpt_8f3a2b1c
Immutable record of policy changes with author, timestamp, and diff, linked to every receipt issued under that version.
$ tg verify rcpt_8f3a2b1c
✓ Signature valid
✓ Policy hash matches
✓ Offline verifiable
Section 5
What customers receive after scoping, tailored to your frameworks and deployment model.
Included deliverables
Section 6
Detailed mappings and guidance for each regulation.
This mapping is for informational purposes and reflects current regulatory guidance as of May 2026. Regulations evolve; contact us for latest updates and custom assessments.