...
| # | Name | Description | Status | Tools | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Use the right SSID | NROs MUST ensure all members only deploy the service under the 'eduroam' SSID. Non-compliant networks MUST NOT be labelled 'eduroam' or anything similar to avoid confusion for visitors. The eduroam SSID MUST NOT be shared with other network services. | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 2 | Adopt AES | eduroam wi-fi services MUST implement WPA2 Enterprise with the use of the CCMP (AES) algorithm | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 3 | Disable WPA-TKIP | The WPA specification MUST NOT be supported and the TKIP algorithm MUST NOT be employed in eduroam services | MUST NOT | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 4 | Separate non-eduroam guests | NRO and its members may offer a public guest Wi-Fi service for those unable to access eudroam; such users SHOULD be provisioned onto a separate network from eduroam visitors, with its own authentication, monitoring, and anti-circumvention measures. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 5 | Ensure clarity | NRO members SHOULD act to minimise any possibility of confusion between eduroam and other guest services they may offer (e.g. to prevent credentials being inappropriately presented) | SHOULD | Check info on web pages and other information sources (OT manual) | ||||||||||
| 6 | Adopt encrypted comms | NRO SHOULD recommend to members that they use a VPN to protect communications between Access Points and the RADIUS server. (Usually there is a controller here?!? Is VPN really needed?) | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 7 | Permit 802.11 only | NROs MUST ensure members offer eduroam ONLY on 802.11-based wireless media (i.e. NOT over bluetooth etc). | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 8 | Well-managed identity system | Ensure a well-managed identity management backend system. | MUST (IdP only) | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 9 | Maintain an audit trail | NROs MUST ensure that they and their members retain authentication and DHCP logs for <period defined in central policy?> to enable the cooperative resolution of identity in the event of abuse of eduroam. All relevant logs MUST be created with synchronisation to a reliable time source (GPS or in its absence NTP/SNTP) | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | 9 | Standardise end-user access | NROs MUST ensure all members offer eduroam users access to the minimum standard ports and protocols, which are specified in the eduroam policy, such that the baseline services (web email and VPN) are consistently available. | MUST | ||||||
| 10 | Logs | Logs of all authentication requests and responses MUST be kept. The minimum log retention time is six months, unless national regulations require otherwise. These logs may constitute personal data and MUST be managed in a GDPR-compliant way. The information in the requests and responses MUST as a minimum include: The time the authentication request was exchanged. The value of the User-Name attribute in the request ('outerEAP-identity'). The value of the Calling-Station-Id attribute in authentication requests. The result of the authentication. The value of Chargeable-User-Identity (if present in Access-Accept message). | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 11 | Standardise end-user access | NROs MUST ensure all members offer eduroam users access to the minimum standard ports and protocols, which are specified in the eduroam policy, such that the baseline services (web email and VPN) are consistently available. | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 12 | Ensure physical security | NROs must advise their members that WiFi APs and cabling SHOULD be be secured as much as possible (e.g. to restrict opportunities to introduce network taps or other tampering). All servers MUST be hosted in a secure environment. | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 13 | Provide physical signage | NRO advises member organisations to deploy physical signage in areas where eduroam is available (e.g. to assist visitors with medical prosthetics) (What does this mean in practice?(WBK)) | SHOULD | Evidence: copy of documentation/web page | ||||||||||
| 14 | Use the CAT | NRO SHOULD maintain a CAT adminstrator/config for its own staff and also recommend CAT usage to all members. Wherever possible, CAT SHOULD be used to assist with client deployments. | SHOULD | Check CAT (OT automatic), NRO verifies that CAT has been strongly recommended to | NRO verifies that this has been communicated toeduroam IdPs/SPs (NRO self) | |||||||||
| 15 | Deprecate manual configuration | Where CAT-assisted end user device configuration is not possible, it SHOULD NOT be undertaken by the end user. Administration staff should undertake such configuration to ensure it is correctly completed. Manual configuration is not recommended. | SHOULD NOT | 10 | Ensure physical security | NROs must advise their members that WiFi APs and cabling SHOULD be be secured as much as possible (e.g. to restrict opportunities to introduce network taps or other tampering). All servers MUST be hosted in a secure environment. | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | 11 | Provide physical signage | NRO advises member organisations to deploy physical signage in areas where eduroam is available (e.g. to assist visitors with medical prosthetics) (What does this mean in practice?(WBK)) | SHOULD | Evidence: copy of documentation/web page | |
| 16 | Provide end-user education | NRO and members SHOULD implement training for end users on the expected legitimate behaviours of eduroam systems. Many attacks rely on incorrect user responses to inappropriate service behaviours such as password requests, certificate mismatch warnings etc. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs and that NRO has offered to help with training implementation (NRO self) | ||||||||||
| 17 | Prevent credential sharing | NROs MUST ensure that all their members enforce the policy that credentials SHOULD NOT be shared between users (or devices where device authentication is used). Automated monitoring of high numbers of simultaneous logins may help with this. | MUST | 12 | Use the CAT | NRO SHOULD maintain a CAT adminstrator/config for its own staff and also recommend CAT usage to all members. Wherever possible, CAT SHOULD be used to assist with client deployments. | SHOULD | Check CAT (OT automatic), NRO verifies that CAT has been strongly recommended to eduroam IdPs/SPs (NRO self) | 13 | Deprecate manual configuration | Where CAT-assisted end user device configuration is not possible, it SHOULD NOT be undertaken by the end user. Administration staff should undertake such configuration to ensure it is correctly completed. Manual configuration is not recommended. | SHOULD NOT | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) Automated monitoring (OT automatic or NRO automatic) | |
| 18 | Select a certificate type | 14 | Provide end-user education | NRO and members SHOULD implement training for end users on the expected legitimate behaviours of eduroam systems. Many attacks rely on incorrect user responses to inappropriate service behaviours such as password requests, certificate mismatch warnings etcundertake a risk-based selection of private vs. public CAs for their RADIUS infrastructure. Private is usually preferrable. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs and that NRO has NROs have offered to help with training implementation and advice (NRO self) | ||||||||
| 19 | Deploy secure CA servers | CA servers MUST be hosted on a dedicated, locked-down server in a secure location, configured for minimum user access. Such servers SHOULD have a fully qualified domain name, although this MAY not be published through DNS | 15 | Prevent credential sharing | NROs MUST ensure that all their members enforce the policy that credentials SHOULD NOT be shared between users (or devices where device authentication is used). Automated monitoring of high numbers of simultaneous logins may help with this. | MUST | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) Automated monitoring (OT automatic or NRO automatic) | |||||||
| 20 | Select an EAP Type | NRO should advise members that they SHOULD use at least one of TLS, TTLS, EAP-FAST or PEAP (see reference 9) | 16 | Select a certificate type | NRO and members SHOULD undertake a risk-based selection of private vs. public CAs for their RADIUS infrastructure. Private is usually preferrable. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs and that NROs have offered help and advice (NRO self) | 17 | Deploy secure CA servers | CA servers MUST be hosted on a dedicated, locked-down server in a secure location, configured for minimum user access. Such servers SHOULD have a fully qualified domain name, although this MAY not be published through DNS. | ||||
| 21 | Implement certificate revocation | If an EAP type which uses client side certificates is used (e.g. EAP-TLS), a robust revocation process SHOULD be in place to cover loss, theft or compromise of devices. | SHOULDMUST | NRO verifies that this has been communicated to eduroam IdPs/SPs SPs (NRO self). NRO checks authentication flows through the FLTRs, identifies the organisations utilizing client certs and shows evidence that a robust revocation process is in place (NRO self) | ||||||||||
| 22 | Disable PAP | Password Authentication Protocol MUST NOT be used between access points and RADIUS servers | MUST NOT | 18 | Select an EAP Type | NRO should advise members that they SHOULD use at least one of TLS, TTLS, EAP-FAST or PEAP (see reference 9) | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||
| 23 | DIsable SPAP | Shiva Password Authentication Protocol MUST NOT be used, as their encryption is reversible (see reference 7) | MUST NOT | 19 | Implement certificate revocation | If an EAP type which uses client side certificates is used (e.g. EAP-TLS), a robust revocation process SHOULD be in place to cover loss, theft or compromise of devices. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self). NRO checks authentication flows through the FLTRs, identifies the organisations utilizing client certs and shows evidence that a robust revocation process is in place SPs (NRO self) | ||||||
| 2024 | Disable PAPMS-CHAPv1 | Challenge Handshake Password Authentication Protocol is considered weak and MUST NOT be used between access points and RADIUS servers. | MUST NOT | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | 21 | DIsable SPAP | Shiva Password Authentication Protocol MUST NOT be used, as their encryption is reversible (see reference 7) | |||||||
| 25 | Use anonymous outer identities | Where supported by the EAP type and the supplicant, it is strongly recommended that anonymous outer identities SHOULD be used. (see reference 10) | SHOULDMUST NOT | NRO verifies that this has been communicated to eduroam IdPs/SPs and checks FTLR logs (NRO self) | ||||||||||
| 2226 | Disable MSSet Operator-CHAPv1 | Challenge Handshake Authentication Protocol is considered weak and MUST NOT be used. | MUST NOT | Name | Where possible, NRO and members SHOULD ensure all Access-Request packets proxied to the NRPS contain the Operator-Name attribute correctly set to the relevant realm. | SHOULD | NRO checks authentication flow through the FTLRs NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | |||||||
| 27 | Operator-Name functionality | The appearance of the Operator-Name attribute (RFC5580) in Access-Requests MUST NOT cause these requests to be treated as invalid | MUST NOT | 23 | Use anonymous outer identities | Where supported by the EAP type and the supplicant, it is strongly recommended that anonymous outer identities SHOULD be used. (see reference 10) | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs and checks FTLR logs (NRO self) | 24 | Set Operator-Name | Where possible, NRO and members SHOULD ensure all Access-Request packets proxied to the NRPS contain the Operator-Name attribute correctly set to the relevant realm. | SHOULD | NRO checks authentication flow through the FTLRs if possible) (NRO self) | |
| 2528 | Enable CUI | Chargeable User Identity (CUI) SHOULD be implemented to enhance accountability of end user behaviour by pseudonymous means. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs and checks FTLR logs (NRO self) | ||||||||||
| 2629 | Implement rogue AP detection | Where available, NRO and members SHOULD monitor for rogue access points. IF possible, automated suppression of rogues SHOULD be implemented. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 2730 | Implement wireless IPS | Where available, NRO and members SHOULD implement Wi-Fi Intrusion Prevention Systems (IPS) to detect AP spoofing, malicious broadcasts etc. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 2831 | Operate to default deny | NROs SHOULD advise all members to operate a default deny policy on all firewalls and access control lists, only granting specific traffic types that are required and have been risk assessed to pass. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 2932 | Provide maps | Websites MAY includes graphical maps of accessible locations, noting additional services such as charging points | MAY | Check information on web site (OT manual) | ||||||||||
| 3033 | UDP fragmentation | Make sure UDP fragmentation works | MUST | Test this once a year with eduroam managed IdP - one account per organisation, verify results (OT automatic) Can be checked by peers. | ||||||||||
| 3134 | Adopt network segmentation | Network segmentation SHOULD be considered, placing roaming users into a separate segment to local organisation users. | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 3235 | Deploy VLAN spoofing countermeasures | the visitor network design SHOULD prevent devices from mailiciously placing themselves into unauthorised VLANs | SHOULD | NRO verifies that this has been communicated to eduroam IdPs/SPs (NRO self) | ||||||||||
| 3336 | audit eduroam IdPs/SPs | NROs SHOULD regularly audit eduroam IdPs/SPs on the criteria mentioned above | SHOULD | Show documentation of audit (OT manual) (Added by WBK) |
...