+NET.2.1 WLAN Operation
---+NET.2.1.G1. Failure or Disruption of a Radio Network
---+NET.2.1.G2. Inadequate Planning of WLAN Usage
---+NET.2.1.G3. Insufficient Rules on WLAN Usage
---+NET.2.1.G4. Inappropriate Selection of Authentication Methods
---+NET.2.1.G5. Incorrect Configuration of WLAN Infrastructure
---+NET.2.1.G6. Insufficient WLAN Security Mechanisms
---+NET.2.1.G7. Eavesdropping on WLAN Communication
---+NET.2.1.G8. Simulating a Valid Access Point (Rogue access Points)
---+NET.2.1.G9. Unprotected LAN Access at Access Points
---+NET.2.1.G10. Hardware Damage
---+NET.2.1.G11. Theft of an Access Point
---+NET.2.1.A1 Definition of a Strategy for WLAN Usage (B)
---+NET.2.1.A2 Selection of a Suitable WLAN Standard [Planner] (B)
---+NET.2.1.A3 Selection of Suitable Crypto Methods for WLAN [Planner] (B)
---+NET.2.1.A4 Suitable Location of Access Points [Building Services] (B)
---+NET.2.1.A5 Secure Basic Configuration of Access Points (B)
---+NET.2.1.A6 Secure Configuration of WLAN Infrastructure (B)
---+NET.2.1.A7 Setting Up a Distribution System [Planner] (B)
---+NET.2.1.A8 Codes of Conduct in the Event of WLAN Security Incidents (B)
---+NET.2.1.A9 Secure Connection of WLANs to a LAN [Planner] (S)
---+NET.2.1.A10 Drawing Up a Security Policy for WLAN Operation (S)
---+NET.2.1.A11 Selection of Suitable WLAN Components (S)
---+NET.2.1.A12 Use of a Suitable WLAN Management Solution (S)
---+NET.2.1.A13 Regular Security Checks of WLANs (S)
---+NET.2.1.A14 Regular Audits of WLAN Components (S)
---+NET.2.1.A15 Using a VPN to Secure WLANs (H)
---+NET.2.1.A16 Additional Protection When Connecting WLANs to a LAN (H)
---+NET.2.1.A17 Protecting Communication Between Access Points (H)
---+NET.2.1.A18 Use of Wireless Intrusion Detection / Wireless Intrusion Prevention Systems (H)
|
NET.2.1 WLAN Operation
IntroductionWireless LANs (WLANs) can be used to create wireless local networks or extend existing wired networks. To this day, almost all the WLAN components available on the market have been based on the IEEE 802.11 standard and its additions. The manufacturer consortium Wi-Fi Alliance plays an important role in this regard as the creator of the industry-agreed “Wi-Fi” standard based on IEEE 802.11. The Wi-Fi Alliance uses the Wi-Fi quality label to confirm that a device has passed certain interoperability and conformity tests. Within organisations, WLANs can be used to work flexibly with mobile devices and enable them to access internal networks. For this purpose, network access is established within a given organisation via access points. Because they can usually be installed quickly and easily, WLANs are also used to establish temporary networks—for example, at trade fairs or smaller events. Furthermore, network access may be offered in public spaces such as airports or train stations through hotspots. This enables mobile users to connect to the Internet or to their organisation's network. Communication then generally takes place between a central access point and the WLAN component of the end device used. ObjectiveThis module systematically demonstrates how WLANs can be established and operated securely in an organisation. Scoping and ModellingModule NET.2.1 WLAN Operation must be applied to all communication networks that are established and operated according to the standard series IEEE 802.11 and its extensions. The module includes basic specifications that must be considered and met when establishing and operating WLANs in organisations. Requirements for the secure use of WLANs are not part of this module. The secure use of WLANs is addressed in module NET.2.2 WLAN Usage. WLANs may be operated in two different modes depending on the needs of the operator in question and the hardware equipment available. In ad-hoc mode, two or more WLAN clients communicate directly with each other. WLANs in ad-hoc mode can set up and configure themselves independently (i.e. without a fixed infrastructure), allowing them to establish a fully meshed parallel network infrastructure. This makes ad-hoc mode unsuitable in an environment that needs to be protected; it is therefore not considered further in this module. In the majority of cases, WLANs are operated in infrastructure mode—that is, the communication of WLAN clients and the connection to wire-bound LAN segments take place via access points. If corresponding services (e.g. RADIUS) are used for WLAN authentication, the corresponding IT systems on which the services are operated must be secured separately. The modules of the SYS.1 layer, such as SYS.1.1 General Server, can be used for this purpose. In principle, any WLAN operations that have been established should be taken into account when implementing the modules NET.1.1 Network Architecture and Design, NET.1.2 Network Management, and DER.2.1 Security Incident Handling. Useful ResourcesThe BSI has published the following additional documents related to WLAN: - BSI Standard for Internet Security (ISi series): Secure Connection of Local Networks to the Internet (ISi-LANA)
The National Institute of Standards and Technology (NIST) has published the following additional documents on WLAN: - NIST Special Publication 800-153, Guidelines for Securing Wireless Local Area Networks (WLANs)
- NIST Special Publication 800-97, Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11
1. Panoramica
| Titolo |
Standard |
|
NET.2.1.A1 Definition of a Strategy for WLAN Usage (B)
|
Before WLANs are used in an organisation, the organisation's general strategy for communication through WLANs MUST be specified. In particular, the organisational units in which WLANs will be used, the applications and purposes they will be used for, and the information that may be transmitted MUST be clarified and defined. The WLAN coverage area MUST also be determined. Furthermore, it MUST be defined right from the planning phase who will be responsible for the administration of the various WLAN components, which interfaces will be in place between the persons in charge who are involved in WLAN operations, and when specific information must be exchanged among the persons in charge.
|
|
NET.2.1.A2 Selection of a Suitable WLAN Standard [Planner] (B)
|
Within the framework of WLAN planning, there MUST be an initial determination of which of the devices operated by the organisation in question (e.g. microwave ovens, Bluetooth devices) radiate into the ISM band at 2.4 GHz and into the 5 GHz band. In addition, the security mechanisms available in the individual WLAN standards MUST be compared. In general, it MUST be ensured that only authentication and encryption methods that are generally considered secure will be used. The organisation MUST document its reasons for choosing a particular WLAN standard. Devices that need to fall back on insecure methods from recognised secure methods MUST NOT be considered during planning.
|
|
NET.2.1.A3 Selection of Suitable Crypto Methods for WLAN [Planner] (B)
|
Communication via the air interface MUST be completely secure in cryptographic terms. Cryptographic methods that are less secure than WPA2 MUST NOT be used. If WPA2 is used with pre-shared keys (WPA2-PSK), a complex key with a minimum length of 20 characters MUST be used.
|
|
NET.2.1.A4 Suitable Location of Access Points [Building Services] (B)
|
Access points MUST be mounted such that they cannot be accessed or stolen. If they are set up, the required areas MUST be adequately covered. Furthermore, it MUST be ensured to the greatest extent possible that the radio waves are not emitted into areas not designated for WLAN coverage. Outside installations MUST be protected appropriately against weather and electrical discharges.
|
|
NET.2.1.A5 Secure Basic Configuration of Access Points (B)
|
Access points MUST NOT be used in their default configuration. Pre-set SSIDs (service set identifiers), passwords, and cryptographic keys MUST be changed prior to productive use. In addition, insecure administration access MUST be disabled. Access points MUST ONLY be administered via a suitably encrypted connection.
|
|
NET.2.1.A6 Secure Configuration of WLAN Infrastructure (B)
|
It MUST be ensured that WLAN communication is not used to couple security zones or bypass established protection safeguards.
|
|
NET.2.1.A7 Setting Up a Distribution System [Planner] (B)
|
Before a wired distribution system is established, a basic decision MUST be made as to whether separation will be performed physically or logically through VLANs on the access switches of the wired LAN in question.
|
|
NET.2.1.A8 Codes of Conduct in the Event of WLAN Security Incidents (B)
|
If a security incident occurs, the IT Operation Department MUST initiate appropriate countermeasures: - At the point where WLAN communication enters the internal LAN in question, communication SHOULD be blocked selectively for every SSID and access point—or even for the entire WLAN infrastructure—in the event of an attack.
- If access points have been stolen, defined security safeguards MUST be implemented to prevent any misuse of the access points or the information stored on them.
- If WLAN clients have been stolen and central certificate-based authentication is being used, the client certificates MUST be blocked.
The possibility of using stolen devices without authorisation in order to access the network of a given organisation MUST be ruled out.
|
|
NET.2.1.A9 Secure Connection of WLANs to a LAN [Planner] (S)
|
If WLANs are connected to a LAN, the transition between the WLANs and the LAN SHOULD be protected—for example, with the help of a packet filter. The access point SHOULD be integrated in line with the requirements of NET.2.1.A7 Setting Up a Distribution System.
|
|
NET.2.1.A10 Drawing Up a Security Policy for WLAN Operation (S)
|
Based on the general security policy of the organisation in question, essential core aspects SHOULD be specified for the secure use of WLANs. The policy SHOULD be known to all persons in charge who are involved in establishing and operating WLANs. It SHOULD form the basis of their work. The implementation of the policy's requirements SHOULD be checked at regular intervals. If the contents of the policy are not implemented, there MUST be a suitable response. The results SHOULD be documented appropriately.
|
|
NET.2.1.A11 Selection of Suitable WLAN Components (S)
|
Based on the results of the planning phase, a requirements list SHOULD be drawn up that can be used to help evaluate the products available on the market. When procuring WLAN components, data protection and the intercompatibility of the components SHOULD be taken into account along with security.
|
|
NET.2.1.A12 Use of a Suitable WLAN Management Solution (S)
|
A central management solution SHOULD be used. The functional range of the solution used SHOULD be in accordance with the requirements of the WLAN strategy at hand.
|
|
NET.2.1.A13 Regular Security Checks of WLANs (S)
|
WLANs SHOULD be checked regularly for security vulnerabilities. In addition, the WLANs provided SHOULD be searched regularly for access points that have been installed without authorisation. Their performance and coverage SHOULD also be measured. The results of security checks SHOULD be documented transparently and compared against the target condition. Deviations SHOULD be investigated.
|
|
NET.2.1.A14 Regular Audits of WLAN Components (S)
|
All components of WLAN infrastructure SHOULD be checked regularly to ensure that all the specified security safeguards have been implemented and all the components have been configured correctly. Access points mounted in public areas SHOULD be checked randomly at regular intervals to determine whether there have been attempts to open or manipulate them by force. The audit results SHOULD be documented transparently and compared against the target condition. Deviations SHOULD be investigated.
|
|
NET.2.1.A15 Using a VPN to Secure WLANs (H)
|
A VPN SHOULD be used to achieve additional protection of WLAN communications.
|
|
NET.2.1.A16 Additional Protection When Connecting WLANs to a LAN (H)
|
If a WLAN infrastructure is connected to a LAN, the transition between WLANs and the LAN SHOULD be secured in line with the applicable increased protection needs.
|
|
NET.2.1.A17 Protecting Communication Between Access Points (H)
|
Communication between access points via the wireless interface and the LAN SHOULD be encrypted.
|
|
NET.2.1.A18 Use of Wireless Intrusion Detection / Wireless Intrusion Prevention Systems (H)
|
Wireless intrusion detection or prevention systems SHOULD be used.
|
1.1 Riferimenti
1.2 Requisiti identificati
1.3 Regolamentazioni correlate
2. Requisiti identificati
Requisiti
| Fonte |
Requisito |
3. Regolamentazioni correlate
Regolamentazioni
| Fonte |
Regolamentazione |
Ticket collegati
|