AC-18_wireless-access
DevOps & SecurityAC-18_wireless-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.
Establish configuration requirements, connection requirements, and implementation guidance for each type of wireless access;
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-18_wireless-access/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ac-18-wireless-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-18 Wireless Access
High-Level Description
Family: Access Control (AC) Framework: NIST SP 800-53 Rev 5
Wireless technologies include microwave, packet radio (ultra-high frequency or very high frequency), 802.11x, and Bluetooth. Wireless networks use authentication protocols that provide authenticator protection and mutual authentication.
What to Check
- Verify AC-18 Wireless Access is documented in SSP
- Validate all 2 control requirements are implemented
- Confirm control is operating effectively
- Review evidence of continuous monitoring for AC-18
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for AC-18 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
Establish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and Authorize each type of wireless access to the system prior to allowing such connections.
Implementation Guidance
Wireless technologies include microwave, packet radio (ultra-high frequency or very high frequency), 802.11x, and Bluetooth. Wireless networks use authentication protocols that provide authenticator protection and mutual authentication.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| AC-18 Wireless Access not implemented | High | Access Control |
| AC-18 partially implemented | Medium | Incomplete Access Control |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-284 | Improper Access Control |
References
- NIST SP 800-53 Rev 5 - AC-18
- 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, AC-17, AC-19, CA-9) reviewed