SR-9(1)_multiple-stages-of-system-development-life-cycle

SR-9(1) Multiple Stages of System Development Life Cycle

Enhancement of: SR-9

High-Level Description

Family: Supply Chain Risk Management (SR) Framework: NIST SP 800-53 Rev 5

The system development life cycle includes research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal. Organizations use a combination of hardware and software techniques for tamper resistance and detection. Organizations use obfuscation and self-checking to make reverse engineering and modifications more difficult, time-consuming, and expensive for adversaries. The customization of systems and system components can make substitutions easier to detect and therefore limit damage.

What to Check

• Verify SR-9(1) Multiple Stages of System Development Life Cycle is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SR-9(1)
• Verify enhancement builds upon base control SR-9

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SR-9(1) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Remediation Guide

Control Statement

Employ anti-tamper technologies, tools, and techniques throughout the system development life cycle.

Implementation Guidance

The system development life cycle includes research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal. Organizations use a combination of hardware and software techniques for tamper resistance and detection. Organizations use obfuscation and self-checking to make reverse engineering and modifications more difficult, time-consuming, and expensive for adversaries. The customization of systems and system components can make substitutions easier to detect and therefore limit damage.

Risk Assessment

CWE Categories

References

• NIST SP 800-53 Rev 5 - SR-9(1)
• NIST SP 800-53A Rev 5 (Assessment Procedures)
• NIST SP 800-53 Rev 5 Full Catalog

Checklist

• Control documented in SSP
• Implementation evidence collected
• Operating effectiveness validated
• Continuous monitoring in place
• Related controls (SA-3) reviewed