OpenParable
Skip to content
← Back to skills

AC-3_access-enforcement

DevOps & Security

AC-3_access-enforcement 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 approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

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_access-enforcement/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ac-3-access-enforcement, 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 Access Enforcement

High-Level Description

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

Access control policies control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (i.e., devices, files, records, domains) in organizational systems. In addition to enforcing authorized access at the system level and recognizing that systems can host many applications and services in support of mission and business functions, access enforcement mechanisms can also be employed at the application and service level to provide increased information security and privacy. In contrast to logical access controls that are implemented within the system, physical access controls are addressed by the controls in the Physical and Environmental Protection ( PE ) family.

What to Check

  • Verify AC-3 Access Enforcement is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for AC-3

How to Test

Step 1: Review Documentation

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

Remediation Guide

Control Statement

Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

Implementation Guidance

Access control policies control access between active entities or subjects (i.e., users or processes acting on behalf of users) and passive entities or objects (i.e., devices, files, records, domains) in organizational systems. In addition to enforcing authorized access at the system level and recognizing that systems can host many applications and services in support of mission and business functions, access enforcement mechanisms can also be employed at the application and service level to provide increased information security and privacy. In contrast to logical access controls that are implemented within the system, physical access controls are addressed by the controls in the Physical and Environmental Protection ( PE ) family.

Risk Assessment

FindingSeverityImpact
AC-3 Access Enforcement not implementedHighAccess Control
AC-3 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 (AC-2, AC-4, AC-5, AC-6, AC-16) reviewed