Google Chronicle Actions

Actions for Google Chronicle

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

Use Cases

Below are the possible use cases for the Send Data action:

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

• You can send data to Google Chronicle to be indexed, searched, and analyzed.

Prerequisites

A Jira account that has permissions to create tickets.

Workflows

• Creating a new Configuration and a new Action

• Creating a new Action from the Location Results page

• Editing a Configuration

• Editing an Action

• Viewing Information about an Action

Google Chronicle Configuration

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

• Customer ID. Unique ID for each Chronicle instance. For details, see: https://cloud.google.com/chronicle/docs/soar/admin-tasks/permissions/where-can-i-see-my-customer-id

• Chronicle Customer Code. Unique code supplied by Google when you subscribe to Chronicle. This field is optional.

• Region Prefix. The region where your instance of Google Chronicle resides. Choices are:

  • United States

  • Europe

  • asia-southeast1

  • europe-west2

  • australia-southeast1

  • me-west1

• Chronicle JSON Key File. Upload the JSON file that includes the credentials for the service account for Lucidum. For details on creating a service account and downloading the JSON file that contains the credentials, see https://developers.google.com/identity/protocols/oauth2/service-account#creatinganaccount .

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

Create or Edit an Action

To create an action for Jira Cloud:

1. In the Create a New Action page, in the General step, enter:

   

    

   • Action Type. Select Send Data from the pulldown options..

   • 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.

2. Click the Next (>) icon.

3. In the Filters page, click Configure Filters.

4. In the Configure Filters for Action page, you define the query for the assets or users that the action will act upon.

   

   • For existing actions, these fields are populated with values from the query for this action.

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

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

   

6. Click the Next (>) icon.

7. In the Schedule step, 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.

8. Click the Next (>) icon.

9. In the Details step, enter the following:

   

    

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

   • Chronicle Target Table Name. Database table in Chronicle where Lucidum data is stored.

   • De-dupe 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 between 0 and the number specified in Settings > System Settings > General > Data Settings > Action Result Retention in Days. This setting specifies the number of days that Lucidum stores action results.

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

     • 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 Google Chronicle.

     • 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 Google Chronicle.