OpenParable
Skip to content
← Back to skills

AC-3(10)_audited-override-of-access-control-mechanisms

DevOps & Security

AC-3(10)_audited-override-of-access-control-mechanisms 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.

Employ an audited override of automated access control mechanisms under [organization-defined] by [organization-defined].

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-3(10)_audited-override-of-access-control-mechanisms/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ac-3-10-audited-override-of-access-control-mechanisms, 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-3(10) Audited Override of Access Control Mechanisms

Enhancement of: AC-3

High-Level Description

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

In certain situations, such as when there is a threat to human life or an event that threatens the organization’s ability to carry out critical missions or business functions, an override capability for access control mechanisms may be needed. Override conditions are defined by organizations and used only in those limited circumstances. Audit events are defined in AU-2 . Audit records are generated in AU-12.

What to Check

  • Verify AC-3(10) Audited Override of Access Control Mechanisms is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for AC-3(10)
  • Verify enhancement builds upon base control AC-3

How to Test

Step 1: Review Documentation

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

Employ an audited override of automated access control mechanisms under [organization-defined] by [organization-defined].

Implementation Guidance

In certain situations, such as when there is a threat to human life or an event that threatens the organization’s ability to carry out critical missions or business functions, an override capability for access control mechanisms may be needed. Override conditions are defined by organizations and used only in those limited circumstances. Audit events are defined in AU-2 . Audit records are generated in AU-12.

Risk Assessment

FindingSeverityImpact
AC-3(10) Audited Override of Access Control Mechanisms not implementedHighAccess Control
AC-3(10) 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-6, AU-10, AU-12, AU-14) reviewed