OpenParable
Skip to content
← Back to skills

SA-11(9)_interactive-application-security-testing

Testing & Quality

SA-11(9)_interactive-application-security-testing is an Agent Skill for testing & quality published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Require the developer of the system, system component, or system service to employ interactive application security testing tools to identify flaws an

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/SA_system-and-services-acquisition/SA-11(9)_interactive-application-security-testing/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sa-11-9-interactive-application-security-testing, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

SA-11(9) Interactive Application Security Testing

Enhancement of: SA-11

High-Level Description

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

Interactive (also known as instrumentation-based) application security testing is a method of detecting vulnerabilities by observing applications as they run during testing. The use of instrumentation relies on direct measurements of the actual running applications and uses access to the code, user interaction, libraries, frameworks, backend connections, and configurations to directly measure control effectiveness. When combined with analysis techniques, interactive application security testing can identify a broad range of potential vulnerabilities and confirm control effectiveness. Instrumentation-based testing works in real time and can be used continuously throughout the system development life cycle.

What to Check

  • Verify SA-11(9) Interactive Application Security Testing is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for SA-11(9)
  • 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(9) 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

ToolPurposeUsage
Manual ReviewDocumentation and interview-basedN/A

Remediation Guide

Control Statement

Require the developer of the system, system component, or system service to employ interactive application security testing tools to identify flaws and document the results.

Implementation Guidance

Interactive (also known as instrumentation-based) application security testing is a method of detecting vulnerabilities by observing applications as they run during testing. The use of instrumentation relies on direct measurements of the actual running applications and uses access to the code, user interaction, libraries, frameworks, backend connections, and configurations to directly measure control effectiveness. When combined with analysis techniques, interactive application security testing can identify a broad range of potential vulnerabilities and confirm control effectiveness. Instrumentation-based testing works in real time and can be used continuously throughout the system development life cycle.

Risk Assessment

FindingSeverityImpact
SA-11(9) Interactive Application Security Testing not implementedMediumSystem and Services Acquisition
SA-11(9) partially implementedLowIncomplete System and Services Acquisition

CWE Categories

CWE IDTitle
CWE-16Configuration

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (none) reviewed