What is a security control overlay?

A tailoring of an existing control baseline for a particular kind of system. SP 800-234 does not define the term itself: it states that it develops an overlay as defined in NIST SP 800-53B. What the HPC overlay does in practice is take the SP 800-53B moderate baseline, work down it control by control, and add supplemental guidance and discussion that say what each control means on an HPC system. The catalogue is not rewritten, and nothing is renumbered. The reading of it changes.

How many controls does SP 800-234 tailor?

Sixty. The overlay's table lists 288 controls: 287 that belong to the SP 800-53B moderate baseline, plus one that does not and was added for HPC, AC-10, Concurrent Session Control. Of those 288, exactly 60 carry tailoring in the form of supplemental guidance, added discussion, or both. AC-10 is one of the 60, which is why the denominator is 288 rather than 287.

Do I need SP 800-223 first?

You need what it contains. Four of the overlay's five tailoring levels are the function zones SP 800-223 defines, and SP 800-234 reproduces that reference architecture and credits it. Its own control discussions send you back there: CA-9 notes that communication connections between zones are outlined in SP 800-223, and SC-8 defines internal connections as those inside the HPC boundary as SP 800-223 defines it. Read the architecture first, then the overlay.

Does SP 800-234 apply to GPU and AI clusters?

It is written for HPC systems, and one of its 14 thematic groups is titled Shared GPUs and Accelerators, so accelerators are inside its scope rather than an afterthought. Whether it binds you is a separate question from whether it fits: outside federal information systems the publication states it may be used on a voluntary basis. A GPU estate bought as an AI project usually has the same shared login plane, scheduler and storage the overlay is written against, so it is worth reading even where nobody requires it.

Is SP 800-234 mandatory for federal HPC?

It carries a federal statutory basis rather than a deadline. SP 800-234 was developed under NIST's FISMA responsibilities, which include minimum requirements for federal information systems, and the same front matter states that it is not binding on national security systems without separate approval and may be used by nongovernmental organizations on a voluntary basis. The overlay is also explicitly a floor: it is built on the moderate baseline, and its own text says a system at a high baseline can be expanded with additional controls.

Framework · NIST SP 800-234

NIST SP 800-234, explained

The control overlay NIST published for high-performance computing. It takes the SP 800-53B moderate baseline and tailors it for a machine that breaks several of the assumptions underneath it. What the overlay changes, who it binds, and how to adopt it on a cluster that is already running.

High-Performance Computing (HPC) Security Overlay

The overlay, counted

288Controls in the overlay's table
287Carried from the SP 800-53B moderate baseline
1Added for HPC: AC-10, Concurrent Session Control
60Tailored with supplemental guidance, discussion, or both
5Levels the tailoring is applied at

AC-10 is one of the 60. It is added to the baseline and tailored at the same time, which is why the denominator is 288.

Final · 4 May 2026Base · SP 800-53B moderate baseline60 of 288 controls tailored

The publication

What NIST SP 800-234 is

NIST Special Publication 800-234 is titled High-Performance Computing (HPC) Security Overlay. It went out as an initial public draft on 1 May 2025 and was published as final on 4 May 2026.

It answers the question SP 800-223 left open. The architecture publication describes what a cluster is and what threatens it, and then stops, by its own description a conceptual guide rather than a checklist. SP 800-234 is the checklist half: which controls apply to this machine, and what each one has to mean once the host is shared, the software is compiled by the person running it, and rebooting a node ends someone’s week of compute.

The publication does not define the word overlay. It borrows the definition, stating in its introduction that it “develops an overlay, as defined in NIST Special Publication (SP) 800-53B.” What it then does is the definition worth carrying in practice. It starts from an existing control baseline, works down it control by control, and adds supplemental guidance and discussion that say what that control means on an HPC system. The catalogue is not rewritten. The reading of it changes.

The base is stated three separate times inside the document, so there is no ambiguity about it: the overlay is built on the moderate baseline defined in SP 800-53B. Its abstract puts the whole thing in one line, that the overlay “tailors 60 security controls from NIST SP 800-53 with supplemental guidance and/or discussion to enhance their applicability in HPC contexts.”

Unlike SP 800-223, it names who it is written for: IT security managers, compliance officers, HPC system administrators, and agency program managers responsible for securing HPC environments. And it names its own ceiling. The abstract offers the overlay as “a robust foundation for securing HPC environments while also allowing for further customization to meet specific operational or mission needs.” A floor to build on, in other words, not the finished answer for every machine.

The author list is the operators again: NIST staff alongside contributors from Argonne, Los Alamos, Lawrence Livermore, Sandia, MIT Lincoln Laboratory, NASA, the Ohio Supercomputer Center, the DoD HPCMP, and the universities of Arkansas and Florida.

The record

Publication: NIST SP 800-234
Initial public draft: 1 May 2025
Final: 4 May 2026
Base: The moderate baseline defined in SP 800-53B
Structure: One control table, 60 tailored entries, 14 thematic groups

Read it at NIST

The mechanics

How the overlay works

An overlay is a reading of a baseline, and this one is countable. Three things define it: what it starts from, how many controls it touches, and where the tailoring is applied.

One cell per control in the overlay’s table: 288 in total, sixty of them tailored, counted in full in the ledger above. Position in the grid carries no meaning; the proportion is the point. Drawn by Alvor from the counts stated in the publication.

Tailored59 controls carrying supplemental guidance, added discussion, or both

AC-10The control added to the baseline; its row is below

Untailored228 controls the overlay carries from the moderate baseline unchanged

Five levels

Tailoring is written for the whole system, and then for each zone in turn.

The publication states it plainly: the tailoring and augmented discussions are conducted at five levels, the entire HPC system, which it calls All Zones, then the Access Zone, the Management Zone, the Computing Zone and the Data Storage Zone. Those four zones are SP 800-223’s, reproduced and credited, with the first shortened to Computing Zone.

All Zones

Access ZoneThe way in

Management ZoneHow it is run

Computing ZoneWhere the work runs

Data Storage ZoneWhat feeds it

The direction of inheritance is set by the table’s own footnotes. Supplemental guidance for All Zones automatically applies to each individual zone, and so does a discussion written for All Zones. A zone column is for what is true of that zone alone.

Supplemental guidance, discussion, or both

Every row in the overlay’s table is marked, and the marks are the whole mechanism. The legend defines four of them.

G: “indicates that the control is tailored with supplemental guidance for All Zones and/or individual zones.”
D: “indicates that a discussion is added for All Zones and/or individual zones.”
N: “indicates that the control does not belong to the moderate control baseline but has been added to the HPC security overlay.” One control carries it: AC-10.
--: “no additional supplemental guidance or discussion.” The control stands as the baseline writes it.

Beyond that legend the publication does not draw an abstract line between the two. Read across the 60 worked entries, a pattern holds: guidance states a practice, and discussion explains the reasoning around it. AC-2 is a fair example of both halves, with supplemental guidance for the Access Zone saying the zone “should be accessible to all authorized accounts” and a discussion for All Zones saying that “an account’s role should dictate its access to the HPC system and specific zones.” Many controls carry both, and the table marks those GD.

One row, exactly as the table has it

AC-10, Concurrent Session Control, is the only control in the overlay marked N. It answers two questions at once: N says it did not come from the moderate baseline, GD says it is tailored like any other row.

Control: AC-10
Moderate baseline: N
All Zones: GD
Access Zone: --
Management Zone: --
Computing Zone: --
Data Storage Zone: --

The publication adds it because it is relevant to controlling the number of user sessions on an HPC system, and notes that it is tailored into several widely used control frameworks already.

How the 60 are organized

By argument, not by control family.

Section 3 sorts the tailored controls into 14 groups for easier comparison, and the group names are the most useful index into the document. They are the recurring fights on a cluster, written down. The tenth is titled Inapplicable to HPC.

3.1Role-Based Access Control
3.2HPC Logging
3.3User Sessions
3.4HPC Contingency Planning
3.5HPC Network Connections
3.6Identification and Authentication
3.7Emergency Handling
3.8User-Developed Software
3.9Impact on HPC Performance and Scalability
3.10Inapplicable to HPC
3.11Shared GPUs and Accelerators
3.12HPC-Specific Training and Security Overlay Tailoring
3.13HPC Management, Operation, and Maintenance
3.14Access to HPC

Section 3, on a real machine

What actually changes on a cluster

Five of the overlay’s 14 groups name arguments we have watched stall for months between a security team and an HPC team. Each one lines up with a row of our own control catalogue, where the same standoff is written from the other side: the control as the enterprise runs it, why it breaks here, and what replaces it.

3.9Overlay group

Impact on HPC Performance and Scalability

The performance argument has a heading of its own in the overlay. Naming it is what lets a team argue the cost of a control without appearing to argue against the control.

The enterprise control

EDR agent on every host

It wakes on its own cadence and desynchronizes tightly-coupled jobs, and both license and telemetry multiply by node count.

What replaces it

eBPF and sampled instrumentation, out-of-band collection, and telemetry drawn from the fabric and the scheduler.

In the control catalogue: Impact on HPC Performance and Scalability

3.5Overlay group

HPC Network Connections

The overlay backs this one with a direct citation to SP 800-223's own zone boundaries, quoted in the FAQ below.

The enterprise control

Inline firewall, IPS, microsegmentation

RDMA bypasses the kernel, so the appliance either inspects traffic that routes around it or reimposes the latency the fabric was built to remove.

What replaces it

Segmentation designed into the topology and the scheduler, enforced at the zone edge rather than the hot path.

In the control catalogue: HPC Network Connections

3.3Overlay group

User Sessions

The enterprise control

MFA and SSO on every login

Hundreds of users share login nodes and one filesystem, and static SSH keys have historically traveled freely between sites.

What replaces it

Short-lived SSH certificates, federated research identity, and multi-factor enforced at the access zone.

In the control catalogue: User Sessions

3.1Overlay group

Role-Based Access Control

The overlay's first group, and usually the first place a conventional catalogue and a shared cluster part ways.

The enterprise control

Least privilege per user

Access is granted to projects rather than people, on a shared filesystem, and research software frequently expects to build and run as root.

What replaces it

Project-scoped ACLs, enclave separation for regulated work, and no shared root anywhere.

In the control catalogue: Role-Based Access Control

3.8Overlay group

User-Developed Software

Nothing else on this list makes an assessor as uneasy, and nothing else sits as close to the reason the machine was bought.

The enterprise control

Change control and a software board

Researchers install their own stacks with Spack and containers, on the cadence the science demands rather than a change window.

What replaces it

Curated base images, a container policy on Apptainer, and provenance on what actually ran.

In the control catalogue: User-Developed Software

The overlay does not write the right-hand column for you. What it does is settle the argument about whether the left-hand column is allowed to be questioned, and it settles it in NIST’s own words, on the same baseline your assessor is already reading from.

The pair

SP 800-223 and SP 800-234

They are one answer published in two halves, more than two years apart. The architecture describes the machine. The overlay marks the controls against it. The dependency runs one way only.

SP 800-223 · February 2024

Describes the machine

Access zoneManagement zoneComputing zoneData storage zone

One system boundary

SP 800-234 · May 2026

Marks the controls, zone by zone

ControlModerate baselineAll ZonesAccess ZoneManagement ZoneComputing ZoneData Storage Zone

288 rows. 60 carry a G, a D, or both.

Scroll sideways for every column

The four function zones SP 800-223 defines become four of the five levels SP 800-234 tailors at. Drawn by Alvor from the structure both publications set out in prose. The overlay’s table is shown as column structure only, and its own text is the authority on what any control is marked.

SP 800-223

What is this machine, and what threatens it?

A reference architecture, a threat analysis that follows the zones, and posture recommendations. It carries no control requirements and it never mentions SP 800-53. Final on 9 February 2024.

NIST SP 800-223, explained

SP 800-234

Which controls apply to it, and what do they mean here?

An overlay on the SP 800-53B moderate baseline: 288 controls in one table, 60 of them tailored, sorted into 14 thematic groups and marked at five levels. Final on 4 May 2026.

Read SP 800-234 at NIST

Read them in this order

The architecture first, because the overlay assumes you have it.

SP 800-234 reproduces the four-zone architecture, credits SP 800-223 for it, and sends you back there inside its own control discussions. Tailoring written for the Computing Zone only means something once you know what that zone holds. The traffic never runs the other way: SP 800-223 was final more than two years earlier and does not cite the overlay.

Applicability

Who SP 800-234 applies to

This gets stated wrongly in both directions, as federal-only on one side and as pure best practice on the other. The publication is clear, and it is both things at once.

Federal information systems

The statutory ground

SP 800-234 was developed under NIST's responsibilities under FISMA, which include minimum requirements for federal information systems. That is the authority the publication is written under, and the front matter says so directly. It also carves out national security systems, which are not bound by it without separate approval.

Everyone else

Voluntary, and invited

The same front matter states that the publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. A pharmaceutical company, a research university outside federal funding, or an AI team with a GPU estate can adopt the overlay without anyone requiring it.

The roles it names

Named in the abstract

IT security managers, compliance officers, HPC system administrators, and agency program managers responsible for securing HPC environments. SP 800-223 names no audience at all, so this specificity belongs to the overlay alone. It is written for the people who have to answer for the machine rather than design it.

A floor, not a ceiling

The overlay expects to be extended.

It is built on the moderate baseline, and the publication gives two worked examples of where that will not be enough. An HPC system supporting multi-tenancy may need its own overlay, developed from this one. A system categorized at a high baseline requires additional considerations and can be expanded with additional controls.

So the honest reading is that adopting SP 800-234 is a starting position rather than a finish line, and that a machine carrying data with stricter conditions than the rest of its workload is exactly the case the publication expects you to build past.

Putting it on a real cluster

Adopting the overlay on a machine that is already running

Sixty tailored controls are a reading, not a project plan. The distance between the publication and a cluster whose control set matches it is the work, and it has to be done without taking the throughput the machine exists to deliver. Three steps, in this order.

01Assess the machine

Start from what the cluster actually does, not the diagram.

The overlay is written against zones, so the first question is which zones you have and where their boundaries really sit. We walk the machine itself, benchmark the workloads that matter, and hand back a threat model and a ranked gap register against the control set that applies to you.

Assess

02Build the control set

One control set, marked the way the overlay marks it.

Every control gets an answer at the level it belongs to: the whole system, or one zone. That is the work the five levels are for, and it is where an argument that has stalled for months usually resolves, because the tailored reading is on the same baseline the assessor is already using.

HPC Security

03Enclave the regulated work

Do not drag the whole machine to your strictest rule.

The overlay expects to be extended where the data demands it. An enclave with its own logins, its own storage and its own approved way out keeps one dataset from pulling every node into scope, and leaves the open science running at the speed it was bought for.

The enclave

The whole practice

HPC security, end to end: the scheduler, the fabric, the parallel filesystem and the login plane.

HPC Security

Frequently asked

NIST SP 800-234 questions, answered

What is a security control overlay?: A tailoring of an existing control baseline for a particular kind of system. SP 800-234 does not define the term itself: it states that it develops an overlay as defined in NIST SP 800-53B. What the HPC overlay does in practice is take the SP 800-53B moderate baseline, work down it control by control, and add supplemental guidance and discussion that say what each control means on an HPC system. The catalogue is not rewritten, and nothing is renumbered. The reading of it changes.
How many controls does SP 800-234 tailor?: Sixty. The overlay's table lists 288 controls: 287 that belong to the SP 800-53B moderate baseline, plus one that does not and was added for HPC, AC-10, Concurrent Session Control. Of those 288, exactly 60 carry tailoring in the form of supplemental guidance, added discussion, or both. AC-10 is one of the 60, which is why the denominator is 288 rather than 287.
Do I need SP 800-223 first?: You need what it contains. Four of the overlay's five tailoring levels are the function zones SP 800-223 defines, and SP 800-234 reproduces that reference architecture and credits it. Its own control discussions send you back there: CA-9 notes that communication connections between zones are outlined in SP 800-223, and SC-8 defines internal connections as those inside the HPC boundary as SP 800-223 defines it. Read the architecture first, then the overlay.
Does SP 800-234 apply to GPU and AI clusters?: It is written for HPC systems, and one of its 14 thematic groups is titled Shared GPUs and Accelerators, so accelerators are inside its scope rather than an afterthought. Whether it binds you is a separate question from whether it fits: outside federal information systems the publication states it may be used on a voluntary basis. A GPU estate bought as an AI project usually has the same shared login plane, scheduler and storage the overlay is written against, so it is worth reading even where nobody requires it.
Is SP 800-234 mandatory for federal HPC?: It carries a federal statutory basis rather than a deadline. SP 800-234 was developed under NIST's FISMA responsibilities, which include minimum requirements for federal information systems, and the same front matter states that it is not binding on national security systems without separate approval and may be used by nongovernmental organizations on a voluntary basis. The overlay is also explicitly a floor: it is built on the moderate baseline, and its own text says a system at a high baseline can be expanded with additional controls.

Sources: NIST SP 800-234, final 4 May 2026, and NIST SP 800-223, final 9 February 2024, both read in full. Publication dates from the document history on the NIST Computer Security Resource Center. Quoted phrases are the publications’ own.

How the tailored controls play out on a running cluster.

Sep 1, 202614 min read

The GPU Cluster Nobody Owns: Securing Enterprise AI Infrastructure

AI teams inside ordinary companies now run HPC-class machines holding models and training data. Why the enterprise security stack misses them, and how the NIST SP 800-223 zone architecture applies.

Aug 28, 202615 min read

CUI on a Shared HPC Cluster: Meeting NIST 800-171 Without Fencing the Whole Machine

How research computing centres meet NIST SP 800-171 and CMMC obligations for controlled unclassified information on shared clusters: the enclave pattern, scoping, and the SP 800-223 zones it builds on.

Aug 25, 202615 min read

Why Your Enterprise Security Controls Break on an HPC Cluster (and What Replaces Them)

Ten enterprise controls, from EDR to change control, and what happens to each on a supercomputer: why it breaks, and the HPC-native control that replaces it, mapped to NIST SP 800-223 and SP 800-234.

Sixty controls, and a machine that has to keep running.

A national-scale system, a campus research cluster, or a GPU estate that arrived as an AI project. Tell us what it runs and what it has to protect, and we scope the work in writing before anyone touches a node.

HPC Security Practice Start with an assessment

NIST SP 800-234, explained

High-Performance Computing (HPC) Security Overlay

What actually changes on a cluster

How the tailored controls play out on a running cluster.

Sep 1, 202614 min read