ShadowTrackr

RSS feed

ShadowTrackr app for Splunk

16 November 2026

Until now, ShadowTrackr data lived in ShadowTrackr. If your SOC lives in Splunk, that meant a second tab, and a lot of copy-pasting an IP address from one to the other. With the new Splunk app access to ShadowTrackr data has drastically improved.

What it does

Most of our integrations pull data in. This one goes the other way: it sends your external attack surface into Splunk. Your SOC can then alert on it, use it to enrich the logs it already has, and explore it in dashboards. It is read-only, so it can't change anything in your ShadowTrackr account. The app is open source (Apache-2.0) and the code is on GitHub.

  • Events. Everything on your timeline (new open ports, vulnerabilities, certificate problems, blacklistings, leaked data, phishy domains) is indexed as CIM-mapped events with the sourcetype shadowtrackr:events.
  • Inventory. Hosts, websites, domains, subnets, certificates, DNS records, mail servers, software, CVEs, suppliers and more are synced into KV Store lookups, including what appeared or disappeared.
  • Dashboards. Six of them, see below.
  • Detections. Twelve scheduled searches and three health checks.
  • Enterprise Security. Every detection also exists as a correlation search that creates notable and risk events with MITRE ATT&CK annotations.
  • Alert webhook (optional). Push ShadowTrackr alerts into Splunk within seconds instead of waiting for the next sync.

The dashboards

  • Overview: events, problems and warnings over time, plus inventory counts and trends.
  • Vulnerabilities & software: CVEs by severity, known exploited and CISA KEV items, vulnerable software and the assets at risk.
  • Certificates: expiry, grades, issuers and weak configurations.
  • Supplier dependency: which suppliers hold your assets, where they are headquartered and who controls them. Handy for NIS2 and digital sovereignty questions. This needs supplier mapping in your plan.
  • Asset 360: one asset from every angle, combined with your own firewall, proxy/WAF, authentication and IDS logs.
  • Search explorer: live API queries that only run when you press Submit.

Your logs, with context

A firewall log tells you that something connected to 203.0.113.10. It doesn't tell you that this is your forgotten staging server, with an exposed admin panel and a known exploited CVE. The app adds a search command that does:

index=firewall action=allowed
| stenrich field=dest_ip
| where st_known=1 AND st_exploited=1

stenrich adds fields such as st_known, st_ports, st_cves, st_max_cvss, st_exploited, st_cisa_kev and st_phishy. It only reads the local lookups and makes no API calls, so it's fast and doesn't eat into your rate limits. If you do want live data, | shadowtrackr query="..." runs ShadowTrackr queries directly from the search bar.

Asset 360 uses the same idea. Point four macros at your own indexes and you can go from an asset to the traffic, logins and IDS hits around it.

Detections

The app ships twelve detections, including:

  • a known exploited vulnerability appears on your attack surface
  • a risky service is exposed
  • a certificate is about to expire
  • there is a subdomain takeover risk
  • an attack hits an asset with a known vulnerability
  • someone browses to a phishy lookalike of your domain
  • a successful external login on an exposed remote access service

The last three combine ShadowTrackr data with your own logs, which is something we can't do on our side.

All detections are disabled by default. I'd rather you switch on the ones you want than wake up to a hundred notables. They are throttled, events older than seven days never fire, and the first inventory sync is treated as a baseline so you don't get an alert for everything you already own. If you use Enterprise Security, enable the "- Rule" version of a detection only, not both.

Setting it up

You need a Business or Enterprise plan (API access), Splunk Enterprise or Splunk Cloud with KV Store enabled, and a read-only API key. We tested on Splunk Enterprise 9.4 and 10.2. MSSPs can use a group read-only key.

  1. Install the app from Splunkbase on your search head.
  2. Create an event index called shadowtrackr.
  3. In ShadowTrackr, create a Read-only key under Settings > API access. It's shown only once.
  4. In the app, add the key under Configuration > Accounts.
  5. Create two inputs: ShadowTrackr Events (every 15 minutes, with a 7-day first backfill) and ShadowTrackr Inventory (four times a day on weekdays).
  6. Check the Data sources panel on the Overview dashboard to see that data is arriving.

Two things that will otherwise bite you: API keys expire after a year by default, and the inputs then quietly stop. (Rolling a key leaves the old one working for a grace period, so you can swap without a gap.) And if your key has an IP restriction, allow your Splunk server's public IP. On Splunk Cloud that's your stack's outbound IPs. The app also has health checks for exactly this: no events for 24 hours, input errors, and failed or stale inventory syncs.

Webhook for real-time alerts

The 15-minute poll is fine for most things, but if you want alerts in Splunk within seconds, add a webhook to an alert in ShadowTrackr using the "Splunk HEC event" payload. In Splunk you enable HEC and create a token for the shadowtrackr index. Your HEC endpoint must be reachable over HTTPS with a certificate from a public CA. Self-signed certificates are refused, and that's not going to change. Retries can occasionally deliver a result twice, so deduplicate on st_result_key. The docs have the full steps.

Security

The API key is stored encrypted in Splunk's credential store, the key is read-only, and the app passes Splunk AppInspect, including the Splunk Cloud checks. Proxies are supported if Splunk can't reach api.shadowtrackr.com directly. And because the source is public, you can read exactly what it does before you install it.

What to do next

  1. Get the app from Splunkbase and follow the setup guide.
  2. Look at the Vulnerabilities & software dashboard first. It's usually the most eye-opening.
  3. Enable one or two detections, watch them for a week, then add more.
  4. Try | stenrich on your firewall or proxy logs.
Older posts >