The Protect and Defend section is all about securing Aruba wireless networks. The goal here is to understand how to protect these networks from unauthorized access and potential threats. This involves setting up methods to verify who is accessing the network, defining what devices can do once they’re connected, encrypting data to keep it safe, and using systems to detect and block any suspicious activities.
Authentication and Access Control help us decide who can connect to the network and what they are allowed to do. This section covers a few major points: the AAA Framework, 802.1X Authentication, EAP Types, and PSK.
AAA stands for Authentication, Authorization, and Accounting:
In Aruba networks, AAA is often managed using two types of servers:
These servers help enforce AAA by verifying users and deciding what they can do once authenticated. For the exam, you’ll need to know how to configure these servers so that they handle authentication and authorization dynamically for various users and devices.
802.1X is a standard protocol specifically designed for authenticating users and devices on wireless networks, commonly paired with a RADIUS server.
The 802.1X Authentication Process involves three main parts:
In this process, the supplicant (user/device) sends its identity to the authenticator (e.g., access point), which then forwards this information to the authentication server. If the identity is confirmed, the user/device is granted network access.
EAP (Extensible Authentication Protocol) is the method that 802.1X uses for authentication. There are several types of EAP, each with its own method for validating identities. Here are the common ones:
EAP-TLS (Transport Layer Security): This is a highly secure, certificate-based authentication method. Each user and device has a unique certificate that verifies their identity. Since it’s complex to set up and requires managing certificates, EAP-TLS is most often used in enterprises.
PEAP (Protected EAP): PEAP creates an encrypted tunnel to protect user credentials during authentication. It usually relies on a username and password. PEAP is simpler to set up than EAP-TLS and is used in many enterprise and corporate environments.
EAP-TTLS (Tunneled Transport Layer Security): Similar to PEAP, EAP-TTLS also provides an encrypted tunnel but supports multiple inner authentication protocols, making it flexible. It can use usernames and passwords but also supports other authentication types.
PSK stands for Pre-Shared Key. It’s a simpler way of securing a network using a password, often called a “Wi-Fi password.” Everyone connecting uses the same key. It’s commonly used for:
However, because everyone uses the same key, PSK isn’t as secure as 802.1X and is mostly limited to networks where advanced security isn’t necessary.
ClearPass is Aruba’s specialized tool for managing network access policies. It dynamically adjusts access based on things like the user’s role, the type of device, and their location.
ClearPass Policy Manager is the brain behind Aruba’s security policies. It allows the network administrator to create different rules and policies that control network access. For example:
ClearPass helps ensure that only authorized users and devices get access to the network and that they only get the appropriate level of access based on defined roles.
In ClearPass, administrators can set up User Roles and Access Control Policies:
User Roles: Different roles are created based on the type of user or job. For instance:
Access Control Policies: These policies set rules about what each user role is allowed to do. For example:
ClearPass can identify different device types, such as smartphones, tablets, or laptops. This is called Device Profiling. Based on the type of device, ClearPass can enforce different policies, like limiting a smartphone’s access to only basic services. This provides flexibility, making it easy to set policies that suit different device types and security needs.
Encryption is about making sure that the data traveling through the network is protected. Aruba networks support several encryption protocols.
WPA2 is the current standard for wireless security and uses AES (Advanced Encryption Standard) for strong encryption. WPA3 is the next generation, with added security features like:
Dynamic Encryption Key Management improves security by making sure that every user has a unique encryption key:
By using unique keys for each session, Aruba networks reduce the risk of data interception.
Even with strong authentication and encryption, threats can still attempt to access the network. This section covers tools that monitor the network for suspicious activities and block unauthorized access.
IDS (Intrusion Detection System) and IPS (Intrusion Prevention System) detect and prevent attacks:
WIPS is a system designed specifically for wireless networks to prevent unauthorized devices and malicious traffic. WIPS continuously scans the network for unusual activity and can take immediate action to stop devices that try to connect without permission.
For the exam, candidates should know how to configure WIPS to prevent unauthorized devices from joining the network, ensuring a secure wireless environment.
To review, Protect and Defend focuses on ensuring that:
Each of these steps ensures that the network remains secure and that only authorized users can access resources.
Aruba ClearPass Guest is designed to securely manage guest access to enterprise networks. It provides temporary network access for visitors, contractors, and customers while ensuring proper authentication and authorization.
ClearPass OnGuard ensures that only healthy and compliant devices can access the network. It scans endpoint security posture before granting network access.
By integrating ClearPass Guest and ClearPass OnGuard, organizations can enforce strong security controls while providing flexibility in network access.
A Rogue AP is an unauthorized access point that is connected to the enterprise network, potentially posing security risks. Aruba Wireless Intrusion Prevention System (WIPS) continuously scans for:
When a rogue AP is detected, Aruba solutions provide containment measures to prevent unauthorized access:
An Evil Twin Attack occurs when an attacker sets up an AP with the same SSID as a legitimate network to trick users into connecting. Aruba WIPS defends against this by:
A Denial of Service (DoS) attack aims to overwhelm network resources, making them unavailable. Aruba’s security tools help defend against:
While WPA2/WPA3 secures wireless communication, MACSec (Media Access Control Security) provides encryption for wired Ethernet links at Layer 2.
Zero Trust assumes that no user, device, or application should be trusted by default, even inside the enterprise network.
By implementing ClearPass Guest, OnGuard, MACSec, WIPS, and Zero Trust, Aruba networks significantly enhance security. These additional topics provide a comprehensive protection strategy against modern threats and ensure only trusted users and devices can access network resources.
Why might a machine-authenticated role not appear in Access Tracker even when the device successfully authenticates?
The device may only be completing user authentication instead of machine authentication.
In environments using ClearPass with 802.1X, both machine authentication and user authentication may be configured. Machine authentication occurs during system startup before the user logs in, using the computer’s credentials in Active Directory. If the workstation does not authenticate during the machine phase (for example, if the computer certificate or AD machine account is missing or misconfigured), only the user authentication event appears in Access Tracker.
Another common cause is policy configuration. If the enforcement policy only checks user credentials and does not include conditions for machine authentication, the machine role will not be applied. Engineers typically verify the authentication method, EAP configuration, and enforcement rules inside ClearPass to ensure both authentication stages are evaluated.
Demand Score: 87
Exam Relevance Score: 90
Why would an Aruba CX switch apply the default role instead of the role returned by ClearPass?
The ClearPass service may be operating in monitor mode or enforcement rules are not being applied.
When ClearPass is configured in monitor mode, it evaluates authentication requests but does not enforce policy decisions such as downloadable user roles. As a result, the switch receives authentication results but continues to apply its local default role.
Another possibility is a mismatch between the enforcement profile and the switch configuration. If the role returned by ClearPass does not exist on the switch or downloadable roles are not enabled, the switch falls back to the default role.
Troubleshooting typically involves verifying RADIUS responses, checking the switch logs (for example show event -r), and confirming enforcement profiles in ClearPass are active rather than monitoring only.
Demand Score: 85
Exam Relevance Score: 88
What is the difference between a threat and a vulnerability in network security?
A threat is a potential attacker or harmful event, while a vulnerability is a weakness that the threat can exploit.
A vulnerability exists when a system has a flaw such as weak authentication, outdated software, or misconfigured network policies. This weakness does not cause damage by itself but creates an opportunity for compromise.
A threat is the actor or event capable of exploiting that weakness. Examples include attackers performing spoofing, malware infections, or denial-of-service attacks.
For example, an outdated management protocol like Telnet is a vulnerability because it sends credentials in plaintext. An attacker capturing the credentials on the network would be the threat exploiting that vulnerability.
Security design focuses on reducing vulnerabilities through patching, encryption, and access controls to minimize the risk posed by threats.
Demand Score: 80
Exam Relevance Score: 92
Why are protocols like Telnet and HTTP considered insecure management protocols?
They transmit data in plaintext without encryption.
Telnet and HTTP do not provide confidentiality for transmitted data. Credentials, configuration commands, and session information are sent as readable text across the network. Any attacker performing packet capture or man-in-the-middle interception can easily extract sensitive information.
Secure alternatives such as SSH and HTTPS protect management traffic by encrypting communication using cryptographic protocols. Encryption ensures that intercepted traffic cannot be interpreted without the proper keys.
Modern network security best practices therefore recommend disabling Telnet and HTTP management access on controllers, switches, and access points and enabling secure protocols like SSH, HTTPS, and authenticated NTP instead.
Demand Score: 76
Exam Relevance Score: 90
How does MPSK help secure IoT or headless devices on a wireless network?
MPSK allows each device to use a unique pre-shared key and user role instead of sharing a single password.
Traditional WPA2-PSK networks use one shared password for all devices. If that password becomes compromised, every device on the network is affected.
Multi-Pre-Shared Key (MPSK) solves this problem by assigning unique credentials to each device. Each IoT device receives its own PSK and can be mapped to a specific user role through ClearPass. That role determines the device’s allowed network access, such as restricting an IoT camera to only its management server.
This approach improves security by isolating devices, limiting lateral movement, and simplifying credential revocation when devices are removed from the network.
Demand Score: 82
Exam Relevance Score: 87
Why might machine and user authentication together fail in an 802.1X wireless deployment?
The authentication order or policy conditions may not correctly handle both authentication stages.
In many enterprise environments, devices first authenticate using machine credentials and later authenticate using user credentials when someone logs in. If ClearPass policies are not configured to handle both authentication types, one stage may overwrite the other or fail completely.
Common configuration problems include missing machine authentication rules, incorrect EAP methods, or endpoint profiling issues. If the policy only checks user identity attributes, the machine authentication result is ignored.
Correct configuration requires policies that evaluate both machine and user identities and then apply a combined enforcement rule that determines the final user role.
Demand Score: 81
Exam Relevance Score: 89