This CIM-Compliant Technology Add-on (TA-Heartbleed) contains a new heartbleedtest command that can be used to check your internal infrastructure and external websites for the recently announced Heartbleed vulnerability.
Upon invoking the command on your Splunk search results, it will run a check against provided host/port values and return a new field, named vulnerable, that will state whether the host values are vulnerable to heartbleed or not.
The command is invoked as follows:
| heartbleedtest serverfield=[serverfield] portfield=[portfield] timeout=[int] poolsize=[int]
Note: fieldvalue, port, timeout and poolsize are optional.
Here are the defaults when they are not specified:
serverfield = dest
portfield = port
timeout = 3
poolsize = 10
NOTE: Use caution with the poolsize. The greater the poolsize, the more memory is used. A poolsize of 100 seems to be a nice sweetspot, but if you go higher, please use caution.
MySplunkSearch | heartbleedtest serverfield=dest portfield=port timeout=3 poolsize=10 | table dest port vulnerable
These are actually the default variables and we do not actually need to declare them – we are doing so here for illustrative purposes. This will run the heartbleed test on using the default serverfield of dest, the default portfield of port, the default timeout of 3 seconds and the default poolsize of 10. It will tabulate the results and tell you if any dest values are vulnerable.
MySplunkSearch | heartbleedtest serverfield=myHostField portfield=myPortField timeout=10 poolsize=100 | table myHostField myPortField vulnerable
This will run the heartbleed test on a serverfield of myHostField, a portfield of myPortField, a timeout of 10 seconds and a poolsize of 100. It will tabulate the results and tell you if any myHostField values are vulnerable.
To install the command – download the TA, then install into Splunk as you would do any other app and you should be all set. The command is set to be global, so should work from any of your existing apps.
We have knocked up a quick Heartbleed Checker dashboard form that allows you to leverage the command on a nice form in Splunk to check hosts/ports individually and get the results back. You should just be able to copy and paste into an empty view/dashboard. Feel free to edit where you see fit.
<form> <label>Heartbleed Checker</label> <fieldset autorun"false"="" submitbutton="true"> <input type="text" token="dest"> <label>Dest</label> </input> <input type="text" token="port"> <label>Port</label> <default>443</default> </input> <input type="text" token="timeout"> <label>timeout</label> <default>3</default> </input> </fieldset> <row> <table> <title>Heartbleed Results</title> <searchstring>index=_* earliest=-60m | head 1 | eval port="$port$" | eval timeout="$timeout$" | eval dest="$dest$" | heartbleedtest | table dest port vulnerable</searchstring> </table> </row> </form>
For support, feedback, questions, concerns – feel free to contact us.
- Added in new poolsize variable that allows for concurrent checking of hosts
- New Socket error message if no connection possible
Our thanks to Kenichi Suda (Macnica Networks Corp. based in Japan) for his help with these new enhancements!
Release 1.1 - Minor bug fix
Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.
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.