SC-18(1)_identify-unacceptable-code-and-take-corrective-actions

SC-18(1) Identify Unacceptable Code and Take Corrective Actions

Enhancement of: SC-18

High-Level Description

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

Corrective actions when unacceptable mobile code is detected include blocking, quarantine, or alerting administrators. Blocking includes preventing the transmission of word processing files with embedded macros when such macros have been determined to be unacceptable mobile code.

What to Check

• Verify SC-18(1) Identify Unacceptable Code and Take Corrective Actions is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SC-18(1)
• 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(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

Remediation Guide

Control Statement

Identify [organization-defined] and take [organization-defined].

Implementation Guidance

Corrective actions when unacceptable mobile code is detected include blocking, quarantine, or alerting administrators. Blocking includes preventing the transmission of word processing files with embedded macros when such macros have been determined to be unacceptable mobile code.

Risk Assessment

CWE Categories

References

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