Map Your Own Controls
Map your controls to NIST SP 800-53 once, and see where they land in 96 frameworks.
Most organisations write their own security controls. Regulators, auditors and customers then ask about them in their own terms: NIS2, ISO 27001, DORA, PCI DSS, SOC 2 and many more. OSA maps 96 frameworks to NIST SP 800-53, the control catalogue behind every OSA pattern. Map your controls to SP 800-53 once, and OSA lines them up against any of those frameworks, clause by clause, and shows you the gaps.
How it works
- Give your AI agent your control list and OSA's skill for agents. The agent maps each of your controls to SP 800-53 and quotes your control text for every match. Where a published crosswalk exists, it checks its work against that too.
- You review the agent's table and make any corrections.
- Your agent sends the SP 800-53 ids to OSA. For each framework you name, OSA returns the matching clauses and the gaps, with the SP 800-53 controls that map to each gap.
- You check each matching clause against the framework's own text to confirm your control covers it in full.
To start, copy this into your agent and fill in your own file and frameworks:
Read https://www.opensecurityarchitecture.org/skills/osa-control-mapping/SKILL.md and follow it. Map the controls in [our control list] to NIST SP 800-53, then line them up against [the frameworks we need, such as NIS2 and ISO 27001:2022] and show me the matching clauses and the gaps.
You can name any of the 96 frameworks OSA maps, as many as you like.
A worked example
OSA's Information Security Policy template uses 63 SP 800-53 controls. Here is how they line up against three of the 96 frameworks:
| Framework | Clauses | Matched | Gaps |
|---|---|---|---|
| NIS2 Directive | 14 | 14 | 0 |
| ISO 27001:2022 | 117 | 90 | 27 |
| EU DORA | 68 | 54 | 14 |
For each gap, OSA lists the SP 800-53 controls that map to that clause. In ISO 27001:2022, for example, 6.1.3 (Risk treatment planning and the Statement of Applicability) is a gap, and RA-07 maps to it.
ISO 27001:2022: 27 gaps
- 6.1.3Risk treatment planning and the Statement of Applicability Controls that map to it: RA-07
- 6.3Planning changes to the ISMS
- 7.1Providing the resources the ISMS needs Controls that map to it: PM-03
- 7.2Competence of people whose work affects security Controls that map to it: PM-13
- 8.3Carrying out the risk treatment plan
- 10.2Corrective action on nonconformities and their root causes
- A.5.6Joining special interest groups and security forums
- A.5.7Gathering and analysing threat intelligence
- A.5.9Inventory and ownership of information and related assets Controls that map to it: CM-08
- A.5.24Setting up incident management plans and roles Controls that map to it: IR-08
- A.5.32Intellectual property rights and software licence compliance Controls that map to it: CM-10
- A.6.1Background screening before joining and during employment
- A.6.2Security responsibilities in employment contracts
- A.6.4Disciplinary process for security policy breaches Controls that map to it: PS-08
- A.6.6Non-disclosure agreements to protect confidential information Controls that map to it: PS-06
- A.7.5Protecting sites from physical and environmental hazards
- A.7.6Rules for work inside secure areas
- A.7.7Rules for a clear desk and a clear screen
- A.7.8Siting equipment securely and protecting it from hazards
- A.7.11Reliable supporting utilities, such as power and cooling
- A.7.12Security of power and data cabling
- A.7.13Secure and timely equipment maintenance
- A.8.5Secure authentication methods, such as multi-factor sign-in
- A.8.11Data masking, such as pseudonymisation and anonymisation
- A.8.17Clock synchronisation to a trusted time source Controls that map to it: AU-08
- A.8.19Controlling what software is installed on operational systems
- A.8.34Planning audit testing to protect live systems
EU DORA: 14 gaps
- Art.5(2)Governance and organisation — management body approval of digital operational resilience strategy
- Art.6(8)ICT risk management framework — documentation and review availability
- Art.9(2)Protection and prevention — ICT system resilience and availability
- Art.11(2)Response and recovery — recovery time and point objectives
- Art.15Simplified ICT risk management framework — proportionality for smaller entities
- Art.16Further harmonisation of ICT risk management tools, methods, processes, and policies
- Art.17(3)(d)ICT-related incident management process — training and communication
- Art.22(1)Supervisory feedback on incident reports Controls that map to it: IR-07
- Art.26Advanced testing — threat-led penetration testing (TLPT)
- Art.27Requirements for TLPT testers — qualifications and independence
- Art.28(7)ICT third-party risk management — incident notification by providers Controls that map to it: SR-08
- Art.28(8)ICT third-party risk management — exit strategies Controls that map to it: SR-12
- Art.30(2)(g)Key contractual provisions — termination and data return Controls that map to it: SR-12
- Art.45(1)Information-sharing arrangements — voluntary sharing of cyber threat intelligence
The same result as JSON: /api/v1/crosswalk?controls=…&framework=nis2,iso_27001_2022,dora
Reading the result
Each matching clause is a place to check. OSA maps whole controls to whole clauses, so read the framework's own text to confirm your control covers everything the clause asks for. NIS2 is mapped article by article, so a broad set of controls matches most of it. Each gap is worth a look too: you may already meet the clause another way, and the controls listed with it are a good place to start.
Seven of OSA's mappings start from a published crosswalk to SP 800-53: HIPAA Security Rule, ISO 27001:2022, ISO 27002:2022, NERC CIP, NIST SP 800-171 Rev 3, NIST CSF 2.0 and NIST SSDF 1.1. Each labels the pairs OSA adds.
Use SP 800-53 base controls such as AC-02 rather than enhancements such as AC-2(1). For a control NIST has withdrawn, OSA names the controls that replaced it.
Your data
Your control text stays on your machine. Your agent sends OSA just the SP 800-53 ids, and OSA uses them only to build the answer. Every mapping is also published in osa-data under CC BY-SA 4.0, so you can work out the same result offline.
For agents
- The method: /skills/osa-control-mapping/SKILL.md
- The route: /api/v1/crosswalk?controls=AC-02,IA-02,SI-04&framework=nis2,iso_27001_2022, up to 320 controls and five frameworks a request. Framework ids: /api/v1/frameworks.
- All routes: /llms.txt and /openapi.yaml.
Tell us
Spotted a mapping that differs from its source? Please raise an issue with what OSA says and what the source says. And if you map your own controls this way, we'd love to hear how it went.