The Splunk Add-on for Recorded Future is designed specifically for Splunk Enterprise Security.
This Add-on integrates with the Splunk ES Threat Intelligence Framework by adding a feed containing information security threat indicators from Recorded Future. With this added feature, defenders can automate the process of finding connections between internal incidents and external sources. This can work bidirectionally: searching Recorded Future for more context around internally observed indicators, or testing trending indicators from open source reporting against internal data sets.
The Add-on also simplifies the workflow of analysts working within the ES environment by adding contextual actions to the Incident Review and event searching and reporting views. This includes information on IPs, domains, file hashes and CVEs.
For more information on Recorded Future, visit www.recordedfuture.com.
To install this Add-on, perform the following steps:
Alternatively, you can download the Add-on using the Splunk Web interface's "Find more apps online" feature. Steps 5 and onwards above must still be completed.
After installation, you will need to set up the Add-on for Recorded Future to communicate with the Recorded Future API. The setup page will request your API token, and the Add-on will not import threat information without this.
The script which retrieves the list of IP number will select a Risk Score Threshold which will produce a set number of entries in the list. By default this number is 25.000. This number can be changed by editing the file recorded_future.conf in the local directory in the app directory. Ex:
max_entries = 25000
Be aware of that increasing this number will significantly increase the load on the server.
External data access and scripts
The app uses a script to retrieve threat information from Recorded Future. This script is run (default every 30 minutes) from a saved search. This data set contains IP numbers which are considered suspicious or malicious by Recorded Future. Each IP has a Risk Score and evidence of why that is assigned to it. The data contains all IPs with a Risk Score of 25 or more (100 being the maximum).
During the execution a https call is made to https://api.recordedfuture.com/ to retrieve the information which is then processed and stored on the Splunk server.
If proxy is a must, you can solve by adding a the following lines to $SPLUNK_HOME/etc/splunk-launch.conf:
If using a large IP risk list (see the Setup section above) it may be advisable to avoid transferring it across cluster nodes. This will however force the lookups to be performed locally on the search head, putting additional strain on that node.
If you want it to perform the search locally, then you can:
- add the parameter local=true to the custom search,
- you can blacklist the lookup file from the indexers:
For more information and to set up your trial or paid subscription, please contact firstname.lastname@example.org (US east coast business hours).
Alternatively, you can download the Add-on using the Splunk Web interface's "Find more apps online" feature.
This version utilizes CIM to improve performance.
Jan. 31, 2017, 3:27 p.m.
Reduces the size of the Recorded Future IP Risk List file used to generate the notable events to improve resource utilization. The size of the list is now configurable after install. This reduces the size of the file and allows it to be downloaded to Indexers for matching against IPs.
Jan. 11, 2017, 1:15 p.m.
Reduces the size of the Recorded Future IP Risk List file used to generate the notable events to improve resource untilzation. The size of the list is now configurable after install.
Dec. 22, 2016, 4:25 p.m.
6.5, 6.4, 6.3
Updated Interval of IP Risk List download. This version downloads the full Recorded Future IP Risk List and performs the correlation on the Search Head.
Nov. 29, 2016, 3:03 p.m.
We updated the add-on to have Splunk run the lookup locally (on the search head), instead of sending it to the indexer(s).
If you wanted to create your own searches or reports and include this lookup (the Recorded Future IP threat list), it will be sent down to the indexer(s). If you don't want it to perform the search this way, then you can:
· add the parameter local=true to the custom search,
· you can blacklist the lookup file from the indexers:
· up the default value for the 'max_content_length' setting in the server.conf file on the indexer.
Sept. 27, 2016, 7:51 p.m.
6.5, 6.4, 6.3
Sept. 22, 2016, 10:21 a.m.
6.5, 6.4, 6.3
Splunk's App Certification program uses a specific set of criteria to evaluate the level of quality, usability and security your app offers to its users. In addition, we evaluate the documentation and support you offer to your app's users.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.