← GRC Hub
Cross-framework Control Crosswalk
Implement once, comply many. 623 edges connecting NIST CSF 2.0, SP 800-53 r5 Moderate, ISO 27001:2022 Annex A, DORA Level 1 + RTS 2024/1774, NIS2 Article 21 + IR 2024/2690, GDPR security and CRA Annex I.
Dataset v1.0.0 · reviewed 2026-06-10 ·
methodology & method hierarchy →
gdpr_security · art25 — Data protection by design and by default (Art. 25)
iso_27001_2022
- A.8.25 — Secure development life cycle (partial, editorial): Privacy by design parallels secure development.
- A.8.27 — Secure system architecture and engineering principles (strong, editorial): Architecture for privacy.
nist_csf_2_0
- PR.PS-06 — Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle. (strong, editorial): Privacy by design ↔ secure development.
- ID.AM-07 — Inventories of data and corresponding metadata for designated data types are maintained. (strong, editorial): Data inventories for designated data types.
Pivot: corresponding controls per target framework
Framework pair: full mapping
Coverage: if I implement X, how much of Y do I cover?
Tick the controls you have implemented in your source framework. The page computes coverage against each target framework using the formula exact = 1.0, strong = 0.75, partial = 0.4, related = 0, capped at 1.0 per target control.
Informational only — not legal advice. Mapping method hierarchy (in order of preference): NIST OLIR machine-readable mappings → ENISA NIS2 implementation guidance → DORA Level 2 RTS/ITS → editorial. Every edge in this dataset is labelled with its
method tag — filter or sort by it on the methodology page.