Forescout Actions

Actions for Forescout #

• Send Data to Forescout. Sends a custom set of Lucidum data to Forescout.

Use Cases #

Below are the possible use cases for these actions:

• If you want to run Lucidum “headless”, you can send relevant data to Forescout on a regular schedule.

• You can send normalized, enriched Lucidum data to Forescout to be indexed, searched, and analyzed.

Prerequisites #

To execute Forescout actions, you must:

• Configure a Forescout API connection beforehand.  See https://docs.forescout.com/bundle/cloud-data-exchange-plugin-v1-0-6-h/page/task-generating-a-query-service-api-key.html.

Workflows #

• Creating a new Configuration and a new Action
• Cloning an Existing Action
• Creating a new Action from the Location Results page
• Editing a Configuration
• Editing an Action
• Viewing Information about an Action

Forescout Configuration #

To create a configuration for Forescout actions:

• Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

• URL. The URL of the Forescout API. For example, https://eaus.app.cloud.forescout.com.

• API Key. An API key that allows access to the Forescout Risk Sharing and Data Exchange API. For details on generating the API, see https://docs.forescout.com/bundle/cloud-data-exchange-plugin-v1-0-6-h/page/task-generating-a-query-service-api-key.html.

• Max # of Records per Payload. The maximum number of records to send to Forescout in each action. The default value is “50”.

Manage Action Token #

To describe an action token for Forescout actions:

1. Click the token icon.

2. In the Manage Action Tokens page, click the plus-sign in the upper right.

Create a New Action #

To create an action for Forescout, contact Lucidum customer care.

1. Go to the Create a New Action page.

   

2. In the General step, enter values in these fields:

   • Action Type. Select Send Data.

     • Send Data. Sends Lucidum data to Forescount.

   • Configuration Name. Select an action configuration from the pulldown options.

   • Action Name. Identifier for the action. This name will appear in the Lucidum Action Center.

   • Description. Description of the action.

3. Click the Next (>) icon.

4. In the Filters page, click Configure Filters.

   /li>

5. The Build a Query page appears.

   

6. In the Build a Query page, you define the query for the assets or users that the action will act upon.

7. Click Next.

8. In the Build a Current Query page, enter the fields, operators, and values for the query. For existing actions, the query is already loaded in this page.

   

9. For details on creating and editing queries in Lucidum, see the section on Building Queries.

   NOTE: To optimize performance, the default time range is Current. If you need to access historical data, contact Lucidum Custom Success for help on using historical data without affecting performance.

10. Click the Apply (page and pencil) icon.

11. Click the Next (>) icon.

12. The Schedule page appears.

    

13. In the Schedule page, enter:

    • Schedule Type. Define the schedule for the action. Choices are:

      • Recurrence. Specify a frequency for the recurring schedule.

      • After Data Ingestion. The action is executed after data ingestion, which happens at least once every 24 hours and can also be triggered manually.

    • Do not trigger the action unless. Specify the number of results from Filters as a prerequisite for executing the action.

14. Click the Next (>) icon.

15. If you selected Send Data in the Action Type field, the Details step looks like this:

    

16. In the Details page, enter the following:

    • Output Fields. For the records selected with the Filters field, specify the columns to display. When creating or editing the query in the Filters field, you can select these fields in the Query Results page > Edit Column button.

    • Dedupe Previous Jobs. In this field, you specify whether you want duplicates of asset IDs (if your query is for assets) or user IDs (if your query is for users). You can specify integers starting at 0 (zero).

      • If you specify “0” (zero), Lucidum includes all the records from the query in each delivery to Datadog.

      • If you specify “1” (one), Lucidum examines the previous webhook payload and excludes records for asset IDs or user IDs that were sent in the delivery to Datadog.

      • If you specify “2” (two), Lucidum examines the last two webhook payloads and excludes records for asset IDs or user IDs that were sent in the previous two deliveries to Datadog.