Organizational Control: Security Impact Analysis
| Control ID: CM-4 Security Impact Analysis | Family: Configuration Management | Source: NIST 800-53r4 |
| Control: 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 Controls: CA-2, CA-7, CM-3, CM-9, SA-4, SA-5, SA-10, SI-2 |
||
| Control Enhancements:
(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 Controls: SA-11, SC-3, SC-7 |
||
| References: NIST Special Publication 800-128. | ||
| Mechanisms:
|
||
| Protocol Implementation Conformance Statements: N/A | ||