Forescout eyeInspect
Forescout eyeInspect is an OT (operational technology) security tool. You can bring asset and security data from Forescout eyeInspect into Brinqa to gain a unified view of your attack surface, thus strengthening your cybersecurity posture.
This document details the information you must provide for the connector to authenticate with Forescout eyeInspect and how to obtain that information from Forescout eyeInspect. See create a data integration for step-by-step instructions on setting up the integration.
Required connection settings
When setting up a data integration, select Forescout eyeInspect from the Connector drop-down. If you cannot find the connector in the drop-down, make sure that you have installed it first. You must provide the following information to authenticate Forescout eyeInspect with Brinqa:
-
Server URL: The Forescout eyeInspect server URL. The default URL format is
https://<server>. -
Username and Password: The username and password associated with the Forescout eyeInspect account, which must have permissions to log in to the API server and return data.
noteThe Forescout eyeInspect user account must have at least the Viewer role assigned to retrieve data from Forescout eyeInspect. This role provides read-only access to assets, alerts, and vulnerabilities. For additional information on configuring user roles and permissions, see the Forescout eyeInspect User Management documentation.
(Optional) Create a Forescout API-only user
In addition to using credentials tied to an existing user account with the Viewer role, you can also create a dedicated API-only user in Forescout eyeInspect. This account is specifically intended for API access and retrieving data. For additional information, see the Forescout eyeInspect documentation.
Additional settings
The Forescout eyeInspect connector contains additional options for specific configuration:
-
Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.
-
Parallel requests: The maximum number of parallel API requests. The default setting is 4.
-
Maximum retries: The maximum number of times that the integration attempts to connect to the Forescout eyeInspect API before giving up and reporting a failure. The default setting is 5.
-
Skip certificate verification: Select this option to allow for untrusted certificates.
Types of data to retrieve
The Forescout eyeInspect connector can retrieve the following types of data from the Forescout eyeInspect API:
Table 1: Data retrieved from Forescout eyeInspect
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Alert | Yes | Alert |
| Alert Definition | Yes | Alert Definition |
| Asset | Yes | Host |
| Vulnerability | Yes | Vulnerability |
| Vulnerability Definition | Yes | Vulnerability Definition |
The Forescout eyeInspect connector does not support operation options for the types of data it retrieves.
For detailed steps on how to view the data retrieved from Forescout eyeInspect in the Brinqa Platform, see How to view your data.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes.
Alert
Table 2: Alert attribute mappings
| Source Field Name | Maps to Attribute |
|---|---|
| ALERT_TYPE | type |
| DESCRIPTION | description |
| FIRST_SEEN | firstFound |
| LAST_SEEN | lastFound |
| RESOURCE_ID | targets |
| STATUS | status |
| UID | uid |
Alert Definition
Table 3: Alert Definition attribute mappings
| Source Field Name | Maps to Attribute |
|---|---|
| CATEGORY | categories |
| CREATED_ON | sourceCreatedDate |
| ENABLED | enabled |
| LAST_MODIFIED | sourceLastModifiedDate |
| NAME | name |
| RECOMMENDATION | recommendation |
| SEVERITY | severity |
| UID | uid |
Asset
Table 4: Asset attribute mappings
| Source Field Name | Maps to Attribute |
|---|---|
| IP_ADDRESS | ipAddresses |
| LAST_SEEN | lastSeen |
| MAC_ADDRESS | macAddresses |
| NAME | name |
| OPERATING_SYSTEM | os |
| TAGS | tags |
| UID | uid |
Vulnerability
Table 5: Vulnerability attribute mappings
| Source Field Name | Maps to Attribute |
|---|---|
| DESCRIPTION | description |
| NAME | name |
| PATCH_AVAILABLE | patchAvailable |
| REINTRODUCED | reintroduced |
| SEVERITY | severity |
| UID | uid |
Vulnerability Definition
Table 6: Vulnerability Definition attribute mappings
| Source Field Name | Maps to Attribute |
|---|---|
| CREATED_ON | sourceCreatedDate |
| DESCRIPTION | description |
| LAST_MODIFIED | sourceLastModified |
| NAME | name |
| PATCH_AVAILABLE | patchAvailable |
| SEVERITY | severity |
| SOURCE | source |
| UID | uid |
APIs
The Forescout eyeInspect connector uses the eyeInspect API v1. Specifically, it uses the following endpoints:
Table 7: Forescout eyeInspect API Endpoints
| Connector Object | API Endpoints |
|---|---|
| Alert | GET /api/v1/alerts |
| Alert Definition | GET /api/v1/alerts |
| Asset | GET /api/v1/hosts |
| Vulnerability | GET /api/v1/hosts |
| Vulnerability Definition | GET /api/v1/hosts |
Vulnerability Definitions are not retrieved from a separate endpoint. Instead, they are derived during syncs from each host's vulnerability (CVE) records returned by the /api/v1/hosts endpoint.
Changelog
The Forescout eyeInspect connector has undergone the following changes:
Table 8: Forescout eyeInspect connector changelog
| Version | Description |
|---|---|
| 3.0.0 | Initial Integration+ release. |