News and insights

Two NIST drafts on taking cyber risk to the board

In October 2026, the US National Institute of Standards and Technology (NIST) published two drafts for public comment. Both are about the same question: how technology risk reaches the people who run an organisation.

NIST guidance is voluntary for most organisations, and these are drafts. There is nothing to comply with yet. But both are written for organisations of any size and sector. And both build on the NIST Cybersecurity Framework (CSF) 2.0, which many organisations already use.

What’s changing

NIST SP 800-221 Rev. 1 (initial public draft). Its full title is “Enterprise Impact of Information and Communications Technology Risk: Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio”. NIST published it on 22 October 2026. Comments are due by 11:59 pm EST on 7 December 2026.

The draft is about feeding ICT risk registers into the enterprise risk profile. The aim is that risks managed at system or department level are visible at enterprise level. It covers cybersecurity, privacy, supply chain, operational technology and the Internet of Things together.

NIST describes an approach that brings risk information from these areas together on a common basis. Risk scenarios can then be expressed in financial, mission and reputational terms. That lets leaders compare ICT risks with other enterprise risks and decide where to spend.

In line with the CSF 2.0 Govern function, the draft says cybersecurity governance should be central to risk management. It expects oversight and resources from senior leadership.

NIST lists these changes in Revision 1:

  • updates reflecting the 2026 revision of OMB Circular A-123
  • revised sections on risk culture, risk capacity and comprehensive risk assessment
  • closer alignment with NIST IR 8286r1, on integrating cybersecurity and enterprise risk management
  • new guidance on using the risk register for workforce decisions, referring to NIST SP 1308
  • recognition that risk can be quantified in more than one way

NIST SP 800-100 Rev. 1 (initial public draft). This is “Information Security Handbook: A Guide for Executive Leadership”. The original handbook dates from 2006. NIST published the draft on 21 October 2026, and comments are due by 4 December 2026.

The revision is restructured to follow the general organisation of CSF 2.0. It gives leaders high-level summaries of governance, risk management, information exchange, awareness and training, contingency planning, configuration management and incident response. It explains how these fit together, and points to other NIST publications for detail.

What it means for you

These drafts describe good practice that applies well beyond the US public sector. A sensible way to use them:

  • Read the drafts while they are open. If something won’t work in your organisation, NIST’s comment template is on each publication page.
  • Check your register reaches the top. Ask whether your board sees the ICT risks it needs to, in terms it can weigh against other risks.
  • Put risks in business terms. Where you can, add a financial range or a mission impact, not only a score.
  • Be clear on tolerance. Decide who can accept which risks, and what happens when a risk sits outside tolerance.
  • Bring the areas together. Keep supplier, privacy and operational technology risks in view alongside cybersecurity, not in separate lists.

How RiskWitness helps

RiskWitness is built around the risk register these drafts describe, and NIST CSF 2.0 is in its framework library.

Record each risk with an owner. Score likelihood and impact before and after controls. Add a cost range, so the board sees the risk in financial terms. Set a review date.

Link it to what it affects. Connect each risk to its assets and suppliers. Rate suppliers by criticality and keep their questionnaires and assurance evidence.

Show the controls. Link controls to risks, record how effective each one is, and test them. Controls are mapped to the requirements of NIST CSF 2.0 in the library.

Make the decision visible. Record a treatment for each risk: reduce, transfer, avoid or accept. An acceptance needs a reason and an expiry. Outside tolerance, a named approver signs it off and confirms it’s them.

Give gaps an owner. Turn each one into an action with a due date. Overdue actions show on the dashboard.

Take it to the board. Produce a PDF report or slide deck. Record the committee meeting, its minutes and its decisions.

Every step is kept in a history that shows who did what, when, and the old and new values. Nobody can edit or delete it. When the board, an auditor, a customer or a regulator asks how a risk was decided, the answer is already written down.

Sources