Identify [organization-defined] that can be performed on the system without identification or authentication consistent with organizational mission...
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill ac-14-permitted-actions-without --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ac 14 Permitted Actions Without?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-ac-14-permitted-actions-without)More formats (shields.io, HTML) on the badges page.
---
name: "AC-14_permitted-actions-without-identification-or-authentication"
description: "Identify [organization-defined] that can be performed on the system without identification or authentication consistent with organizational mission..."
category: "authorization"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- ac-14
- ac
tech_stack:
- aws
- azure
- gcp
- linux
- windows
cwe_ids:
- CWE-284
chains_with:
- AC-8
- IA-2
- PL-2
prerequisites: []
severity_boost:
AC-8: "Chain with AC-8 for comprehensive security coverage"
IA-2: "Chain with IA-2 for comprehensive security coverage"
PL-2: "Chain with PL-2 for comprehensive security coverage"
---
# AC-14 Permitted Actions Without Identification or Authentication
## High-Level Description
**Family:** Access Control (AC)
**Framework:** NIST SP 800-53 Rev 5
Specific user actions may be permitted without identification or authentication if organizations determine that identification and authentication are not required for the specified user actions. Organizations may allow a limited number of user actions without identification or authentication, including when individuals access public websites or other publicly accessible federal systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations identify actions that normally require identification or authentication but may, under certain circumstances, allow identification or authentication mechanisms to be bypassed. Such bypasses may occur, for example, via a software-readable physical switch that commands bypass of the logon functionality and is protected from accidental or unmonitored use. Permitting actions without identification or authentication does not apply to situations where identification and authentication have already occurred and are not repeated but rather to situations where identification and authentication have not yet occurred. Organizations may decide that there are no user actions that can be performed on organizational systems without identification and authentication, and therefore, the value for the assignment operation can be "none."
## What to Check
- [ ] Verify AC-14 Permitted Actions Without Identification or Authentication is documented in SSP
- [ ] Validate all 2 control requirements are implemented
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for AC-14
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for AC-14 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 | Test web application access controls | `hackbrowser` |
## Remediation Guide
### Control Statement
Identify [organization-defined] that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and
Document and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication.
### Implementation Guidance
Specific user actions may be permitted without identification or authentication if organizations determine that identification and authentication are not required for the specified user actions. Organizations may allow a limited number of user actions without identification or authentication, including when individuals access public websites or other publicly accessible federal systems, when individuals use mobile phones to receive calls, or when facsimiles are received. Organizations identify actions that normally require identification or authentication but may, under certain circumstances, allow identification or authentication mechanisms to be bypassed. Such bypasses may occur, for example, via a software-readable physical switch that commands bypass of the logon functionality and is protected from accidental or unmonitored use. Permitting actions without identification or authentication does not apply to situations where identification and authentication have already occurred and are not repeated but rather to situations where identification and authentication have not yet occurred. Organizations may decide that there are no user actions that can be performed on organizational systems without identification and authentication, and therefore, the value for the assignment operation can be "none."
## Risk Assessment
| Finding | Severity | Impact |
| -------------------------------------------------------------------------------- | -------- | ------------------------- |
| AC-14 Permitted Actions Without Identification or Authentication not implemented | High | Access Control |
| AC-14 partially implemented | Medium | Incomplete Access Control |
## CWE Categories
| CWE ID | Title |
| ------- | ----------------------- |
| CWE-284 | Improper Access Control |
## References
- [NIST SP 800-53 Rev 5 - AC-14](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=ac-14)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)
## Checklist
- [ ] Control documented in SSP
- [ ] Implementation evidence collected
- [ ] Operating effectiveness validated
- [ ] Continuous monitoring in place
- [ ] Related controls (AC-8, IA-2, PL-2) reviewed
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!