1 — Mapping method hierarchy
Every edge in the crosswalk dataset carries a method tag. Methods are used in this order of preference:
olir — NIST OLIR machine-readable Informative References (CSF 2.0 ↔ SP 800-53 r5, etc.). Authoritative.
enisa-guidance — ENISA's technical implementation guidance for NIS2 Implementing Regulation (EU) 2024/2690.
dora-l2 — Direct correspondence between DORA Level 1 articles and the Delegated / Implementing Regulations (RTS 2024/1774, RTS 2024/1772, ITS 2024/2956).
editorial — Industry-consensus mappings authored here. Always carries a rationale per edge; not official guidance from any standards body.
You can filter by method in the API: GET /api/v1/crosswalk?method=olir.
2 — Edge strength & coverage formula
Each crosswalk edge has a strength band:
| Strength | Factor | Description |
| exact | 1.0 | Same scope, same expectation; meeting one fulfils the other. |
| strong | 0.75 | Substantially overlapping; meeting one fulfils most of the other. |
| partial | 0.4 | Material overlap on a subset of expectations. |
| related | 0 | Conceptually related but not a coverage relationship. |
Coverage of target framework T given implemented source set S:
coverage(T | S) = (1 / |T|) · Σ_{t ∈ T} min(1.0, max_{s ∈ S} factor(edge(s, t)))
That is: for each target control, take the strongest applicable edge from the implemented set, cap at 1.0, then average across the target framework.
3 — Benchmark k-anonymity rule
The Anonymous Benchmarking module (when live) only returns aggregates for slices where n ≥ 20. Below that, the query falls back to the parent aggregate (e.g. NACE top-level instead of NACE division). This is stated publicly so consultants and clients can interpret the comparison correctly.