AC-24_access-control-decisions
DevOps & SecurityAC-24_access-control-decisions 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.
[organization-defined] to ensure [organization-defined] are applied to each access request prior to access enforcement.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/AC_access-control/AC-24_access-control-decisions/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ac-24-access-control-decisions, 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-24 Access Control Decisions
High-Level Description
Family: Access Control (AC) Framework: NIST SP 800-53 Rev 5
Access control decisions (also known as authorization decisions) occur when authorization information is applied to specific accesses. In contrast, access enforcement occurs when systems enforce access control decisions. While it is common to have access control decisions and access enforcement implemented by the same entity, it is not required, and it is not always an optimal implementation choice. For some architectures and distributed systems, different entities may make access control decisions and enforce access.
What to Check
- Verify AC-24 Access Control Decisions is documented in SSP
- Confirm control is operating effectively
- Review evidence of continuous monitoring for AC-24
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for AC-24 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
| Tool | Purpose | Usage |
|---|---|---|
| cloud-audit-mcp | Check IAM policies and access controls | cloud_audit_iam_policies |
| hackbrowser-mcp | Test web application access controls | browser_auth_test |
Remediation Guide
Control Statement
[organization-defined] to ensure [organization-defined] are applied to each access request prior to access enforcement.
Implementation Guidance
Access control decisions (also known as authorization decisions) occur when authorization information is applied to specific accesses. In contrast, access enforcement occurs when systems enforce access control decisions. While it is common to have access control decisions and access enforcement implemented by the same entity, it is not required, and it is not always an optimal implementation choice. For some architectures and distributed systems, different entities may make access control decisions and enforce access.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| AC-24 Access Control Decisions not implemented | High | Access Control |
| AC-24 partially implemented | Medium | Incomplete Access Control |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-284 | Improper Access Control |
References
- NIST SP 800-53 Rev 5 - AC-24
- NIST SP 800-53A Rev 5 (Assessment Procedures)
- NIST SP 800-53 Rev 5 Full Catalog
Checklist
- Control documented in SSP
- Implementation evidence collected
- Operating effectiveness validated
- Continuous monitoring in place
- Related controls (AC-2, AC-3) reviewed