Recorded Future

Ingest threat intelligence indicators from Recorded Future risk lists with Elastic Agent.


Version	1.24.0 (View all)
Compatible Kibana version(s)	8.12.0 or higher
Supported Serverless project types What's this?	Security Observability
Subscription level What's this?	Basic
Level of support What's this?	Elastic

The Recorded Future integration fetches risklists from the Recorded Future API. It supports domain, hash, ip and url entities.

In order to use it you need to define the entity and list to fetch. Check with Recorded Future for the available lists for each entity. To fetch indicators from multiple entities, it's necessary to define one integration for each.

Alternatively, it's also possible to use the integration to fetch custom Fusion files by supplying the URL to the CSV file as the Custom URL configuration option.

Expiration of Indicators of Compromise (IOCs)

The ingested IOCs expire after certain duration. An Elastic Transform is created to faciliate only active IOCs be available to the end users. This transform creates a destination index named logs-ti_recordedfuture_latest.threat-1 which only contains active and unexpired IOCs. The destination index also has an alias logs-ti_recordedfuture_latest.threat. When setting up indicator match rules, use this latest destination index to avoid false positives from expired IOCs. Please read ILM Policy below which is added to avoid unbounded growth on source .ds-logs-ti_recordedfuture.threat-* indices.

ILM Policy

To facilitate IOC expiration, source datastream-backed indices .ds-logs-ti_recordedfuture.threat-* are allowed to contain duplicates from each polling interval. ILM policy is added to these source indices so it doesn't lead to unbounded growth. This means data in these source indices will be deleted after 5 days from ingested date.

NOTE: For large risklist downloads, adjust the timeout setting so that the Agent has enough time to download and process the risklist.

An example event for threat looks as following:

{
    "@timestamp": "2024-03-29T13:00:04.736Z",
    "agent": {
        "ephemeral_id": "fe05693b-59ec-47c6-9d5e-b0ef7c71ee65",
        "id": "bc94f76a-cdb2-4211-9412-c5d6c5711711",
        "name": "docker-fleet-agent",
        "type": "filebeat",
        "version": "8.12.1"
    },
    "data_stream": {
        "dataset": "ti_recordedfuture.threat",
        "namespace": "ep",
        "type": "logs"
    },
    "ecs": {
        "version": "8.11.0"
    },
    "elastic_agent": {
        "id": "bc94f76a-cdb2-4211-9412-c5d6c5711711",
        "snapshot": false,
        "version": "8.12.1"
    },
    "event": {
        "agent_id_status": "verified",
        "category": [
            "threat"
        ],
        "dataset": "ti_recordedfuture.threat",
        "ingested": "2024-03-29T13:00:14Z",
        "kind": "enrichment",
        "risk_score": 75,
        "timezone": "+00:00",
        "type": [
            "indicator"
        ]
    },
    "input": {
        "type": "log"
    },
    "log": {
        "file": {
            "path": "/tmp/service_logs/rf_file_default.csv"
        },
        "offset": 57
    },
    "recordedfuture": {
        "evidence_details": [
            {
                "Criticality": 2,
                "CriticalityLabel": "Suspicious",
                "EvidenceString": "2 sightings on 1 source: PolySwarm. Most recent link (Mar 23, 2024): https://polyswarm.network/scan/results/file/63212aa8c94098a844945ed1611389b2e1c9dc3906a5ba9d7d0d320344213f4f",
                "MitigationString": "",
                "Name": "linkedToMalware",
                "Rule": "Linked to Malware",
                "SightingsCount": 2,
                "Sources": [
                    "source:doLlw5"
                ],
                "SourcesCount": 1,
                "Timestamp": "2024-03-23T17:10:20.642Z"
            },
            {
                "Criticality": 3,
                "CriticalityLabel": "Malicious",
                "EvidenceString": "3 sightings on 3 sources: Polyswarm Sandbox Analysis, Recorded Future Triage Malware Analysis, PolySwarm. Most recent link (Mar 23, 2024): https://polyswarm.network/scan/results/file/63212aa8c94098a844945ed1611389b2e1c9dc3906a5ba9d7d0d320344213f4f",
                "MitigationString": "",
                "Name": "positiveMalwareVerdict",
                "Rule": "Positive Malware Verdict",
                "SightingsCount": 3,
                "Sources": [
                    "source:hzRhwZ",
                    "source:ndy5_2",
                    "source:doLlw5"
                ],
                "SourcesCount": 3,
                "Timestamp": "2024-03-23T16:36:02.000Z"
            }
        ],
        "name": "63212aa8c94098a844945ed1611389b2e1c9dc3906a5ba9d7d0d320344213f4f",
        "risk_string": "2/17"
    },
    "tags": [
        "forwarded",
        "recordedfuture"
    ],
    "threat": {
        "feed": {
            "name": "Recorded Future"
        },
        "indicator": {
            "file": {
                "hash": {
                    "sha256": "63212aa8c94098a844945ed1611389b2e1c9dc3906a5ba9d7d0d320344213f4f"
                }
            },
            "provider": [
                "PolySwarm",
                "Polyswarm Sandbox Analysis",
                "Recorded Future Triage Malware Analysis"
            ],
            "type": "file"
        }
    }
}

Exported fields

Field	Description	Type
@timestamp	Event timestamp.	date
cloud.account.id	The cloud account or organization id used to identify different entities in a multi-tenant environment. Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.	keyword
cloud.availability_zone	Availability zone in which this host is running.	keyword
cloud.image.id	Image ID for the cloud instance.	keyword
cloud.instance.id	Instance ID of the host machine.	keyword
cloud.instance.name	Instance name of the host machine.	keyword
cloud.machine.type	Machine type of the host machine.	keyword
cloud.project.id	Name of the project in Google Cloud.	keyword
cloud.provider	Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean.	keyword
cloud.region	Region in which this host is running.	keyword
container.id	Unique container id.	keyword
container.image.name	Name of the image the container was built on.	keyword
container.labels	Image labels.	object
container.name	Container name.	keyword
data_stream.dataset	Data stream dataset name.	constant_keyword
data_stream.namespace	Data stream namespace.	constant_keyword
data_stream.type	Data stream type.	constant_keyword
ecs.version	ECS version this event conforms to. `ecs.version` is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events.	keyword
error.message	Error message.	match_only_text
event.category	This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. `event.category` represents the "big buckets" of ECS categories. For example, filtering on `event.category:process` yields all events relating to process activity. This field is closely related to `event.type`, which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories.	keyword
event.created	`event.created` contains the date/time when the event was first read by an agent, or by your pipeline. This field is distinct from `@timestamp` in that `@timestamp` typically contain the time extracted from the original event. In most situations, these two timestamps will be slightly different. The difference can be used to calculate the delay between your source generating an event, and the time when your agent first processed it. This can be used to monitor your agent's or pipeline's ability to keep up with your event source. In case the two timestamps are identical, `@timestamp` should be used.	date
event.dataset	Event dataset	constant_keyword
event.ingested	Timestamp when an event arrived in the central data store. This is different from `@timestamp`, which is when the event originally occurred. It's also different from `event.created`, which is meant to capture the first time an agent saw the event. In normal conditions, assuming no tampering, the timestamps should chronologically look like this: `@timestamp` < `event.created` < `event.ingested`.	date
event.kind	This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. `event.kind` gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data is coming in at a regular interval or not.	keyword
event.module	Event module	constant_keyword
event.original	Raw text message of entire event. Used to demonstrate log integrity or where the full log message (before splitting it up in multiple parts) may be required, e.g. for reindex. This field is not indexed and doc_values are disabled. It cannot be searched, but it can be retrieved from `_source`. If users wish to override this and index this field, please see `Field data types` in the `Elasticsearch Reference`.	keyword
event.severity	The numeric severity of the event according to your event source. What the different severity values mean can be different between sources and use cases. It's up to the implementer to make sure severities are consistent across events from the same source. The Syslog severity belongs in `log.syslog.severity.code`. `event.severity` is meant to represent the severity according to the event source (e.g. firewall, IDS). If the event source does not publish its own severity, you may optionally copy the `log.syslog.severity.code` to `event.severity`.	long
event.type	This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. `event.type` represents a categorization "sub-bucket" that, when used along with the `event.category` field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types.	keyword
host.architecture	Operating system architecture.	keyword
host.containerized	If the host is a container.	boolean
host.domain	Name of the domain of which the host is a member. For example, on Windows this could be the host's Active Directory domain or NetBIOS domain name. For Linux this could be the domain of the host's LDAP provider.	keyword
host.hostname	Hostname of the host. It normally contains what the `hostname` command returns on the host machine.	keyword
host.id	Unique host id. As hostname is not always unique, use values that are meaningful in your environment. Example: The current usage of `beat.name`.	keyword
host.ip	Host ip addresses.	ip
host.mac	Host mac addresses.	keyword
host.name	Name of the host. It can contain what `hostname` returns on Unix systems, the fully qualified domain name, or a name specified by the user. The sender decides which value to use.	keyword
host.os.build	OS build information.	keyword
host.os.codename	OS codename, if any.	keyword
host.os.family	OS family (such as redhat, debian, freebsd, windows).	keyword
host.os.kernel	Operating system kernel version as a raw string.	keyword
host.os.name	Operating system name, without the version.	keyword
host.os.name.text	Multi-field of `host.os.name`.	text
host.os.platform	Operating system platform (such centos, ubuntu, windows).	keyword
host.os.version	Operating system version as a raw string.	keyword
host.type	Type of host. For Cloud providers this can be the machine type like `t2.medium`. If vm, this could be the container, for example, or other information meaningful in your environment.	keyword
input.type	Type of Filebeat input.	keyword
labels	Custom key/value pairs. Can be used to add meta information to events. Should not contain nested objects. All values are stored as keyword. Example: `docker` and `k8s` labels.	object
labels.is_ioc_transform_source	Field indicating if its the transform source for supporting IOC expiration. This field is dropped from destination indices to facilitate easier filtering of indicators.	constant_keyword
log.file.path	Path to the log file.	keyword
log.flags	Flags for the log file.	keyword
log.offset	Offset of the entry in the log file.	long
message	For log events the message field contains the log message, optimized for viewing in a log viewer. For structured logs without an original message field, other fields can be concatenated to form a human-readable summary of the event. If multiple messages exist, they can be combined into one message.	match_only_text
recordedfuture.evidence_details	List of sightings used as evidence for this indicator.	flattened
recordedfuture.list	User-configured risklist.	keyword
recordedfuture.name	Indicator value.	keyword
recordedfuture.risk_string	Details of risk rules observed.	keyword
tags	List of keywords used to tag each event.	keyword
threat.feed.name	Display friendly feed name	constant_keyword
threat.indicator.as.number	Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.	long
threat.indicator.as.organization.name	Organization name.	keyword
threat.indicator.as.organization.name.text	Multi-field of `threat.indicator.as.organization.name`.	match_only_text
threat.indicator.confidence	Identifies the vendor-neutral confidence rating using the None/Low/Medium/High scale defined in Appendix A of the STIX 2.1 framework. Vendor-specific confidence scales may be added as custom fields.	keyword
threat.indicator.email.address	Identifies a threat indicator as an email address (irrespective of direction).	keyword
threat.indicator.file.hash.md5	MD5 hash.	keyword
threat.indicator.file.hash.sha1	SHA1 hash.	keyword
threat.indicator.file.hash.sha256	SHA256 hash.	keyword
threat.indicator.file.hash.sha512	SHA512 hash.	keyword
threat.indicator.first_seen	The date and time when intelligence source first reported sighting this indicator.	date
threat.indicator.geo.country_iso_code	Country ISO code.	keyword
threat.indicator.geo.location	Longitude and latitude.	geo_point
threat.indicator.ip	Identifies a threat indicator as an IP address (irrespective of direction).	ip
threat.indicator.last_seen	The date and time when intelligence source last reported sighting this indicator.	date
threat.indicator.marking.tlp	Traffic Light Protocol sharing markings.	keyword
threat.indicator.provider	The name of the indicator's provider.	keyword
threat.indicator.type	Type of indicator as represented by Cyber Observable in STIX 2.0.	keyword
threat.indicator.url.domain	Domain of the url, such as "www.elastic.co". In some cases a URL may refer to an IP and/or port directly, without a domain name. In this case, the IP address would go to the `domain` field. If the URL contains a literal IPv6 address enclosed by `[` and `]` (IETF RFC 2732), the `[` and `]` characters should also be captured in the `domain` field.	keyword
threat.indicator.url.extension	The field contains the file extension from the original request url, excluding the leading dot. The file extension is only set if it exists, as not every url has a file extension. The leading period must not be included. For example, the value must be "png", not ".png". Note that when the file name has multiple extensions (example.tar.gz), only the last one should be captured ("gz", not "tar.gz").	keyword
threat.indicator.url.full	If full URLs are important to your use case, they should be stored in `url.full`, whether this field is reconstructed or present in the event source.	wildcard
threat.indicator.url.full.text	Multi-field of `threat.indicator.url.full`.	match_only_text
threat.indicator.url.original	Unmodified original url as seen in the event source. Note that in network monitoring, the observed URL may be a full URL, whereas in access logs, the URL is often just represented as a path. This field is meant to represent the URL as it was observed, complete or not.	wildcard
threat.indicator.url.original.text	Multi-field of `threat.indicator.url.original`.	match_only_text
threat.indicator.url.path	Path of the request, such as "/search".	wildcard
threat.indicator.url.port	Port of the request, such as 443.	long
threat.indicator.url.query	The query field describes the query string of the request, such as "q=elasticsearch". The `?` is excluded from the query string. If a URL contains no `?`, there is no query field. If there is a `?` but no query, the query field exists with an empty string. The `exists` query can be used to differentiate between the two cases.	keyword
threat.indicator.url.scheme	Scheme of the request, such as "https". Note: The `:` is not part of the scheme.	keyword

Changelog

Version	Details	Kibana version(s)
1.24.0	Enhancement View pull request Add destination index alias and fix docs.	8.12.0 or higher
1.23.0	Enhancement View pull request Add dashboards and list field	8.12.0 or higher
1.22.0	Enhancement View pull request Set sensitive values as secret.	8.12.0 or higher
1.21.0	Enhancement View pull request Make `threat.indicator.url.full` available for rule detections.	8.8.0 or higher
1.20.2	Enhancement View pull request Changed owners	8.8.0 or higher
1.20.1	Bug fix View pull request Fix exclude_files pattern.	8.8.0 or higher
1.20.0	Enhancement View pull request Limit request tracer log count to five.	8.8.0 or higher
1.19.0	Enhancement View pull request ECS version updated to 8.11.0.	8.8.0 or higher
1.18.1	Bug fix View pull request Fix the parse of providers information.	8.8.0 or higher
1.18.0	Enhancement View pull request Improve 'event.original' check to avoid errors if set.	8.8.0 or higher
1.17.0	Enhancement View pull request ECS version updated to 8.10.0.	8.8.0 or higher
1.16.0	Enhancement View pull request Add DLM policy. Add owner.type to package manifest. Update format_version to 3.0.0 Enhancement View pull request Add tags.yml file so that integration's dashboards and saved searches are tagged with "Security Solution" and displayed in the Security Solution UI.	8.8.0 or higher
1.15.1	Bug fix View pull request Replace dotted YAML keys.	—
1.15.0	Enhancement View pull request Update package-spec to 2.10.0.	8.8.0 or higher
1.14.0	Enhancement View pull request Update package to ECS 8.9.0.	8.8.0 or higher
1.13.0	Enhancement View pull request Document duration units.	8.8.0 or higher
1.12.0	Enhancement View pull request Ensure event.kind is correctly set for pipeline errors.	8.8.0 or higher
1.11.0	Enhancement View pull request Update package to ECS 8.8.0.	8.8.0 or higher
1.10.0	Enhancement View pull request Add IOC field to transform source to easily filter destination indices with unexpired indicators	8.8.0 or higher
1.9.0	Enhancement View pull request Support for IoC Expiration	8.8.0 or higher
1.8.0	Enhancement View pull request Add a new flag to enable request tracing	8.7.1 or higher
1.7.0	Enhancement View pull request Scrape provider details from evidence field.	8.0.0 or higher
1.6.0	Enhancement View pull request Update package to ECS 8.7.0.	8.0.0 or higher
1.5.0	Enhancement View pull request Update package to ECS 8.6.0.	8.0.0 or higher
1.4.1	Bug fix View pull request Use ECS definition for `threat.indicator.geo.location`.	8.0.0 or higher
1.4.0	Enhancement View pull request Update package to ECS 8.5.0.	—
1.3.0	Enhancement View pull request Update package to ECS 8.4.0	8.0.0 or higher
1.2.1	Bug fix View pull request Expose request timeout setting and increase it to 5m. Bug fix View pull request Do not fail on invalid URLs.	8.0.0 or higher
1.2.0	Enhancement View pull request Update categories to include `threat_intel`.	8.0.0 or higher
1.1.0	Enhancement View pull request Update package to ECS 8.3.0.	8.0.0 or higher
1.0.1	Enhancement View pull request update readme added link to recorded future API documentation	8.0.0 or higher
1.0.0	Enhancement View pull request Make GA	8.0.0 or higher
0.1.3	Enhancement View pull request Update package descriptions	—
0.1.2	Enhancement View pull request Add field mapping for event.created	—
0.1.1	Enhancement View pull request Add documentation for multi-fields	—
0.1.0	Enhancement View pull request Initial release	—

On this page

Article navigation

Expiration of Indicators of Compromise (IOCs)

ILM Policy

Changelog