Ensure User Identity Confidentiality in EAP-TLS
Use available methods to keep user identities private when using EAP-TLS for wireless network authentication.
Plain language
This control is about making sure that when people log into a Wi-Fi network using EAP-TLS (a secure login method), their identities are kept private. It's important because if someone's identity gets exposed, hackers can steal their information or impersonate them to access sensitive parts of the network.
Framework
ASD Information Security Manual (ISM)
Control effect
Preventative
Classifications
NC, OS, P, S, TS
ISM last updated
Aug 2021
Control Stack last updated
19 Mar 2026
E8 maturity levels
N/A
Official control statement
User identity confidentiality is used if available with EAP-TLS implementations.
Why it matters
Without EAP-TLS identity confidentiality, user identities may be exposed in 802.1X exchanges, enabling targeted attacks and aiding unauthorised access attempts.
Operational notes
Verify EAP-TLS is configured for identity privacy (e.g., anonymous outer identity) and routinely test captures to confirm real user IDs are not disclosed during authentication.
Implementation tips
- The IT team should ensure that the wireless network uses a setup that supports user identity confidentiality when using EAP-TLS. They can do this by configuring the network settings to prioritise privacy features during the setup process.
- System administrators should keep the network's firmware and software up to date. They should schedule regular checks and updates, as newer versions often include better security features, including improved identity confidentiality.
- Ensure that staff are trained on the importance of security when accessing the network. The HR team can organise workshops or training sessions to educate employees about safe login practices and how to protect their identities.
- Management should review the organisation’s current methods of handling user identity data related to network access. They should implement policies that enforce the use of aliases or anonymised identifiers where possible.
- The procurement team should choose equipment and software that supports advanced security features, including identity confidentiality. They should seek advice from IT specialists before purchasing new network hardware or software.
Audit / evidence tips
- AskThe policy document on user identity protection in EAP-TLS: Request documentation detailing how the organisation protects user identities during wireless authentication GoodDocument will list specific technologies and practices used to ensure user identity confidentiality
- AskNetwork configuration reports: Request evidence of current network configurations GoodConfiguration will have encryption and anonymisation settings enabled
- AskTraining records: Request records of employee training sessions. Look to see if these sessions cover network security and identity confidentiality practices. Good records will show regular and recent training attendance by relevant staff
- AskSystem update logs: Request logs showing recent firmware or software updates to network equipment GoodLog will indicate that systems are regularly and recently maintained
- AskProcurement criteria: Request criteria or guidelines used when purchasing network technology GoodWill highlight a preference for equipment that supports strong encryption and user identity protection features
Cross-framework mappings
How ISM-1711 relates to controls across ISO/IEC 27001, ISO/IEC 42001, Essential Eight, and ASD ISM.
ISO 27001
| Control | Notes | Details |
|---|---|---|
| layers Partially meets (1) expand_less | ||
| Annex A 8.5 | ISM-1711 requires that user identity confidentiality features are used where available in EAP-TLS implementations to prevent exposure of ... | |
These mappings show relationships between controls across frameworks. They do not imply full equivalence or certification.