| name | SC-18(2)_acquisition-development-and-use |
| description | Verify that the acquisition, development, and use of mobile code to be deployed in the system meets [organization-defined]. |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","sc-18-2","sc","enhancement"] |
| tech_stack | ["aws","azure","gcp","linux","windows","network"] |
| cwe_ids | ["CWE-311"] |
| chains_with | [] |
| prerequisites | ["SC-18"] |
| severity_boost | {} |
SC-18(2) Acquisition, Development, and Use
Enhancement of: SC-18
High-Level Description
Family: System and Communications Protection (SC)
Framework: NIST SP 800-53 Rev 5
None.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SC-18(2) 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 |
|---|
| cloud-audit-mcp | Check encryption and network controls | cloud_audit_encryption |
| nmap | Network scanning | nmap -sV --script ssl-enum-ciphers |
Remediation Guide
Control Statement
Verify that the acquisition, development, and use of mobile code to be deployed in the system meets [organization-defined].
Implementation Guidance
None.
Risk Assessment
| Finding | Severity | Impact |
|---|
| SC-18(2) Acquisition, Development, and Use not implemented | High | System and Communications Protection |
| SC-18(2) partially implemented | Medium | Incomplete System and Communications Protection |
