- ClassificationCategoryCybersecurityDomainCybersecurityFramework FamilyNIST Special Publications
- Regulatory ContextTypeGuidanceLegal InstrumentGuidanceSectorCross-SectorIndustryCross-Industry
- Region / PublisherRegionNorth AmericaRegion DetailUnited StatesPublisherNational Institute of Standards and Technology (NIST)
- VersioningVersionOriginal edition (August 2011) with errata update of October 10, 2019Effective DateAugust 2011Issue DateAugust 2011 (errata update October 10, 2019)
- AdoptionAdoption ModelVoluntaryImplementation ComplexityMedium
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
SP 800-128 is a U.S. government publication, free of charge from NIST and not subject to copyright in the United States (attribution is appreciated); the platform links to the official text.
Framework text is licensed by its publisher and is included only where stated above.
- NIST SP 800-128 is the NIST guide to security-focused configuration management (SecCM) of information systems.
- Published August 2011 with errata updated October 10, 2019, it is guidance for federal systems and voluntary for anyone else.
- It implements the Configuration Management family of controls in SP 800-53, CM-1 through CM-9, under FISMA and FIPS 200.
- It sets out four SecCM phases, ten core concepts, baselines, change control, and monitoring.
- SmartSuite IT Asset Management holds configuration items, IT Service Management runs change requests, and Compliance Management holds the CM controls and evidence.
Overview
NIST Special Publication 800-128, Guide for Security-Focused Configuration Management of Information Systems, is the NIST guide to building, controlling and monitoring secure system configurations. Published in August 2011 and updated with errata on October 10, 2019, it is written for the people who manage the security of U.S. federal information systems and may be used voluntarily by any other organization. It is guidance, not a law or a certifiable standard. Its central term, security-focused configuration management (SecCM), means the management and control of configurations for systems to enable security and facilitate the management of information security risk.
NIST developed the guide under the Federal Information Security Modernization Act of 2014 (44 U.S.C. 3551 et seq.). Section 1.1 explains the basis: federal agency security programs must include policies and procedures that ensure compliance with minimally acceptable system configuration requirements, managing system configurations is a minimum security requirement in FIPS 200, and the guide provides implementation guidelines for the Configuration Management family of controls in SP 800-53, CM-1 through CM-9. It applies to all federal information systems other than national security systems, which may use it with the approval of the responsible federal officials.
The guide has three chapters and nine appendices. Chapter 2 sets out the fundamentals: the four SecCM phases (section 2.2), ten core concepts (2.3) and the roles involved (2.4). Chapter 3 describes the process for each phase and the use of the Security Content Automation Protocol (SCAP). Appendices D to I supply a sample SecCM plan outline, a change request template, secure configuration practices, process flow charts, a Configuration Control Board charter and a security impact analysis template.
Why does it matter?
A system is in constant change from patches, new components, security threats and changing business functions, and almost every change adjusts its configuration (Chapter 1). SP 800-128 gives federal agencies, and any organization that borrows the guide, one defined process that builds information security into configuration management, so that an unreviewed change cannot quietly undo a secure state. Monitoring under section 3.4 then finds the components and settings that have drifted from the approved baseline before an attacker does.
Key benefits include:
- An approved baseline
A baseline configuration is a set of specifications that has been formally reviewed and agreed on at a point in time and can be changed only through change control (section 2.3.7, control CM-2).
- Change reviewed before it happens
Each change is requested, recorded, analyzed for security impact, tested, approved, implemented, verified and closed out (section 3.3.2, controls CM-3 and CM-4).
- Visibility of components
A component inventory (2.3.4, CM-8) and monitoring show unapproved items, such as a test router left on the network or a wireless access point set up without management consent (3.4).
- Named accountability
Section 2.4 assigns SecCM duties to the CIO, senior agency information security officer, authorizing official, system owner, SecCM Program Manager, system security officer, system administrator, developer and system user.
- Automated evidence
SCAP-enabled tools check settings against expected baselines and produce standardized assessment evidence for many SP 800-53 controls (section 3.5).
How does it work?
Chapter 2 defines the structure. SecCM is organized into four phases (section 2.2): Planning; Identifying and Implementing Configurations; Controlling Configuration Changes; and Monitoring. Chapter 3 gives, for each phase, the activities with their primary and supporting roles, expected inputs and expected outputs. Monitoring results can send the program back to any earlier phase, because the processes in all four phases are reviewed and revised as risk changes.
Planning (section 3.1) produces the SecCM policy and SecCM plan at the organization and system levels, sets up the Configuration Control Board (CCB), selects tools and defines metrics. Identifying and implementing configurations (3.2) establishes secure configurations from recognized benchmarks, called common secure configurations in the guide, such as the National Checklist Program and DISA STIGs, then implements them in an approved baseline that can cover settings, software loads, patch levels and how the system is arranged.
Controlling change (3.3) starts with access restrictions for change (3.3.1) and then runs a nine-step change process (3.3.2): request, record, decide whether the change needs configuration control, analyze, test, approve, implement, verify and close out. Security impact analysis (3.3.3) happens at every system development life cycle phase, and records are kept and archived (3.3.4). Monitoring (3.4) scans for components missing from the inventory and for differences between actual and baseline configurations, with SCAP automation (3.5) for large estates.
Key Elements
- Four SecCM phases
Planning, identifying and implementing configurations, controlling configuration changes and monitoring (section 2.2, detailed in Chapter 3).
- SecCM policy and plan (2.3.1, 2.3.2)
Policy states senior management's expectations through measurable objectives; the plan describes how the policy is implemented for an organization or a system. They support CM-1 and CM-9.
- Configuration Control Board (2.3.3)
A group with the collective responsibility and authority to review and approve changes, acting as a check and balance against criteria such as scope, cost and security impact (CM-3).
- Component inventory and configuration items (2.3.4, 2.3.5)
The inventory records components, each within one system boundary and under one system owner (CM-8). A configuration item is an aggregation of components managed as a single entity.
- Baseline and secure configurations (2.3.6, 2.3.7)
Approved baselines are built from secure settings, patch levels and the principle of least functionality, and older baselines stay available for review or rollback (CM-2, CM-6, CM-7).
- Change control and security impact analysis (2.3.8, 2.3.9)
Documented control of proposed changes, access restrictions to enforce the process, and analysis of each change by qualified staff for its effect on security posture (CM-3, CM-4, CM-5).
- Monitoring and SCAP (2.3.10, 3.4, 3.5)
Assessment and reporting against baselines and the component inventory, with SCAP 1.3 specifications such as XCCDF, OVAL and CPE supporting automated checks.
What does it cover?
Section 1.1 states the applicability: all federal information systems other than national security systems, with use on national security systems possible with approval of the officials who hold policy authority. State, local and tribal governments and private sector organizations are encouraged to consider the guide. The guidelines cover a system and its components, including hardware, software, firmware and documentation, across the system life cycle. For external or service-oriented environments such as cloud service providers, the concepts can help organizations set assurance requirements for suppliers. Section 1.2 names the audience: CIOs, senior agency information security officers and authorizing officials; program managers and system designers; system owners and administrators; and auditors, inspectors general and assessors.
What are its objectives?
Per its abstract and Chapter 3, the guide aims to manage and monitor the configurations of systems to achieve adequate security and minimize organizational risk while supporting the desired business functionality and services.
Define security-focused configuration management as the security aspect of an organization's overall configuration management process.
Provide guidelines for implementing the Configuration Management control family in SP 800-53 (CM-1 through CM-9).
Establish an approved baseline configuration for each system and a controlled process for changing it.
Feed configuration monitoring into continuous monitoring and the Risk Management Framework.
Promote automated configuration assessment with SCAP and the National Checklist Program.
Framework in Context
SP 800-128 provides supporting information for SP 800-53 and for the Implement, Assess and Monitor steps of the Risk Management Framework in SP 800-37 (section 1.3). SP 800-137 gives the more specific guidance on information security continuous monitoring that SecCM monitoring feeds, SP 800-39 supplies the risk management levels the guide draws on, and SP 800-70 and SP 800-126 cover the National Checklist Program and SCAP. In the NIST Cybersecurity Framework 2.0 the same practice appears as PR.PS-01, configuration management practices are established and applied.
Common Framework Mappings
Organizations map SP 800-128 to the control sets below so that one SecCM program supplies baselines, change records and monitoring evidence for each of them.
Mapped frameworks include:
NIST 800-53 Rev.5
NIST 800-53B Rev. 5
NIST 800-37 Rev.2
NIST CSF 2.0
NIST 800-171 Rev. 3
CIS Controls v8.1
ISO 27002:2022
ITIL 4
COBIT 2019
DISA STIGs
CIS Benchmarks
How SmartSuite Supports NIST SP 800-128
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use IT Asset Management (ITAM) to hold the component inventory and configuration items with owner and lifecycle, IT Service Management (ITSM) to run change requests with approvals and history, and Compliance Management to hold the CM controls, their tests and evidence, with the CCB, system owners and security officers named as owners.
Component Inventory and Configuration Items
Record components and group them into configuration items in IT Asset Management (ITAM), each with one system owner and a lifecycle (sections 2.3.4 and 2.3.5).
Baseline Register
Keep each approved baseline with its version, the common secure configuration it came from and its approver, and retain older baselines for review or rollback (2.3.7).
Change Request Workflow
Run the section 3.3.2 steps in IT Service Management (ITSM): request, record, security impact analysis, test, CCB approval, implementation, verification and close-out.
Configuration Control Board Records
Hold CCB membership, the charter, meeting decisions and the approvals linked to each change, following the Appendix H charter sample.
Monitoring Findings
Log the results of baseline and inventory assessments in Cyber & IT Risk, including unapproved components and deviations, and track each to closure (3.4).
CM Control Evidence
Hold CM-1 through CM-9 as requirements in Compliance Management with the SecCM plan, test results and evidence, and report status to system owners and auditors.
Related frameworks

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

NIST SP 800-53B holds the low, moderate, high and privacy control baselines from NIST SP 800-53 Rev. 5, the high water mark selection rule, tailoring guidance and overlays.

NIST SP 800-37 Rev. 2 is the NIST Risk Management Framework: seven steps from Prepare to Monitor, with the tasks, roles and authorization decisions federal agencies apply under OMB A-130.

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST SP 800-171 Rev. 3 (May 14, 2024): 97 CUI security requirements in 17 families with organization-defined parameters, derived from the SP 800-53B moderate baseline.

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.
Frequently Asked Questions For NIST SP 800-128
SP 800-128 is the NIST guide to security-focused configuration management (SecCM), published in August 2011 and updated with errata on October 10, 2019. Section 1.1 aims it at organizations that manage the security of federal information systems, and section 1.2 lists CIOs, security officers, system owners, administrators and assessors as its audience. State, local and tribal governments and private organizations are encouraged to use it voluntarily.
SecCM is the management and control of configurations for systems to enable security and facilitate the management of information security risk (Chapter 1). The guide assumes information security is part of an organization's overall configuration management and concentrates on its security aspects. Its goal, stated in Chapter 3, is to manage and monitor configurations to achieve adequate security and minimize organizational risk.
Section 2.2 names them: Planning; Identifying and Implementing Configurations; Controlling Configuration Changes; and Monitoring. Chapter 3 covers each in sections 3.1 to 3.4, and monitoring results can send the program back to any earlier phase. Section 3.5 adds the use of SCAP to automate checking.
Section 1.1 says the guide provides implementation guidelines for the Configuration Management family, CM-1 through CM-9. Section 2.3 ties each concept to controls: CM-1 and CM-9 for policy and the SecCM plan, CM-2 for baselines, CM-3 to CM-5 for change control, security impact analysis and access restrictions, CM-6 and CM-7 for settings and least functionality, and CM-8 for the component inventory.
It is guidance. The authority statement says it may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States, and that it does not alter standards NIST made mandatory for federal agencies. Federal agencies remain responsible for the policies and procedures on minimally acceptable system configuration requirements in their security programs (section 1.1), which this guide helps them implement.

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


