OpenParable
Skip to content
← Back to skills

AC-4(26)_audit-filtering-actions

DevOps & Security

AC-4(26)_audit-filtering-actions 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.

When transferring information between different security domains, record and audit content filtering actions and results for the information being fil

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/AC_access-control/AC-4(26)_audit-filtering-actions/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ac-4-26-audit-filtering-actions, 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.

AC-4(26) Audit Filtering Actions

Enhancement of: AC-4

High-Level Description

Family: Access Control (AC) Framework: NIST SP 800-53 Rev 5

Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined policy. Content filtering actions and the results of filtering actions are recorded for individual messages to ensure that the correct filter actions were applied. Content filter reports are used to assist in troubleshooting actions by, for example, determining why message content was modified and/or why it failed the filtering process. Audit events are defined in AU-2 . Audit records are generated in AU-12.

What to Check

  • Verify AC-4(26) Audit Filtering Actions is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for AC-4(26)
  • Verify enhancement builds upon base control AC-4

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AC-4(26) 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 IAM policies and access controlscloud_audit_iam_policies
hackbrowser-mcpTest web application access controlsbrowser_auth_test

Remediation Guide

Control Statement

When transferring information between different security domains, record and audit content filtering actions and results for the information being filtered.

Implementation Guidance

Content filtering is the process of inspecting information as it traverses a cross-domain solution and determines if the information meets a predefined policy. Content filtering actions and the results of filtering actions are recorded for individual messages to ensure that the correct filter actions were applied. Content filter reports are used to assist in troubleshooting actions by, for example, determining why message content was modified and/or why it failed the filtering process. Audit events are defined in AU-2 . Audit records are generated in AU-12.

Risk Assessment

FindingSeverityImpact
AC-4(26) Audit Filtering Actions not implementedHighAccess Control
AC-4(26) partially implementedMediumIncomplete Access Control

CWE Categories

CWE IDTitle
CWE-284Improper Access Control

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (AU-2, AU-3, AU-12) reviewed