si-7-17-runtime-application-self-protection

name	SI-7(17)_runtime-application-self-protection
description	Implement [organization-defined] for application self-protection at runtime.
category	input-validation
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","si-7-17","si","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-20"]
chains_with	["SI-16"]
prerequisites	["SI-7"]
severity_boost	{"SI-16":"Chain with SI-16 for comprehensive security coverage"}

SI-7(17) Runtime Application Self-protection

Enhancement of: SI-7

High-Level Description

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

Runtime application self-protection employs runtime instrumentation to detect and block the exploitation of software vulnerabilities by taking advantage of information from the software in execution. Runtime exploit prevention differs from traditional perimeter-based protections such as guards and firewalls which can only detect and block attacks by using network information without contextual awareness. Runtime application self-protection technology can reduce the susceptibility of software to attacks by monitoring its inputs and blocking those inputs that could allow attacks. It can also help protect the runtime environment from unwanted changes and tampering. When a threat is detected, runtime application self-protection technology can prevent exploitation and take other actions (e.g., sending a warning message to the user, terminating the user's session, terminating the application, or sending an alert to organizational personnel). Runtime application self-protection solutions can be deployed in either a monitor or protection mode.

What to Check

• Verify SI-7(17) Runtime Application Self-protection is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SI-7(17)
• Verify enhancement builds upon base control SI-7

How to Test

Step 1: Review Documentation

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