OpenParable
Skip to content
← Back to skills

AU-5(3)_configurable-traffic-volume-thresholds

DevOps & Security

AU-5(3)_configurable-traffic-volume-thresholds is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Enforce configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity and [organization-defined] netwo

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/AU_audit-and-accountability/AU-5(3)_configurable-traffic-volume-thresholds/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/au-5-3-configurable-traffic-volume-thresholds, 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.

AU-5(3) Configurable Traffic Volume Thresholds

Enhancement of: AU-5

High-Level Description

Family: Audit and Accountability (AU) Framework: NIST SP 800-53 Rev 5

Organizations have the capability to reject or delay the processing of network communications traffic if audit logging information about such traffic is determined to exceed the storage capacity of the system audit logging function. The rejection or delay response is triggered by the established organizational traffic volume thresholds that can be adjusted based on changes to audit log storage capacity.

What to Check

  • Verify AU-5(3) Configurable Traffic Volume Thresholds is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for AU-5(3)
  • Verify enhancement builds upon base control AU-5

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AU-5(3) 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 logging configurationcloud_audit_logging
AWS CLIReview CloudTrail/CloudWatchaws cloudtrail describe-trails

Remediation Guide

Control Statement

Enforce configurable network communications traffic volume thresholds reflecting limits on audit log storage capacity and [organization-defined] network traffic above those thresholds.

Implementation Guidance

Organizations have the capability to reject or delay the processing of network communications traffic if audit logging information about such traffic is determined to exceed the storage capacity of the system audit logging function. The rejection or delay response is triggered by the established organizational traffic volume thresholds that can be adjusted based on changes to audit log storage capacity.

Risk Assessment

FindingSeverityImpact
AU-5(3) Configurable Traffic Volume Thresholds not implementedMediumAudit and Accountability
AU-5(3) partially implementedLowIncomplete Audit and Accountability

CWE Categories

CWE IDTitle
CWE-778Insufficient Logging

References

Checklist

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