OpenParable
Skip to content
← Back to skills

SI-11_error-handling

Development

SI-11_error-handling is an Agent Skill for development published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited;

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-11_error-handling/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/si-11-error-handling, 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-11 Error Handling

High-Level Description

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

Organizations consider the structure and content of error messages. The extent to which systems can handle error conditions is guided and informed by organizational policy and operational requirements. Exploitable information includes stack traces and implementation details; erroneous logon attempts with passwords mistakenly entered as the username; mission or business information that can be derived from, if not stated explicitly by, the information recorded; and personally identifiable information, such as account numbers, social security numbers, and credit card numbers. Error messages may also provide a covert channel for transmitting information.

What to Check

  • Verify SI-11 Error Handling is documented in SSP
  • Validate all 2 control requirements are implemented
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for SI-11

How to Test

Step 1: Review Documentation

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

Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited; and Reveal error messages only to [organization-defined].

Implementation Guidance

Organizations consider the structure and content of error messages. The extent to which systems can handle error conditions is guided and informed by organizational policy and operational requirements. Exploitable information includes stack traces and implementation details; erroneous logon attempts with passwords mistakenly entered as the username; mission or business information that can be derived from, if not stated explicitly by, the information recorded; and personally identifiable information, such as account numbers, social security numbers, and credit card numbers. Error messages may also provide a covert channel for transmitting information.

Risk Assessment

FindingSeverityImpact
SI-11 Error Handling not implementedHighSystem and Information Integrity
SI-11 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 (AU-2, AU-3, SC-31, SI-2, SI-15) reviewed