sa-11-5-penetration-testing

name	SA-11(5)_penetration-testing
description	Require the developer of the system, system component, or system service to perform penetration testing: At the following level of rigor: [organizatio
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","sa-11-5","sa","enhancement"]
tech_stack	["any"]
cwe_ids	["CWE-16"]
chains_with	["CA-8","PM-14","PM-25","PT-2","SA-3","SI-2","SI-6"]
prerequisites	["SA-11"]
severity_boost	{"CA-8":"Chain with CA-8 for comprehensive security coverage","PM-14":"Chain with PM-14 for comprehensive security coverage","PM-25":"Chain with PM-25 for comprehensive security coverage"}

SA-11(5) Penetration Testing

Enhancement of: SA-11

High-Level Description

Family: System and Services Acquisition (SA) Framework: NIST SP 800-53 Rev 5

Penetration testing is an assessment methodology in which assessors, using all available information technology product or system documentation and working under specific constraints, attempt to circumvent the implemented security and privacy features of information technology products and systems. Useful information for assessors who conduct penetration testing includes product and system design specifications, source code, and administrator and operator manuals. Penetration testing can include white-box, gray-box, or black-box testing with analyses performed by skilled professionals who simulate adversary actions. The objective of penetration testing is to discover vulnerabilities in systems, system components, and services that result from implementation errors, configuration faults, or other operational weaknesses or deficiencies. Penetration tests can be performed in conjunction with automated and manual code reviews to provide a greater level of analysis than would ordinarily be possible. When user session information and other personally identifiable information is captured or recorded during penetration testing, such information is handled appropriately to protect privacy.

What to Check

• Verify SA-11(5) Penetration Testing is documented in SSP
• Validate all 2 control requirements are implemented
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SA-11(5)
• Verify enhancement builds upon base control SA-11

How to Test

Step 1: Review Documentation

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