Log: the record of events.
The Log is the record of events: a permanent, tamper-evident record of what AI saw, decided and did, held in your AWS or Azure account (or GenWA AWS as agreed). It is the source the evidence packs are generated from.
When AI is involved in a decision, few businesses can show what it saw, what it produced or who approved it.
Disputes, audits and incidents turn into reconstruction exercises, and gaps are read against you.
of businesses using AI have security practices that cover it
DSIT, 2026The benefits of Log.
The people who feel the problem first.
A record you can rely on.
Evidence for the file.
Answer, quickly, what happened and who owned it.
Three ways teams use Log.
See what AI saw and did around an event.
Show what was sent and who approved it.
Produce the record for a period or a process.
Works best alongside.
Register, data-flow map, control matrix and exception log, generated from the record.
See Evidence Packs Exception LogEvery breach, block and override, with who owned it.
See Exception Log RulesPolicy as enforced rules: approved models by task, data type and risk.
See Rules All of EvidenceA record of what AI saw, produced and who approved it, with reports against the regulations and your policies. Used with Guard.
See the Evidence modulePrices are indicative ranges, confirmed in writing before you commit. Estimates are replaced by your own figures once your health check runs.
See Log working on your business.
First findings within 48 hours of the health check · Audit fee credited against year one