Absolute

Anomali supports the ingestion of Absolute logs. The following article explains the steps you must complete to ingest Absolute logs into Anomali.

Onboarding steps

Prerequisites

You must have admin privileges to create access token.

Step 1: Create Access Token

1. Sign in to your Absolute platform.

2. Navigate to API Token Management.

3. Click Create New API Token.

4. (Optional) Provide a descriptive name for the token.

5. Click Save.

Step 2: Add Absolute as new log source

To add Absolute as a new log source on the Anomali platform:

1. Navigate to Search > Log Source Management.

2. Click New to add a new log source.

3. Enter a name for the log source.

4. (Optional) Enter a description for the log source.

5. Select Absolute as the source type.

6. Select API as the ingestion method.

7. Select API as the ingest method.

8. Provide the Basic Configuration details:

   1. Token ID: Enter the token ID of the access token from Step 1: Create Access Token.

   2. API URL: Enter the account access key you obtained in Absolute .

   3. Wildcard Log Schema: Provide the wildcard log schema.

9. (Optional) Next to the Basic Configuration section, click on the Advanced Options link to provide additional information about the event log data:

   1. Enter one or more parameters that provide additional context about the data. For example, "File format" indicates the format of the event log data being shipped, or "File extension" that indicates the extension of the logs.

   2. Enter the corresponding value of the parameter. For example, CSV is a file format. Similarly, ".gzip" is a file extension.

10. Click Save to add the log source.

Step 3: Configure permissions

You can set permissions to decide which roles can view, add, or edit log sources. To do so, configure the following parameters:

1. Owner: Select an owner of the view from the list of users. This is the email address of the owner.

2. Type: Select the type of permission assigned to the view:

   1. Private: Only the owner has read and write privileges, that is, no other user can access or edit the view.

   2. Shared: Allows you to set the read-write privileges for a role that is mapped to different users, granting read-write permissions to all users assigned that role. You can also assign read or write permissions to everyone in your organization.

Step 4: Check log source status

Once added, the status of the log source becomes Create Requested. See Log Source Statuses to understand the different types statuses assigned to log sources.

Step 5: Receive confirmation email

You will receive a notification email from Anomali once you have created a new log source request. The Log Source Management page will show the status as Create Requested.

Once the log source has been provisioned and is ready for use, Anomali will send you another email and the Log Source Management page status for the log source will change to Active.