Skip to main content

NET-24.1: Wireless Networking Authentication & Encryption

NET 9 — Critical Protect

Mechanisms exist to secure Wi-Fi (e.g., IEEE 802.11) and prevent unauthorized access by: (1) Authenticating devices trying to connect; and (2) Encrypting transmitted data.

Renumbered: Formerly NET-15.1 in SCF 2025.4.

Control Question: Does the organization secure Wi-Fi (e.g., IEEE 802.11) and prevent unauthorized access by: (1) Authenticating devices trying to connect; and (2) Encrypting transmitted data?

General (22)
Framework Mapping Values
GovRAMP AC-18(01)
GovRAMP Moderate AC-18(01)
GovRAMP High AC-18(01)
IEC 62443-4-2 2019 NDR 1.6(1)
NIST 800-53 R4 AC-18(1)
NIST 800-53 R5.2 AC-18(01)
NIST 800-53B R5 (moderate) (source) AC-18(01)
NIST 800-53B R5 (high) (source) AC-18(01)
NIST 800-82 R3 AC-18(01)
NIST 800-82 R3 MODERATE OT Overlay AC-18(01)
NIST 800-82 R3 HIGH OT Overlay AC-18(01)
NIST 800-171 R2 (source) 3.1.17
NIST 800-171 R3 (source) 03.01.16.a 03.01.16.b 03.01.16.d
NIST 800-171A (source) 3.1.17[a] 3.1.17[b]
NIST 800-171A R3 (source) A.03.01.16.a[04] A.03.01.16.b A.03.01.16.d[01] A.03.01.16.d[02]
PCI DSS 4.0.1 (source) 1.3 2.3.1 2.3.2 4.2.1
PCI DSS 4.0.1 SAQ A-EP (source) 4.2.1
PCI DSS 4.0.1 SAQ B-IP (source) 2.3.1 2.3.2
PCI DSS 4.0.1 SAQ C (source) 2.3.1 2.3.2 4.2.1
PCI DSS 4.0.1 SAQ C-VT (source) 2.3.1 2.3.2
PCI DSS 4.0.1 SAQ D Merchant (source) 2.3.1 2.3.2 4.2.1
PCI DSS 4.0.1 SAQ D Service Provider (source) 2.3.1 2.3.2 4.2.1
US (7)
EMEA (7)
APAC (2)
Framework Mapping Values
APAC New Zealand NZISM 3.9 18.2.10.C.01 18.2.10.C.02 18.2.11.C.01 18.2.11.C.02 18.2.11.C.03 18.2.11.C.04 18.2.11.C.05 18.2.12.C.01 18.2.12.C.02 18.2.13.C.01 18.2.14.C.01 18.2.15.C.01 18.2.16.C.01 18.2.17.C.01 18.2.18.C.01 18.2.19.C.01 18.2.19.C.02 18.2.19.C.03 18.2.20.C.01 18.2.20.C.02 18.2.20.C.03 18.2.21.C.01 18.2.22.C.01 18.2.23.C.01 18.2.23.C.02 18.2.24.C.01 18.2.25.C.01
APAC Singapore CCOP CII 2026 5.8.1(b) A.3.1(b)
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.01.16.A 03.01.16.B 03.01.16.D

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

Network Security (NET) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with NET domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Network security-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Wireless access is protected via secure authentication and encryption.

Level 2 — Planned & Tracked

Network Security (NET) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with NET domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with NET domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with NET domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Network security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Network security management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ IT personnel define secure networking practices to protect the Confidentiality, Integrity, Availability and Safety (CIAS) of the organization's TAASD. ▪ Secure Baseline Configurations (SBC) enforce the principles of least privileges and least functionality for boundary protection technologies.

Level 3 — Well Defined

Network Security (NET) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with NET domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with NET domain capabilities are well-documented and kept current by process owners. ▪ A network security management team, or similar function, is appropriately staffed and supported to implement and maintain NET domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of network security operations (e.g., network management solution and log aggregator). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with NET domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ Secure Baseline Configurations (SBC) enforce the principles of least privileges and least functionality for boundary protection technologies. ▪ An implemented and operational capability exists to secure Wi-Fi (e.g., IEEE 802.11) and prevent unauthorized access by: (1) Authenticating devices trying to connect; and (2) Encrypting transmitted data.

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. NET-24.1_A01 wireless access to the system is protected using authentication.
  2. NET-24.1_A02 wireless access to the system is protected using encryption.
  3. NET-24.1_A03 information is/are maintained during preparation for transmission.
  4. NET-24.1_A04 information is/are maintained during reception.

Evidence Requirements

E-NET-14 Wireless Networking Configuration

Documented evidence of wireless networking configuration, including authentication and encryption, wireless boundaries and guest network isolation.

Network Security

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)

Small

  • Secure Baseline Configurations (SBC)

Medium

  • Secure Baseline Configurations (SBC)

Large

  • Secure Baseline Configurations (SBC)

Enterprise

  • Secure Baseline Configurations (SBC)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.