Anti-tamper controls address OWASP ASI-09 (Governance & Compliance Bypass) — the risk that governance controls are circumvented through configuration tampering, policy replacement, or privilege escalation.
Why This Matters
Compliance alignment: NIST AI RMF (GOVERN 1.2 — accountability), ISO 42001 (A.8.4 — AI system integrity), SOC 2 CC6.1 (logical access), EU AI Act Article 15 (robustness).
Forbidden Config Keys
Certain configuration keys are forbidden — any attempt to set them triggers immediate rejection with a tamper alert. These keys represent configurations that would fundamentally undermine governance.Default Forbidden Keys
Custom Forbidden Keys
Organizations can add domain-specific forbidden keys:Bundle Integrity Validation
Policy bundles must pass integrity validation before they are loaded. This prevents tampered or unauthorized bundles from being applied.Signature Verification
Bundle Structure
Integrity Validation Flow
Workload Identity Binding
Workload identity binding ensures that the TealTiger governance engine runs as the expected process on the expected infrastructure. It prevents an attacker from replacing the governance engine with a permissive stub.Platform Support
Capability Negotiation
Capability negotiation limits what the application code can do with the governance engine at runtime. The engine exposes only the capabilities that the application is authorized to use.Separation of Duties
TealTiger enforces separation between three roles:Configuration
Related Documentation
- FREEZE Rules — Immutable safety controls
- TealProof — Bundle integrity evidence
- NHI Governance — Workload identity for agents
- SOC/IR Pipeline — Tamper alerts in SIEM
- OWASP Policy Pack — ASI-09 coverage
- Code Change Governance — Two-person rule

