National Vulnerability Database

National Vulnerability Database

National Vulnerability
Database

NIST Special Publication 800-53 (Rev. 4)

Security and Privacy Controls for Federal Information Systems and Organizations

CM-4 SECURITY IMPACT ANALYSIS

Family:
CM - CONFIGURATION MANAGEMENT
Class:
Priority:
P2 - Implement P2 security controls after implementation of P1 controls.
Baseline Allocation:
Low Moderate High
CM-4 CM-4 CM-4 (1)

Control Description

The organization analyzes changes to the information system to determine potential security impacts prior to change implementation.

Supplemental Guidance

Organizational personnel with information security responsibilities (e.g., Information System Administrators, Information System Security Officers, Information System Security Managers, and Information System Security Engineers) conduct security impact analyses. Individuals conducting security impact analyses possess the necessary skills/technical expertise to analyze the changes to information systems and the associated security ramifications. Security impact analysis may include, for example, reviewing security plans to understand security control requirements and reviewing system design documentation to understand control implementation and how specific changes might affect the controls. Security impact analyses may also include assessments of risk to better understand the impact of the changes and to determine if additional security controls are required. Security impact analyses are scaled in accordance with the security categories of the information systems.

Related to: CA-2CA-7CM-3CM-9SA-4SA-5SA-10SI-2

Control Enhancements

CM-4(1) SECURITY IMPACT ANALYSIS | SEPARATE TEST ENVIRONMENTS
The organization analyzes changes to the information system in a separate test environment before implementation in an operational environment, looking for security impacts due to flaws, weaknesses, incompatibility, or intentional malice.
Supplemental Guidance: Separate test environment in this context means an environment that is physically or logically isolated and distinct from the operational environment. The separation is sufficient to ensure that activities in the test environment do not impact activities in the operational environment, and information in the operational environment is not inadvertently transmitted to the test environment. Separate environments can be achieved by physical or logical means. If physically separate test environments are not used, organizations determine the strength of mechanism required when implementing logical separation (e.g., separation achieved through virtual machines).
Related to: SA-11SC-3SC-7
CM-4(2) SECURITY IMPACT ANALYSIS | VERIFICATION OF SECURITY FUNCTIONS
The organization, after the information system is changed, checks the security functions to verify that the functions are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security requirements for the system.
Supplemental Guidance: Implementation is this context refers to installing changed code in the operational information system.
Related to: SA-11

References

NIST Special Publication 800-128 https://csrc.nist.gov/publications/search?keywords-lg=800-128