SC-18(5)_allow-execution-only-in-confined-environments

SC-18(5) Allow Execution Only in Confined Environments

Enhancement of: SC-18

High-Level Description

Family: System and Communications Protection (SC) Framework: NIST SP 800-53 Rev 5

Permitting the execution of mobile code only in confined virtual machine environments helps prevent the introduction of malicious code into other systems and system components.

What to Check

• Verify SC-18(5) Allow Execution Only in Confined Environments is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SC-18(5)
• Verify enhancement builds upon base control SC-18

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SC-18(5) 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

Allow execution of permitted mobile code only in confined virtual machine environments.

Implementation Guidance

Permitting the execution of mobile code only in confined virtual machine environments helps prevent the introduction of malicious code into other systems and system components.

Risk Assessment

CWE Categories

References

• NIST SP 800-53 Rev 5 - SC-18(5)
• 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 (SC-44, SI-7) reviewed