ExamGecko
Question list
Search
Search

List of questions

Search

Related questions






Refer to the scenario. # Introduction to the customer You are helping a company add Aruba ClearPass to their network, which uses Aruba network infrastructure devices. The company currently has a Windows domain and Windows CA. The Window CA issues certificates to domain computers, domain users, and servers such as domain controllers. An example of a certificate issued by the Windows CA is shown here. The company is in the process of adding Microsoft Endpoint Manager (Intune) to manage its mobile clients. The customer is maintaining the on-prem AD for now and uses Azure AD Connect to sync with Azure AD. # Requirements for issuing certificates to mobile clients The company wants to use ClearPass Onboard to deploy certificates automatically to mobile clients enrolled in Intune. During this process, Onboard should communicate with Azure AD to validate the clients. High availability should also be provided for this scenario; in other words, clients should be able to get certificates from Subscriber 2 if Subscriber 1 is down. The Intune admins intend to create certificate profiles that include a UPN SAN with the UPN of the user who enrolled the device. # Requirements for authenticating clients The customer requires all types of clients to connect and authenticate on the same corporate SSID. The company wants CPPM to use these authentication methods: EAP-TLS to authenticate users on mobile clients registered in Intune TEAR, with EAP-TLS as the inner method to authenticate Windows domain computers and the users on them To succeed, EAP-TLS (standalone or as a TEAP method) clients must meet these requirements: Their certificate is valid and is not revoked, as validated by OCSP The client's username matches an account in AD # Requirements for assigning clients to roles After authentication, the customer wants the CPPM to assign clients to ClearPass roles based on the following rules: Clients with certificates issued by Onboard are assigned the "mobile-onboarded" role Clients that have passed TEAP Method 1 are assigned the "domain-computer" role Clients in the AD group "Medical" are assigned the "medical-staff" role Clients in the AD group "Reception" are assigned to the "reception-staff" role The customer requires CPPM to assign authenticated clients to AOS firewall roles as follows: Assign medical staff on mobile-onboarded clients to the "medical-mobile" firewall role Assign other mobile-onboarded clients to the "mobile-other" firewall role Assign medical staff on domain computers to the "medical-domain" firewall role All reception staff on domain computers to the "reception-domain" firewall role All domain computers with no valid user logged in to the "computer-only" firewall role Deny other clients access # Other requirements Communications between ClearPass servers and on-prem AD domain controllers must be encrypted. # Network topology For the network infrastructure, this customer has Aruba APs and Aruba gateways, which are managed by Central. APs use tunneled WLANs, which tunnel traffic to the gateway cluster. The customer also has AOS-CX switches that are not managed by Central at this point. # ClearPass cluster IP addressing and hostnames A customer's ClearPass cluster has these IP addresses: Publisher = 10.47.47.5 Subscriber 1 = 10.47.47.6 Subscriber 2 = 10.47.47.7 Virtual IP with Subscriber 1 and Subscriber 2 = 10.47.47.8 The customer's DNS server has these entries cp.acnsxtest.com = 10.47.47.5 cps1.acnsxtest.com = 10.47.47.6 cps2.acnsxtest.com = 10.47.47.7 radius.acnsxtest.com = 10.47.47.8 onboard.acnsxtest.com = 10.47.47.8 You have imported the root certificate for the Windows CA to the ClearPass CA Trust list. Which usages should you add to it based on the scenario requirements?



Refer to the scenario. # Introduction to the customer You are helping a company add Aruba ClearPass to their network, which uses Aruba network infrastructure devices. The company currently has a Windows domain and Windows CA. The Window CA issues certificates to domain computers, domain users, and servers such as domain controllers. An example of a certificate issued by the Windows CA is shown here. The company is in the process of adding Microsoft Endpoint Manager (Intune) to manage its mobile clients. The customer is maintaining the on-prem AD for now and uses Azure AD Connect to sync with Azure AD. # Requirements for issuing certificates to mobile clients The company wants to use ClearPass Onboard to deploy certificates automatically to mobile clients enrolled in Intune. During this process, Onboard should communicate with Azure AD to validate the clients. High availability should also be provided for this scenario; in other words, clients should be able to get certificates from Subscriber 2 if Subscriber 1 is down. The Intune admins intend to create certificate profiles that include a UPN SAN with the UPN of the user who enrolled the device. # Requirements for authenticating clients The customer requires all types of clients to connect and authenticate on the same corporate SSID. The company wants CPPM to use these authentication methods: EAP-TLS to authenticate users on mobile clients registered in Intune TEAR, with EAP-TLS as the inner method to authenticate Windows domain computers and the users on them To succeed, EAP-TLS (standalone or as a TEAP method) clients must meet these requirements: Their certificate is valid and is not revoked, as validated by OCSP The client's username matches an account in AD # Requirements for assigning clients to roles After authentication, the customer wants the CPPM to assign clients to ClearPass roles based on the following rules: Clients with certificates issued by Onboard are assigned the "mobile-onboarded" role Clients that have passed TEAP Method 1 are assigned the "domain-computer" role Clients in the AD group "Medical" are assigned the "medical-staff" role Clients in the AD group "Reception" are assigned to the "reception-staff" role The customer requires CPPM to assign authenticated clients to AOS firewall roles as follows: Assign medical staff on mobile-onboarded clients to the "medical-mobile" firewall role Assign other mobile-onboarded clients to the "mobile-other" firewall role Assign medical staff on domain computers to the "medical-domain" firewall role All reception staff on domain computers to the "reception-domain" firewall role All domain computers with no valid user logged in to the "computer-only" firewall role Deny other clients access # Other requirements Communications between ClearPass servers and on-prem AD domain controllers must be encrypted. # Network topology For the network infrastructure, this customer has Aruba APs and Aruba gateways, which are managed by Central. APs use tunneled WLANs, which tunnel traffic to the gateway cluster. The customer also has AOS-CX switches that are not managed by Central at this point. # ClearPass cluster IP addressing and hostnames A customer's ClearPass cluster has these IP addresses: Publisher = 10.47.47.5 Subscriber 1 = 10.47.47.6 Subscriber 2 = 10.47.47.7 Virtual IP with Subscriber 1 and Subscriber 2 = 10.47.47.8 The customer's DNS server has these entries cp.acnsxtest.com = 10.47.47.5 cps1.acnsxtest.com = 10.47.47.6 cps2.acnsxtest.com = 10.47.47.7 radius.acnsxtest.com = 10.47.47.8 onboard.acnsxtest.com = 10.47.47.8 You have started to create a CA to meet the customer's requirements for issuing certificates to mobile clients, as shown in the exhibit below. What change will help to meet those requirements and the requirements for authenticating clients?


Question 31 - HPE6-A84 discussion

Report
Export

A customer has an AOS 10-based mobility solution, which authenticates clients to Aruba ClearPass Policy Manager (CPPM). The customer has some wireless devices that support WPA2 in personal mode only.

How can you meet these devices' needs but improve security?

A.
Use MPSK on the WLAN to which the devices connect.
Answers
A.
Use MPSK on the WLAN to which the devices connect.
B.
Configure WIDS policies that apply extra monitoring to these particular devices.
Answers
B.
Configure WIDS policies that apply extra monitoring to these particular devices.
C.
Connect these devices to the same WLAN to which 802.1X-capable clients connect, using MACAuth fallback.
Answers
C.
Connect these devices to the same WLAN to which 802.1X-capable clients connect, using MACAuth fallback.
D.
Enable dynamic authorization (RFC 3576) in the AAA profile for the devices.
Answers
D.
Enable dynamic authorization (RFC 3576) in the AAA profile for the devices.
Suggested answer: A

Explanation:

MPSK (Multi Pre-Shared Key) is a feature that allows assigning different pre-shared keys (PSKs) to different devices or groups of devices on the same WLAN. MPSK improves security over WPA2 in personal mode, which uses a single PSK for all devices on the WLAN. With MPSK, you can create and manage multiple PSKs, each with its own role, policy, and expiration date. You can also revoke or change a PSK for a specific device or group without affecting other devices on the WLAN. MPSK is compatible with devices that support WPA2 in personal mode only, as they do not need to support any additional protocols or certificates.

To use MPSK on the WLAN to which the devices connect, you need to enable MPSK in the WLAN settings and configure the PSKs in Aruba ClearPass Policy Manager (CPPM). You can find more information about how to configure MPSK in the [Configuring Multi Pre-Shared Key - Aruba] page and the [ClearPass Policy Manager User Guide] . The other options are not correct because they either do not improve security or are not applicable for devices that support WPA2 in personal mode only. For example, configuring WIDS policies that apply extra monitoring to these particular devices would not prevent them from being compromised or spoofed, but rather detect and mitigate potential attacks. Connecting these devices to the same WLAN to which 802.1X-capable clients connect, using MAC-Auth fallback, would not provide strong authentication or encryption, as MAC addresses can be easily spoofed or captured. Enabling dynamic authorization (RFC 3576) in the AAA profile for the devices would not affect the authentication process, but rather allow CPPM to change the attributes or status of a user session on the controller without requiring re-authentication.

asked 16/09/2024
Pedro Miguel Garcia Valdes
43 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first