Policy Enforcer's ClearPass Connector communicates with the Clearpass Radius server using the Clearpass API. As part of threat remediation, Policy Enforcer's Clearpass Connector uses enforcement profiles. This section provides information for configuring Clearpass so that Policy Enforcer can invoke the appropriate enforcement profiles.
As part of the configuration, on ClearPass you will create two enforcement profiles, one for quarantine and one for terminate. Then you will use them in the ClearPass enforcement policy. Once ClearPass is configured, you will configure a ClearPass Connector on Policy Enforcer.
On ClearPass you will configure the following:
Configure the API Client:
Note: You must login as ClearPass Guest to see the API services menu.
Figure 63: ClearPass API Client Operator Profile Minimum Privileges
Note: When the Access Token Lifetime expires, you must generate a new Client Secret and update it in the Policy Enforcer Connector UI page.
Figure 64: ClearPass Edit API Client
Configure a Custom Attribute:
Figure 65: ClearPass Edit Attribute
Configure Enforcement Profiles:
Figure 66: ClearPass Enforcement Profile: Quarantine
Note: The data displayed at the bottom of the screen is for example and not for configuration purposes. Note that the 4th attribute can be set for the accounting packets to be sent by the NAS device to the Clearpass Radius server.
Note: To configure this profile, copy the default system profile [Juniper Terminate Session] and edit the profile name and attributes.
Note: If there are any vendor-specific additional attributes required for the Terminate COA, those needs to be added here. For example, in the case of Juniper Networks Trapeze Wireless Clients, the [JNPR SDSN Terminate Session] profile requires two additional attributes: NAS-IP-Address and User-Name.
Figure 67: ClearPass Enforcement Profile: Terminate
Configure an Enforcement Policy:
In ClearPass, navigate to Configuration > Enforcement > Policies. Both profiles you created must be added to all the enforcement policies for endpoints addressed by Policy Enforcer.
Figure 68: ClearPass Enforcement Policy
Note: Rules Evaluation should be set to "First applicable."
Note: Make sure the default termination enforcement profile for each of the supported vendors is not superseded by any of its enforcement profile copies. Also make sure that all the attributes required for termination are set in the profile. (As in the previous Juniper Networks Trapeze Wireless Clients example.)
Enable Insight:
Set the Log accounting Interim-update Packets as TRUE:
© 2017 Juniper Networks, Inc. All rights reserved