# NIST SP 800-53 Rev. 5 SR-9(1) — Multiple Stages Of System Development Life Cycle - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-9-1-multiple-stages-of-system-development-life-cycle - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › SR — Supply Chain Risk Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `SR-9(1)`·high·Component: **Supply Chain Risk Management** ## What this control requires > Implement anti-tamper technologies, tools, and techniques throughout the system development life cycle, which includes research and development, design, manufacturing, acquisition, delivery, integration, operations, Maintenance, and disposal. A combination of hardware and software techniques, such as obfuscation and self-checking, should be used to make reverse engineering and modifications more difficult, time-consuming, and expensive for adversaries. Customizing systems and components helps in detecting substitutions, thus limiting potential damage. This control supports the Tamper Resistance, Security Measures capability within the Supply Chain Risk Management family. > > — NIST SP 800-53 Rev. 5, Control SR-9(1) ### In plain English Implement anti-tamper technologies, tools, and techniques throughout the system development life cycle, which includes research and development, design, manufacturing, acquisition, delivery, integration, operations, Maintenance, and disposal. In practice, this means you can prove you security management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Supply Chain Risk Management**, the assessor will trace your implementation back to the catalogue reference (Control SR-9(1)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Endpoint Protection **MDM.** Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token. **EDR.** Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h. #### Secure Development **Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline. **Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence. ### Operational checklist - **Security.** Document the trigger, the owner and the cadence. - **Maintenance.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Time.** Document the trigger, the owner and the cadence. - **Hardware.** Document the trigger, the owner and the cadence. - **Scope:** management, system, time, protection, hardware, software, maintenance, components. ## Evidence to collect - **User Device Scan.** MDM compliance state per user device (Intune / Jamf / Workspace ONE). Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Focus: Multiple Stages Of System Development Life Cycle. ## Common pitfalls - Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure. - CI security checks set to warn-only; the merge button is faster than the security feedback. ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SR-5** — Acquisition Strategies, Tools, And Methods](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-5-acquisition-strategies-tools-and-methods) - [**Control CM-8(9)** — Assignment Of Components To Systems](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-8-9-assignment-of-components-to-systems) - [**Control SR-4(3)** — Validate As Genuine And Not Altered](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-4-3-validate-as-genuine-and-not-altered) - [**Control SC-38** — Operations Security](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-38-operations-security) - [**Control CM-8(1)** — Updates During Installation And Removal](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-8-1-updates-during-installation-and-removal) - [**Control PM-30** — Supply Chain Risk Management Strategy](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pm-30-supply-chain-risk-management-strategy) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control SR-9(1)` Topics: endpoint securityendpoint protectionsecure development ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.