si-4-24-indicators-of-compromise

name	SI-4(24)_indicators-of-compromise
description	Discover, collect, and distribute to [organization-defined] , indicators of compromise provided by [organization-defined].
category	input-validation
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","si-4-24","si","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-20"]
chains_with	["AC-18"]
prerequisites	["SI-4"]
severity_boost	{"AC-18":"Chain with AC-18 for comprehensive security coverage"}

SI-4(24) Indicators of Compromise

Enhancement of: SI-4

High-Level Description

Family: System and Information Integrity (SI) Framework: NIST SP 800-53 Rev 5

Indicators of compromise (IOC) are forensic artifacts from intrusions that are identified on organizational systems at the host or network level. IOCs provide valuable information on systems that have been compromised. IOCs can include the creation of registry key values. IOCs for network traffic include Universal Resource Locator or protocol elements that indicate malicious code command and control servers. The rapid distribution and adoption of IOCs can improve information security by reducing the time that systems and organizations are vulnerable to the same exploit or attack. Threat indicators, signatures, tactics, techniques, procedures, and other indicators of compromise may be available via government and non-government cooperatives, including the Forum of Incident Response and Security Teams, the United States Computer Emergency Readiness Team, the Defense Industrial Base Cybersecurity Information Sharing Program, and the CERT Coordination Center.

What to Check

• Verify SI-4(24) Indicators of Compromise is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SI-4(24)
• Verify enhancement builds upon base control SI-4

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SI-4(24) 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 integrity monitoring	cloud_audit_monitoring
AWS CLI