ShadowTrackr

Integrations

The integrations described here use external sources to pull data into ShadowTrackr, or enrich your data with data from external sources. The Splunk app works the other way round and brings your ShadowTrackr data into Splunk. You only have to put in your API key and enable it, no code required :-) If you want to extract ShadowTrackr data and use it in another application, you can do with the API.

Please note that these integrations are all optional. ShadowTrackr has extensive discovery and scan capabilities without them. We've included them here so you can have all the data you need to manage your external attack surface in one place.
Shodan and Censys scan the entire internet and pick up all lot of IoT and ICS devices.
ShadowServer

You can find the built-in integrations under Settings in the GUI.


Shodan

Shodan is a search engine that lets users search for various types of servers connected to the internet using a variety of filters. Some have also described it as a search engine of service banners, which are metadata that the server sends back to the client.

The big difference with ShadowTrackr is that Shodan scans a large part of the hosts on internet and mostly focuses on ICS and IoT. ShadowTrackr does scan IoT and ICS, but not as extensively. Our detection rules are more focused on remote login services and edge devices used in company networks.
ShadowTrackr scans all your assets and all related infrastructure (not the entire internet), and tracks your historic data. So, in short: ShadowTrackr is more suited for discovering and monitoring your entire attack surface, Shodan is a good integration to get more ICS/IoT. If you expect to find ICS/IoT, then enabling the Shodan integration is useful.

When scanning subnets for new hosts, results can differ. Not all scans are the same and it might be that some scans are blocked and others are not. The same is true for the IP addresses of the scanner nodes. If you expect this might be the case, then enabling the Shodan integration is also useful. This might result in new hosts being found and a better view of your attack surface. Once found through Shodan, ShadowTrackr will discover and process all infrastructure related to the new host as usual.

Shodan data is pulled into ShadowTrackr on the first time an asset is found and then renewed every three days. Note that if you use the ShadowTrackr API and want to include the raw Shodan data you have to set the full parameter to True. See exporting raw data for details.

Censys


Censys is an internet intelligence platform that allows users to search for hosts and services exposed on the public internet using a wide range of structured filters. It collects and indexes data from continuous internet-wide scans, including protocol handshakes and service metadata, giving users visibility into how systems are configured and exposed.

The main difference with ShadowTrackr is that Censys performs large-scale scanning across the global internet based on its own scanning methodology. ShadowTrackr, focuses on discovering and monitoring your own assets and all related infrastructure rather than scanning the entire internet. It also maintains historical visibility of your attack surface over time. In short: ShadowTrackr is better suited for continuous attack surface discovery and monitoring, while Censys is more suited for broad exposure research and detailed internet-wide service intelligence. If you need additional context about how your assets appear externally or want to identify exposures discovered by independent global scans, enabling the Censys integration can be valuable.

When scanning IP ranges or subnets for new hosts, differences in scan coverage and timing can lead to varying results. Some networks may block certain scanner sources while allowing others, and scanning frequency can also affect what is detected. In such cases, enabling the Censys integration may help uncover hosts or services that were not initially identified, improving overall visibility into your external attack surface. Once a host is identified through Censys, ShadowTrackr will automatically correlate and map all related infrastructure as part of its normal discovery process.


Shadowserver


Shadowserver is a threat intelligence organization that collects and distributes security data about malicious activity, exposed services, and vulnerabilities observed across the internet. Its remediation reports help network owners identify infected systems, misconfigurations, and other security issues affecting their infrastructure.

The main difference with ShadowTrackr is that Shadowserver gathers intelligence from large-scale external sources and shares this information through targeted reports. These reports can be used to enrich asset discovery and provide additional host data that may not be identified through regular attack surface scans. ShadowTrackr focuses on scanning and monitoring your organization’s infrastructure in depth, maintaining historical visibility and providing extensive reporting capabilities. In short: ShadowTrackr is better suited for continuous attack surface management, while Shadowserver is more suited for receiving external threat intelligence and alerts about security issues detected in the wild.

Because Shadowserver uses different collection methods and vantage points, it may detect assets or incidents that ShadowTrackr has not yet discovered. Integrating Shadowserver data can therefore improve discovery and provide useful alerts that enhance visibility into potential risks affecting your environment. Future versions of the integration may expand support for additional alert types.

When configuring the integration, it is important to understand the scope of the Shadowserver reports you receive. Some organizations — such as industry CERTs or law-enforcement agencies — may receive data covering entire sectors or jurisdictions. In such cases, enabling the “no suggestions” option in ShadowTrackr helps prevent large numbers of unrelated assets from being added as discovery suggestions.

Shadowserver data can be imported into ShadowTrackr to enrich host information and support asset discovery workflows. By correlating this external intelligence with internally discovered infrastructure, ShadowTrackr provides a more complete and actionable view of your organization’s external attack surface.

Splunk

The ShadowTrackr app for Splunk works in the other direction from the integrations above: it brings your ShadowTrackr data into Splunk, so your SOC can alert on it, enrich its own logs with it and explore it in dashboards. It is published on Splunkbase, is open source (Apache-2.0) and the code is on GitHub.

The app needs a ShadowTrackr Business or Enterprise subscription (for API access) and Splunk Enterprise or Splunk Cloud Platform with the KV Store enabled. It is tested on Splunk Enterprise 10.2 and 9.4. It only reads from ShadowTrackr and uses the API, so it can never change your assets.

What you get
Events: every event on your ShadowTrackr timeline is indexed in Splunk (sourcetype shadowtrackr:events), classified with the CIM tags alert, change and vulnerability.
Inventory: your hosts, websites, URLs, domains, subnets, certificates, DNS records, mail servers, software, CVEs, suppliers and more are synced into KV Store lookups, with the history of what appeared and disappeared.
Dashboards: Overview, Vulnerabilities & software, Certificates, Supplier dependency, Asset 360 and Search explorer.
Detections: 12 scheduled searches, plus 3 health checks, that ship disabled. You enable the ones you want and attach your own alert actions (email, ticketing, SOAR).
Enterprise Security: every detection also ships as a correlation search that creates notable events and risk events, with MITRE ATT&CK annotations, and an asset lookup of your internet-facing hosts and websites.
Search commands: | stenrich adds ShadowTrackr context to any search, and | shadowtrackr runs a ShadowTrackr query live from Splunk.
Alert webhook (optional): ShadowTrackr alerts are pushed into Splunk within seconds.

Installation


1. Install the app on your search head (Apps > Manage Apps > Browse more apps, search for ShadowTrackr, or install the package from Splunkbase). In a distributed deployment, also install it on the heavy forwarders or indexers that receive the webhook.
2. Create an event index named shadowtrackr. If you use another name, change the shadowtrackr_index search macro and pick that index on the inputs.
3. In ShadowTrackr, go to Settings > API access and create a key with the Read-only access level. An MSSP can collect all its customers with one Group read-only key, created in the group settings. The key is shown only once, so copy it straight away.
4. In the app, open Configuration > Accounts and add an account with the key. Leave the API base URL as it is. The key is stored encrypted in the Splunk credential store. If Splunk reaches the internet through a proxy, set it under Configuration > Proxy.
5. Open Inputs > Create New Input and create a ShadowTrackr Events input (default: every 15 minutes, with a 7 day backfill on the first run) and a ShadowTrackr Inventory input (default: 07:00, 10:00, 13:00 and 16:00 on weekdays).
6. Open the Overview dashboard. The Data sources panel at the bottom shows when the events input, the inventory input and the webhook last delivered data.

Two things about the API key need attention. Keys expire after one year by default, and when it expires the inputs stop with "API key expired", so note the date or choose "never". To replace a key, roll it in ShadowTrackr (the old key keeps working for a grace period) and paste the new key into the account. If you restrict the key to IP addresses, add the public IP address Splunk connects from. On Splunk Cloud these are the outbound IP addresses of your stack.

Dashboards


DashboardShows
Dashboard:
Overview
Shows:
Events, problems and warnings over time, inventory counts and trends.
Dashboard:
Vulnerabilities & software
Shows:
CVEs by severity, exploited and CISA KEV, vulnerable software and assets at risk. Open findings are shown by default, resolved ones stay listed for 7 days, marked resolved.
Dashboard:
Certificates
Shows:
Expiry, grades, issuers and weak configurations.
Dashboard:
Supplier dependency
Shows:
The suppliers behind your assets (hosting, registrars, certificate issuers, mail and SaaS), how many assets each holds, where they are headquartered and where they are controlled from. Needs supplier mapping in your ShadowTrackr plan.
Dashboard:
Asset 360
Shows:
One IP, hostname or URL from every angle: the ShadowTrackr inventory, findings, CVEs, certificates, DNS and events, next to your own firewall, proxy/WAF, authentication and IDS logs for that asset and its related IPs and hostnames. Click an asset in any other dashboard to open it here.
Dashboard:
Search explorer
Shows:
Live queries against the ShadowTrackr API, with clickable examples. Runs only when you press Submit.

Asset 360 finds your own logs through four macros that use the CIM tags, so they work with any CIM-compliant add-on. For speed, point them at your own indexes under Settings > Advanced search > Search macros: shadowtrackr_asset_network (firewall), shadowtrackr_asset_web (proxy, web server, WAF), shadowtrackr_asset_auth (authentication) and shadowtrackr_asset_ids (IDS/IPS).

Detections


All detections are disabled after installation. Enable the ones you want under Settings > Searches, reports, and alerts (filter on ShadowTrackr -) and add an alert action. Each returns CIM-style fields and is throttled, so the same finding does not fire over and over. Events older than 7 days never fire, so the first backfill does not flood your alert queue, and inventory detections treat the first sync as the baseline.
DetectionFires when
Detection:
Problem detected
Fires when:
ShadowTrackr reports a problem (level 90 and up).
Detection:
New known exploited vulnerability
Fires when:
A newly found CVE is known exploited, is on the CISA KEV list or has an NCSC NL advisory.
Detection:
Certificate expiring
Fires when:
A certificate expires within 14 days, or expired in the last 30 days and was not renewed.
Detection:
Risky service exposed
Fires when:
A risky port opens (RDP, SMB, telnet, databases and so on). The list of ports is a lookup you can replace.
Detection:
Subdomain takeover risk
Fires when:
A possible subdomain takeover, a stale DNS record, or a record pointing to a domain for sale.
Detection:
Asset blacklisted
Fires when:
One of your IPs or domains appears on a blacklist.
Detection:
Phishy domain found
Fires when:
A new or changed lookalike domain of yours.
Detection:
Leaked data found
Fires when:
Your keywords, domains or emails show up in a breach, a dump or on Pastebin.
Detection:
Webhook alert received
Fires when:
A ShadowTrackr alert pushes a result through the webhook.
Detection:
Attack on vulnerable asset
Fires when:
Your IDS/IPS/WAF sees attacks on an asset that has CVEs.
Detection:
Web traffic to phishy domain
Fires when:
A user or host visits a lookalike of your domains.
Detection:
External login on exposed remote access
Fires when:
A successful SSH, RDP, VNC, telnet or WinRM login from an internet address on an asset where ShadowTrackr sees that service exposed.

The last three combine your own logs with ShadowTrackr's inventory. The three health checks tell you when no events arrived for 24 hours, when the inputs log errors, and when an inventory sync failed or is more than 4 days old. With Splunk Enterprise Security, enable the - Rule version of a detection instead of the plain one, not both, or every finding fires twice.

Enrich your own logs


| stenrich adds ShadowTrackr context to any search. It makes no API calls: it reads the inventory lookups, so any role that can read them can use it.
index=firewall action=allowed | stenrich field=dest_ip | where st_known=1 AND st_vulnerable=1
index=proxy | stenrich field=url | where st_phishy=1

It looks up IPs, hostnames and URLs and adds fields such as st_known (does ShadowTrackr know this asset), st_in_scope, st_ports, st_services, st_software, st_cves, st_max_cvss, st_exploited, st_cisa_kev, st_web_grade, st_cert_expires, st_phishy, st_first_seen and st_last_seen. The full list is in the app documentation.

| shadowtrackr runs a query in the ShadowTrackr search language against the API and returns the rows, for example:
| shadowtrackr query="index=hosts problem=yes"
| shadowtrackr query="index=events earliest=-1d level>=80" | stats count by source

This command reads the encrypted API key, which in Splunk needs the list_storage_passwords capability. Admins have it. The app deliberately does not grant it to other roles, because that capability exposes every stored secret in Splunk. Other users can still use stenrich, the lookups and the dashboards.

Receive alerts by webhook


ShadowTrackr can push the results of an alert straight into Splunk through the HTTP Event Collector (HEC), usually within seconds instead of the 15 minute polling interval.
1. In Splunk, open Settings > Data inputs > HTTP Event Collector, enable the global setting and create a token. Leave indexer acknowledgement off, set the source type to shadowtrackr:alert and allow only the shadowtrackr index.
2. In ShadowTrackr, open an alert and add a webhook with the payload Splunk HEC event, the URL https://your-splunk:8088/services/collector/event and the custom header Authorization: Splunk [HEC token].

ShadowTrackr calls this URL from the internet, so your HEC endpoint must be reachable over HTTPS with a certificate from a public CA. Self-signed certificates are refused, and there is no option to switch verification off. On Splunk Cloud use the HEC URL of your stack. Retried deliveries repeat a result, so searches in the app deduplicate on st_result_key. See Webhooks for the details of the payload.

Troubleshooting


SymptomCheck
Symptom:
No events
Check:
Search index=_internal source=*shadowtrackr_*.log*. The inputs log every run and every API error there.
Symptom:
"Invalid API key" or "no API access"
Check:
The key is revoked, was created on another install, or your subscription has no API access. Create a new key.
Symptom:
"API key expired"
Check:
Create or roll a key in ShadowTrackr and paste it into the account under Configuration > Accounts.
Symptom:
HTTP 403 with a valid key
Check:
The key has an IP allowlist that does not include the public IP address of your Splunk, or a group key asks for an organization outside its group.
Symptom:
Connection errors
Check:
Splunk cannot reach api.shadowtrackr.com. Set the proxy under Configuration > Proxy.
Symptom:
Dashboards empty
Check:
Check that the Inventory input exists and has run once, and that the KV Store is up.
Symptom:
Webhook events do not arrive
Check:
Test the token with curl against /services/collector/event, and check that it allows the shadowtrackr index.

Questions or problems with the app? Contact support, or open an issue on GitHub.