There is a comment window open right now that most operations leaders will never see. It closes on a Monday, it concerns equipment they already own, and the version their contracts cite was published three years ago.
NIST's own project page says it plainly: the comment period for the initial public draft of SP 800-82 Revision 4, the Guide to Operational Technology (OT) Security, is open through November 30.
That is the whole of the headline, and it is enough to justify a procurement conversation this month.
What NIST's published pages establish
The operational technology security project page carries a recent-updates note dated September 21, 2026. It reads: "A comment period for the initial public draft of SP 800-82r4 (Revision 4), Guide to Operational Technology (OT) Security, is open through November 30th."
The predecessor is documented at both ends. SP 800-82 Revision 3 was published in September 2023 and superseded Revision 2 of June 3, 2015. Its own publication page carries a planning note, also dated September 21, 2026, pointing readers to the Revision 4 draft with comments due November 30, 2026.
So the timeline is simple to state and awkward to ignore. A guidance document that enterprises have been citing for three years is being revised in public, and the comment window closes at the end of this month.
What this edition did not do is read the draft. Neither the text nor a summary of its contents was reviewed here, so no characterization is made of what it adds, removes or changes. The published record establishes the deadline and the process. It does not, in the pages reviewed, establish the substance.
Why operational technology is the hard case
NIST's abstract for Revision 3 states its purpose in one clause: securing operational technology "while addressing their unique performance, reliability, and safety requirements."
The same text defines the category. OT encompasses programmable systems and devices that interact with the physical environment, and that detect or cause a direct change through the monitoring or control of devices, processes and events. The listed examples are industrial control systems, building automation systems, transportation systems, physical access control systems, and environmental monitoring and measurement systems.
For an enterprise buyer, that list is not abstract. It is the distribution center's conveyor controls, the plant's line equipment, the loading dock's access system, the cold chain's monitoring.
Those systems share a property that office software does not. The equipment outlives the software, the vendors are numerous, and a patch window and a production window are not the same window.
The NIST Cybersecurity Framework, in its 2.0 form, organizes outcomes around six functions: Govern, Identify, Protect, Detect, Respond and Recover. The observation that Respond and Recover receive the least rehearsal is this publication's analysis, not a finding in the framework.
The procurement half is already published
CISA's Secure by Design initiative carries a document aimed directly at this audience: "Secure by Demand: Priority Considerations for Operational Technology Owners and Operators when Selecting Digital Products." The page describes it as intended to help owners and operators procure operational technology products.
The initiative is voluntary guidance rather than a certification, and it places the obligation upstream. It states that "Every technology provider must take ownership at the executive level to ensure their products are secure by design," and that the burden has been "placed disproportionately on the shoulders of consumers and small organizations and away from the producers of the technology."
That pairing is the practical point, and it is the part a buyer can act on today. The technical guide is still in draft. The purchasing guide is already published. An organization that waits for the final NIST text before asking its vendors procurement questions has the order backwards.
Why framework language ends up in your contracts
This section is analysis.
Framework language becomes questionnaire language, and questionnaire language becomes contract language. The sentence a vendor eventually quotes back in a security review is frequently a sentence that began as a draft paragraph during a comment period, and the organizations that wrote comments are the ones whose objections were answered.
A comment window is also among the cheapest forms of influence available to a mid-market company. Filing requires no membership and no procurement. Not filing is a choice too, and it is the one most enterprises make.
There is a second, less comfortable reason to pay attention. A revision that takes roughly three years to move from publication to redraft describes a problem that is not fully solved. Operational technology security is difficult to write guidance for precisely because the constraints are physical. If the guidance is still being argued over, the same ambiguity probably exists on your own plant floor.
The dockets are not standing still
One adjacent deadline is documented on an approved source. The NIST Cybersecurity Framework page lists a public comment window running until December 7, 2026 for Special Publication 800-221r1, an initial public draft on the enterprise impact of information and communications technology risk, described as helping organizations improve ICT risk management "in alignment with established frameworks, including the CSF 2.0."
Operational technology security and enterprise ICT risk are two vocabularies that meet in the same procurement conversation. Both are open for comment in the same stretch of weeks.
Four questions before the next OT purchase
- Which edition of the guidance is your vendor citing? Revision 3 is a September 2023 document whose successor is in draft. A vendor quoting a standard should be able to name the edition and its publication date.
- What will this equipment record about its own failure? Not whether it is reliable. What log exists, where it lives, and whether it survives the device going down.
- Who owns the patch decision on the plant floor? A named role and a documented window. If the answer is "whoever can get the line stopped," the process is the constraint, not the software.
- What does the security questionnaire ask that this system cannot answer today? That gap is the honest scope of the work, and it is cheaper to find before the purchase order than after.
A 30-day check
- Days 1 to 5. List every system on site that meets NIST's definition of operational technology, by location and by vendor.
- Days 6 to 10. For each, record which guidance edition your security questionnaire currently references.
- Days 11 to 15. Read CISA's Secure by Demand considerations for OT owners and operators, and mark the questions your current vendors cannot answer.
- Days 16 to 22. Identify the one system whose failure would stop outbound flow, and write down who decides to patch it.
- Days 23 to 30. Decide whether your organization will file a comment before the window closes, and who signs it.
What remains unconfirmed
- The contents of the SP 800-82 Revision 4 draft. Neither the document nor a summary of it was reviewed for this edition, and no claim is made about what it changes.
- Whether the November 30 comment deadline will be extended. No extension appeared in the material reviewed.
- What comment volume either docket has received, and whether any enterprise or trade association has filed.
- The substance of SP 800-221r1. Its comment window was reviewed; its text was not.
- Whether any organization has changed a purchase, a contract or an audit outcome as a result of either draft. None is asserted.
- Market data. No stock, index or valuation figures were reviewed for this edition.
Evidence notes and limits
NIST's operational technology security project page is the source for the September 21, 2026 recent-updates note and for the quoted statement that a comment period for the initial public draft of SP 800-82r4 is open through November 30th. It is also the source for the description of operational technology as encompassing programmable systems or devices that interact with the physical environment and that detect or cause a direct change through monitoring or control of devices, processes and events, with examples including industrial control systems, building automation systems, transportation systems, physical access control systems, and environmental monitoring and measurement systems.
NIST's publication page for SP 800-82 Revision 3 is the source for its September 2023 publication date, its supersession of Revision 2 dated June 3, 2015, the September 21, 2026 planning note pointing to the Revision 4 draft with public comments due November 30, 2026, and the quoted purpose of securing operational technology "while addressing their unique performance, reliability, and safety requirements." It is guidance rather than a certification, and no conformity determination is drawn from it.
The NIST Cybersecurity Framework page is the source for the comment window running until December 7, 2026 on Special Publication 800-221r1, for its initial-public-draft status, and for the quoted description that it helps organizations improve ICT risk management in alignment with established frameworks including CSF 2.0. The framework's six functions are cited as named functions only; the observation about Respond and Recover is this publication's analysis.
CISA's Secure by Design page is the source for the existence and stated purpose of "Secure by Demand: Priority Considerations for Operational Technology Owners and Operators when Selecting Digital Products"; for the quoted statement that "Every technology provider must take ownership at the executive level to ensure their products are secure by design"; and for the quoted statement that the burden has been "placed disproportionately on the shoulders of consumers and small organizations and away from the producers of the technology." It is voluntary guidance, and no certification or measured outcome is asserted from it.
The Revision 4 draft itself was not retrieved or read. The reading of framework language as contract language, the point about revision timelines as a signal of difficulty, the four questions and the 30-day check are this publication's analysis. Nothing here establishes that any organization improved security, passed an audit or prevented an incident.
The advertisement above is separate from this analysis and is not a source for any claim in it.