Incoming feed - Binary Defense Systems Artillery Threat Intelligence Feed
This procedure describes how to configure incoming feeds for a particular feed data source, transport type, or content type.
For more information about configuring common options shared across all incoming feeds, see Configure incoming feeds general options.
|
Specifications |
Transport type |
Binary Defense Systems Artillery Threat Intelligence Feed |
Content type |
Binary Defense JSON |
Ingested data |
IPv4 addresses. |
Processed data |
Indicators. |
Description |
The extension ingests a flat feed of malicious IPv4 indicators into the platform. |
Configure the incoming feed
Create or edit an incoming feed.
From the Transport type drop-down menu, select Binary Defense Systems Artillery Threat Intelligence Feed.
From the Content type drop-down menu, select Binary Defense JSON.
The API URL field is automatically filled in with the default domain for the endpoint.
You can add a proxy or set up ports according to your needs.
Default value: https://www.binarydefense.com/banlist.txt.The SSL verification checkbox is automatically selected.
In the Path to SSL certificate file field, you can enter the path to your PEM file.
It is also possible to leave the field blank.To store your changes, click Save; to discard them, click Cancel.
Test the feed
In the top navigation bar, click Data Configuration > Incoming feeds.
Click the feed that you just created, using the steps above.
In the Overview view, click Download now.
Click Ingested entities and check that entities have been ingested into the platform.
Or:
In the top navigation bar, click Intelligence > All intelligence > Browse.
Click the Entities tab.
In the top-left corner, click .
From the Source drop-down menu, select the incoming feed you have just created, using the steps.
You can also filter also by entity type: from the Entity drop-down menu, select the entity types you want to include in the filtered results.