Join our Newsletter — 33% off our NHI Course
Home› Guides› NIST CSF 2.0 Informative References and OLIR Guide:…
Guide Regulations & Frameworks

NIST CSF 2.0 Informative References and OLIR Guide: Finding and Using Official Crosswalks

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Most teams that map NIST CSF 2.0 to SP 800-53, ISO/IEC 27001 or CIS Controls rebuild a crosswalk by hand that NIST already publishes, or reuse a vendor spreadsheet without knowing who wrote it or how it was checked. Informative references are the NIST mechanism for recording how elements of one document relate to another, and the National Online Informative References (OLIR) Program is where they are submitted, reviewed, stored and compared. This guide explains what an informative reference is, the three ways to get CSF 2.0 references (the Excel download, the CSF 2.0 Reference Tool built on CPRT, and the OLIR catalog), how to read the relationship fields defined in NIST IR 8278A Rev. 1, what NIST does and does not check, and how to turn references into an Organisational Profile and evidence plan. It is for GRC analysts, control owners, auditors and anyone asked to prove "we already meet that". General mapping method and choice of anchor framework are covered in the Control Mapping Guide; this page is about the NIST sources themselves.

Key takeaways

  • Informative references are crosswalks, not requirements. NIST describes them as mappings that show how an organisation may achieve CSF 2.0 Core outcomes; meeting a mapped control is evidence towards an outcome, not proof of it.
  • Three access routes serve different jobs. The Excel download is quickest for a snapshot, the CSF 2.0 Reference Tool (built on the Cybersecurity and Privacy Reference Tool, CPRT) filters and exports Excel or JSON, and the OLIR catalog covers more focal documents and produces comparison reports.
  • Read who wrote the mapping. Both NIST and non-NIST entities submit references; NIST runs limited conformance testing against IR 8278A Rev. 1 but does not test non-NIST mappings for correctness, and listing is not endorsement.
  • Relationship fields carry the meaning. A set theory mapping says whether a reference element is a subset of, intersects with, equals, is a superset of or is not related to the CSF element, with a rationale and an optional strength from 0 to 10.
  • Derived mappings are a starting point only. NIST states that Derived Relationship Mappings (for example ISO to SP 800-53 through CSF) are non-authoritative.

What informative references are, and what they are not

NIST SP 1347, the CSF 2.0 Informative References Quick-Start Guide, describes informative references as records of relationships between elements of two or more cybersecurity documents, so practitioners can see where standards overlap. Within CSF 2.0 each reference points to the parts of another document where a reader can learn more about achieving an outcome. In OLIR terms the NIST document is the focal document (here CSF 2.0) and the other is the reference document (for example ISO/IEC 27001:2022).

ItemWhat it isWhere it livesUse it for
CSF 2.0 Core outcomeFunction, Category and Subcategory statements such as PR.AA-01CSF 2.0 publication and Reference ToolWhat to achieve
Implementation ExampleShort, action-oriented illustrations attached to Subcategories (for PR.AA-01 one example is to issue, manage and revoke certificates, identity tokens, keys and other credentials)CSF 2.0 Reference Tool and Excel snapshotIdeas for how to achieve an outcome
Informative ReferenceA mapping from Subcategories to elements of another documentOLIR catalog, Excel download, Reference ToolWhich controls in your chosen framework relate to the outcome
Derived Relationship MappingA computed comparison of two reference documents through a shared focal documentOLIR DRM toolA first draft for reference-to-reference comparison, to be checked by hand
Organisational ProfileCurrent and Target state of selected outcomes for your organisationYour GRC recordsPrioritising gaps; references supply control detail

Why it matters for evidence: SP 1347 lists three practical uses: seeing which requirements a new control would satisfy, which requirements are already met, and which may conflict when adopting a new standard. That is the "test once, comply many" claim, and informative references let you trace it to a published source rather than an internal assumption.

Three ways to get CSF 2.0 references

RouteWhat you getStrengthsWatch for
Excel download (Informative References page)All published CSF 2.0 informative references in one English .xlsx, with translations of the core available in several languagesFast, offline, easy to pivotA snapshot: re-download when references are added or updated
CSF 2.0 Reference ToolBrowser tool on CPRT: filter by reference, select rows, export Excel or JSONMachine-readable; good for loading into a GRC platformChoose the reference version explicitly before export
OLIR Informative Reference CatalogEvery listed OLIR across focal documents (CSF 1.1 and 2.0, Privacy Framework, SP 800-53 Rev. 5, NISTIR 8259A and others), plus the cross-reference comparison report and DRM toolMost customisable; shows developer, status and historySP 1347 notes that exports may lag behind current data

CPRT itself is the NIST project that holds reference data from NIST cybersecurity and privacy standards, guidelines and frameworks in structured form, downloadable as XLSX and JSON. If your tooling consumes OSCAL or JSON catalogues, CPRT exports avoid copying from PDFs.

References currently listed for CSF 2.0

The NIST Informative References page lists, among others, mappings for SP 800-53 Rev. 5 (release 5.2.0), SP 800-171 Rev. 3, CIS Controls v8.1, ISO/IEC 27001:2022 (two entries), PCI DSS 4.0.1, the Cloud Controls Matrix v4.0, the CRI Profile v2.0, the NICE Framework v2.0.0, the Secure Controls Framework, the Cyber Governance Code of Practice and the OWASP Top 10 for LLM Applications, alongside a number of smaller community and vendor submissions. The list changes as submissions complete review, so check the page rather than relying on this snapshot. For the SCF, see the Secure Controls Framework Guide.

Reading the relationship fields (IR 8278A Rev. 1)

NIST IR 8278A Rev. 1, Submission Guidance for OLIR Developers (final, February 2024), defines the OLIR template and three concept relationship styles. Knowing them is the difference between "mapped" and "equivalent".

StyleRelationship valuesWhat it tells you
Concept crosswalkNo characterisation: elements are simply linkedRelated topic only; never treat as coverage
Set theory relationship mappingsubset of, intersects with, equal, superset of, not related to; rationale syntactic, semantic or functionalHow much of one element the other covers, and on what basis (syntactic is strictest, functional loosest)
Supportive relationship mappingsupports, is supported by, identical, equivalent, contrary, no relationship; optional properties example of, integral to, precedesWhether achieving one concept helps achieve the other
  • Strength of relationship: an integer from 0 to 10, where equal is 10 and not related to is 0. Subset, superset and intersects relationships score 7 to 9 when much more similar than dissimilar, 4 to 6 when roughly balanced and 1 to 3 when much more dissimilar. It applies to lateral documents only and is N/A otherwise.
  • Template fields: Table 2 of IR 8278A Rev. 1 lists fields such as Focal Document Element, Reference Document Element, Rationale, Relationship, Relationship Type, Relationship Explanation, Relationship Property, Security Control Baseline, Comments and Strength of Relationship.
  • Practical rule: for audit reuse, rely on "equal" or "superset of" with a semantic or syntactic rationale. "Intersects with" means you must check what the reference element leaves out.

Derived mappings and comparison reports

The OLIR Derived Relationship Mapping tool lets you choose a focal document and several reference documents, generate a display report and download it as CSV or JSON (JSON schema version 1.2). The common use is to compare two non-NIST documents, such as ISO/IEC 27001 and CIS Controls, through their shared CSF mappings. NIST states that DRMs are non-authoritative and a starting point. The cross-reference comparison report does a similar job for coverage: which focal elements each reference touches.

  • Why derived links mislead: if ISO control X intersects CSF outcome A, and CIS safeguard Y intersects the same outcome, X and Y may share nothing beyond the topic. Two "intersects" links do not make an equivalence.
  • When DRMs are worth it: scoping a gap analysis quickly, for example finding which CIS safeguards have no ISO counterpart at all, before an analyst confirms each pair.
  • When to use a direct mapping instead: where a direct, published mapping exists between the two documents, prefer it. For ISO and CSF together see the NIST CSF to ISO 27001 Mapping Guide, and for SP 800-53 to ISO see the NIST SP 800-53 to ISO 27001 Mapping Guide.

Turning references into a profile and evidence plan

SP 1347 gives two use cases: tracing from a NIST source (SP 800-221A on ICT risk) through CSF 2.0 to SP 800-53 controls, and comparing CSF 2.0 with ISO/IEC 27001:2022 to find gaps and conflicts and build a Target Profile. A repeatable workflow:

  1. Pick the frameworks you must evidence. Usually the one you are certified or assessed against (ISO, SP 800-53, PCI DSS) plus CSF 2.0 for reporting.
  2. Download the references and record versions. Note the reference name, version and download date in the working file so later reviewers can reproduce it.
  3. Filter to your Profile scope. Select the CSF Subcategories in your Organisational Profile; drop the rest.
  4. Classify each link. Use the relationship and strength fields to mark each as full reuse, partial reuse (needs extra evidence) or topic only.
  5. Assign evidence once. For each control in your anchor framework, define one evidence item and list the outcomes it supports.
  6. Review conflicts. Where the reference documents require different values (review frequency, retention, key length), adopt the stricter one or document the exception.
  7. Re-check on change. When NIST posts a new reference version or a framework is revised (SP 800-53 releases, CIS updates), diff the reference and update the classification.

Small organisations: the Excel download and one anchor framework are enough; DRMs add little. Large or multi-regime organisations: load CPRT JSON exports into the GRC platform, keep the classification as data and automate the diff when references change.

AI-assisted mapping: SP 1347 includes guidance that AI-generated mappings should be reviewed by subject matter experts. Treat model output as a concept crosswalk until a person has assigned relationship and rationale.

Where identity fits

CSF 2.0 places identity in PR.AA Identity Management, Authentication, and Access Control. PR.AA-01 reads "Identities and credentials for authorized users, services, and hardware are managed by the organization", which explicitly includes services, and PR.AA-05 covers access permissions with least privilege and separation of duties. When you read the informative references for these Subcategories, check whether the mapped controls in your anchor framework actually cover non-human identities. Many control texts were written with human users in mind, so a "superset of" relationship on paper can still leave service accounts, API keys and workload identities without an owner or review. Add explicit evidence for them. See the Non-Human Identity (NHI) Guide and the Audit Readiness for AI Agents and NHIs.

CSF 2.0 SubcategoryQuestion to ask of each mapped controlEvidence to add for NHIs
PR.AA-01 identities and credentials managedDoes the control cover services and hardware, or only workforce users?Inventory of service accounts, keys and certificates with owner and expiry
PR.AA-05 permissions defined, managed, enforced and reviewedDoes the review include machine entitlements and token scopes?Periodic entitlement review output for non-human identities
ID.AM-01 hardware inventories maintainedIs device identity linked to the asset record?Device certificate or identifier per asset
GV.SC-04 suppliers known and prioritisedAre supplier integrations and their credentials part of supplier records?List of third-party OAuth apps and API connections per supplier

This table is NHI Mgmt Group's own guidance on reading references, not part of any NIST informative reference.

Submitting an OLIR

  • Start from the focal document template: NIST provides an .xlsx template per focal document (CSV and JSON may also be released) on the Focal Document Templates page.
  • Follow IR 8278A Rev. 1: complete the template fields and the general information (reference document, informative reference name, whether it is comprehensive) in the submission tool.
  • Expect public review: NIST holds a 30-day public review of a draft candidate OLIR; the developer then has 30 days to respond to comments. Minor changes to a listed OLIR also trigger a 30-day comment period.
  • Understand what review means: NIST checks conformance with the submission guidance, not the correctness of a non-NIST mapping. Consumers must still judge quality.

Measuring whether it works

  • Provenance coverage: percentage of mapping rows in your GRC tool that cite a named, versioned informative reference rather than an internal assumption.
  • Classification completeness: share of mapped pairs with a recorded relationship and reuse decision (full, partial, topic only).
  • Evidence reuse ratio: average number of framework requirements satisfied per evidence item, tracked so it does not rise on weak links.
  • Audit challenge rate: number of mapped claims an auditor rejects per cycle, ideally trending to zero.
  • Currency: days between a NIST reference update and your mapping refresh.

Common failure patterns

  • Treating a concept crosswalk as coverage: a topic link is presented to auditors as equivalence and fails on the first sample.
  • Chaining derived mappings: ISO to CSF to SP 800-53 links are used as an official ISO to SP 800-53 mapping, against NIST's own non-authoritative warning.
  • Ignoring authorship: a vendor or community submission is used as if NIST authored it. Check the developer field.
  • Stale versions: a CSF 1.1 mapping or an older SP 800-53 release is still driving evidence after the reference was updated for CSF 2.0 or SP 800-53 Rev. 5.2.0.
  • Human-only reading of identity controls: PR.AA mappings are marked complete although no control evidence covers service accounts or workload identities.
  • Unreviewed AI output: a model-generated crosswalk enters the GRC tool without an analyst assigning relationships.

Practitioner checklist

  • Download the CSF 2.0 informative references and record name, version and date for each one you use.
  • Prefer NIST-authored references; check the developer field for every non-NIST one.
  • Classify each pair using the set theory relationship, rationale and strength fields.
  • Rely on "equal" or "superset of" for evidence reuse and add evidence for "intersects with".
  • Treat Derived Relationship Mappings as a draft and confirm each pair by hand.
  • Use CPRT JSON exports to load references into GRC tooling rather than copying from PDFs.
  • Check that PR.AA mappings are evidenced for non-human identities as well as users.
  • Re-check mappings whenever NIST posts a new reference version.

Standards and references

Related NHI Mgmt Group resources: Control Mapping Guide · NIST CSF to ISO 27001 Mapping Guide · NIST SP 800-53 Guide · Secure Controls Framework Guide · Audit Evidence and Continuous Controls Monitoring Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.