sc-5-3-detection-and-monitoring

name	SC-5(3)_detection-and-monitoring
description	Employ the following monitoring tools to detect indicators of denial-of-service attacks against, or launched from, the system: [organization-define...
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","sc-5-3","sc","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows","network"]
cwe_ids	["CWE-311"]
chains_with	["CA-7","SI-4"]
prerequisites	["SC-5"]
severity_boost	{"CA-7":"Chain with CA-7 for comprehensive security coverage","SI-4":"Chain with SI-4 for comprehensive security coverage"}

SC-5(3) Detection and Monitoring

Enhancement of: SC-5

High-Level Description

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

Organizations consider the utilization and capacity of system resources when managing risk associated with a denial of service due to malicious attacks. Denial-of-service attacks can originate from external or internal sources. System resources that are sensitive to denial of service include physical disk storage, memory, and CPU cycles. Techniques used to prevent denial-of-service attacks related to storage utilization and capacity include instituting disk quotas, configuring systems to automatically alert administrators when specific storage capacity thresholds are reached, using file compression technologies to maximize available storage space, and imposing separate partitions for system and user data.

What to Check

• Verify SC-5(3) Detection and Monitoring is documented in SSP
• Validate all 2 control requirements are implemented
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SC-5(3)
• Verify enhancement builds upon base control SC-5

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SC-5(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
cloud-audit-mcp	Check encryption and network controls	cloud_audit_encryption
nmap	Network scanning	nmap -sV --script ssl-enum-ciphers