300-715 practice question 35 of 35

An administrator is configuring posture with Cisco ISE and wants to check that specific services are present on the workstations that are attempting to access the network. What must be configured to accomplish this goal?

Full set: 294 questions
Answer options
A: Create a registry posture condition using a non-OPSWAT API version.
B: Create an application posture condition using a OPSWAT API version.
C: Create a compound posture condition using a OPSWAT API version.
D: Create a service posture condition using a non-OPSWAT API version. Correct answer
Correct Answer:
D. Create a service posture condition using a non-OPSWAT API version.
Explanation

To verify the presence and state of specific services on a client workstation, a "Service" posture condition must be configured in Cisco ISE. This is a native or "Cisco-defined" condition type that directly queries the operating system's service manager (e.g., on Windows or macOS). This functionality is built into the Cisco AnyConnect posture agent and does not utilize the OPSWAT API, which is primarily leveraged for checking the compliance status of third-party security applications like antivirus, antispyware, and personal firewalls.

Why Incorrect

A. A registry posture condition is used to check for the existence or value of specific registry keys, not to verify the status of system services.
B. An application posture condition checks for running processes (applications), which is different from checking the status of an installed background service.
C. A compound posture condition is used to logically group multiple simple conditions (like file, service, or registry) together with AND/OR logic, not to perform the initial service check itself.

References

1. Cisco Identity Services Engine Administrator Guide, Release 3.1, "Posture Conditions" section: "You can create conditions for applications, files, services, registry entries, or use compound conditions... Service Condition: Checks if a service is running on a client." This guide distinguishes these native conditions from those that use the OPSWAT compliance module for third-party security software. (Reference: Cisco Identity Services Engine Administrator Guide, Release 3.1, Chapter: Posture Services, Section: Configure Posture Policies).

2. Cisco Identity Services Engine Administrator Guide, Release 2.7, "Configure Posture Conditions" section: This document explicitly lists "Service Condition" as a type of posture condition. It details the process of specifying a service name and its required state (Running, Not Running, or Not Installed). The configuration options confirm this is a direct check and not dependent on the OPSWAT framework. (Reference: Cisco Identity Services Engine Administrator Guide, Release 2.7, Policy Elements > Conditions > Posture > Posture Conditions).

Scroll to Top