AC-3(12)_assert-and-enforce-application-access
DevOps & SecurityAC-3(12)_assert-and-enforce-application-access 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.
Require applications to assert, as part of the installation process, the access needed to the following system applications and functions: [organiz...
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-3(12)_assert-and-enforce-application-access/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ac-3-12-assert-and-enforce-application-access, 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(12) Assert and Enforce Application Access
Enhancement of: AC-3
High-Level Description
Family: Access Control (AC) Framework: NIST SP 800-53 Rev 5
Asserting and enforcing application access is intended to address applications that need to access existing system applications and functions, including user contacts, global positioning systems, cameras, keyboards, microphones, networks, phones, or other files.
What to Check
- Verify AC-3(12) Assert and Enforce Application Access is documented in SSP
- Validate all 3 control requirements are implemented
- Confirm control is operating effectively
- Review evidence of continuous monitoring for AC-3(12)
- 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(12) 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
Require applications to assert, as part of the installation process, the access needed to the following system applications and functions: [organization-defined]; Provide an enforcement mechanism to prevent unauthorized access; and Approve access changes after initial installation of the application.
Implementation Guidance
Asserting and enforcing application access is intended to address applications that need to access existing system applications and functions, including user contacts, global positioning systems, cameras, keyboards, microphones, networks, phones, or other files.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| AC-3(12) Assert and Enforce Application Access not implemented | High | Access Control |
| AC-3(12) partially implemented | Medium | Incomplete Access Control |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-284 | Improper Access Control |
References
- NIST SP 800-53 Rev 5 - AC-3(12)
- 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 (CM-7) reviewed