QuestionQ56

VerifiedProtect and Defend

The customer's security team has added a requirement: TEAP settings delivered to domain clients must use anonymous for the outer method. AOS mobility administrators now report that every wireless client appears under the same anonymous name, which makes troubleshooting difficult.

What should you recommend to best balance the security and mobility-administration needs?

Explanation

An anonymous TEAP outer identity protects the actual user or device name during the outer EAP exchange. The authenticated inner identity remains available as Authentication:TEAP-Method-2-Username. An enforcement profile can return that value in the RADIUS IETF User-Name AVP, allowing AOS mobility administrators to identify and troubleshoot clients without changing the required anonymous outer method.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!