OpenParable
Skip to content
← Back to skills

SA-11(4)_manual-code-reviews

Testing & Quality

SA-11(4)_manual-code-reviews 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 perform a manual code review of [organization-defined] using the following

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(4)_manual-code-reviews/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sa-11-4-manual-code-reviews, 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(4) Manual Code Reviews

Enhancement of: SA-11

High-Level Description

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

Manual code reviews are usually reserved for the critical software and firmware components of systems. Manual code reviews are effective at identifying weaknesses that require knowledge of the application’s requirements or context that, in most cases, is unavailable to automated analytic tools and techniques, such as static and dynamic analysis. The benefits of manual code review include the ability to verify access control matrices against application controls and review detailed aspects of cryptographic implementations and controls.

What to Check

  • Verify SA-11(4) Manual Code Reviews is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for SA-11(4)
  • 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(4) 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 perform a manual code review of [organization-defined] using the following processes, procedures, and/or techniques: [organization-defined].

Implementation Guidance

Manual code reviews are usually reserved for the critical software and firmware components of systems. Manual code reviews are effective at identifying weaknesses that require knowledge of the application’s requirements or context that, in most cases, is unavailable to automated analytic tools and techniques, such as static and dynamic analysis. The benefits of manual code review include the ability to verify access control matrices against application controls and review detailed aspects of cryptographic implementations and controls.

Risk Assessment

FindingSeverityImpact
SA-11(4) Manual Code Reviews not implementedMediumSystem and Services Acquisition
SA-11(4) 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