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 30 - HPE6-A84 discussion

Report
Export

You need to install a certificate on a standalone Aruba Mobility Controller (MC). The MC will need to use the certificate for the Web UI and for implementing RadSec with Aruba ClearPass Policy Manager. You have been given a certificate with these settings:

Subject: CN=mc41.site94.example.com

No SANs

Issuer: CN=ca41.example.com

EKUs: Server Authentication, Client Authentication

What issue does this certificate have for the purposes for which the certificate is intended?

A.
It has conflicting EKUs.
Answers
A.
It has conflicting EKUs.
B.
It is issued by a private CA.
Answers
B.
It is issued by a private CA.
C.
It specifies domain info in the CN field instead of the DC field.
Answers
C.
It specifies domain info in the CN field instead of the DC field.
D.
It lacks a DNS SAN.
Answers
D.
It lacks a DNS SAN.
Suggested answer: D

Explanation:

A DNS SAN (Subject Alternative Name) is an extension of the X.509 certificate standard that allows specifying additional hostnames or IP addresses that the certificate can be used for. A DNS SAN is useful for validating the identity of the server or client that presents the certificate, especially when the common name (CN) field does not match the hostname or IP address of the server or client.

In this case, the certificate has a CN of mc41.site94.example.com, which is the fully qualified domain name (FQDN) of the standalone Aruba Mobility Controller (MC). However, this CN may not match the hostname or IP address that the MC uses for the Web UI or for implementing RadSec with Aruba ClearPass Policy Manager. For example, if the MC uses a different FQDN, such as mc41.example.com, or an IP address, such as 192.168.1.41, for these purposes, then the certificate would not be valid for them. Therefore, the certificate should have a DNS SAN that includes all the possible hostnames or IP addresses that the MC may use for the Web UI and RadSec.

asked 16/09/2024
Arthur Moron
31 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first