DORAICT incidents, and us as a provider
Insurers and reinsurers are financial entities under DORA. A time-stamped trail helps you evidence the timeline of an ICT incident (Art. 17 and 19). If you use our hosted service, we are your ICT third-party provider (Art. 28 ff.); the record service can also run in your own data centre.
Solvency II · ORSAControls you can show to the risk function
Where AI agents run underwriting or claims steps, their operational risk belongs in your system of governance and your own risk and solvency assessment. Signed runs show the risk function and internal audit which controls actually ran, not only which were designed.
EIOPADocumentation and record keeping for AI
EIOPA's Opinion on AI governance and risk management names documentation and record keeping as one of six areas, next to human oversight and explainability, and ties it to the existing duty to keep orderly records.
ISO/IEC 42001Records for an AI management system
If you run or plan an AI management system under ISO/IEC 42001, signed runs can serve as its operational records. We are not certified under ISO/IEC 42001, and a record does not certify you.
ISO/IEC 42001:2023
EU AI ActLogs, and marking of AI content
High-risk systems must log automatically (Art. 12); providers and deployers keep the logs for at least six months (Art. 19, 26(6)). Art. 50(2) asks for machine-readable marking of AI-generated content. A record helps you evidence the log; whether its scope is enough for your purpose is your decision.
GDPRAccountability, privacy by design
Sensitive values sit in a record only as hashes, which supports accountability and privacy by design (Art. 5(2), 25, 32) and answers to an automated decision (Art. 22(3)). It supports these duties; it does not replace your own assessment.