Which policy enforces this control?
The Compliance Center maps every framework control to the Raidu policy that enforces it, across EU AI Act, HIPAA, NIST AI RMF, and other frameworks.
Solutions · Compliance and Risk
It is already written down. Framework controls mapped to live Raidu policies, with tamper-evident records linked per control.
Runs inside your AWS, GCP or Kubernetes install.
Last reviewed
Illustrative. No customer data.
The difference
What you get asked
The Compliance Center maps every framework control to the Raidu policy that enforces it, across EU AI Act, HIPAA, NIST AI RMF, and other frameworks.
Each control links directly to the tamper-evident records that prove it ran. Records are SHA-256 hashed, linked so any change shows, and stored write-once. An export is available per control or per framework.
Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744, requires high-risk AI systems to record their own events from 2 December 2027 (Annex III). Every call through Tower is already written to a tamper-evident record, linked so any change shows.
Products
The product
Product windows from the films, with sample data. No customer data.
The record
Every framework control links to the policy that enforces it and the records that prove it ran, tamper-evident and ready for export.
The clock
1 January 2027
Colorado AI Act (SB 26-189) becomes operative. High-risk AI systems must meet its transparency and audit requirements.
Colorado SB 26-189
13 May 2027
Full DPDP obligations commence. Penalties up to ₹250 crore per instance under India's Digital Personal Data Protection Act.
DPDP Gazette G.S.R. 843(E) to 846(E)
2 December 2027
EU AI Act (Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744) requires high-risk AI systems to record their own events. Every call through Tower already meets this requirement.
Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744, Annex III
Common questions