You are setting up HPE Aruba Networking SSE. Which use case requires you to apply a non-default device posture in a rule?

HPE Aruba Networking SSE uses device posture profiles to assess the security state of an endpoint before granting access. A non-default device posture involves creating a specific profile to check for conditions beyond basic connectivity, such as the presence and status of antivirus software, firewall status, or OS patch level. This profile is then applied as a condition within a Real-time Policy Enforcement rule to determine access rights. Checking for antivirus software is a prime example of applying such a specific, non-default posture check to enforce security compliance.

A. Applying threat inspection is a standard traffic filtering function based on destination or content, not the security state of the client device itself.
C. Redirecting a client is a remediation action that can be triggered by a failed posture check, but it is not the posture check rule itself.
D. Integrating with ClearPass OnGuard is a configuration step that enables the collection of posture data, not the use case of applying that data in a policy rule.

1. HPE Aruba Networking SSE Administration Guide: In the "Policy > Device Posture" section, the guide details the creation of device posture profiles. It explicitly lists "Antivirus" and "Antispyware" as check types that can be configured to verify if the software is installed and running. This directly supports the use case in option B.

2. HPE Aruba Networking SSE Administration Guide: The "Policy > Security > Real-time Policy Enforcement" section explains how to build access rules. It shows that a "Device Posture Profile" can be selected as a criterion for a rule, confirming that the configured posture check is applied within a policy to grant or deny access.