Skip to main content

LevelBlue Labs Open Threat Exchange

Connector Category: API Feed Source

Notice

The AlienVault integration is now available in Intel Exchange as LevelBlue Labs Open Threat Exchange from v3.7.6.0 (EA) onwards.

LevelBlue Labs Open Threat Exchange (OTX) integration with Intel Exchange enables you to ingest the latest vulnerability and threat indicator feeds from OTX and gain actionable insights into who is attacking you, the tools and systems they use, and related indicators of compromise. OTX provides solutions to detect and respond to threats across cloud, on-premises, and hybrid environments.

OTX integration with Intel Exchange retrieves threat data objects related to:

  • Vulnerabilities

  • Reports

Configure OTX

Integrate OTX as a feed source and start receiving threat intel in Intel Exchange. You can use the following sections for more information:

Configure OTX as a Feed Source

Configure OTX as an API feed source in Intel Exchange

Before you Start

  • You must have the base URL and API key of your OTX account.

  • You must have the View API Feed, View Feed Source, Create Feed Source, and Update Feed Source permissions in Intel Exchange.

Steps

To configure OTX as an API feed source in Intel Exchange, follow these steps:

  1. Go to Administration > Integration Management. In Feed Sources, click APIs.

  2. Click Add API Source.

  3. Search and select LevelBlue Labs Open Threat Exchange.

  4. Click Add Instance.

    1. Instance Name: Enter a unique name to identify the instance. For example, LevelBlue Labs-Prod.

    2. Base URL: Enter the base URL of your OTX instance. The default base URL is https://otx.alienvault.com/

    3. API Token: Enter the API token to authenticate with OTX.

    4. Select Verify SSL to verify the SSL certificate and secure the connection between the Intel Exchange and OTX servers. By default, the verification is enabled.

      Note

      Enabling SSL verification is recommended. If you disable this option, it may result in the use of an expired SSL certificate while configuring the instance. This may not establish the connection properly, and you will not be notified in case of a broken or improper connection.

  5. Click Save.

After OTX is configured successfully, you can view the feed channels. You can configure multiple instances by clicking Manage > Add More.

Configure OTX Feed Channels

Configure the feed channels to retrieve threat data from OTX and store them in collections within Intel Exchange.

Steps

To configure the feed channels, follow these steps:

  1. Go to Administration > Integration Management. In FEED SOURCES, click APIs.

  2. Search and select LevelBlue Labs Open Threat Exchange.

  3. Click the vertical ellipsis, and select Manage.

  4. Click Manage Feed Channels.

  5. Select a feed channel and turn on the toggle. Use the following information while configuring the channel:

    • Start Date and Time: Enter the date and time to start polling feeds. Select a date within 15 days from the current date.

    • Collection Name: Enter the name of the collection to group the feed data. For example, LevelBlue Labs Open threat Exchange Feeds. Intel Exchange creates the collection and stores all the feeds from the feed channel.

    • Polling Cron Schedule: Select from one of the following Polling Cron Schedule types to define when to poll the data:

      • Manual: Allows you to manually poll from the source collection.

      • Auto: Allows you to automatically poll for threat intel from sources at specific time intervals. The default polling cron schedule is Auto. Enter a frequency in minutes between 60 and 10080 minutes in Polling Time. The default polling time is 240 minutes.

    • TLP: Set the TLP for the feeds that do not have a TLP already assigned. The default TLP is Amber. Alternatively, you can select None to ensure that no TLP is assigned to the feeds.

    • Default Source Confidence: Enter the confidence score for the feeds that do not have a confidence score already assigned. The default confidence score is 100.

    • Deprecates after: Specify the number of days after which the threat data (indicator) will be marked as deprecated, unless the source defines its own expiry duration. The allowed range is 1-180 days.

    • Custom Score: Select the Relevance and Severity Score for the channel.

    • Default Tags: Select any tags to identify and categorize the feeds.

  6. Click Save.

The feed channel is configured, and you can poll feeds from the channel. You can enable the other feed channels and poll feeds, and view the feeds.

Test Feed Channel Connectivity

Test the connectivity of the OTX API feed channels to ensure that the connection with the correct API endpoint is established and that you have permission to poll feeds.

Before you Start

  • Ensure that the OTX API feed source is enabled.

  • Ensure that the feed channel for which you want to test connectivity is enabled.

Steps

To test the connectivity of a feed channel, follow these steps:

  1. Go to Administration > Integration Management. In Feed Sources, click APIs.

  2. Search and select the LevelBlue Labs Open Threat Exchange.

  3. On a feed channel, click the vertical ellipsis and select View Details.

  4. In the Working Status section, click Test Connectivity.

If the connection is established, then the working status shows Running. If the connectivity is broken, then the working status shows a Connection Error. Hover over the tooltip next to Connection Error to view the error code.

Note

When a feed channel loses connectivity, it is automatically disabled, and the system attempts to restore connectivity three times every hour. If the connectivity is successfully restored, the feed channel is automatically re-enabled.

To understand the error code and troubleshoot broken connectivity, see Troubleshoot Integrations.

OTX Feed Channels

The following table lists the feed channel and the API endpoint used to retrieve feeds from OTX:

Feed Channel

API Endpoint/Method

Retrieve Vulnerability Feeds

Python SDK method: getallindicators(modified_since)

For each CVE, a detailed call is made using the general get() method with the endpoint /api/indicators/cve/{cve}/general

Retrieve Pulse Feeds

Python SDK method: getall() and get_pulse_details(pulse_id)