NIST SP 800-128, "Guide for Security-Focused Configuration Management of Information Systems," organizes the information-security side of configuration management into four phases — Planning, Identifying and Implementing Configurations, Controlling Configuration Changes, and Monitoring — covering how to establish a secure baseline, control changes to it, and monitor for drift. Its own abstract explains the focus: "the focus of this document is on implementation of the information system security aspects of configuration management," which is why the publication coins the term security-focused configuration management (SecCM) — "the management and control of secure configurations for a system to enable security and facilitate the management of risk." Authored by Arnold Johnson, Kelley Dempsey and Ron Ross of NIST with Sarbari Gupta and Dennis Bailey of Electrosoft Services, it was originally published in August 2011 and received substantive and editorial errata updates on 10 October 2019. NIST's publication page lists it as Final, with no later revision as of November 2026.
Key takeaways
- SP 800-128 leaves the split to the system owner, and its rules fit a firmware product well.
- Identifying and Implementing Configurations (Sec.
- Understand the change, including unscheduled or unauthorized changes found after the fact.
- Synthetic example, for illustration only: the product and versions are invented.
Where does SecCM fit in SP 800-53's CM family and the RMF?
Section 1.3 of the publication is explicit about its role: it "provides guidelines for implementation of the Configuration Management family of controls defined in NIST [SP 800-53] (CM-1 through CM-9)," and separately "provides important supporting information for the Implement Step, Assess Step, and the Monitor Step" of the Risk Management Framework described in NIST SP 800-37. The publication notes that more specific guidance on the RMF's Monitor step itself sits in NIST SP 800-137, Information Security Continuous Monitoring — SP 800-128's own Monitoring phase (below) supports that RMF step by addressing specifically the system's structural architecture and configuration settings, rather than continuous monitoring in general. Chapter One also states the guidelines apply to all federal systems other than national security systems, while noting state/local/tribal governments and private-sector organizations are "encouraged to consider using these guidelines, as appropriate".
What are a Configuration Item, a baseline and a CM Plan?
Section 2.1.1 grounds the whole guide in a few core definitions:
- Configuration Management (CM) — "a collection of activities focused on establishing and maintaining the integrity of products and systems, through control of the processes for initializing, changing, and monitoring the configurations of those products and systems."
- Configuration Item (CI) — "an identifiable part of a system (e.g., hardware, software, firmware, documentation, or a combination thereof) that is a discrete target of configuration control processes."
- Baseline Configuration — "a set of specifications for a system, or CI within a system, that has been formally reviewed and agreed on at a given point in time, and which can be changed only through change control procedures," used "as a basis for future builds, releases, and/or changes."
- Configuration Management Plan (CM Plan) — a comprehensive description of roles, responsibilities, policies and procedures, built from four parts: the Configuration Control Board (CCB) charter (a group with authority to control and approve changes), Configuration Item Identification (methodology for selecting and naming CIs), Configuration Change Control (the process for updating baseline configurations), and Configuration Monitoring (assessing/testing compliance with the established baseline and reporting on it).
Section 2.1.3 adds the formal definition of the publication's namesake term: "Security-Focused Configuration Management (SecCM) is the management and control of secure configurations for a system to enable security and facilitate the management of risk," built on general CM concepts but focused on "the implementation and maintenance of the established security requirements of the organization and systems."
How should a device maker define Configuration Items for a firmware fleet?
SP 800-128 leaves the split to the system owner, and its rules fit a firmware product well. In the "Determine Configuration Items" task of Section 3.1.2, a system is written as "System = {CI1, CI2, …CIn}", each CI "is part of one, and only one, system", and a CI may combine system components with "non-component (NC) system objects (e.g., documentation, diagrams, firmware)". Each CI gets "an unambiguous identifier" and carries enough data "to enable it to be rebuilt from scratch": owner, placement, component inventory, version numbers, dependencies on other CIs and custom software. For a device maker that suggests one CI per thing that is released and changed on its own schedule:
| CI (example split) | What it contains | Typical owner |
|---|---|---|
| Bootloader and root-of-trust settings | Bootloader binary, signing-key IDs, fuse and debug-lock settings | Platform team |
| Main firmware image, per hardware revision | Image hash, version, component inventory (firmware SBOM), build configuration | Firmware team |
| Default device configuration | Shipped settings: enabled services, ports, accounts, update policy | Product security |
| Update infrastructure | Update server, signing service, release channel rules | DevOps |
| Customer-facing documents | Hardening guide, configuration reference, release notes | Technical writing |
The publication also asks that "tools and testing processes used to validate deviations from approved system baseline configurations are under configuration control", so the build system and the test rig that sign off a release are CIs too.
What are the four phases of SecCM?
Section 2.2 organizes SecCM activity into four major phases, detailed in Chapter Three:
Planning(Sec. 3.1) — developing SecCM policy and procedures, covering areas such as SecCM plans, integration into existing security program plans, the CCB, configuration change control processes, tools, common secure configurations and baseline configurations, monitoring, and compliance metrics. The guide notes it's "typically more cost-effective" to build this at the organizational or mission/business-process risk-management level rather than per-system. Identifying and Implementing Configurations(Sec. 3.2) — developing, reviewing, approving and implementing a secure baseline configuration that represents "the most secure state consistent with operational requirements and constraints," covering configuration settings, software loads, patch levels, physical/logical arrangement, security-control implementation and documentation, automated where possible for interoperability and uniformity. Controlling Configuration Changes(Sec. 3.3) — ensuring changes to the approved baseline are "formally identified, proposed, reviewed, analyzed for security impact, tested, and approved prior to implementation," using access restrictions, process automation, change windows, and verification/audit activities to limit unauthorized or undocumented changes. Monitoring(Sec. 3.4) — validating that the system still adheres to organizational policy, procedure and the approved baseline; identifying undiscovered or undocumented components, misconfigurations, vulnerabilities and unauthorized changes. Per Figure 2-1, "SecCM monitoring activities may loop back to any of the previous phases" — the process is explicitly cyclical, not a one-time sign-off.
How does change control work for a firmware update?
Section 3.3.2 gives nine steps, and a firmware release fits them directly: request the change; record it; decide whether it needs configuration control (pre-approved change types are noted and skip analysis, but documentation "may still require updating"); analyse its security impact; test it "for security and functional impacts"; approve it, usually at the CCB; implement it; verify it; and close it. The verification step is strict: a change request is "not closed until it has been confirmed that the change was deployed without issues", using checks such as vulnerability scans and reassessment of affected controls.
The security impact analysis in Section 3.3.3 has five parts:
Understand the change, including unscheduled or unauthorized changes found after the fact. Identify vulnerabilitiesFor commercial components, this "may include, but is not limited to, a search of the National Vulnerability Database (NVD)"; custom code gets "a more in-depth analysis". Assess risksand decide between acceptance, avoidance (the change is not approved) and mitigation. Assess impact on existing security controls, including other components that depend on the one being changed. Plan safeguards and countermeasureswhere the risk is not acceptable.
Appendix I supplies a template for this analysis. After approval, Section 3.3.4 makes the new baseline current while "the previous baseline is no longer valid but is retained for historical purposes", which "allows for a rollback or restoration" if a production release fails. For a fleet, that is the record that says which firmware version a device should roll back to.
What does a firmware change request look like? (worked example)
Synthetic example, for illustration only: the product and versions are invented. A gateway maker plans release 4.2.1 to replace a TLS library flagged in 4.2.0.
| Step (SP 800-128 §3.3.2) | Record for change request CR-0412 |
|---|---|
| Request, record | Source: vulnerability alert on the TLS library in image 4.2.0 |
| Requires control? | Yes: changes the main firmware image CI |
| Security impact analysis | NVD search on the new library version; checks that cipher defaults and certificate handling are unchanged |
| Test | Regression suite plus a component-inventory diff, 4.2.0 vs 4.2.1 |
| Approve | CCB approves; signing service signs the image |
| Implement, verify | Staged rollout to 5 % of the fleet; post-update scan confirms the old library is gone |
| Record and archive | Baseline 4.2.1 becomes current; 4.2.0 kept as the rollback target |
The inventory diff is the step most teams skip, and it is the one that proves the vulnerable component left the image.
Which SP 800-53 Rev. 5 controls postdate SP 800-128?
SP 800-128 cites CM-1 through CM-9, but the current Rev. 5 control catalog — NIST publishes it as machine-readable OSCAL content, version 5.2.0 — runs to CM-14. The additions are CM-10 Software Usage Restrictions, CM-11 User-installed Software, CM-12 Information Location, CM-13 Data Action Mapping and CM-14 Signed Components. CM-14 is the one aimed at firmware: prevent installation of organization-defined "software and firmware components" without verification that each "has been digitally signed using a certificate that is recognized and approved by the organization", and its guidance names "firmware version updates, patches, service packs, device drivers, and basic input/output system updates." CM-2(3) Retention of Previous Configurations asks an organization to keep previous baseline versions "to support rollback", and its guidance lists "hardware, software, firmware, configuration files". A device that verifies signed updates (see secure boot and root of trust and OTA update security) lets the customer meet CM-14 without extra tooling.
What should a device ship with so customers can run SecCM?
The customer runs SecCM; the device has to make it possible. NIST's IR 8259A core baseline (May 2020) defines a Device Configuration capability: "the configuration of the IoT device's software can be changed, and such changes can be performed by authorized entities only." It lists three abilities: change the software configuration settings, restrict changes to authorized entities, and "restore the device to a secure configuration defined by an authorized entity." A device that can export its settings in a readable form, reject unauthorized changes and reset to a documented secure default gives a customer's Monitoring phase something to compare against.
Where does SCAP fit in automated configuration monitoring?
Section 3.5 describes SCAP as "a suite of specifications that standardize the format and nomenclature by which information about software flaws and secure configurations can be communicated," enabling SCAP-enabled tools to "automatically verify the installation of patches, check system security configuration settings against an expected baseline, and examin[e] systems for signs of compromise." Federal agencies pair SCAP-enabled tools with SCAP-expressed checklists, such as those in NIST's National Checklist Program repository, customized to organizational requirements, to generate standardized assessment and compliance evidence for SP 800-53 controls — the publication states this can provide "a substantial savings in effort and cost" versus manual checking. The 10 October 2019 update refreshed the documented baseline to SCAP Version 1.3, built from components including the Extensible Configuration Checklist Description Format (XCCDF) 1.2 for authoring and reporting checklists, the Open Vulnerability and Assessment Language (OVAL) 5.11.2 for representing configuration information and machine state, and the Open Checklist Interactive Language (OCIL) 2.0 for checks requiring human input. NIST also encourages vendors to support Common Vulnerabilities and Exposures (CVE), Common Configuration Enumeration (CCE) and Software Identification (SWID) Tags so SCAP tooling can reference consistent identifiers.
Which SP 800-53 controls does Appendix F tie each best practice to?
The 2019 update added explicit "Associated NIST SP 800-53 Control" lines to each best-practice topic in Appendix F. Examples: patch/change-related checklists tie to CM-6; the overall CM plan/checklist discipline ties to CM-1 and CM-6; least-functionality topics (removing unnecessary services) tie to CM-7; remote access controls tie to AC-17; password/authenticator management ties to IA-2 and IA-5; endpoint protections tie to SC-7, SC-18, SI-3, SI-4; cryptographic protections tie to SC-13; patch and vulnerability management ties to CM-2, CM-3, CM-4, SI-2; and application whitelisting ties to CM-5, CM-7, CM-11, SI-7. Appendix D supplies a sample outline for a SecCM Plan, Appendix E a sample configuration change request template, Appendix G flow charts for SecCM processes, and Appendix H a sample CCB charter.
What are the common pitfalls?
- One CI for the whole product. A single CI hides which part changed; split by release cadence and owner.
- Closing a change request at deployment. Section 3.3.2 keeps it open until verification shows the change deployed without issues.
- Deleting old baselines. Section 3.3.4 and CM-2(3) keep them for rollback, incident response and audits.
- Leaving the build and test tooling out of configuration control, which the publication names as a CI type.
What is a workable starting point?
Write down what counts as a Configuration Item before arguing about baselinesThe CI/baseline-configuration distinction only works if the organization has already agreed on the discrete hardware, software, firmware and documentation targets that configuration control applies to. Treat the four phases as a loop, not a checklistMonitoring findings feed back into planning, baselines or change control; an annual audit is not a Monitoring phase. Use Appendix F's control cross-references to scope evidence collectionEndpoint hardening maps to SC-7/SC-18/SI-3/SI-4, for example, so the assessor knows which artifact answers which control. Automate what SCAP covers, and budget for what it doesn'tSCAP tooling handles machine-checkable settings and patch state; policy judgments and human-verified controls still need manual reporting. Map to the current CM family, not only CM-1 to CM-9SP 800-128 predates CM-10 to CM-14; check control IDs against the current SP 800-53 control catalog.
SoftWSP covers one input to this process: the component inventory of a firmware image. Device & Firmware Security extracts an SBOM from an uploaded image as CycloneDX 1.6 JSON and matches it against NVD, CISA KEV, FIRST EPSS and CISA's CSAF ICS advisories; an engineer reviews each AI-drafted, cited report, and a watchlist alert can fire on a CVE ID or a vendor and product. Running it on the old and new image gives the inventory evidence for the "identify vulnerabilities" step. SoftWSP does not read configuration settings, hold baselines or detect drift. The same change-control discipline appears in NERC CIP-010 for grid operators.
This guide summarises NIST SP 800-128 (August 2011, including the October 2019 errata update) and the related SP 800-53 publication page; it is not a substitute for the full text and does not constitute compliance or legal advice.
Put this guide to work
Frequently asked questions
What is NIST SP 800-128?
"Guide for Security-Focused Configuration Management of Information Systems" — a NIST publication, per its own abstract, that "provides guidelines for organizations responsible for managing and administering the security of federal information systems and associated environments of operation." It coins the term **security-focused configuration management (SecCM)**, defined as "the management and control of secure configurations for a system to enable security and facilitate the management of risk," to emphasize the information-security slice of an organization's broader configuration management (CM) practice. Authored by Arnold Johnson, Kelley Dempsey and Ron Ross (NIST) with Sarbari Gupta and Dennis Bailey (Electrosoft Services), it was originally published in **August 2011** and carries substantive and editorial errata updates as of **10 October 2019** (recorded in its own Errata table); NIST's publication page lists its current status as **Final**, with no later revision superseding it as of November 2026.
What are the four phases of SecCM?
Section 2.2 states that SecCM activities "can be organized into four major phases: Planning; Identifying and Implementing Configurations; Controlling Configuration Changes; and Monitoring," detailed further in Chapter Three. **Planning** (Sec. 3.1) develops SecCM policy, procedures and plans, typically at the organizational or mission/business-process risk-management level. **Identifying and Implementing Configurations** (Sec. 3.2) develops, reviews, approves and implements the secure baseline configuration — "the most secure state consistent with operational requirements and constraints." **Controlling Configuration Changes** (Sec. 3.3) ensures changes are "formally identified, proposed, reviewed, analyzed for security impact, tested, and approved prior to implementation." **Monitoring** (Sec. 3.4) validates the system still adheres to the approved baseline, and — per Figure 2-1 — can "loop back to any of the previous phases" when it finds drift.
What is a Configuration Item and a baseline configuration?
Section 2.1.1 defines a **Configuration Item (CI)** as "an identifiable part of a system (e.g., hardware, software, firmware, documentation, or a combination thereof) that is a discrete target of configuration control processes," and a **Baseline Configuration** as "a set of specifications for a system, or CI within a system, that has been formally reviewed and agreed on at a given point in time, and which can be changed only through change control procedures" — used as "a basis for future builds, releases, and/or changes." A **Configuration Management Plan (CM Plan)**, per the same section, documents the roles, policies and procedures covering four parts: the Configuration Control Board (CCB) charter, configuration item identification methodology, configuration change control process, and configuration monitoring/reporting process.
How does SP 800-128 connect to SP 800-53, the RMF, and SCAP?
Section 1.3 states the publication "provides guidelines for implementation of the Configuration Management family of controls defined in NIST [SP 800-53] (CM-1 through CM-9)" and "provides important supporting information for the Implement Step, Assess Step, and the Monitor Step" of the Risk Management Framework described in [NIST SP 800-37](/guides/nist-sp-800-37-risk-management-framework/), noting that more specific Monitor-step guidance sits in NIST SP 800-137. Section 3.5 covers the **Security Content Automation Protocol (SCAP)**, describing it as "a suite of specifications that standardize the format and nomenclature by which information about software flaws and secure configurations can be communicated," used by SCAP-enabled tools to automatically verify patch installation, check configuration settings against an expected baseline, and generate standardized compliance evidence — the publication documents **SCAP Version 1.3**, built from components including XCCDF 1.2, OVAL 5.11.2 and OCIL 2.0.
Sources
- NIST: SP 800-128, Guide for Security-Focused Configuration Management of Information Systems (includes updates as of 10-10-2019) — publication page
- NIST SP 800-128 (Johnson, Dempsey, Ross, Gupta, Bailey), full text PDF
- NIST: SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations — publication page
- NIST OSCAL content: SP 800-53 Rev. 5 control catalog, JSON (Release 5.2.0; CM-1 to CM-14, CM-2(3), CM-14 Signed Components)
- NIST IR 8259A, IoT Device Cybersecurity Capability Core Baseline (May 2020, PDF)
- NIST National Checklist Program Repository
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 131 guides.

In this cluster
Questions about this page?
