ClearPass Onboard can operate as a certificate authority for BYOD provisioning. When the goal is to issue device certificates that are trusted for authentication to the company's own ClearPass cluster, using the Onboard CA as a root CA creates a self-contained trust chain controlled by the organization. HPE Aruba documentation explains that Onboard can operate directly as a root CA or as an intermediate CA, and that a common root CA is required in a ClearPass cluster so provisioned devices can authenticate through any node.
EST is used for enrollment workflows and does not define the desired trust boundary. A registration authority validates and forwards requests but is not the CA that issues the certificates.

When establishing a cluster of HPE Aruba Networking ClearPass servers, it is recommended to install a CA- signed certificate for HTTPS on the Subscriber before it joins the cluster. This ensures secure communication between the servers in the cluster and provides a trusted certificate for client connections.
1.HTTPS Security: A CA-signed certificate for HTTPS ensures that all web-based communication to and from the ClearPass server is encrypted and secure.
2.Cluster Communication: Secure communication between ClearPass nodes in the cluster is essential for synchronization and data integrity.
3.Client Trust: Clients accessing the ClearPass server will trust the CA-signed certificate, avoiding security warnings and ensuring smooth operations.
Reference: ClearPass documentation and best practices for clustering and certificate management recommend installing CA-signed certificates for secure HTTPS communication.

When using HPE Aruba Networking ClearPass Device Insight (CPDI) and you need to reclassify a device to a custom type and apply this classification to all devices with similar attributes, both already discovered and newly discovered, you should follow these steps:
1.Navigate to the device details in CPDI.
2.Select the option to reclassify the device.
3.Create a user rule based on the desired attributes of the device.
4.Choose the "Save & Reclassify" option.
This process ensures that the device is reclassified according to the new custom type and that the rule is applied to all existing and future devices with matching attributes, maintaining consistent classification across the network.
Reference: The ClearPass Device Insight user guide includes detailed instructions on device classification, rule creation, and managing device attributes to maintain accurate network visibility and security.

Integrating HPE Aruba Networking ClearPass Policy Manager (CPPM) and HPE Aruba Networking ClearPass Device Insight (CPDI) can help a company implement Zero Trust Security by allowing CPDI to use tags to inform CPPM that clients are using prohibited applications.
CPPM can then take action, such as telling the network infrastructure to quarantine those clients, ensuring that only compliant and trusted devices have network access.
1. Device Insight Tags: CPDI can monitor client behavior and tag devices that are using prohibited applications.
2. Policy Enforcement: CPPM can use these tags to apply specific enforcement actions, such as quarantining non-compliant devices.
3. Zero Trust Implementation: This integration supports Zero Trust Security by ensuring that all devices are continuously monitored and controlled based on their behavior and compliance with security policies.

To set up HPE Aruba Networking ClearPass Policy Manager (CPPM) for certificate-based authentication of 802.1X supplicants, you need to upload the root CA certificate as a Trusted CA with the EAP usage. This configuration allows the ClearPass server to validate the certificates presented by the supplicants during the 802.1X authentication process. By marking the certificate for EAP usage, ClearPass can properly authenticate the supplicant devices using the trusted certificate authority (CA) that issued their certificates.