SEC-02 / Frameworks

NIST CSF 2.0 for manufacturers: one language for IT, OT and the board

NIST Cybersecurity Framework (CSF) 2.0 is a voluntary, outcome-based framework that organizes cybersecurity into six functions: Govern, Identify, Protect, Detect, Respond and Recover. For a manufacturer, its main value is a single structure that the board, IT and OT can all report against, with the NIST Manufacturing Profile translating outcomes to plant conditions.

7 min read Updated CISOsCIOsPlant managersOT engineers

Key takeaways

  • CSF 2.0 was published in February 2024. It added a sixth function, Govern, which covers strategy, roles, policy, oversight and supply chain risk.
  • Use profiles (current and target) to plan, and tiers to describe how risk is managed. Tiers are not a maturity score to chase.
  • NIST's Manufacturing Profile (IR 8183) maps CSF outcomes to manufacturing. The CSF 2.0 version (Rev. 2) was still an initial public draft when we checked in November 2026.
  • CSF tells you what outcomes to reach, not how. Pair it with IEC 62443 and NIST SP 800-82 for OT detail.
  • One CSF profile per site, rolled up into one company view, gives the board a consistent picture across offices and plants.

Most mid-market manufacturers have the same problem. IT reports on endpoints and phishing. The plants report on downtime and OEE. The board asks "are we secure?" and gets two different answers in two different vocabularies. The NIST Cybersecurity Framework (CSF) 2.0 does not fix your firewalls, but it gives everyone one structure to report against. That is why it is worth adopting even if no regulator asks you to.

What CSF 2.0 is

CSF 2.0 is a voluntary framework from the US National Institute of Standards and Technology, published in February 2024. It describes cybersecurity outcomes, not specific controls. It is technology-neutral, so it applies to an ERP system and to a packaging line, and it was broadened in 2.0 to cover organizations of every size and sector, not just critical infrastructure.

It has three parts:

  • The Core: six functions, broken into categories and subcategories (outcomes).
  • Tiers: four levels describing how rigorous your risk governance and management are.
  • Profiles: a current profile (where you are) and a target profile (where you want to be), plus community profiles written for a sector.

The six functions

Function What it asks Manufacturing example
Govern (GV) Who decides, under what strategy and policy, with what oversight? Board-approved OT security policy; named owner per plant; supplier risk process for OEMs
Identify (ID) What do we have and what are the risks? OT asset inventory, network drawings, risk assessment per line
Protect (PR) How do we prevent or limit harm? Segmentation, remote access control, hardened engineering workstations, backups
Detect (DE) How do we find attacks and anomalies? OT network monitoring, alerting on PLC program changes
Respond (RS) What happens when something is found? OT incident playbook, who can isolate a line, who calls the OEM
Recover (RC) How do we get back to production? Tested restore of PLC logic and HMI images, recovery priorities by line

Govern is the big change

Govern sits at the center of the other five. Its categories cover organizational context, risk management strategy, roles and responsibilities, policy, oversight, and cybersecurity supply chain risk management. For manufacturers, two of these matter most:

  • Roles and responsibilities. Who owns OT security: the plant manager, engineering, IT or the CISO? CSF 2.0 expects an answer. See IT/OT convergence governance for common models.
  • Supply chain risk management. Your OEMs, integrators and cloud providers are part of your attack surface. Govern makes vendor risk a leadership topic, not an afterthought in purchasing.

Plant-floor reality: Govern is where AI projects show up too. A predictive maintenance pilot that ships historian data to a vendor cloud is a supplier relationship, a data flow and a policy question. If it is not in the Govern picture, it is shadow IT on the plant floor.

Tiers: describing rigor, not scoring

CSF tiers describe how an organization governs and manages cybersecurity risk:

  1. Partial: ad hoc, reactive, limited awareness.
  2. Risk Informed: risk management practices exist but are not organization-wide policy.
  3. Repeatable: practices are formally approved and consistently applied.
  4. Adaptive: practices adapt based on lessons learned and changing threats.

Tiers are meant to guide decisions about the right level of rigor. They are not a maturity score that must go up every year. A three-plant manufacturer might sensibly target Tier 3 for governance and Tier 2 for some legacy sites for a few years.

Watch out: Do not report "we are Tier 2.4" to the board. Tiers are categorical. Report target versus current outcomes per function instead.

Profiles: the working tool

Profiles are where CSF becomes useful on the shop floor.

  • A current profile records which outcomes you achieve today, and how well.
  • A target profile records which outcomes you need, given your risk, customers and regulators.
  • The gap between them becomes your roadmap.

For a multi-site company, build one profile per plant plus one for corporate IT, using the same template. Roll them up. The board sees one view, and each plant manager sees their own gaps.

 Corporate IT profile ----\
 Plant A profile ----------+--> Company profile --> Board report
 Plant B profile ----------+        (GV ID PR DE RS RC)
 Plant C profile ----------/

The CSF Manufacturing Profile (NIST IR 8183)

NIST publishes a community profile for manufacturing as NIST IR 8183. Rev. 1, aligned to CSF 1.1, organizes guidance around manufacturing mission objectives such as human safety, environmental safety, product quality, production goals and protection of trade secrets. It maps each CSF outcome to how it applies in a manufacturing system.

The CSF 2.0 update, NIST IR 8183 Rev. 2, was released as an initial public draft on September 29, 2025, with comments due November 17, 2025. According to NIST, the draft realigns guidance to the CSF 2.0 functions including Govern, and adds guidance on supply chain risk management, platform security and technology infrastructure resilience. When we checked the NIST CSRC page on November 17, 2026, it still listed only the initial public draft.

What that means in practice:

  • Use the Rev. 2 draft for its CSF 2.0 structure, but note in your documents that it is a draft.
  • Rev. 1 remains a solid reference for the manufacturing-specific interpretation.
  • Check the CSRC page before an audit or customer submission. A final version may appear.

How CSF fits with OT standards

CSF tells you what outcomes to reach. It does not tell you how to segment a control network or what a PLC should support. For that you need OT-specific guidance:

Need Use
Board and enterprise structure CSF 2.0
OT-specific guidance mapped to CSF NIST SP 800-82 and the Manufacturing Profile
Zone and conduit design, security levels, supplier requirements IEC 62443
Certifiable management system ISO/IEC 27001
EU legal duties NIS2, Cyber Resilience Act

NIST also publishes informative references that map CSF 2.0 outcomes to other frameworks. Our framework crosswalk and the crosswalk workbook show how CSF, 62443, NIS2 and ISO 27001 line up so you do the work once and report it several ways.

Using CSF as the board-level language

Boards do not need subcategory detail. They need to know whether the important outcomes are in place, where the gaps are and what it costs to close them.

A simple quarterly board view:

Function Corporate IT Plant A Plant B Plant C Top gap
Govern On target On target Partial Partial No named OT owner at B and C
Identify On target Partial Gap Partial No OT asset inventory at B
Protect Partial Partial Gap Partial Flat network at B; OEM remote access
Detect Partial Gap Gap Gap No OT monitoring
Respond Partial Gap Gap Gap No OT incident playbook
Recover On target Partial Partial Gap PLC backups untested

Pair it with three or four plain questions the board should be asking. Our board questions page and the board AI risk briefing template cover AI and OT risk together.

What good looks like

After the first cycle, a manufacturer using CSF well has a current and target profile for every site and for corporate IT, built on the same template. Each gap has an owner, a budget line and a date. The board sees one page per quarter, in the six functions, with plant-level detail available on request. Plant managers can explain their own gaps without a consultant in the room. And when a customer questionnaire or a NIS2 audit arrives, the answers come from the profile rather than from a scramble.

Effort and cost

For a 500 to 1,500 person manufacturer with a small IT team:

  • First current profile (all sites): roughly 3 to 6 weeks of part-time effort, mainly interviews and site walks.
  • Target profile: a half-day workshop with the CIO or CISO, operations, engineering and EHS.
  • Ongoing: quarterly refresh of the board view, annual profile update.

Outside help can speed up the first profile. It should not own it. If your team cannot explain its own profile, it will not maintain it.

Common mistakes

  • Treating CSF as a control checklist and scoring every subcategory 1 to 5 without asking whether it matters.
  • Building an IT-only profile and leaving the plants out because "OT is different".
  • Chasing a higher tier everywhere instead of setting targets by risk.
  • Ignoring Govern because it looks like paperwork. It is where ownership and supplier risk live.
  • Citing the Manufacturing Profile Rev. 2 as final when it was still a draft when we checked.

Where to start: Monday-morning checklist

  1. Name one owner for the CSF program and one contact per plant.
  2. Download CSF 2.0 and the Manufacturing Profile (Rev. 1 and the Rev. 2 draft).
  3. Run a two-hour current-profile session at one plant using the six functions.
  4. Write the target profile with operations and EHS in the room, not just IT.
  5. Turn the top five gaps into funded projects with owners and dates.
  6. Run the OT security maturity assessment for a quick baseline across sites.

NIST documents are revised often. Check the NIST CSRC page for the latest status before citing a draft, and confirm any regulatory or contractual use with counsel.

Sources and further reading

  1. NIST Cybersecurity Framework (NIST)
  2. NIST IR 8183 Rev. 2 (Initial Public Draft), CSF 2.0 Manufacturing Profile (NIST CSRC)
  3. CSF 2.0 Manufacturing Profile initial draft announcement (NIST CSRC)
  4. NIST SP 800-82 Rev. 3, Guide to Operational Technology Security (NIST CSRC)

This guide is general information for manufacturers, not legal advice. Confirm regulatory obligations with qualified counsel.

FAQ

Frequently asked questions

Is NIST CSF 2.0 mandatory for manufacturers?

No. CSF 2.0 is voluntary for private companies in the US and elsewhere. It shows up in customer questionnaires, insurance applications and some government contracts, and many regulators accept it as a reasonable reference. Its main use for a manufacturer is as an organizing structure that links IT, OT and board reporting, not as a compliance target.

What changed from CSF 1.1 to CSF 2.0?

CSF 2.0 added the Govern function, broadened the scope from critical infrastructure to all organizations, gave supply chain risk management more weight, and reorganized categories and subcategories. NIST also published implementation examples, quick-start guides and an online reference tool. The core idea of profiles and tiers stayed the same.

Is there a NIST CSF 2.0 manufacturing profile?

NIST published the initial public draft of NIST IR 8183 Rev. 2, the CSF 2.0 Manufacturing Profile, on September 29, 2025, with comments closing November 17, 2025. When we checked in November 2026, no final version was listed on the NIST CSRC page. Rev. 1, aligned to CSF 1.1, remains available and still useful.

How do CSF tiers differ from IEC 62443 security levels?

CSF tiers (Partial, Risk Informed, Repeatable, Adaptive) describe how rigorously an organization governs and manages cybersecurity risk. IEC 62443 security levels describe how strong an attacker a specific zone, system or component can resist. A company can be Tier 3 overall and still have zones that only reach security level 1.

Related guides

Know where your plants stand

Score your AI governance, OT security and data readiness in about 10 minutes each. Results stay in your browser.