# NIST SP 800-53 Rev. 5 AC-18 — Wireless Access - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-18-wireless-access - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › AC — Access Control - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `AC-18`·high·Component: **Access Control** ## What this control requires > Establishes configuration and connection requirements for wireless access; authorizes each type before connection. Uses authentication protocols to ensure authenticator protection and mutual authentication for wireless networks like 802.11x and Bluetooth. This control supports the Wireless Access Point capability within the Access Control family. > > — NIST SP 800-53 Rev. 5, Control AC-18 ### In plain English Establishes configuration and connection requirements for wireless access; authorizes each type before connection. In practice, this means you can prove you access management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Access Control**, the assessor will trace your implementation back to the catalogue reference (Control AC-18) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Configuration Management **Policy-as-code.** Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises. **IaC.** Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production. **Drift.** Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register. ### Operational checklist - **Access.** Document the trigger, the owner and the cadence. - **Configuration.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Wireless.** Document the trigger, the owner and the cadence. - **Scope:** management, access control, authentication, protection, identity, configuration, review, capability. ## Evidence to collect - **Identity Scan.** IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Wireless Access. ## Common pitfalls - Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.1.16** — Wireless Access](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-16-wireless-access) - [**CIS Controls v8 6.7** — Centralize Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-7-centralize-access-control) - [**BSI C5:2020 PS-04** — Physical site access control](https://support.icompaas.com/compliance/bsi-c5-2020/ps-04-physical-site-access-control) - [**SOC 2 (2017 TSC) CC6.4** — Physical Access Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-4-physical-access-controls) - [**ISO/IEC 27001:2022 A.8.2** — Privileged access rights](https://support.icompaas.com/compliance/iso-27001-2022/a-8-2-privileged-access-rights) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control AC-11** — Device Lock](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-11-device-lock) - [**Control AC-14** — Permitted Actions Without Identification Or Authentication](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-14-permitted-actions-without-identification-or-authentication) - [**Control AC-6(6)** — Privileged Access By Non-Organizational Users](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-6-6-privileged-access-by-non-organizational-users) - [**Control AC-9** — Previous Logon Notification](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-9-previous-logon-notification) - [**Control AC-9(1)** — Unsuccessful Logons](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-9-1-unsuccessful-logons) - [**Control AC-10** — Concurrent Session Control](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-10-concurrent-session-control) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control AC-18` Topics: identity accessidentity managementaccess reviewprivileged accessconfiguration management ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.