| name | SR-3_supply-chain-controls-and-processes |
| description | Establish a process or processes to identify and address weaknesses or deficiencies in the supply chain elements and processes of [organization-def... |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","sr-3","sr"] |
| tech_stack | ["any"] |
| cwe_ids | [] |
| chains_with | ["CA-2","MA-2","MA-6","PE-3","PE-16","PL-8","PM-30","SA-2","SA-3","SA-4"] |
| prerequisites | [] |
| severity_boost | {"CA-2":"Chain with CA-2 for comprehensive security coverage","MA-2":"Chain with MA-2 for comprehensive security coverage","MA-6":"Chain with MA-6 for comprehensive security coverage"} |
SR-3 Supply Chain Controls and Processes
High-Level Description
Family: Supply Chain Risk Management (SR)
Framework: NIST SP 800-53 Rev 5
Supply chain elements include organizations, entities, or tools employed for the research and development, design, manufacturing, acquisition, delivery, integration, operations and maintenance, and disposal of systems and system components. Supply chain processes include hardware, software, and firmware development processes; shipping and handling procedures; personnel security and physical security programs; configuration management tools, techniques, and measures to maintain provenance; or other programs, processes, or procedures associated with the development, acquisition, maintenance and disposal of systems and system components. Supply chain elements and processes may be provided by organizations, system integrators, or external providers. Weaknesses or deficiencies in supply chain elements or processes represent potential vulnerabilities that can be exploited by adversaries to cause harm to the organization and affect its ability to carry out its core missions or business functions. Supply chain personnel are individuals with roles and responsibilities in the supply chain.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SR-3 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
