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

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

- Skill: `cyberstrikeus/sr-9-1-multiple-stages-of-system-development-life-cycle` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/sr-9-1-multiple-stages-of-system-development-life-cycle`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/sr-9-1-multiple-stages-of-system-development-life-cycle/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/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

| Tool          | Purpose                           | Usage |
| ------------- | --------------------------------- | ----- |
| Manual Review | Documentation and interview-based | N/A   |

## 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

| Finding                                                                  | Severity | Impact                                  |
| ------------------------------------------------------------------------ | -------- | --------------------------------------- |
| SR-9(1) Multiple Stages of System Development Life Cycle not implemented | Medium   | Supply Chain Risk Management            |
| SR-9(1) partially implemented                                            | Low      | Incomplete Supply Chain Risk Management |

## CWE Categories

| CWE ID | Title                 |
| ------ | --------------------- |
| N/A    | No direct CWE mapping |

## References

- [NIST SP 800-53 Rev 5 - SR-9(1)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=sr-9.1)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)

## Checklist

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