Which of the following requires secure connector to resolve?

The Forescout platform can resolve the logged-in user through various agentless methods, such as WMI for Windows or SSH for Linux. However, these methods require open administrative ports and valid credentials, which are often restricted or blocked by host firewalls and network security policies in many enterprise environments. The Secure Connector is an agent that initiates a secure, outbound connection to the Forescout appliance, bypassing these restrictions. Therefore, in environments where agentless polling is not feasible, the Secure Connector is required to reliably resolve the user's authentication and login status on the endpoint.

A. Authentication login (advanced): This is not a standard, formally defined Forescout property, making it an imprecise and less accurate choice than a fundamental property.

B. Authentication certificate status: This is typically resolved agentlessly by the PKI (Public Key Infrastructure) Plugin, which queries a Certificate Authority (CA) server.

C. HTTP login user: This property is resolved agentlessly by the Directory Plugin, which monitors network authentication traffic or integrates with web proxies.

E. Signed-In status: This is functionally synonymous with "Authentication login," but the latter is a more formally used term for the property within the platform.

1. Forescout Administration Guide, Version 8.2, Page 91, "SecureConnector": "The agent overcomes challenges that may be associated with agentless discovery and control, for example, when endpoints are behind a personal firewall, when administrative credentials are not available, or when remote registry services are disabled." This source confirms that the agent is required when standard agentless methods for gathering endpoint data (like login status) are blocked.

2. Forescout eyeSight Endpoint Property Reference Guide, Version 8.2, Page 115, "Logged In User": This document lists the "HPS Agent Manager" (which manages Secure Connector) as a primary source for resolving the logged-in user. It also lists agentless sources like "HPS Inspection Engine" (WMI) and "SSH Login," confirming that while agentless methods exist, the agent is a distinct and necessary alternative.

3. Forescout Platform and eyeSight Administration Course (FSCA) Student Guide: The courseware consistently emphasizes that a primary use case for deploying the Secure Connector is to gain visibility, including user information, on endpoints where agentless methods like WMI/SSH are unavailable due to security restrictions.