SIS-licensed ISO clauses and controls·an add-on inside the AI clients and agents you already use
    See the standards module →
    Use casesSecurity

    ISO 27001 → NIST CSF 2.0 through the canonical control library

    An ISO/IEC 27001:2022-certified company must report security posture to its US parent on NIST CSF 2.0. Instead of maintaining a hand-built mapping spreadsheet, the team asks Ansvar's control library to walk Annex A.5.26 (incident response) through the canonical control spine to CSF 2.0 — with the provenance of every mapping edge, and an honest line on what the library will and will not claim.

    Citations5
    Tool calls4
    Captured withclaude-fable-5

    How the gateway answered

    Captured 4 August 2026 — a point-in-time run; corpora and tools have been updated since.

    Editor's note. Tool calls, results, citations and the trace on this page are a real gateway session (company tier, 4 August 2026). The narrative answer was composed from those results for readability rather than pasted verbatim from the run.
    Captured sessionclaude-fable-5 · company tier · gateway.ansvar.eu
    You

    Using Ansvar: we're ISO 27001:2022-certified and our US parent reports on NIST CSF 2.0. Which canonical control sits behind Annex A.5.26, where does it land in CSF 2.0, and what's the provenance of each mapping?

    Ansvar gateway — 4 tool calls
    crosswalk(from_framework="iso27001" from_ref="A.5.26" to_framework="nist-csf")→ 24 CSF 2.0 subcategories via pivot control IR-4 — every path a review-approved NIST OLIR related-to edge with stored direction, confidence and OLIR sheet-row source_ref; navigation links only, no coverage claim derived
    get_control(control_id="IR-4")→ IR-4 Incident Handling — full 800-53r5 statement + discussion, 29 approved mappings: ISO 27001:2022 ×3, CSF 2.0 ×24, 800-171 r3 ×1, plus the 800-53 identity edge
    resolve(requirement_id="nis2:2022#art-21")→ Citation descriptor: 'Cybersecurity risk-management measures', normative/active, EUR-Lex ELI URL, live gateway resolution via get_provision(EU, NIS2, art. 21) against eu-regulations; licence EUR-Lex-Decision-2011-833
    coverage()→ Library state: 23 frameworks, 1,196 controls, 2,360 mappings loaded (catalog 800-53r5 5.2.0); NIS2 register carries 48 normative requirements; cross-framework set-theory typing pending human review — coverage counts stay at zero until reviewed, by design
    Cited answer

    Where ISO 27001 incident response lands in NIST CSF 2.0

    The question. We hold ISO/IEC 27001:2022 certification; our US parent reports on NIST CSF 2.0. Which canonical control sits behind Annex A.5.26 (response to information security incidents), where does it land in CSF 2.0, and what is the provenance of each mapping?

    The pivot: one canonical control. The control library resolves ISO/IEC 27001:2022 Annex A.5.26 onto the canonical spine at IR-4 — Incident Handling (NIST SP 800-53 Rev 5, catalog release 5.2.0). The edge is a NIST OLIR informative reference — the SP 800-53 Rev 5 → ISO/IEC 27001:2022 mapping, 2023-10-12 update, sheet IR row 22 — carried in the library as a review-approved related-to edge with provenance_origin: nist-published. …

    Download PDFDownload Markdown

    Every claim traces to a source you can open

    A typical AI assistant invents a citation that looks plausible. Ansvar retrieves the real one. Every finding above rests on one of these 5 sources — official legislation, standards clause maps, standard mapping, framework, and control catalog — linked wherever the source is publicly reachable; catalog rows served through the gateway are quoted as fetched. No citation is fabricated — every source was retrieved through Ansvar and can be checked.

    Run this on your own data

    Bring your own documents and scope, and we'll run it end-to-end — every finding cited and validated by the expert who delivers it.

    See the coverage behind this run on the IT & cloud security sector page.