
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.
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.
shadowtrackr:events.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.
The app ships twelve detections, including:
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.
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.
shadowtrackr.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.
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.
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.
| stenrich on your firewall or proxy logs.Until now, an API key in ShadowTrackr could do everything your account could do. That is convenient, but it is not how you want to hand out access to a script, a SIEM or a colleague's dashboard. We added two things to fix that: API keys with a limited scope, and HMAC signatures on webhooks. Both help with the security measures that EU regulation asks of you.
When you create an API key, you now choose what it is allowed to do. A key for your reporting dashboard only needs to read. A key for a ticketing integration might only need to read findings. A key that can change settings or delete things is something very few integrations need.
Some examples of how this works in practice:
Existing keys keep working as before. You can replace them with scoped keys when it suits you. The API documentation lists the available scopes.
An alert can call a webhook, but until now the receiving side had no way to know that the call really came from ShadowTrackr. Anyone who found your endpoint URL could send it fake alerts.
You can now turn on HMAC signing for a webhook. ShadowTrackr calculates a signature over the payload with a secret that only you and ShadowTrackr know, and sends it in a header with every call. Your endpoint calculates the same signature and compares. If it does not match, you throw the request away.
This gives you two things:
The secret is stored encrypted and shown only once, like the custom header values. It works with all payload types, so it also covers JSON results, Splunk HEC and the rest. The documentation has a short verification example you can paste into your own code.
Regulation like NIS2, DORA and the GDPR does not tell you which header to use. It does expect you to show that you control who can access what, and that you protect your data in transit and know where it came from. These two options map onto that quite directly:
To be clear, no feature makes you compliant on its own. What these two do is give you controls you can point to, instead of a shared key and an unauthenticated endpoint. ShadowTrackr is hosted in Germany and run by an EU company, so your data stays inside the EU while you do this.
Every domain collects old DNS records. A campaign site that was shut down, a test server that was never removed, a hosting account that expired. The record stays, and it keeps pointing at a server that is no longer yours. That is how subdomain takeovers happen. I added a report for this to ShadowTrackr, and I extended the webhook options so you can get the alerts in the tools you already use.
The new report lists web addresses of yours that point to a server that is not set up for them. You can run it from the search bar with $subdomain_takeover_report. It also appears in the report library under the DNS category, where you can schedule it.
Each result is one of two things:
Addresses that point to another domain of your own organisation are left out, because those are not findings. Possible takeovers are listed first. The fix is usually simple: remove the DNS record, or point the name back to a server you control.
The weekly PDF report now has a "Subdomain takeover" section too. It sits in the urgent part of the report, so you will see these findings without having to go looking for them.
An alert can call a webhook instead of sending an email. Choose Call webhook as the action and pick a payload:
You can also add up to 10 custom headers to every call, for example an Authorization header to authenticate to the receiving tool. Header values are stored encrypted and shown masked after you save.
A good combination is an alert on $subdomain_takeover_report that posts to your security channel. The same applies to any other query.
One thing to know: ShadowTrackr verifies the TLS certificate of your endpoint, and there is no option to switch that off. A self-signed certificate is refused. This matters for self-managed Splunk, which ships with a self-signed certificate. The documentation has step-by-step instructions for each tool.