NIST’s December 2015 RFI asked if another body should steward its cyber framework; respondents said not yet
On December 11, 2015, NIST asked whether another organization should coordinate its cybersecurity framework. Respondents were comfortable with NIST’s continued lead, with transition to be considered later. In our reading, that kept the framework free and nameable in a 2017 executive order.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
On December 11, 2015, NIST asked whether another organization should coordinate its cybersecurity framework. Respondents were comfortable with NIST’s continued lead, with transition to be considered later. In our reading, that kept the framework free and nameable in a 2017 executive order.
- The week The notice recounted how the document was built.
- Stewardship: who should own the framework The notice did not assume NIST would stay in charge.
- Change control: when and how the framework should change Two positions stood out in the examples.
- Content: what respondents asked to add NIST’s analysis grouped content suggestions under a theme titled Update to Framework Content. [3] The examples were specific.
- Regulatory position: a voluntary document among mandatory rules The RFI’s ninth question asked how to prevent duplication of, and conflict with, regulatory requirements. [1] It quoted the 2014 Act’s own wording. [1] [2] The question recognized that the framework was being read by people who also answered to regulators.
- How the outcome reached different organizations For a bank, the framework stayed a reference rather than an obligation.
- The strongest objections The record supports part of this.
- What a leader would check today The framework a 2026 organization uses is version 2.0. [7] The RFI’s questions still describe the decisions a leader makes about it.
- Why the stewardship answer carried the most weight The RFI asked 25 numbered questions, and the content answers are the easiest to see.
- With hindsight The RFI’s main outcomes can be read in later NIST documents.
The week
On Friday, December 11, 2015, the National Institute of Standards and Technology published a request for information in the Federal Register. [1] Its title was Views on the Framework for Improving Critical Infrastructure Cybersecurity. [1] Comments were due by 5:00 p.m. Eastern time on February 9, 2016. [1]
The institute said Executive Order 13636 had directed the work, and that the framework was released on February 12, 2014, after a year-long open process. [1] The notice described the framework as standards, methodologies, procedures and processes that align policy, business and technological approaches to cyber risk. [1]
The notice recounted how the document was built. The institute used an RFI published on February 26, 2013, five open public workshops and a 45-day comment period on a draft announced on October 29, 2013. [1] It then sought views on users’ experiences through another RFI published on August 26, 2014, and a workshop held on October 29 and 30, 2014. [1]
By December 2015 the institute’s role rested on a statute as well as the executive order. The Cybersecurity Enhancement Act of 2014, approved December 18, 2014, amended the institute’s organic statute. [2] It directed the institute, on an ongoing basis, to facilitate and support the development of a voluntary, consensus-based, industry-led set of standards and practices to cost-effectively reduce cyber risks to critical infrastructure. [2]
The Act also set limits. The institute was to coordinate closely with private sector entities, critical infrastructure owners and operators, Sector Coordinating Councils and Information Sharing and Analysis Centers. [2] It was to align with voluntary international standards to the fullest extent possible. [2] It was not to prescribe specific solutions or specific information and communications technology products or services. [2]
One limit addressed regulators directly. The Act said information shared with the institute for this work may not be used by any federal, state, tribal or local agency to regulate the activity of any entity. [2] It also told the institute to prevent duplication of regulatory processes and conflict with regulatory requirements and mandatory standards. [2]
The December notice organized its questions under four headings. The first was use of the framework. [1] It asked how organizations used the document, giving internal management and communications, vendor management and C-suite communication as examples. [1] It asked about experience with specific parts, naming the Core, Profile, Implementation Tiers and Privacy Methodology. [1] It asked what had limited use, and what metrics organizations used to track any reduction in cybersecurity risk. [1]
One question in that first group quoted the 2014 Act. It asked what steps should be taken to “prevent duplication of regulatory processes and prevent conflict with or superseding of regulatory requirements, mandatory standards, and related processes.” [1]
The second heading was possible updates. [1] The notice asked whether the document should be updated, what should be changed, removed or added, and how to update it while minimizing disruption for current users. [1] It asked whether work in the nine areas of the February 2014 Roadmap should inform an update. [1] The notice listed those areas: authentication, automated indicator sharing, conformity assessment, workforce, data analytics, federal agency alignment, international aspects, supply chain risk management and technical privacy standards. [1]
The third heading was sharing information on using the framework. [1] The notice asked what was inhibiting the sharing of best practices and what the government could do to increase it. [1]
The fourth heading stood apart from the others. It was titled Private Sector Involvement in the Future Governance of the Framework. [1] It asked whether the institute should consider transitioning some or even all of the document’s coordination to another organization. [1] It asked what might move, such as the Core, Profiles, Tiers or Informative References, and to what kind of organization. [1] Its examples included not-for-profit or for-profit, and U.S. or multinational. [1] It also asked whether such an organization could be self-sustaining, and how a transition might affect current users. [1]
The notice said the information would inform the institute’s planning and help build the agenda for a workshop planned for April 6 and 7, 2016, in Gaithersburg, Maryland. [1] It said all comments would be posted without change or redaction. [1] It also noted that, while the work had focused on critical infrastructure, the RFI generally used the broader term “organizations.” [1]
In December 2015, the NIST Cybersecurity Framework was a voluntary document released in February 2014. [1] NIST’s own questions offered internal management, vendor management and C-suite communication as examples of how organizations used it. [1] In our reading, the RFI NIST published on December 11 asked whether that vocabulary should stay with the government. [1]
Our argument is that the answer mattered more than the content questions in the same notice. Respondents were comfortable with NIST’s continued leadership, though NIST’s analysis said transition should be considered at a later date. [3] [4] Keeping it at NIST kept the framework free, public and bound by the 2014 Act’s limits. [2] In our reading, that status is what let a 2017 executive order make it federal agency policy without turning it into private-sector regulation. [6] The price was slow, consensus-paced change. Version 1.1 arrived on April 16, 2018, and version 2.0 on February 26, 2024. [5] [7]
The RFI posed four kinds of decision, and we take them in turn:
- Stewardship: who should own and coordinate the framework.
- Change control: when and how it should be updated.
- Content: what it should add, from authentication to supply chain risk.
- Regulatory position: how a voluntary document should relate to rules that are not voluntary.
The four do not overlap. The first is about the owner, the second about the process, the third about the text and the fourth about how others use the text. After them we look at how the outcome reached different kinds of organization, take the strongest objections and end with what a leader would check today.
Stewardship: who should own the framework
What NIST asked
The notice did not assume NIST would stay in charge. It asked whether NIST should consider transitioning some or all of the framework’s coordination to another organization. [1] It asked what kind of organization could take it on and whether that organization could be self-sustaining. [1] It also asked what factors should be used to judge whether a transition partner could work with domestic and international organizations and governments. [1]
The question had a statutory backdrop. The 2014 Act called for a voluntary, consensus-based, industry-led set of standards and practices. [2] An industry-led document could, in principle, be led from outside government. The RFI tested whether industry wanted that.
What respondents said
NIST’s March 24, 2016 analysis reviewed 105 responses. [3] It summarized the governance theme in one line: respondents were comfortable with NIST’s continued leadership, though transition should be considered at a later date. [3] Its key terms for the theme included “Premature to Transition,” “NIST Retention” and “No Cost.” [3]
The examples NIST chose showed the reasons. One respondent said transferring responsibility to the private sector would be premature. [3] Another said private-sector governance might come eventually, with NIST keeping a hand on it. [3] A third worried that a new steward might gather less private input or make the framework a purchase-only document. [3] Other responses looked further ahead. One said much of the governance should eventually move to an international standards organization. [3]
The analysis also listed a separate theme, Optimal Industry Leadership: any possible future steward should be a respected, internationally recognized, neutral third-party organization. [3] Its examples included a response saying the framework should be transitioned to a group hosted by an entity such as the National Cybersecurity Center of Excellence. [3] Another suggested a not-for-profit, U.S.-based organization that could charge nominal membership fees to be self-sustaining. [3] The responses were not uniform. NIST’s own summary of them was continued NIST leadership, with transition to be considered at a later date. [3]
NIST’s June 9, 2016 summary of the RFI and its April workshop described the feedback as near unanimous. [4] It said NIST was encouraged to maintain a significant presence in the framework’s governance for the foreseeable future. [4] A majority of participants suggested it might be too early for a different governance structure. [4] The summary’s next steps said NIST would continue its role as convener of framework stakeholders. [4]
Sharing practice: the steward as convener
The RFI’s third heading asked what was inhibiting the sharing of best practices and what the government could do to increase sharing. [1] The answers tied sharing to stewardship. NIST’s analysis listed a theme it called Challenges in Sharing Best Practices, saying more sharing was needed. [3]
The June 2016 summary reported that NIST was seen as well positioned to facilitate sharing of information and current practices on framework use. [4] Participants supported NIST managing sharing sites that aggregate information from framework users. [4] They also said many workshop participants were unaware of the Industry Resources pages NIST already maintained. [4]
Participants asked NIST to change a word. They recommended describing “best practice” sharing as “current practice” sharing, reserving “best” for practices measured and adjudicated as better than others. [4] They said the label would need to come from an impartial organization recognized for its expertise. [4]
The same summary recorded a barrier. Respondents worried that publicly sharing current practices might help adversaries gather intelligence. [4] Some workshop participants said sharing could raise liability, including under customer and vendor non-disclosure agreements, while others reported no such concern. [4] Several participants worried that self-assessments themselves might raise liability exposure, and the summary said consensus was not reached. [4]
For a bank or a health system, that barrier is familiar. Counsel weighs whether a written self-assessment becomes evidence against the organization. A neutral government convener, bound by a statute that bars regulatory use of what it receives, answered part of that worry. [2] In our reading, a commercial steward collecting the same material would not have carried the same statutory protection.
Why the owner mattered to a regulated organization
For a bank or a hospital, the framework’s owner decided three practical things. The first was cost. NIST’s framework publications state that they are available free of charge. [5] [7] One governance example in NIST’s analysis drew the contrast directly, warning against a purchase-only document. [3]
The second was neutrality. The 2014 Act barred NIST from prescribing specific products or services. [2] In our reading, a steward funded by members or sales would not have carried that statutory limit.
The third was a protection for what organizations told NIST. The Act said information shared with NIST for the framework could not be used by government agencies to regulate the entity. [2] An organization describing its weaknesses in a comment letter had that assurance in the statute. In our reading, a private steward could not have offered the same assurance.
What NIST did not settle
The RFI did not close the governance question for good. The analysis framed it as something to consider later. [3] The June 2016 summary said NIST would publish a framework governance methodology as part of the upcoming minor update. [4] It said that document would set stakeholder roles, approximate timeframes for future updates and guidance on what counts as a minor or major update. [4]
The summary of changes in version 1.1 does not list such a methodology among its updates. [5] Its six listed changes cover compliance language, self-assessment, supply chain risk, authentication, Tiers and coordinated vulnerability disclosure. [5] We did not find, in the documents cited here, a published schedule for framework updates. A leader planning around the framework still had to watch for drafts rather than a calendar.
Change control: when and how the framework should change
What NIST asked and heard
The RFI asked whether the framework should be updated and what the best way would be to update it while minimizing disruption. [1] NIST’s analysis found diverse comments on whether an update was necessary or desirable. [3] Its key terms ranged from “Update Now” to “Do Not Update.” [3]
Two positions stood out in the examples. Some respondents wanted the framework treated as a living document that keeps pace with new technology. [3] Others said version 1.0 was sufficient and an update should wait. [3] One suggested a version 1.1 limited to selected items, followed by scheduled updates. [3]
On process, the analysis summarized a single view: updates should come through a collaborative process with minimal disruption to current industry use. [3] Examples asked for change histories, advance notice and a transition window. [3] One suggested publishing the Core separately so references could change without reissuing the whole document. [3]
What NIST decided
The June 2016 summary said NIST was proceeding with a minor update. [4] It said NIST would focus on clarifying and refining the framework to minimize disruption to current users. [4] It named topics under strong consideration: updated Informative References, clearer guidance on Tiers, placement of cyber threat intelligence in the Core and supply chain risk. [4] It promised a draft for comment in early calendar year 2017. [4]
Version 1.1 records how that went. It says it incorporates comments on two drafts. [5] Its acknowledgments list over 120 comments on a January 10, 2017 first draft and over 85 comments on a December 5, 2017 second draft. [5] They also list the 105 responses to the December 2015 RFI and input from over 1,200 attendees at the 2016 and 2017 workshops. [5]
The compatibility promise was explicit. Version 1.1 says current users should be able to implement it with minimal or no disruption, and that compatibility with version 1.0 was an explicit objective. [5]
What change control meant for an organization’s own records
A framework that changes slowly is easier to map to. A bank that had mapped its policies to version 1.0 could carry that mapping into 1.1 with limited changes, given NIST’s compatibility objective. [5] The cost of the slow cadence fell elsewhere. Topics raised in early 2016 responses, such as a more visible governance section, waited for 2.0. [3] [7]
For a compliance officer, the practical consequence is version control. A risk assessment, a vendor questionnaire and an internal audit report may each cite a different framework version. Those versions use different identifiers. Version 1.1 places supply chain risk under ID.SC in the Identify Function. [5] Version 2.0 places it under GV.SC in the new Govern Function. [7] An evidence package that mixes the two needs a crosswalk, or a reviewer may treat the gap as missing work.
The case for faster change
There is a fair objection to the pace. Threats moved faster than the framework did. The RFI responses themselves asked for threat intelligence and authentication content. [3] A document on this cadence cannot be the only guide to current attack techniques.
NIST’s own feedback suggests the framework was not designed to carry that detail. The June 2016 summary reported that participants found the framework fit at upper levels of an organization and was not granular enough to be the only framework in use. [4] CSF 2.0 moved its Informative References and Implementation Examples online, where NIST says they are updated regularly. [7] The slow core and the faster online material split the job between them.
Content: what respondents asked to add
The requests
NIST’s analysis grouped content suggestions under a theme titled Update to Framework Content. [3] The examples were specific. One asked for guidance for small and less mature organizations. [3] Another asked for threat intelligence as its own Category under Detect. [3] The same response asked for a more visible governance section, either a sixth Function or a Category under Identify. [3]
Other examples asked for expanded supply chain content across the lifecycle of supplier relationships. [3] One proposed a new Subcategory saying authentication of authorized users is protected by multiple factors. [3] Other examples dealt with Tiers: one asked for a maturity model, and another warned that Tiers used outside an organization’s own risk process invite false comparisons. [3]
The June 2016 summary reported the same priorities after the workshop. It said respondents and participants identified authentication as a major area needing further development, with many pointing to the Protect Function. [4] It said supply chain risk management was identified as a critical area for inclusion. [4] It also recorded concern about Tiers and a lack of clarity about how to use them. [4]
What version 1.1 added
Version 1.1’s summary table answers several of those requests. It added a Supply Chain Risk Management Category with multiple Subcategories to the Core. [5] It added a section on buying decisions and expanded the section on communicating requirements with stakeholders. [5] It added Cyber Supply Chain Risk Management criteria to the Tiers. [5]
On identity, version 1.1 renamed the Access Control Category to Identity Management and Access Control. [5] It added one Subcategory for authentication and one for identity proofing. [5] It also added a Subcategory on the vulnerability disclosure lifecycle and a new section on self-assessing cybersecurity risk. [5]
On Tiers, version 1.1 clarified their relation to Profiles. [5] It said that although organizations at Tier 1 are encouraged to consider moving toward Tier 2 or greater, Tiers do not represent maturity levels. [5]
What waited for 2.0
The governance request waited. CSF 2.0 lists six Core Functions: Govern, Identify, Protect, Detect, Respond and Recover. [7] It describes Govern as covering the organization’s cybersecurity risk management strategy, expectations and policy. [7] Govern’s Categories are Organizational Context, Risk Management Strategy, Roles, Responsibilities, and Authorities, Policy, Oversight and Cybersecurity Supply Chain Risk Management. [7]
Version 2.0 also moved supply chain risk into Govern, under GV.SC. [7] Its preface says 2.0 contains new features that highlight the importance of governance and supply chains. [7]
We cannot show that a particular 2016 comment caused a particular 2024 change. The documents show a sequence. Respondents asked for governance, supply chain and authentication content in early 2016. [3] Version 1.1 added supply chain and authentication. [5] Version 2.0 added Govern. [7]
Assessment and measurement
The RFI asked what metrics organizations used to track any reduction in cybersecurity risk. [1] The answers showed a gap. Workshop participants said the potential for sharing practices was limited by the early state of framework use and the absence of widely accepted assessment methods. [4]
NIST responded on two tracks. The June 2016 summary said NIST had begun writing self-assessment criteria, the Cybersecurity Excellence Builder, based on the framework and on concepts from the Baldrige Performance Excellence Program. [4] Participants had said such a tool must be strictly voluntary, and that third-party assessment with public recognition could be prohibitive. [4]
Version 1.1 then added a new Section 4.0, Self-Assessing Cybersecurity Risk with the Framework. [5] Its summary table says the section explains how organizations can use the framework to understand and assess their risk, including the use of measurements. [5]
For a chief information security officer, the distinction matters in board reporting. A self-assessment against the framework describes the program in the organization’s own terms. A third-party certification would make a claim to outsiders. The framework, as revised, supported the first and did not create the second. [5]
Privacy, workforce and federal alignment
Three other Roadmap topics came back in the responses. On privacy, workshop participants generally agreed that the framework’s methodology for privacy and civil liberties should give more actionable guidance. [4] One RFI response warned that going beyond the version 1.0 methodology could layer unnecessary privacy obligations on top of existing ones. [3] Participants also raised concern that privacy guidance might hinder international adoption, since requirements differ across countries. [4]
On workforce, the 2016 summary said respondents and participants identified workforce development as a major issue. [4] They pointed to the NICE National Cybersecurity Workforce Framework as key guidance the framework should draw on. [4]
On federal alignment, participants agreed that the relationship between the framework and the NIST Risk Management Framework needed clarification. [4] They named the DoD Risk Management Framework and FedRAMP as approaches to align with. [4]
CSF 2.0 includes a figure on the relationship between cybersecurity and privacy risk. [7] It lists human resources specialists, acquisition professionals and auditors among its possible users. [7] These are modest answers to large requests. They show that the framework took up the topics without becoming a privacy rule or a staffing standard.
What the content changes meant for each kind of organization
In our reading, the supply chain additions matched vendor management work a regional bank already does. Version 1.1’s buying-decisions section gave a shared vocabulary for questions a bank asks a core processor or a cloud provider. [5]
For a health system, the authentication and identity proofing Subcategories matched pressures on remote access, clinician sign-on and patient portals. [5] The framework did not set a method. It named an outcome that a health system could map its own controls to.
For a federal agency, the additions arrived in a document it was by then required to use. [6] In our reading, each new Subcategory became something an agency’s risk report could be measured against.
For a smaller organization, such as a credit union or an ambulatory network, the content grew while the RFI’s request for small-organization guidance was handled outside the core. [3] CSF 2.0 points smaller organizations to Quick Start Guides that NIST hosts online. [7]
Regulatory position: a voluntary document among mandatory rules
The question in the RFI
The RFI’s ninth question asked how to prevent duplication of, and conflict with, regulatory requirements. [1] It quoted the 2014 Act’s own wording. [1] [2] The question recognized that the framework was being read by people who also answered to regulators.
What respondents said
NIST’s analysis summarized a theme it labeled Regulation. [3] It said many users described regulation as a necessary consideration in building their programs, and cautioned about the potential negative impact of additional requirements. [3] The key terms were “No regulation,” “Compliance,” “Overlap” and “Flexible.” [3]
The examples split. One said broader adoption of the framework as a regulatory tool, though not as a regulation, would let an organization assess once and report to many regulators. [3] Another suggested that regulators map their rules to the framework to see what was duplicated. [3] Others asked that the framework stay flexible enough to add or remove components to meet specific rules. [3]
The June 2016 summary turned this into a request. It said participants felt NIST should support the framework’s role as non-mandatory guidance by mapping sector regulations to the Core. [4] It also reported interest in using the framework to translate assessment results across sectoral, regulatory and geographic settings. [4]
What version 1.1 said about compliance
Version 1.1 addressed the word directly. Its first listed change clarified that terms like “compliance” can be confusing and mean very different things to different stakeholders. [5] It said the framework has utility as a structure and language for organizing and expressing compliance with an organization’s own cybersecurity requirements. [5]
That sentence set a boundary. The framework could describe how an organization met its rules. It did not become the rule. In our reading, a framework profile was evidence about a program for a bank examiner or an auditor, not a certificate of anything.
What the 2017 order did
Federal agencies were treated differently. Executive Order 13800 was signed on May 11, 2017. [6] It said that, effective immediately, each agency head shall use the framework, or any successor document, to manage the agency’s cybersecurity risk. [6]
The order attached work to that duty. Each agency head had to provide a risk management report to the Secretary of Homeland Security and the Director of OMB within 90 days of the order. [6] The report had to document risk mitigation and acceptance choices, including any accepted risk from unmitigated vulnerabilities. [6] It also had to describe the agency’s action plan to implement the framework. [6]
In our reading, the order depended on NIST still owning the document. It named a NIST framework “or any successor document.” [6] A framework held by a private steward could have changed hands, terms or price. A NIST publication could be named once and followed through its revisions.
The two-track result
The outcome was a framework with two legal characters. For federal agencies it was mandatory under the order. [6] For a bank, a health system or a county, it remained voluntary unless a regulator, a contract or a state law said otherwise. The 2014 Act’s bar on using information shared with NIST for regulation applied to all of them. [2]
That two-track result shaped what leaders had to manage. An agency program director answered to the order and to OMB. A bank’s chief information security officer answered to examiners who might use the framework as a reference without making it a rule. A health system’s compliance officer answered to the HIPAA Security Rule, which the framework did not replace.
How the outcome reached different organizations
Federal agencies
The June 2016 summary reported that federal respondents used the framework alongside the NIST Risk Management Framework, or to communicate risk posture for FISMA reporting. [4] It said Fiscal Year 2016 CIO FISMA metrics were organized by the framework’s Core Functions. [4] It also reported a clear need to clarify how the framework related to the Risk Management Framework. [4]
The 2017 order turned that use into a requirement. [6] For an agency, the RFI’s outcome meant a document it already used for reporting became the basis of an accountable risk decision by the agency head. [6]
Banks and credit unions
For a bank, the framework stayed a reference rather than an obligation. Its value was as a common language across a holding company, its vendors and its board. The 2016 summary recorded interest in using it to translate assessment results across regulatory environments. [4] In our reading, that use required the framework to stay stable and free, which NIST’s continued stewardship preserved.
A credit union and a large bank faced the same document with different resources. The RFI analysis recorded a call for more guidance for small and medium-sized businesses. [3] CSF 2.0 answered with Quick Start Guides aimed at making the framework accessible to smaller organizations. [7]
Health systems and ambulatory networks
Health organizations appeared in the RFI responses. One example in NIST’s analysis said the healthcare sector could benefit from consensus-based guidelines on privacy and information security risk management. [3] Another, on the governance question, said a transition partner should understand healthcare’s challenges and should not charge organizations to use the framework. [3]
For a health system, the framework’s voluntary status mattered in both directions. It did not change what HIPAA required. It did give a structure for describing a security program to a board, a cyber insurer or a partner that asked for one.
State and local governments
State and local agencies were named in the 2014 Act as bodies NIST should consult. [2] They were not bound by the 2017 order, which addressed federal agency heads. [6] For a county or a state agency, the framework stayed voluntary unless state policy adopted it.
The strongest objections
Objection one: keeping NIST in charge slowed the framework
The record supports part of this. One RFI response asked for a more visible governance section in 2016. [3] It arrived in 2024. [7] A private standards body with a scheduled cycle might have moved faster.
The objection leaves out the constraint respondents themselves set. NIST reported that the need to minimize disruption from updates was one of the clearest takeaways from the 2016 feedback. [4] A faster cycle would have added mapping work for every organization that used the document. The slow pace was the price of the stability users asked for.
Objection two: a voluntary framework became a compliance checklist anyway
Version 1.1 itself acknowledged the risk when it said “compliance with the Framework” can be confusing. [5] Respondents in 2016 also noted increasing use of the framework as an assessment method, including among third-party assessment organizations. [4]
The framework’s text resisted that reading. Version 1.1 said Tiers are not maturity levels. [5] CSF 2.0 says it does not prescribe how outcomes should be achieved. [7] In our reading, a checklist use was a choice by its users, not a feature of the document.
Objection three: the governance question was never really asked of the right people
The RFI went to the public, and NIST posted all comments. [1] The responses came from organizations that already used or followed the framework. [3] Organizations that had never heard of it could not weigh in. NIST’s analysis listed awareness as a theme of its own: much progress, but more needed. [3]
That is a fair limit on what the RFI could show. It does not change the outcome. Some responses did favor a transition, as NIST’s analysis recorded, but its summary of the theme was continued NIST leadership, and NIST named no alternative steward. [3] [4]
Objection four: a voluntary framework has no force
A skeptic would say a voluntary document changes nothing that a rule does not already require. The 2014 Act chose that design on purpose. It called for an approach that “may be voluntarily adopted by owners and operators of critical infrastructure.” [2] It barred NIST from prescribing specific solutions or products. [2]
The record shows force arriving by other routes. An executive order made the framework mandatory for federal agencies in 2017. [6] The 2016 respondents described using it with vendors, service providers and partners to communicate requirements. [4] Version 1.1 then added a section on buying decisions. [5] In our reading, contracts and purchasing gave the framework reach in the private sector that no rule required.
The objection has some weight for small organizations. A credit union or a rural clinic with no regulator asking for the framework, and no large customer requiring it, has little external reason to adopt it. The case for those organizations rests on the framework’s value as a plan, which the RFI responses on small-business guidance tried to strengthen. [3]
What a leader would check today
The framework a 2026 organization uses is version 2.0. [7] The RFI’s questions still describe the decisions a leader makes about it.
- Which version does each internal mapping, audit report and vendor questionnaire use, and is there a crosswalk between them?
- Who owns each Govern Category, from risk strategy to oversight to supplier risk, and does the board see the result?
- Does the program describe compliance with the organization’s own requirements, as version 1.1 framed it, rather than compliance with the framework?
- Are supplier contracts and buying decisions tied to the supplier outcomes in the framework, rather than handled in a separate track?
- If the organization is a federal agency, does its risk report document accepted risks the way Executive Order 13800 asked agency heads to?
These checks are good practice, not requirements, except where a regulator, contract or order makes them one. Organizations should check with counsel on what applies to them.
Evidence an auditor would ask for
An internal auditor reviewing a framework-based program would start with the current profile. Version 2.0 describes an Organizational Profile as a description of current or target posture in terms of the Core’s outcomes. [7] The auditor would ask who approved the target profile and when. The Govern Function makes that approval an outcome in its own right, under Roles, Responsibilities, and Authorities and under Oversight. [7]
The auditor would next ask how the gaps between current and target were prioritized. Version 2.0 says creating current and target profiles helps an organization compare where it is with where it wants to be. [7] A gap list without owners, dates or funding decisions shows the comparison was made but not acted on.
The third request would be the mapping. If the organization reports to a regulator in that regulator’s terms, the mapping to the framework is the bridge. The 2016 participants asked NIST to map sector regulations to the Core for exactly this reason. [4] An organization that maintains its own mapping should record the framework version and the rule version it used.
The cost of keeping the program framework-based
There is effort on the other side. Each framework revision means a remapping project, training for control owners and a revised board narrative. Version 1.1 kept that effort small by design. [5] Version 2.0 added a Function and moved Categories, which is larger work. [7]
A health system with a small security team may decide the framework is a reporting layer over its HIPAA program, not the program itself. A regional bank may use it as the outline of its information security program report to the board. An agency has less choice, given the 2017 order. [6] Each choice is defensible. The mistake would be to adopt the framework’s language without assigning the Govern outcomes to people who can decide them.
Why the stewardship answer carried the most weight
The RFI asked 25 numbered questions, and the content answers are the easiest to see. Supply chain, authentication and Govern can be read in the published versions. [5] [7] The stewardship answer is harder to see because it was a decision not to change anything.
In our view, that decision did the most work. A framework held by a government agency, free to use and bound by a statute that kept it voluntary, could be cited by an executive order, mapped by regulators and adopted by boards. [2] [6] The same text owned by a private body could have been any of those things only by license or by contract. The December 2015 notice asked the question openly, and respondents favored continuity for the time being. [1] [3]
With hindsight
The RFI’s main outcomes can be read in later NIST documents. NIST issued version 1.1 on April 16, 2018. [5] It listed the 105 responses to the December 2015 RFI among the inputs to the update. [5] It listed the two drafts, published January 10, 2017 and December 5, 2017, and the 2016 and 2017 workshops. [5]
Version 1.1 delivered the minor update NIST had promised in June 2016. [4] [5] It added supply chain risk to the Core, refined identity and access control, clarified Tiers and added self-assessment guidance. [5] It said current users should be able to implement it with minimal or no disruption. [5]
The governance outcome held. NIST continued as convener, as its June 2016 summary said it would. [4] Version 2.0, published February 26, 2024, is a NIST publication that states it is available free of charge. [7] We found no transfer of the framework to another organization in the documents cited here.
The federal track followed in 2017. Executive Order 13800, signed May 11, 2017, required each agency head to use the framework or any successor document. [6] In our reading, the words “or any successor document” covered revisions like 2.0. [6] We have not traced later changes to the order in this article, so we describe it as it was issued.
Version 2.0 changed the framework’s scope and name. It says that before 2.0 the framework was called the Framework for Improving Critical Infrastructure Cybersecurity, and that this title is not used for CSF 2.0. [7] Its abstract says it can be used by any organization regardless of size, sector or maturity. [7] The December 2015 RFI had already used the broader word “organizations” for its questions. [1]
Version 2.0 added the kind of governance content one RFI response had asked for, as a sixth Function or a Category under Identify. [3] [7] It lists Govern first among six Functions. [7] It says Govern informs what an organization may do to achieve and prioritize the outcomes of the other five Functions. [7] It names executives, boards of directors, acquisition professionals, lawyers and auditors among those who can use it. [7]
Supply chain risk moved again. Version 1.1 placed it in Identify. [5] Version 2.0 placed it in Govern as Cybersecurity Supply Chain Risk Management. [7] For organizations that had built supplier programs around 1.1’s identifiers, the move meant remapping.
Version 2.0 also took up the RFI’s request to separate fast-changing material from the core. One 2016 response had suggested publishing the Core separately so references could change more easily. [3] CSF 2.0 says NIST now provides Implementation Examples and Informative References online and updates them regularly. [7]
What did not hold as planned was the governance methodology. The June 2016 summary said NIST would publish one with the minor update. [4] Version 1.1’s summary of changes does not list one. [5] The documents cited here do not show a fixed update schedule.
What held up most clearly was the decision the RFI framed as optional: keeping the framework public and under NIST. That kept it inside the 2014 Act’s limits on prescribing products and on regulatory use of shared information. [2] It let the 2017 order name it. [6] It left banks, health systems and local agencies free to adopt it on their own terms, or under their regulators’ terms, rather than under a license. [7]
Spotted an error? Tell us and we will check it and correct the article where needed.