You have an Aruba Mobility Controller (MC). for which you are already using Aruba ClearPass Policy
Manager (CPPM) to authenticate access to the Web Ul with usernames and passwords You now want
to enable managers to use certificates to log in to the Web Ul CPPM will continue to act as the
external server to check the names in managers' certificates and tell the MC the managers' correct
rote
in addition to enabling certificate authentication. what is a step that you should complete on the
MC?
C
Explanation:
To enable managers to use certificates to log into the Web UI of an Aruba Mobility Controller (MC),
where Aruba ClearPass Policy Manager (CPPM) acts as the external server for authentication, it is
essential to ensure that the MC trusts the HTTPS certificate used by CPPM. This involves uploading a
trusted CA certificate to the MC that matches the one used by CPPM. Additionally, configuring a
username and password for CPPM on the MC might be necessary to secure and facilitate
communication between the MC and CPPM. This setup ensures that certificate-based authentication
is securely validated, maintaining secure access control for the Web UI.
:
Aruba Mobility Controller configuration guides that detail the process of setting up certificate-based
authentication.
Best practices for secure authentication and certificate management in enterprise network
environments.
A company has Aruba Mobility Controllers (MCs). Aruba campus APs. and ArubaOS-CX switches. The
company plans to use ClearPass Policy Manager (CPPM) to classify endpoints by type The ClearPass
admins tell you that they want to run Network scans as part of the solution
What should you do to configure the infrastructure to support the scans?
D
Explanation:
To configure the infrastructure to support network scans as part of the ClearPass Policy Manager
(CPPM) solution, creating SNMPv3 users on ArubaOS-CX switches is necessary. Ensuring that the
credentials for these SNMPv3 users match those configured on CPPM is crucial for enabling CPPM to
perform network scans effectively. SNMPv3 provides a secure method for network management by
offering authentication and encryption, which are essential for safely conducting scans that classify
endpoints by type. This configuration allows CPPM to communicate securely with the switches and
gather necessary data without compromising network security.
:
ArubaOS-CX configuration manuals that discuss SNMP settings.
Network management and security guidelines that emphasize the importance of secure SNMP
configurations for network scanning and monitoring.
You have deployed a new Aruba Mobility Controller (MC) and campus APs (CAPs). One of the WLANs
enforces 802.IX authentication lo Aruba ClearPass Policy Manager {CPPM) When you test connecting
the client to the WLAN. the test falls You check Aruba ClearPass Access Tracker and cannot find a
record of the authentication attempt You ping from the MC to CPPM. and the ping is successful.
What is a good next step for troubleshooting?
C
Explanation:
When dealing with a failed 802.1X authentication attempt to a WLAN enforced by Aruba ClearPass
Policy Manager (CPPM) where no record of the attempt is seen in ClearPass Access Tracker, a good
next troubleshooting step is to check the CPPM Event Viewer. Since you are able to successfully ping
from the Mobility Controller to CPPM, this indicates that there is network connectivity between
these two devices. The lack of a record in Access Tracker suggests that the issue may not be with the
RADIUS/EAP certificate or user credentials, but possibly with the ClearPass service itself or its
reception of authentication requests. The Event Viewer can provide detailed logs that might reveal
internal errors or misconfigurations within CPPM that could prevent it from processing
authentication attempts properly.
Refer to the exhibit.
This company has ArubaOS-Switches. The exhibit shows one access layer switch, Swllcn-2. as an
example, but the campus actually has more switches. The company wants to slop any internal users
from exploiting ARP
What Is the proper way to configure the switches to meet these requirements?
C
Explanation:
To prevent users from exploiting Address Resolution Protocol (ARP) on a network with ArubaOS-
Switches, the correct approach would be to enable DHCP snooping globally and on VLAN 201 before
enabling ARP protection, as stated in option C. DHCP snooping acts as a foundation by tracking and
securing the association of IP addresses to MAC addresses. This allows ARP protection to function
effectively by ensuring that only valid ARP requests and responses are processed, thus preventing
ARP spoofing attacks. Trusting ports that connect to employee devices directly could lead to
bypassing ARP protection if those devices are compromised.
The company’s goal is to prevent internal users from exploiting ARP within their ArubaOS-Switch
network. Let’s break down the options:
Option A (Incorrect): Enabling ARP protection globally on Switch-1 and all VLANs is not the best
approach. ARP protection should be selectively applied where needed, not globally. It’s also not clear
why Switch-1 is mentioned when the exhibit focuses on Switch-2.
Option B (Incorrect): Making ports connected to employee devices trusted for ARP protection is a
good practice, but it’s not sufficient by itself. Trusted ports allow ARP traffic, but we need an
additional layer of security.
Option C (Correct): This is the recommended approach. Here’s why:
DHCP Snooping: First, enable DHCP snooping globally. DHCP snooping helps validate DHCP messages
and builds an IP-MAC binding table. This table is crucial for ARP protection to function effectively.
VLAN 201: Enable DHCP snooping specifically on VLAN 201 (as shown in the exhibit). This ensures
that DHCP messages within this VLAN are validated.
ARP Protection: Once DHCP snooping is in place, enable ARP protection. ARP requests/replies from
untrusted ports with invalid IP-to-MAC bindings will be dropped. This prevents internal users from
exploiting ARP for attacks like man-in-the-middle.
Option D (Incorrect): While static ARP bindings can enhance security, they are cumbersome to
manage and don’t dynamically adapt to changes in the network.
:
ArubaOS-Switch Management and Configuration Guide for WB_16_10 - Chapter 15: IP Routing
Features
Aruba Security Guide
Which attack is an example or social engineering?
A
Explanation:
An example of a social engineering attack is described in option A, where an email is used to
impersonate a bank and deceive users into entering their bank login information on a counterfeit
website. Social engineering attacks exploit human psychology rather than technical hacking
techniques to gain access to systems, data, or personal information. These attacks often involve
tricking people into breaking normal security procedures. The other options describe different types
of technical attacks that do not primarily rely on manipulating individuals through deceptive personal
interactions.
Refer to the exhibit.
You have set up a RADIUS server on an ArubaOS Mobility Controller (MC) when you created a WLAN
named "MyEmployees .You now want to enable the MC to accept change of authorization (CoA)
messages from this server for wireless sessions on this WLAN.
What Is a part of the setup on the MC?
A
Explanation:
To enable an ArubaOS Mobility Controller (MC) to accept Change of Authorization (CoA) messages
from a RADIUS server for wireless sessions on a WLAN, part of the setup on the MC involves creating
a dynamic authorization, or RFC 3576, server with the provided IP address (10.5.5.5) and the correct
shared secret. This setup allows the MC to handle CoA requests, which are used to change the
authorization attributes of a session after it has been authenticated, such as disconnecting a user or
changing a user's VLAN assignment.
What is one way a noneypot can be used to launch a man-in-the-middle (MITM) attack to wireless
clients?
C
Explanation:
A honeypot can be used to launch a Man-in-the-Middle (MITM) attack on wireless clients by
examining wireless clients' probe requests and then broadcasting the SSIDs in those probes. Clients
with those SSIDs in their preferred network list may then automatically connect to the honeypot,
believing it to be a legitimate network. Once the client is connected to the attacker's honeypot, the
attacker can intercept, monitor, or manipulate the client's traffic, effectively executing a MITM
attack.
Which correctly describes a way to deploy certificates to end-user devices?
A
Explanation:
ClearPass Onboard is part of the Aruba ClearPass suite and it provides a mechanism to deploy
certificates to end-user devices, regardless of whether or not they are members of a Windows
domain. ClearPass Onboard facilitates the configuration and provisioning of network settings and
security, including the delivery and installation of certificates to ensure secure network access. This
capability enables a bring-your-own-device (BYOD) environment where devices can be securely
managed and provided with the necessary certificates for network authentication.
You have been instructed to look in the ArubaOS Security Dashboard's client list Your goal is to find
clients mat belong to the company and have connected to devices that might belong to hackers
Which client fits this description?
D
Explanation:
In the context of the ArubaOS Security Dashboard, if the goal is to find company clients that have
connected to devices potentially operated by hackers, you would look for a client that is classified as
'Interfering' (indicating a security threat) while being connected to an 'AP Classification: Rogue'. A
rogue AP is one that is not under the control of network administrators and is considered malicious
or a security threat. Therefore, the client fitting this description is:
MAC address: d8:50:e6:f3:70:ab; Client Classification: Interfering; AP Classification: Rogue
You configure an ArubaOS-Switch to enforce 802.1X authentication with ClearPass Policy Manager
(CPPM) denned as the RADIUS server Clients cannot authenticate You check Aruba ClearPass Access
Tracker and cannot find a record of the authentication attempt.
What are two possible problems that have this symptom? (Select two)
CD
Explanation:
If clients cannot authenticate and there is no record of the authentication attempt in Aruba ClearPass
Access Tracker, two possible problems that could cause this symptom are:
The RADIUS shared secret does not match between the switch and CPPM. This mismatch would
prevent the switch and CPPM from successfully communicating, so authentication attempts would
fail, and no record would appear in Access Tracker.
CPPM does not have a network device profile defined for the switch's IP address. Without a network
device profile, CPPM would not recognize authentication attempts coming from the switch and
would not process them, resulting in no logs in Access Tracker.
The other options are incorrect because:
Users logging in with the wrong credentials would still generate an attempt record in Access Tracker.
Clients configured to use a mismatched EAP method would also generate an attempt record in
Access Tracker.
Clients not configured to trust the root CA certificate for CPPM's RADIUS/EAP certificate might fail
authentication, but the attempt would still be logged in Access Tracker.