RK-002HighProviderPreventive
Log Integrity and Tamper Protection
Providers must ensure that logs are protected against tampering, unauthorised deletion, or modification, using cryptographic integrity controls, write-once storage, or equivalent technical measures.
Articles:Article 12(1)Article 12(2)
Evidence Examples
- Log integrity mechanism description
- Cryptographic hash verification procedure
- Immutable log storage configuration
Standards
ISO/IEC 27001:2022 A.8.15ISO 42001:2023 §9.1
Related controls
- RK-001Automatic Event Logging CapabilityArticle 12(1) requires that high-risk AI systems are designed and developed with automatic logging capabilities, enabling the reconstruction of events…
- RK-003Log Retention for Minimum 10 YearsArticle 18(1) requires that providers retain technical documentation and logs for at least 10 years after the high-risk AI system is placed on the market…
- RK-004Log Accessibility for Competent AuthoritiesProviders must ensure that event logs are accessible to competent national authorities and market surveillance authorities upon request, with procedures…
- RK-005Event Traceability and ReconstructionLogs must enable the tracing and reconstruction of decision events to understand the inputs processed, the outputs generated, and the conditions under…
- RK-006Performance and Operational Metrics LoggingProviders must log performance and operational metrics relevant to verifying that the AI system operates within the parameters established in the…
- RK-007Anomaly and Error Detection LoggingThe logging system must capture anomalous behaviour, errors, and unexpected outputs from the AI system in operation, enabling timely detection of…
Related EU AI Act terms
Upgrade when it needs to be
The free questionnaire returns preliminary signals. The Full Assessment turns real system material into a governed decision record - extraction, component separation, evidence, national overlays, and a review-ready dossier.
Start free risk preview