icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

We are working on something new...

A Fresh New Splunkbase
We are designing a New Splunkbase to improve search and discoverability of apps. Check out our new and improved features like Categories and Collections. New Splunkbase is currently in preview mode, as it is under active development. We welcome you to navigate New Splunkbase and give us feedback.
Log4Shell Vulnerability: Information and guidance for you. Get resources.

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading NodeZero App for Splunk
SHA256 checksum (nodezero-app-for-splunk_200.tgz) 44832bf97beafb9d88d1cfa1e4636a1b7f34b917c019db44b2d96994ec65f940
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate


NodeZero App for Splunk

Splunk Cloud
NodeZero provides continuous autonomous penetration testing as a true SaaS offering. With NodeZero, cybersecurity teams proactively find and fix internal and external attack vectors before attackers can exploit them.

The NodeZero App for Splunk allows users to ingest pentest results directly into Splunk, merging insights gained from the attacker's perspective with existing data and workflows.

New to NodeZero? Find out more at: https://horizon3.ai

App Contents

  • Add-on included
    The NodeZero App for Splunk comes bundled with the NodeZero Add-on for Splunk built in, which contains the modular input for pulling NodeZero pentests results into the Splunk index of your choosing. There is no need to install both on a standalone instance.

  • Sample Dashboard
    There exists a sample dashboard, NodeZero Operations, to demonstrate how one might view summary information across all penetration tests visible in Splunk, then drilldown through specific weaknesses to see exactly what operations NodeZero took against certain hosts during a specific time range.

CIM Compliant

Weakness data has been mapped to the CIM Vulnerability datamodel


NodeZero API Key

An API key is required to access the API. The key is tied to an existing user account with Org Admin privileges in the Horizon3.ai portal.
(At this time, API keys are manually provisioned by Horizon3.ai. If you don’t have an API key, please contact your Horizon3.ai representative to acquire one.)


Save API Key to Splunk credential store

On the Configuration page, click the Add button on the Accounts sub-tab

  • Name is a simple name that gets used by the Inputs page
  • Description is for any notes/details about the API Key/Account
  • API Key is an encrypted field for saving the NodeZero API Key

Create the Input

On the 'Inputs' tab, click "Create New Input"

  • Name (required) is a simple name that gets used by the modular input
  • Description (optional) is for any notes about the modular input
  • API Account (required) is a dropdown single select to choose the account for which you wish to pull data
  • Index (required) the index to which you would like to ingest NodeZero data
  • Polling Interval (optional) Default is 86400 seconds (daily). How frequently you want to poll for new data

Once the input is saved, it immediately begins attempting to pull data from the NodeZero API

Index macro

For the sample dashboard to work, it relies on a macro called: h3_index. The default value for this macro is: (), and will only work if your events are being sent do the default index (usually main). Set the macro (via Settings > Advanced Search > Search Macros) to whatever index you selected when defining your modular input (e.g., (index=my_nodezero_test_index)

Verify data is being indexed

To make sure the modular input is doing its job, you can run the following search:

`h3_index` | stats values(sourcetype) as st

You should see three sourcetypes:


There is also a non-navigable dashboard at /en-US/app/nodezero/kvstore_state that will show a table based on the KVstore the modular input uses to store app state. This can be used during troubleshooting to see what data has been pulled for each pentest.


For troubleshooting information, view ExecProcessor logs and the nodezero logs:

    index=_internal (sourcetype=splunkd nodezero component=ExecProcessor) OR sourcetype="nodezero-*"

Note: Don't forget the asterisk on the end of sourcetype=nodezero*, as they often show up as nodezero-too-small.

For more logs: set LOGGING to DEBUG in the Configuration tab


Email splunk@horizon3.ai with any questions, comments, or concerns. Feedback is greatly appreciated!

Release Notes

Version 2.0.0
June 9, 2022

Initial release to Splunkbase

Subscribe Share

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
Splunk, Splunk>,Turn Data Into Doing, Data-to-Everything, and D2E are trademarks or registered trademarks of Splunk Inc. in the United States and other countries. All other brand names,product names,or trademarks belong to their respective owners.