- ClassificationCategoryCybersecurityDomainCybersecurityFramework FamilyNIST Special Publications
- Regulatory ContextTypeGuidanceLegal InstrumentGuidelineSectorCross-SectorIndustryCross-Industry
- Region / PublisherRegionNorth AmericaRegion DetailUnited StatesPublisherNational Institute of Standards and Technology (NIST)
- VersioningVersionRevision 3 OT overlay (September 28, 2023; Revision 4 initial public draft September 2026)Effective DateSeptember 28, 2023Issue DateSeptember 28, 2023
- AdoptionAdoption ModelVoluntaryImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
NIST SP 800-82 Rev. 3, with the OT overlay in Appendix F, is free of charge from NIST; the CSRC record links the publication at DOI 10.6028/NIST.SP.800-82r3.
Framework text is licensed by its publisher and is included only where stated above.
- The High baseline of the NIST SP 800-82 Rev. 3 OT overlay is the SP 800-53B high baseline tailored for high-impact OT systems.
- It applies where at least one of confidentiality, integrity, and availability is categorized high under FIPS 199.
- NIST published Revision 3 on September 28, 2023; a Revision 4 draft is open for comment until November 30, 2026.
- Appendix F adds and removes controls for OT and attaches OT Discussion to many of them.
- The guide's own power-plant SCADA example lands at integrity high and availability high, selecting the High column.
Overview
The High baseline of the NIST SP 800-82 Rev. 3 OT overlay is the set of SP 800-53 Rev. 5 controls that Appendix F of the Guide to Operational Technology (OT) Security allocates to high-impact OT systems: systems in which at least one of confidentiality, integrity and availability is categorized high under FIPS 199 (SP 800-53B Section 2.2). NIST published Revision 3 on September 28, 2023. The High baseline starts from the high baseline of NIST SP 800-53B (see the SP 800-53B High baseline page), adds and removes controls for OT and attaches OT Discussion to many of them; this page describes that baseline only.
The guide as a whole runs from an OT overview and the IT-to-OT differences in Section 2, through the OT cybersecurity program in Section 3, risk management and the RMF for OT in Section 4, security architecture in Section 5 and the Cybersecurity Framework in Section 6, to appendices on threats and incidents, organizations, capabilities and tools, and the overlay in Appendix F. Its authors come from NIST and MITRE, and the Document History on CSRC shows drafts of April 23, 2021 and April 26, 2022 before the final of September 28, 2023. A Revision 4 initial public draft is open for comment until November 30, 2026, and Revision 3 stays current until that revision is final.
High-impact OT is the level at which the guide's own categorization example lands: the power-plant SCADA system in Section 4.3.2 ends with integrity HIGH and availability HIGH, so it selects the High column of Table 22. From there an organization works through the F.7 family tables, applies the F.4 tailoring rules and documents the result in the OT security plan.
Why does it matter?
FIPS 199 reserves the high level for a loss that could have a severe or catastrophic adverse effect, and the overlay's own rationale for AC-3(11) spells out what that means for OT: severe degradation or loss of mission capability, major damage to organizational assets, or harm to individuals involving the loss of life or life-threatening injuries. The SP 800-53B high baseline is the largest of the three, and Appendix F adjusts it for OT rather than simply enlarging it, adding four high-only items and removing an enhancement that high-impact OT often cannot satisfy.
Key benefits include:
- Four additions found only at High
F.7 adds AC-3(11) Restrict Access to Specific Information Types, IA-12(1) Supervisor Authorization for identity proofing, SC-47 Alternate Communications Paths and SI-13 Predictable Failure Prevention to the High baseline alone, each with a rationale tied to high-impact consequences.
- Loss of view or control treated as a safety matter
The SC-47 OT Discussion asks which systems need alternate communication paths so that a loss of communication does not lead to an unacceptable loss of view or control or to a safety event.
- Latent faults in long-running OT
The SI-13 rationale notes that OT may run far longer than conventional systems, so flaws such as integer overflow can surface, and that restarting a system or application may not be acceptable for operational reasons.
- A realistic penetration-testing requirement
CA-8(1), the independent penetration testing agent or team, is removed from the High baseline because the OT expertise needed may not exist in independent personnel, although an independent test is still recommended.
- The same OT additions as the other baselines
CP-12 Safe Mode, SI-17 Fail-Safe Procedures, MA-7 Field Maintenance, AU-4(1), AC-17(9), SA-4(12), SC-7(28), SC-7(29), SC-41 and SC-45 are added at every impact level, so a High system carries them too.
How does it work?
The baseline is chosen by security categorization, which Section 4.3.2 illustrates with the FIPS 199 example of a SCADA system that distributes electric power for a large military installation. Management rated the sensor data at no impact for confidentiality and high for integrity and availability, and the administrative information low on all three; the high-water mark made the system {confidentiality LOW, integrity HIGH, availability HIGH}, and management then raised confidentiality to MODERATE. Because at least one objective is high, the system is high impact and takes the High column of Table 22; Table 7 records the result through Task C-2 in the security, privacy and SCRM plans.
The High column of Table 22 in F.3 is the fullest of the three. AC-2 carries enhancements (1) (2) (3) (4) (5) (11) (12) (13); AC-6 carries (1) (2) (3) (5) (7) (9) (10); AC-18 carries (1) (3) (4) (5); AU-6 carries (1) (3) (5) (6); CP-2 carries (1) (2) (3) (5) (8); CP-10 carries (2) (4) (6); MP-6 carries (1) (2) (3); SC-7 carries (3) (4) (5) (7) (8) (18) (21) (28) (29); and SR-9(1) appears at High only. Three items that the Moderate baseline adds, SC-7(18) Fail Secure, SC-24 Fail in Known State and PE-6(4), are already in the SP 800-53B high baseline and are therefore marked Select rather than Add here.
Every F.7 family table marks each row Select, Add or Remove for the Low, Moderate and High baselines, states the OT Discussion and gives the rationale for each change, in the format that Fig. 22 illustrates with AU-4. Where a High control cannot be applied as written, F.4 allows a compensating control under PL-11, with the reason, the equivalence and the accepted residual risk written into the OT security plan. The SI-17 OT Discussion adds that the same failure event may call for a different response at a different impact level, and F.4 allows the value of an assignment to differ between baselines, so a High system can set stricter conditions than a Moderate one.
Key Elements
- High column of Table 22 (F.3)
The controls and enhancements allocated to high-impact OT systems, with Bold for OT discussion, Underline for additions beyond SP 800-53B and Strikethrough for removals.
- High-only additions (F.7)
AC-3(11) Restrict Access to Specific Information Types, IA-12(1) Supervisor Authorization, SC-47 Alternate Communications Paths and SI-13 Predictable Failure Prevention, each marked Add in the High column alone.
- Additions shared with the Moderate baseline (F.7)
AC-17(10) Authenticate Remote Commands, AT-2(4) anomalous-behavior training, CP-10(6) Component Protection, MA-4(1) Logging and Review of nonlocal maintenance, PE-22 Component Marking and SR-5(1) Adequate Supply.
- Additions at every impact level (F.7)
AC-17(9) Disconnect or Disable Access, AU-4(1) Transfer to Alternate Storage, CP-12 Safe Mode, MA-7 Field Maintenance, SA-4(12) Data Ownership, SC-7(28) Connections to Public Networks, SC-7(29) Separate Subnets to Isolate Functions, SC-41, SC-45 and SI-17 Fail-Safe Procedures.
- Removals from the High baseline (F.7)
CA-8(1) Independent Penetration Testing Agent or Team, SC-10 Network Disconnect (its intent is covered by AC-17(9) for OT) and SI-8(2) Spam Protection automatic updates (spam transport mechanisms are removed from the OT).
- Selected rather than added at High
SC-7(18) Fail Secure, SC-24 Fail in Known State and PE-6(4) Monitoring Physical Access to Systems sit in the SP 800-53B high baseline already, so the overlay marks them Select at High while adding them at Moderate.
- Tailoring and compensating controls (F.4)
The rule that compensating controls under PL-11 are alternative safeguards, not exceptions or waivers, with the three points recorded in the OT security plan and assignments that may differ by baseline.
- Scope limits (F.2 and Appendix F)
Controls that appear only in the privacy baseline are excluded, and the guidelines reach national security systems only with express approval from the federal officials who hold policy authority over them.
What does it cover?
Appendix F was prepared for federal agencies under FISMA 2014, PPD-21 and Executive Order 13636; F.2 adds that non-governmental organizations may use it voluntarily. It is intended for all OT systems in all industrial sectors and may be tailored further for a sector such as pipelines or energy, or for a single system. The High baseline applies to the subset of those systems whose FIPS 199 categorization contains at least one high objective: a plant, utility or facility system where a failure of integrity or availability could cause severe or catastrophic harm to operations, assets or people. Low- and moderate-impact OT systems use the other two baselines on their own pages.
What are its objectives?
Appendix F sets out the purposes of the overlay; at the High level they translate into the following:
Provide guidance for securing high-impact OT systems by tailoring the SP 800-53 Rev. 5 controls and the SP 800-53B high baseline for OT (Appendix F, F.2).
Address the severe or catastrophic consequences of a high-impact loss, including loss of mission capability and harm to individuals, through controls such as AC-3(11) and SC-47 (F.7 rationale).
Keep high-impact OT operating through failures with CP-12 Safe Mode, SI-17 Fail-Safe Procedures, SI-13 Predictable Failure Prevention and alternate communications paths (F.7).
Remove requirements that high-impact OT cannot reliably meet, such as CA-8(1), while recommending the practice where feasible (F.7).
Record every tailoring choice, compensating control and residual-risk acceptance in the OT security plan (F.4).
Framework in Context
The High baseline rests on NIST SP 800-53 Rev. 5 for the control catalog and on NIST SP 800-53B for the high baseline and the overlay concept in its Appendix C (see the SP 800-53B and SP 800-53B High baseline pages). F.4 cites Section 3.3 of NIST SP 800-37 Rev. 2 for control tailoring, F.2 points to the NIST Privacy Framework for privacy risk in OT, while Section 6 of the guide relates OT practice to the Cybersecurity Framework. The Low OT overlay and Moderate OT overlay pages describe the other two baselines. The CSRC record also lists the Potential updates spreadsheet of July 10, 2024 and the Revision 4 initial public draft (comments due November 30, 2026).
Common Framework Mappings
Owners of high-impact OT usually report against sector regulations and control catalogs as well, so the High OT baseline is commonly mapped to the following frameworks.
Mapped frameworks include:
CIS Controls v8.1
IEC 62443
ISO 27001:2022
ISO 27002:2022
NERC CIP
NIST CSF 2.0
NIST 800-53 Rev.5
PCI DSS 4.0.1
SOC 2
How SmartSuite Supports NIST SP 800-82 Rev. 3 (High OT Overlay)
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Cyber & IT Risk for the High column of Table 22 and the AC-3(11) information-type restrictions, Operational Resilience & Business Continuity for the safe mode, fail-safe, failover and alternate-communications decisions, and Internal Audit Management for the assessment and penetration-testing evidence that CA-2 and CA-8 require.
High Baseline Control Register
Hold every control and enhancement in the High column of Table 22 as a record in Cyber & IT Risk, with its F.7 status (Select, Add or Remove), the OT Discussion text and the responsible owner.
Categorization and High-Water-Mark Record
Document the FIPS 199 impact per information type together with the system category that Task C-2 (Table 7) produced, so the reason the system sits in the High baseline is on file.
Information-Type Access Restrictions
Keep the AC-3(11) list of information types that are sensitive, proprietary, trade secret or safety related, with the access restrictions applied to each, as linked records in Cyber & IT Risk.
Failure, Failover and Alternate Paths Plan
Record the CP-12 safe mode conditions, SI-17 fail-safe procedures, SI-13 failure-prevention measures and SC-47 alternate communications paths in Operational Resilience & Business Continuity, with test dates.
Assessment and Penetration-Testing Evidence
Schedule CA-2 control assessments and CA-8 penetration tests in Internal Audit Management, and file the documented reason where an independent agent under CA-8(1) was not used.
Compensating-Control and Residual-Risk Log
Log each F.4 compensating control with why the baseline control could not be implemented, the equivalence case and the residual risk that was accepted, in Compliance Management with the security plan reference.
Related frameworks

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

IEC 62443-4-2:2019 sets technical security requirements for IACS components, with seven foundational requirements and security levels 1 to 4.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

MITRE ATT&CK is a free knowledge base of adversary tactics, techniques and sub-techniques from The MITRE Corporation, updated twice a year; the current release is v20.0.

NERC CIP (CIP-002 through CIP-015) are the mandatory cybersecurity and physical security Reliability Standards for the North American bulk electric system, approved by FERC.
Frequently Asked Questions For NIST SP 800-82 Rev. 3 (High OT Overlay)
Systems categorized as high impact under FIPS 199, which SP 800-53B Section 2.2 defines as any system in which at least one of confidentiality, integrity and availability is high. The guide's own example in Section 4.3.2, a SCADA system distributing power for a large military installation, ends at {confidentiality MODERATE, integrity HIGH, availability HIGH} and is therefore a high-impact system.
Four items are marked Add at High only in F.7: AC-3(11) Restrict Access to Specific Information Types, IA-12(1) Supervisor Authorization, SC-47 Alternate Communications Paths and SI-13 Predictable Failure Prevention. The High baseline also carries the additions it shares with Moderate (AC-17(10), AT-2(4), CP-10(6), MA-4(1), PE-22, SR-5(1)) and those made at every level (CP-12, SI-17, MA-7, AU-4(1), AC-17(9), SA-4(12), SC-7(28), SC-7(29), SC-41, SC-45).
F.7 explains that specific expertise is necessary to conduct effective penetration testing on OT systems and that it may not be feasible to find independent personnel with that skillset. An independent penetration test agent or team is still recommended, but it is not required for every high-impact OT system. CA-8 itself remains selected, and SC-10 and SI-8(2) are also removed at High.
Every baseline adds CP-12 Safe Mode and SI-17 Fail-Safe Procedures; SI-13 Predictable Failure Prevention and SC-47 Alternate Communications Paths are added at High; and SC-7(18) Fail Secure and SC-24 Fail in Known State are selected because the SP 800-53B high baseline already contains them. The SI-17 OT Discussion notes that fail-safe states should account for human safety, physical systems and the environment, and that responses may differ by impact level.
Appendix F describes the overlay as a partial tailoring of the SP 800-53 Rev. 5 controls and the SP 800-53B baselines, following the overlay concept in SP 800-53B Appendix C; the High baseline is the SP 800-53B high baseline tailored for OT. The CSRC record for SP 800-82 Rev. 3 notes that the initial public draft of Revision 4 is open for public comment until November 30, 2026, so Revision 3 and its overlay remain current until Revision 4 is final.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


