Crosswalk pair
ISO/IEC 42001 and NIST Cybersecurity Framework, control by control
10 canonical controls in Keel’s library satisfy clauses of both ISO/IEC 42001 and NIST Cybersecurity Framework. Implement each once, attach the evidence once, and it counts toward each standard. The overlap is the work you don’t repeat.
The overlap
What the two libraries have in common
Every figure here counts canonical controls in Keel’s library, not clauses of either standard. Each standard’s own authored count is on its framework page.
10
Controls that satisfy both
Canonical controls that crosswalk to at least one clause of each.
38
In Keel’s library for ISO/IEC 42001
26% of them also map to NIST Cybersecurity Framework.
50
In Keel’s library for NIST Cybersecurity Framework
20% of them also map to ISO/IEC 42001.
30
Evidence artifacts expected
Across the shared controls, from Keel’s evidence guidance. Gathered once.
-
ISO/IEC 42001 26%
10 controls of 38 in Keel’s library for ISO/IEC 42001 also map to NIST Cybersecurity Framework.
-
NIST Cybersecurity Framework 20%
10 controls of 50 in Keel’s library for NIST Cybersecurity Framework also map to ISO/IEC 42001.
The mapping
Controls that satisfy both
Each row is one control in Keel’s library and the clauses it answers on each side. Do the work once; both columns are then evidenced by the same artifacts.
| Canonical control | ISO/IEC 42001 clauses | NIST Cybersecurity Framework clauses |
|---|---|---|
| Governance & Risk | ||
| Continual improvement Improvement of the management system is run as an activity with a record, not held as an intention. Opportunities are captured from everywhere they arise - audit findings, the results of measurement and evaluation, decisions out of management reviews, incidents and near misses, and suggestions from the people actually doing the work - and held in one place instead of in the meeting each came out of. Each is evaluated and either taken forward with an owner and a date or closed with the reason it was not, so a rejected idea is a decision rather than a silence. Once an improvement is made, its effect on the suitability, adequacy and effectiveness of the system is checked, so improvement is something that can be shown to have happened rather than asserted at the next audit. The routine execution of the work counts as a source in its own right: what the operational processes, procedures and activities themselves show while they are being run - the step that is always skipped, the check that never fires, the manual workaround everybody has quietly adopted - is captured on the same terms as a finding from an audit, because the people running a process daily see more of it than any evaluation does. Where the thing being improved is an AI system, the improvement activity is built into the system’s own update cycle and is measurable: an update carries the improvement it is meant to deliver and the measure that will show whether it did, checked afterwards rather than asserted, and interested parties - the people who operate the system, the people it is used on, and those who represent them - are engaged regularly as part of that cycle rather than consulted once at launch. The opportunities are not confined to the system: what the organization delivers is in scope too. Improving products and services to meet known requirements and to address needs and expectations that are coming rather than current, correcting, preventing or reducing undesired effects, and improving how the system itself performs are all determined and selected against as improvement opportunities, rather than run as three unrelated programs. And the standing question - what in the system’s suitability, adequacy and effectiveness should be improved next - is answered from evidence rather than appetite: the results of analysis and evaluation and the outputs of management review are considered together to decide whether there is a need or an opportunity that has to be addressed. | 10.1 | ID.IM-03 |
| Interested parties & their requirements The parties with a stake in the management system are identified - customers, regulators and supervisory authorities, employees, owners and investors, suppliers, insurers, and anyone else whose requirements bear on it - and what each of them requires is recorded specifically enough to be tested against rather than as a category. That includes the legal, regulatory and contractual obligations that follow from each relationship. The organization then records which of those requirements it will meet through the management system and which it will not, so the boundary is a decision on the record with a reason attached rather than an omission nobody noticed. The list is reviewed on a cadence, and whenever a new obligation, contract, relationship or regulator arrives. The parties inside the organization count as well as those outside it - the functions whose work the system constrains, and the people who have to operate it - and what each of them expects of the way cybersecurity risk is managed is recorded beside what it requires of the organization, and considered in the decisions taken, so an expectation that was heard is visibly carried through rather than noted and passed over. | 4.2 | GV.OC-02 |
| Internal audit program A risk-based internal audit program evaluates conformity and effectiveness at planned intervals, and again when an environmental or operational change could have undermined what was last evaluated; each evaluation covers both technical testing and non-technical review of whether the documented policies and procedures are actually being met. The program itself is written down - how often audits run, what methods they use, who is responsible for them, what each one covers and how it reports - and nobody audits their own work, so a finding is an independent judgement rather than a self-assessment. The results of each audit go to the management responsible for the area audited, and the program and its results are retained as evidence that it ran. It rests on a documented assessment, authorization and monitoring policy with supporting procedures, issued to the roles it binds, owned by a named official, and reviewed and updated on a defined cadence. Independence is a property of the assessor and not only of the reporting line: assessments are carried out by assessors or assessment teams with no responsibility for what they are assessing and no stake in the result - internal to the organization but outside the area, or brought in from outside it - and the organization states what level of independence it requires before the assessment is commissioned rather than judging it afterwards. That independence extends to the ongoing case as well as the scheduled one: where controls are monitored continuously between audits, independent assessors monitor them too, so the periodic audit is not the only unbiased look the organization ever takes. What an evaluation produces is treated as an input to improvement and not only as a conformity verdict: the findings, the observations and the opportunities each audit identifies are recorded as improvements with owners and dates and carried into the organization’s improvement process, so an audit changes something rather than closing. | 9.2 | ID.IM-01 |
| Leadership commitment & accountability Top management is accountable for whether the management system works, and the accountability is exercised rather than asserted. It approves the policy and the objectives and satisfies itself that they fit the direction the organization is actually going in; it requires the system’s requirements to be built into how the business already runs rather than bolted alongside it; it makes sure the resources the system needs are available; it tells the organization why conforming to the system matters, in its own voice; it directs and supports the people whose work makes the system effective; it promotes improvement; and it backs other managers in exercising leadership over the parts of the system that are theirs. What it decided, when, and on what basis is recorded, so the commitment is evidenced by acts rather than by a signature on a policy. Leadership is accountable for cybersecurity risk itself and not only for the system that manages it, and it fosters the culture that has to go with that: risk-aware, ethical, and expected to keep improving rather than to hold a standard once reached. It also requires cybersecurity risk management activities and their outcomes to be carried inside the organization’s enterprise risk management process - the same register, the same reporting line, the same committee that hears the other risks - rather than in a security-only record that never reaches the people who allocate capital against it. It promotes two habits by name rather than by implication: the process approach, meaning the work is understood, run and improved as connected processes with defined inputs, outputs and owners; and risk-based thinking, meaning what could go wrong is considered while the work is being planned rather than after it has gone wrong. And it satisfies itself that the system achieves the results it was set up to achieve - the intended outcomes, checked - so leadership answers for the system’s effect and not only for its existence. | 5.1 | GV.RR-01, GV.RM-03 |
| Management review Leadership reviews how the management system is performing at planned intervals and decides what to do about it: what will be improved, and what about the system itself has to change. Each decision leaves the review with a named owner and a date rather than as a sentiment in the minutes, the previous review’s decisions are picked back up at the next one so nothing is decided twice and never done, and the record of the review and its outputs is retained. The risk management strategy is one of the review’s standing subjects: what the strategy actually produced is reviewed for what it says about the direction being taken, and the strategy itself is then reviewed and adjusted for whether it still covers the requirements the organization is under and the risks on its register - so a strategy the year has overtaken is changed at the review rather than reaffirmed by it. The review is planned rather than convened, and what it has to consider is fixed in advance: the status of actions from previous reviews; changes in the external and internal issues that bear on the system; the satisfaction of customers and the feedback of other interested parties; how far the objectives set for the system have been met; how the processes are performing and whether what the organization delivers conforms; the nonconformities raised and the corrective actions taken; the results of monitoring and measurement; audit results; how external providers are performing; whether the resources the system has are adequate; the effectiveness of the actions taken on risks and opportunities; and the opportunities for improvement on the table. An input that is missing on the day is recorded as missing rather than passed over, so the review is answerable for what it did not see as well as for what it decided. Where the organization develops or uses AI, the AI governance program is a standing subject of the same review rather than a separate forum: what the AI systems in scope did, what the risks and impacts recorded against them showed, and what should change - taken with the rest of the agenda by the same leadership, so an AI decision is weighed against the organization’s other commitments instead of beside them. | 9.3 | GV.OV-01, GV.OV-02 |
| Management system communication plan What the management system has to communicate is decided in advance and written down rather than left to whoever remembers: on what subjects, when, to whom inside the organization, to whom outside it, by whom, and by what means. The plan covers what goes out routinely - policy changes, objectives, how the system is performing, the obligations people are under, including what each part of the organization is responsible for in operating the system - and what goes out on a trigger, and it names who is authorised to speak externally so a communication that carries an obligation is not made by whoever picked up the phone. It is reviewed when the audience, the obligations or the system change, and what was communicated, to whom and when is recorded, so the plan can be shown to have been followed rather than merely written. Cybersecurity risk has its own named lines within that plan: which risks are reported upward and to whom, how a risk raised in one part of the organization reaches the other parts it affects, and how risk arising from suppliers and other third parties enters those same lines instead of staying inside the relationship that produced it. The plan covers the incident case too, so recovery activities and the progress made in restoring operational capability are communicated to the designated internal and external stakeholders on terms set in advance rather than on whatever the responders have time for. | 7.4 | GV.RM-05, RC.CO-03 |
| Management system scope statement The boundaries of the management system are decided and written down as a scope statement: which parts of the organization, which locations, which activities, which information and which technology sit inside it, and what sits outside. The statement is reasoned from the issues determined about the organization’s context and from what interested parties require, rather than drawn to be convenient, and it states the interfaces and dependencies between what the organization does itself and what is done for it by others - so a boundary drawn around a service someone else runs is visible on the page instead of implied by its absence. The scope is available as documented information, and it is revisited when the organization, its activities, or those dependencies change. Those dependencies are understood and made known, not merely bounded: the outcomes, capabilities and services the organization relies on others to provide are named in the scope record along with what inside the organization depends on each, and the record is made available to the roles whose work assumes them - so a dependency is something the organization can point at rather than something it learns about when the dependency fails. The scope names the products and services it covers, not only the organizational units, because a boundary drawn around a division says nothing about which of its offerings the system is answering for. And where a requirement of the standard the system is built against is judged not to apply inside that boundary, the judgment is recorded with the reason it holds - which requirement, why it cannot affect the organization’s ability to deliver conforming products and services, and who decided - so an exclusion is an argument on the page rather than a silence in the scope. | 4.3 | GV.OC-05 |
| Organizational context The internal and external issues that bear on the management system are determined and written down: what the organization does and how it is structured, the technology and information it depends on, the people and culture inside it, and outside it the markets it sells into, the laws and contracts binding it, the threat environment it operates in and whatever else could affect whether the system achieves what it exists to achieve. Each issue is recorded with enough reasoning that a reader can see why it matters here rather than in general, and the record is revisited on a defined cadence and whenever something material changes - an acquisition, a new market, a new regulator, a new class of threat - so it is the current picture and not the one taken when the system was first set up. The mission the organization exists to carry out is stated as part of that record, in its own words rather than by implication, and the cybersecurity risk decisions taken under the management system are traced back to it - so a risk is prioritized for what it would do to the mission rather than for how alarming it sounds. | 4.1 | GV.OC-01 |
| Resources for the management system The resources the management system needs in order to be established, run, kept running and improved are determined and provided, not assumed: the people and the time they are actually given rather than the time the plan says they have, the tools and technology, the information, and the budget. The determination distinguishes what the organization can meet from its own capability from what it has to obtain from outside, and it is written down so a shortfall is visible as a shortfall. It is revisited when the system’s scope, its workload or the organization changes, so a system that has grown is not still resourced for the size it was when it started. Security and privacy are budgeted as a discrete line rather than absorbed into a general technology allocation. The high-level security and privacy requirements for a system or a service are determined while the business process it serves is being planned, rather than after the design is fixed; what it will cost to protect it is then determined, documented and allocated as part of the organization’s capital planning and investment process; and that amount appears as a discrete line item in the programming and budgeting record - so an underfunded control is a visible decision rather than an unexplained gap. Adequacy is judged against the risk strategy rather than against last year’s allocation: what is provided is set commensurate with the risks the organization has said it will manage, the roles it has assigned and the policies it has issued - and where it is not, the shortfall is recorded against the part of the strategy it fails to fund. People are determined as their own class of resource rather than counted inside a budget line: the persons necessary for the system to be implemented effectively, and for its processes to be operated and controlled, are identified from the work that has to be done and are then actually provided - so a process with nobody assigned to run it is visible before it fails rather than after. Where the management system depends on data and on computing capacity - not only on people, tools and money - those are determined and provided as resource classes in their own right, so a system planned without the data it needs, or without the compute to run what it plans, is a visible shortfall rather than a later discovery. | 7.1 | GV.RR-03 |
| Risk & opportunity planning Working from the organization’s context and what its interested parties require, the risks and opportunities the management system must address are determined and recorded; an action is planned for each and built into the system’s own processes rather than run alongside them; and those actions are afterwards evaluated for whether they worked, in proportion to the potential impact of the risk or opportunity. Opportunity is treated as the other side of the same determination rather than as a separate exercise: the strategic opportunities open to the organization - the positive risks - are characterized in the same terms as the negative ones and brought into the same discussion, so a decision to accept a risk in order to take an opportunity is made once, in one place, with both sides of it visible. | 6.1.1 | GV.RM-07 |
Beyond the pair
Where else this work counts
A framework is lit when a shared control above also maps to it. Unlit means none of them do — an absence, not a judgment about that standard.
Also reached by these 10 controls
- AI Governance Essentials
- Amazon Appstore Child-Directed Apps
- Apple App Store Kids Category
- CIS Critical Security Controls
- COPPA
- ESG Essentials
- EU AI Act
- GDPR
- Google Play Families
- HIPAA
- ISO 9001
- ISO/IEC 27001
- NIST AI Risk Management Framework
- NIST SP 800-171
- NIST SP 800-53
- PCI DSS
- SOC 2
- SOX (Sarbanes-Oxley) Section 404
- US Employment Law - Federal Baseline
Nearby pairs
- NIST Cybersecurity Framework and ISO/IEC 27001 45 shared controls
- NIST Cybersecurity Framework and NIST SP 800-53 33 shared controls
- NIST Cybersecurity Framework and SOC 2 26 shared controls
- NIST Cybersecurity Framework and NIST SP 800-171 22 shared controls
- NIST Cybersecurity Framework and PCI DSS 20 shared controls
- NIST Cybersecurity Framework and SOX (Sarbanes-Oxley) Section 404 20 shared controls
The thesis
Why this is one project, not two
On a crosswalk-native model, NIST Cybersecurity Framework mostly lights up controls you already built for ISO/IEC 42001. You’re not re-uploading the same screenshot for a second audit. You apply the framework and see the genuine delta worth working. That’s the whole idea behind collect once, comply everywhere.
Next step
Add NIST Cybersecurity Framework to the work you already did
Apply both frameworks in one workspace and see the overlap measured against the controls you already hold.