
Organizations rarely operate under a single cybersecurity framework. A SaaS provider may pursue ISO 27001 certification, receive customer requests for a SOC 2 report, and have GDPR obligations for its processing activities. NIS2 may also apply, depending on its services, sector, size, and national implementation. A defense supplier faces a different combination of standards and contractual requirements, but encounters the same engineering problem: overlapping requirements maintained as disconnected work.
Spreadsheet crosswalks help identify that overlap. They become less reliable when a row saying “related” is interpreted as “satisfied,” or when nobody can explain which document versions were compared.
The technical objective is not to eliminate framework-specific detail. It is to build a reusable mapping layer that preserves it: what can be shared, what remains uncovered, where the relationship came from, and who reviewed it.
Two NIST initiatives address different parts of this problem: the National Online Informative References Program, known as OLIR, and the OSCAL Control Mapping Model. Understanding their roles helps teams move from static crosswalks to maintainable compliance infrastructure.
Many mapping projects fail because they put three different objects in the same spreadsheet column.
A requirement describes an obligation, expectation, or desired outcome from a source document. A control describes the organization's response: an activity, technical mechanism, or management process. Evidence supports a conclusion about whether that response exists and operates as intended.
For example, several frameworks may address access management. An organization's control might require quarterly reviews of privileged access across its production environment. Evidence could include the reviewed account inventory, approval records, exception tickets, and proof that inappropriate permissions were removed.
These objects need separate relationships:
A published crosswalk normally helps with the first relationship. It does not establish the other three.
This distinction also prevents inappropriate comparisons between different kinds of assurance. ISO 27001 concerns a scoped information security management system. SOC 2 is an attestation report, not a certification. GDPR imposes obligations according to processing activities and organizational roles. A certificate or report does not establish compliance with the regulation.
Scope must therefore travel with the mapping decision. A production access review may support an assessment of the SaaS service while saying nothing about an excluded subsidiary or an unrelated HR system. Similar wording cannot bridge that boundary.
OLIR provides a standardized way for subject matter experts to describe relationships between elements of reference documents and supported NIST focal documents. Focal documents can include the NIST Cybersecurity Framework, NIST SP 800-53, or the NIST AI Risk Management Framework.
An informative reference might connect an industry requirement to a NIST CSF 2.0 Subcategory. It is an assertion about the relationship between those elements, not evidence that an organization has implemented either one.
The program adds useful context around those assertions:
NIST distinguishes three OLIR mapping styles: concept crosswalks, set-theory relationship mappings, and supportive relationship mappings. Their purposes differ. A concept crosswalk can help people navigate related ideas, while a set-theory relationship can express a more specific assertion about how two elements overlap.
For implementation planning, that difference matters. “These elements concern incident response” is useful for discovery, but insufficient to decide whether one process covers another requirement's reporting conditions, recipients, or deadlines.
Treat OLIR publication status and authorship as review inputs. A publisher-owned mapping may provide valuable insight into intended meaning, but its relevance still depends on the versions and scope under examination. Final publication should not be translated into an internal conclusion that every mapped obligation is satisfied.
The deliverable from sourcing OLIR material should be a source register: the reference used, its status, document versions, authoring party, retrieval date, and intended use. Keep the original alongside any normalized representation so reviewers can reconstruct the import.
OSCAL, the Open Security Controls Assessment Language, provides machine-readable models for control catalogs, profiles, system security plans, assessment plans, assessment results, and related compliance information. Its broader purpose is to make security documentation structured and exchangeable rather than dependent on document layout.
The OSCAL Control Mapping Model represents relationships between controls and control elements from documentary sources. It supports machine-readable representations in JSON, YAML, or XML, including relationships at a finer level than a whole control.
The model's relationship vocabulary includes equal-to, equivalent-to, subset-of, superset-of, intersects-with, and no-relationship. These should not become interchangeable labels for “roughly similar.”
| Relationship | Practical interpretation | Review question |
|---|---|---|
equal-to | An assertion that the compared elements are equal under the selected mapping basis | Are conditions and boundaries genuinely identical? |
equivalent-to | An assertion of equivalence despite differences in expression | What basis justifies treating the elements as equivalent? |
subset-of | The source element is contained within the target element | Which target expectations remain outside the source? |
superset-of | The source element contains the target element | Does that broader requirement apply to this implementation? |
intersects-with | The elements overlap without complete containment | What is shared, and what is exclusive to each side? |
no-relationship | An explicit assertion that the compared elements are unrelated | Why was the candidate rejected? |
Direction matters. A source that is a subset of a target becomes a superset when the comparison is reversed. An importer that swaps document positions without adjusting the relationship changes the meaning.
The model can distinguish mapping bases such as syntactic similarity, semantic meaning, and functional outcome. Two statements may share terminology but require different actions; differently worded statements may serve a similar security function.
It can also represent supporting context around provenance, responsible parties, status, confidence, coverage, gaps, and mapping methods. Some operational information may belong in the surrounding review system rather than a particular schema field. Follow the NIST model documentation for the representation you implement, and pin the model or schema version used by your tooling.
Machine-readable does not mean automatically correct. Schema validation can check structure and permitted values. It cannot establish that an analyst's interpretation of two requirements is sound.
OLIR is a program, publication process, catalog, and source of mapping assertions. OSCAL supplies a technical representation for storing, exchanging, and processing relationships.
An organization can therefore use OLIR as one external mapping source and OSCAL as its canonical internal representation. Other sources may include publisher-provided crosswalks, regulatory analysis, customer requirements, and internally reviewed expert mappings.
OSCAL's scope is broader than OLIR's NIST-oriented submission structure. Suitable catalogs or profiles can represent direct relationships such as IT-Grundschutz to ISO 27001, NIS2 to an internal control library, or a customer requirement to an organizational control. Such relationships do not necessarily qualify as OLIR submissions.
A practical architecture looks like this:
External and internal mapping sources
↓
Source preservation and import
↓
Document, version, and identifier resolution
↓
Normalized mapping collections
↓
Technical validation and expert review
↓
Controls, implementations, evidence, and assessments
↓
Gap analysis and change-impact work
Keep source assertions separate from internal adoption decisions. An external publisher may assert equivalence while an internal reviewer concludes that only partial reuse is appropriate for the organization's scope. Preserve both records rather than silently rewriting the external mapping.
Start with a register of obligations and assurance objectives. For each source, record the applicable version, organizational role, affected services, geographic context, assessment boundary, and reason for inclusion.
This prevents a customer expectation from being mistaken for a statutory duty. A customer subject to NIS2 may impose supply-chain requirements without making its supplier directly subject to the directive. NIS2 applicability requires its own analysis under relevant national law.
Likewise, do not add every SOC 2 category merely because it exists. Record the intended engagement scope. For ISO 27001, preserve management-system requirements, risk treatment, and Statement of Applicability decisions instead of reducing the standard to an Annex A checklist.
The output is a scope matrix that tells reviewers which mappings could be relevant before they spend time interpreting them.
Resolve each imported identifier against the correct document edition. Preserve clause hierarchy, control identifiers, statement identifiers where available, and the original reference location.
A useful internal key combines document identity, version, and element identifier. A display label alone is unsafe: identical control numbers can have different meanings across editions or publications.
Break compound requirements into reviewable elements when necessary. If one paragraph requires a policy, assigned responsibilities, testing, and reporting, a single whole-paragraph mapping may hide three uncovered expectations. Retain the parent relationship so users can reconstruct the source context.
Respect publication and licensing conditions when storing source text. Where full-text storage is inappropriate, retain permitted identifiers, references, and original analytical notes.
Candidate generation can use existing crosswalks, shared terminology, security objectives, or AI-assisted analysis. Its output should be a review queue, not an approved mapping collection.
For each consequential assertion, reviewers should examine the actual elements and record:
Confidence is useful for prioritizing review, but it is not a coverage percentage. A reviewer can be highly confident that two requirements only partially overlap. Keep confidence in the assertion separate from implementation status and evidence sufficiency.
Rejecting a candidate is also valuable. Retaining a documented no-relationship decision helps stop future imports or automated suggestions from repeatedly presenting the same misleading match.
Run technical checks before approval: unresolved references, missing versions, invalid relationship values, duplicates, and unexpected direction reversals should all be visible.
Then conduct semantic review. Ask whether the relationship preserves the actor, required action, protected object, timing, conditions, and expected outcome. For legal requirements, involve someone qualified to assess the obligation rather than relying solely on security-domain similarity.
Use workflow states such as proposed, under review, approved for a defined use, rejected, and superseded. These are practical operating recommendations, not universal statutory requirements. An approval should specify what it permits: discovery, planning, evidence reuse, or support for an assessment conclusion.
Before putting normalized mappings into reporting, build a small regression fixture with deliberately difficult cases: a reversed subset relationship, an unresolved statement identifier, two conflicting source assertions, and a mapping to a superseded edition. Define the expected result for each case. An import should quarantine ambiguous records rather than silently choose the newest-looking document or discard the conflicting assertion.
Test repeat imports as well. Importing the same collection twice should not create duplicate work or overwrite an internal approval. Use stable identities and retain revision history so a changed external assertion becomes a review event, not an invisible replacement.
For interchange, test a round trip: export an approved sample, import it into a clean test environment, and compare identifiers, direction, rationale, and provenance. If workflow metadata cannot travel in the chosen representation, document the accompanying format and its limitations. Otherwise, a technically valid export may lose precisely the context that made the mapping trustworthy.
These are practical engineering safeguards. They make automation predictable without pretending that software tests can validate the underlying legal or security interpretation.
Once requirement relationships are understood, define a common control library around real operational activities. Domains such as identity, vulnerability management, incident response, supplier assurance, and recovery are useful starting points.
Each control needs an accountable owner and an implementation description that another engineer can execute. “Access is reviewed regularly” is too vague. Specify the covered systems and account types, reviewer, cadence, decision criteria, exception process, and evidence produced.
Do not assume the “strictest requirement” automatically satisfies everything else. Requirements can be incomparable: longer log retention may help an assurance objective while creating privacy questions about necessity and access. Higher review frequency cannot replace a missing legal assessment.
Use a shared baseline plus explicit additions:
| Control area | Potentially reusable implementation | Separate assessment or addition |
|---|---|---|
| Access management | Provisioning, authentication, permission reviews, removal | Coverage of particular systems, identities, and assessment periods |
| Recovery | Backups, restore procedures, recovery exercises | Required recovery objectives and service-specific test coverage |
| Supplier management | Inventory, security assessment, review ownership | GDPR processor-contract terms and separate transfer analysis |
| Incident response | Detection, triage, containment, investigation | Legal triggers, recipients, deadlines, and reporting content |
| Risk assessment | Asset and dependency context, treatment tracking | Risks to individuals and processing-specific privacy analysis |
Under GDPR, security of processing is risk based. Shared security controls may support Article 32, but lawful basis, transparency, processing records, individual rights, DPIAs where required, and international transfers need their own assessment. An asset inventory can inform a processing record without replacing its purposes, data categories, recipients, and retention information.
ISO 27001 similarly includes management-system work that cannot be inferred from operational controls alone. Scope, risk treatment, the Statement of Applicability, internal audit, and management review are distinct deliverables.
A central repository reduces duplication only if reviewers understand what each artifact proves.
As a practical recommendation, record evidence ownership, collection date, covered period, affected systems, source, version, access restrictions, and the conclusion it supports. Keep the underlying artifact separate from the assessment statement.
A quarterly access-review export might show which permissions existed on a date. The approval record shows who reviewed them. Remediation tickets show whether inappropriate access was removed. None of those artifacts alone necessarily demonstrates the complete control.
Time also changes reuse. A SOC 2 Type II engagement examines operation across a period, while a point-in-time artifact covers a narrower interval. When designing collection, distinguish control frequency, assessment period, and artifact freshness. A recent screenshot does not reconstruct months of missing execution records.
Assessment scope matters equally. Confirm that the evidence covers the relevant service, population, environment, and control variation. Separate customer-managed permissions from provider-managed administrative access rather than treating one export as evidence for both.
Evidence can contain sensitive information or personal data. Apply appropriate access controls, minimize unnecessary content, and define retention deliberately. Reusing an artifact does not mean distributing its unrestricted original to every reviewer.
The deliverable is an evidence plan for each common control: what is collected, when, from where, by whom, and which assessment questions it can support.
Coordinate that plan with a shared assurance calendar. Schedule related owner interviews and evidence checks together where their scopes align, while retaining separate assessment conclusions. Agree evidence expectations with the relevant assessors before relying on reuse. A common collection process can support several engagements, but it cannot force each assessor to accept the same sample or eliminate additional testing. For periodic controls, schedule collection at execution time rather than waiting until the audit approaches.
Consider an illustrative SaaS organization with 45 employees. Assume its production service is within an ISO 27001 ISMS scope, it is preparing for a SOC 2 Security engagement, and it processes personal data as both controller and processor in different activities. Also assume an applicability assessment has established NIS2 duties under the relevant national implementation.
These are scenario assumptions, not claims about typical staffing, legal applicability, or project effort.
The organization imports mapping candidates around incident management and defines a common control, IR-01: reported security events are triaged, assigned an incident owner, investigated, contained, and documented through closure.
That control is useful across the program, but the mapping review identifies several distinct elements:
| Element | Shared work | Additional requirement-specific work |
|---|---|---|
| Detection and triage | Incident ticket, severity assessment, response owner | Determine which legal and contractual triggers need assessment |
| Investigation | Timeline, affected systems, impact, containment records | Establish personal-data roles and significant-incident criteria |
| Notification | Approved communication workflow and contact register | Apply the correct recipients, clocks, content, and exceptions |
| Closure | Recovery evidence and lessons learned | Complete required follow-up reports and document decisions |
The team therefore maps specific incident-process elements rather than asserting that IR-01 fully satisfies every related obligation.
For personal-data breaches, GDPR Article 33 distinguishes roles. A processor notifies the controller without undue delay. A controller assesses supervisory notification without undue delay and, where feasible, within 72 hours after awareness, unless the breach is unlikely to create a risk to individuals' rights and freedoms. High risk can require communication to individuals under Article 34, subject to its exceptions.
For significant incidents under NIS2 Article 23, the EU reporting structure includes a 24-hour early warning, a 72-hour notification, and generally a final report within one month of notification. The organization checks applicable national and sector rules rather than treating this summary as its complete reporting procedure.
The incident record consequently holds separate trigger assessments and awareness timestamps. Where several duties apply, their clocks run in parallel. ISO-oriented containment work does not postpone a legal reporting decision.
The evidence package includes the ticket history, decision log, communications approvals, submission records where notification occurred, and reasoning where notification was not required. A tabletop exercise tests the branching logic with security, legal, service operations, and communications participants.
The mapping outcome is precise: reuse the response machinery, preserve the distinct reporting obligations, and assess both implementation and evidence. The remaining gaps become owned tasks—for example, an untested regulator contact route or missing processor-to-controller escalation instructions.
A mapping library becomes unreliable if it only records the framework names used at initial setup.
When a source changes, compare more than identifiers. Requirements can be split, merged, renamed, expanded, or moved without an obvious numbering signal. Create a document-level change record and identify every mapping connected to changed elements.
A practical update sequence is:
Operational changes should trigger the same process. Adding a cloud provider, changing identity architecture, or moving a service into scope can invalidate evidence reuse even when the framework has not changed.
Derived mappings require particular care. OLIR can produce Derived Relationship Mappings by comparing how two reference documents relate to a shared focal document. NIST describes these as non-authoritative starting points, not verified direct crosswalks. If A relates to C and B relates to C, that does not establish that A and B are equivalent.
Use derived relationships to prioritize investigation. Do not propagate compliance conclusions through a graph merely because a path exists.
Choose one representative service and a few control areas with both meaningful overlap and visible differences. Access reviews, supplier management, and incident response make useful candidates because they expose scope, ownership, evidence, and legal interpretation issues.
The pilot should produce a bounded set of inspectable deliverables:
Evaluate the pilot by whether another reviewer can reproduce its conclusions. Can they explain why a relationship was approved, locate the relevant source, identify uncovered expectations, and see which systems the evidence covers?
Common mistakes include mapping entire control domains as equivalent, hiding exceptions in comments, leaving shared controls without a primary owner, and confusing evidence availability with effective operation. Another is building a large mapping library before testing whether it supports an actual assessment.
In Secani, a grounded starting workflow is to model the representative service and its supporting target objects, name owners and reviewers, and connect existing evidence to requirements, controls, and decisions. Missing material and unresolved questions become tasks. AI-assisted suggestions remain draft work until a person checks sources and approves the decision with a traceable record. Secani's connected-evidence and review approach keeps mapping decisions attached to their sources, owners, and implementation context.
For a concrete framework pairing, see NIS2 and ISO 27001.
Yes. A spreadsheet can be a review interface if it preserves versions, direction, rationale, scope, and provenance. The limitation is not the grid itself, but weak validation, disconnected evidence, and difficult change management. Define the data model before choosing the interface.
No. Confidence in a generated suggestion is not an accountable review decision. Use AI to surface candidates and differences, then require human approval for consequential mapping and evidence conclusions.
Take one existing crosswalk row and reconstruct its reasoning. Identify both source versions, read the mapped elements, state the relationship and direction, document the uncovered delta, and connect it to a real control and evidence package. If that record survives independent review, repeat the method across the pilot. That is the foundation of reusable compliance infrastructure.

OSCAL · July 19, 2026 · 8 Min.
Every OSCAL validator claims to validate OSCAL. We enumerated all 348 constraint occurrences in the NIST sources, proved or excluded each one, and then ran the comparison against the Java CLI for real.

OSCAL · July 14, 2026 · 7 Min.
OSCAL turns compliance documents into structured data: eight document models, three formats, and an ecosystem that is becoming the standard for regulation.

OSCAL · July 16, 2026 · 6 Min.
With RFC-0024 and the Consolidated Rules 2026, FedRAMP makes structured authorization data mandatory. The deadlines are staggered – the direction is unambiguous.
Secani connects scopes, evidence, tasks, and AI agents in one shared workspace.