Recorded Future is a threat intelligence provider that allows you to access known bad incidents of compromise and entity enrichment capabilities. It has 6 different modules and charges on a per-user basis for access to the product. The 6 different modules are:
Security Operations: Providing intel into SIEM / SOAR platforms.
Standalone Threat Intelligence: An extension of Security Operations providing context and enrichment of known and emerging threats/incidents.
Brand Intelligence: Monitoring an organization’s external exposure.
Vulnerability Management: Intelligence into the prioritization of threats.
Third party intelligence: Data from third party sources.
Geo-political: More focussed on nation-state attacks and threat indicators.
Recorded Future also charges customers for each integration they use. For example, a mutual customer of Recorded Future and Devo using this integration will pay Recorded Future a subscription fee. |
Feature | Details |
---|---|
Allow parallel downloading ( |
|
Running environments |
|
Populated Devo events |
|
Data Source | Description | API Endpoint | Collector service name | Devo Table | Available from release |
IpAddressLookupPuller | This endpoint provides a list of IPs classified as Threat by Recorded Future. |
|
type: | Lookup
|
|
DomainLookupPuller | This endpoint provides a list of domains classified as Threat by Recorded Future. |
|
| Lookup
|
|
FileHashLookupPuller | This endpoint returns a list of file hashes classified as Threat by Recorded Future. |
|
| Lookup
|
|
UrlLookupPuller | This endpoint returns a list of URL classified as Threat by Recorded Future. |
|
| Lookup
|
|
VulnerabilityLookupPuller | This endpoint returns a list of vulnerabilities classified as Threat by Recorded Future. |
|
| Lookup
|
|
PublicUkraineRussiaIpsLookupPuller | This endpoint returns a list of IPs related with Russia and Ukraine. |
|
| Lookup
|
|
This collector only requires a source configuration by generating a Recorded Future API key. Recorded Future clients with Advanced or Core licenses, and one or more Connect API subscriptions can create and manage their API tokens directly in the Recorded Future portal.
Here you find the necessary steps to enable the collection.
Steps | Screenshots | |
1 | Login to your Recorded Future account. Open the Menu in the upper-right corner and select the option User Settings. | ![]() |
2 | Select the API Access tab. To create a new API token, click on Generate New API Token. | ![]() |
3 | Enter a name for the token in the Name field. Then click on Generate. | - |
4 | Select Devo from the drop-down integration list | - |
5 | Click on the Generate new API token button. The new API token appears in the table below. Make a note of the token value as this is required for the ingest Configuration. |
- |
Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.
This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details. |
Setting | Details |
---|---|
| This param refers to the endpoint used by the collector to pull data. |
| This is the access token provided by Recorded Future. |
| This configuration allows you to define what data sources will be pulled. |
Authentication Method | Token |
---|---|
Token |
Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).
We use a piece of software called Collector Server to host and manage all our available collectors. If you want us to host this collector for you, get in touch with us and we will guide you through the configuration. This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running. StructureThe following directory structure should be created for being used when running the collector:
Devo credentialsIn Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in ![]()
Editing the config.yaml file
Replace the placeholders with your required values following the description table below:
Download the Docker imageThe collector should be deployed as a Docker container. Download the Docker image of the collector as a .tgz file by clicking the link in the following table:
Use the following command to add the Docker image to the system:
The Docker image can be deployed on the following services: DockerExecute the following command on the root directory
Docker ComposeThe following Docker Compose file can be used to execute the Docker container. It must be created in the
To run the container using docker-compose, execute the following command from the
|
Release | Released on | Release type | Details | Recommendations |
---|---|---|---|---|
| New features:
|
| ||
| Improvement:
Vulnerabilities mitigated:
|
| ||
| New features:
|
|
Here you will find a brief checklist of the important configurations that need to be done for deploying this collector:
Configuration | Requirements |
---|---|
Recorded Future API key |
Refer to the Enable the collection section. |