OpenParable
Skip to content
← Back to skills

SI-3(6)_testing-and-verification

Testing & Quality

SI-3(6)_testing-and-verification 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.

Test malicious code protection mechanisms [organization-defined] by introducing known benign code into the system;

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/SI_system-and-information-integrity/SI-3(6)_testing-and-verification/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/si-3-6-testing-and-verification, 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.

SI-3(6) Testing and Verification

Enhancement of: SI-3

High-Level Description

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

None.

What to Check

  • Verify SI-3(6) Testing and Verification is documented in SSP
  • Validate all 2 control requirements are implemented
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for SI-3(6)
  • Verify enhancement builds upon base control SI-3

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SI-3(6) 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
cloud-audit-mcpCheck integrity monitoringcloud_audit_monitoring
AWS CLIReview GuardDuty/Inspectoraws guardduty list-detectors

Remediation Guide

Control Statement

Test malicious code protection mechanisms [organization-defined] by introducing known benign code into the system; and Verify that the detection of the code and the associated incident reporting occur.

Implementation Guidance

None.

Risk Assessment

FindingSeverityImpact
SI-3(6) Testing and Verification not implementedHighSystem and Information Integrity
SI-3(6) partially implementedMediumIncomplete System and Information Integrity

CWE Categories

CWE IDTitle
CWE-20Improper Input Validation

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (CA-2, CA-7, RA-5) reviewed