Secure System Modification
LOW MODERATE HIGHRequirements NIST SOURCE
Implement the security design principle of secure system modification in [systems or system components].
Discussion (NIST Supplemental Guidance)
The principle of secure system modification states that system modification maintains system security with respect to the security requirements and risk tolerance of stakeholders. Upgrades or modifications to systems can transform secure systems into systems that are not secure. The procedures for system modification ensure that if the system is to maintain its trustworthiness, the same rigor that was applied to its initial development is applied to any system changes. Because modifications can affect the ability of the system to maintain its secure state, a careful security analysis of the modification is needed prior to its implementation and deployment. This principle parallels the principle of secure evolvability.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for SA-8(31) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- systems or system components that implement the security design principle of secure system modification are defined;
- <SA-08(31)_ODP systems or system components> implement the security design principle of secure system modification.
Examine
[SELECT FROM: System and services acquisition policy; configuration management policy and procedures; procedures addressing the security design principle of secure system modification used in the specification, design, development, implementation, and modification of the system; system design documentation; system configuration settings and associated documentation; change control records; security and privacy requirements and specifications for the system; system security and privacy architecture; system security plan; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with the responsibility for determining system security and privacy requirements; organizational personnel with system specification, design, development, implementation, and modification responsibilities; system developers; organizational personnel with information security responsibilities].
Test
[SELECT FROM: Organizational processes for applying the security design principle of secure system modification in system specification, design, development, implementation, and modification; mechanisms supporting the application of the security design principle of secure system modification in system specification, design, development, implementation, and modification; mechanisms that enforce security policies; organizational processes for managing change configuration; mechanisms supporting configuration control].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SA-8(31). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- System and services acquisition policy
- system security plan
Configuration
- configuration management policy and procedures
- system design documentation
- system configuration settings and associated documentation
- system security and privacy architecture
Testing
- Organizational processes for applying the security design principle of secure system modification in system specification, design, development, implementation, and modification
- mechanisms supporting the application of the security design principle of secure system modification in system specification, design, development, implementation, and modification
- mechanisms that enforce security policies
- organizational processes for managing change configuration
- mechanisms supporting configuration control
Other Records
- procedures addressing the security design principle of secure system modification used in the specification, design, development, implementation, and modification of the system
- change control records
- security and privacy requirements and specifications for the system
- other relevant documents or records