[non-validated] DORA SFS 3 / SF C: Data Integrity & Availability Protocols (Unverified Draft)
Generated catalog draft. No operational assessment or human approval is claimed.
[non-validated] This question has unresolved selected work.
Question
[non-validated] Has the entity implemented documented data integrity verification mechanisms and availability safeguards for information assets as required by the repository's DORA topic boundaries for Protection, access and data security?
Explanation
[non-validated] Has the entity implemented documented evidence of data integrity verification mechanisms (e.g., checksum validation) and availability safeguards (e.g., redundancy systems) as specified in the repository's 'DORA: Protection, access and data security' topic boundaries for the current review period?
Criterion and evidence
Assess documented evidence covering data integrity verification (e.g., checksum procedures, audit logs) and availability safeguards (e.g., failover systems) per repository topic description requirements. Apply relevant standard/simplified framework per proportionality provisions. Evidence must cover current supervisory review period; absence of documented evidence remains pending and does not constitute automatic failure. Alternatives: Validated implementation under simplified framework per Article 15(3) where entity classification criteria apply (repository sources lack specific classification guidance).
AI assistance prompt
Develop sixteen bounded yes/no factors for DORA: Protection, access and data security. Protect ICT systems and information through proportionate access, data and network safeguards. Cover identity and access controls, authentication, least privilege, cryptography, data security, physical/environmental safeguards and network segregation. Apply the relevant standard or simplified framework. SFS 4 owns change/patch lifecycle; SFS 5 owns detection. DORA article references: 9, 15. Verify entity-role applicability and current primary sources. Missing evidence stays pending; no compliance or assessment is implied.
Clarifications
What constitutes sufficient evidence for data integrity and availability verification?
Documented evidence must reference repository topic description requirements: e.g., implementation records for checksum validation procedures and redundancy/failover systems dated within the current review period. Missing evidence remains pending; automatic negative outcome is excluded per repository boundaries. Simplified framework applies only when entity classification criteria are verified (repository sources lack implementation guidance for this determination).
References
DORA: Protection, access and data security