ASD ISM 1711 Ensure user identity confidentiality in EAP-TLS
What it says
User identity confidentiality is used if available with EAP-TLS implementations.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishUse available methods to keep user identities private when using EAP-TLS for wireless network authentication.
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.
Free. Save your status, tasks and notes.
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.
How to implement
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.
Keep it running
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.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The policy document on user identity protection in EAP-TLS: Request documentation detailing how the organisation protects user identities during wireless authentication.
Look at
Whether the policy outlines methods for maintaining confidentiality.
Good evidence
Document will list specific technologies and practices used to ensure user identity confidentiality.
- Check 2 of 5What an auditor asks for
Ask for
Network configuration reports: Request evidence of current network configurations.
Look at
Whether they explicitly support identity confidentiality in EAP-TLS settings.
Good evidence
Configuration will have encryption and anonymisation settings enabled.
- Check 3 of 5What an auditor asks for
Ask for
Training 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.
- Check 4 of 5What an auditor asks for
Ask for
System update logs: Request logs showing recent firmware or software updates to network equipment.
Look at
Dates and details showing they are up-to-date and that updates include security enhancements focused on user identity protection.
Good evidence
Log will indicate that systems are regularly and recently maintained.
- Check 5 of 5What an auditor asks for
Ask for
Procurement criteria: Request criteria or guidelines used when purchasing network technology.
Look at
Evidence that security and identity confidentiality features are prioritised.
Good evidence
Will highlight a preference for equipment that supports strong encryption and user identity protection features.
Mappings
Closest match in ISO/IEC 27001: A.8.5, Secure authentication technologies and procedures, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.5.
ISM-1711 requires that user identity confidentiality features are used where available in EAP-TLS implementations to prevent exposure of user identifiers during network authentication. Annex A 8.5 requires implementing secure authentication technologies and procedures appropriate to access restrictions, which would include selecting and configuring EAP-TLS securely where it is used. ISM-1711 is a specific technical configuration requirement for one authentication method, while Annex A 8.5 is broader across authentication methods and procedures.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.