Changelog
Every tagged version of the Whisper add-on for Splunk, dated from the release tags themselves, with what shipped in the one version you can install.
Changelog Documentation
Release history for the Whisper Security Add-on for Splunk (TA-whisper-graph). Every version number and every date below comes from the add-on repository's release tags. Where the package's own CHANGELOG.md and the tag list disagree, the tag list wins: a tag is a thing you can download and a changelog entry is not.
| This page describes | Whisper Security Add-on for Splunk (TA-whisper-graph) — every tagged version, published or not |
| Published | 1.0.0, and nothing else. Splunkbase app 8695, release date 29 April 2026; the listing showed no other version when it was read on 2026-08-10 |
| Verified on | Splunk Enterprise 10.2, and only 10.2 — CI job test-integration, container image splunk/splunk:10.2. Unit tests run on Python 3.11 and 3.13 |
| Declared support | The Splunkbase listing declares Splunk Enterprise and Splunk Cloud at platform versions 10.2, 10.3, 10.4 and 10.5, and CIM 8.x / 6.x. The shipped app.manifest declares no platformRequirements block at all, and declares the Network Resolution and Threat Intelligence data models at >=4.0.0. The GA release notes add Splunk Enterprise Security 7.x, which nothing in the package states |
| Untested | Splunk 10.3, 10.4 and 10.5 — declared on the listing, exercised by no CI job · Splunk Cloud on either management plane · every Enterprise Security version, the 7.x of the release notes included · every pre-1.0 tag, none of which was ever published |
| Last checked | 2026-08-10 |
1.0.0 — 2026-04-29
The first published release, and still the only one. Three independent sources give the same date: app.manifest carries releaseDate: 2026-04-29, the v1.0.0 tag was published that day, and Splunkbase says 29 April 2026.
What shipped
- Search commands.
whisperlookupstreams enrichment for hostnames, IPs and ASNs with a KV Store-backed cache;whisperqueryruns parameterised read-only Cypher straight from SPL;whisperschemadiscovers node labels, relationship types and properties;whisperflushandwhisperevictmanage the local cache. See Search commands. - Modular inputs. A threat-intelligence collector, a DNS baseline collector for change detection, and a watchlist collector. See Modular inputs.
- KV Store collections.
whisper_enrichment_cache,whisper_precomputed_enrichment,whisper_ip_intel,whisper_domain_intel,whisper_watchlistandwhisper_dns_baseline. See Lookups. - Enterprise Security. CIM compliance for the Network Traffic, DNS and Threat Intelligence data models via field aliases, event types and tags; the threat-intelligence framework fed from the IP and domain collections; an adaptive response action for correlation searches and notable events. See Enterprise Security Integration.
- Dashboards. Investigation, Attack Surface Timeline, Compliance Summary, SPF Compliance and Mail Config. See Dashboards.
- Saved searches. Scheduled cache eviction, population of the threat-intelligence collections, and worked examples that enrich DNS domains, destination IPs and proxy hostnames. See Saved searches.
- Setup and operations. A UCC-based configuration UI that writes credentials to
storage/passwords, structuredkey=valuelogging throughwhisper_logging, a[diag]stanza driven bywhisper_diag.pyfor support bundles, and a least-privilegewhisper_userrole inauthorize.conf.
What the sources disagree about
Five places where the repository, the tag list and the Splunkbase listing say different things. None of them is settled silently.
The package id changed after the version bump. The v1.0.0 release notes call the package TA-whisper-security. The commit that renamed it to TA-whisper-graph landed between the version bump and the tag, so the tagged artifact, its app.manifest, its app.conf [package] stanza and the published .spl all say TA-whisper-graph. Splunk keys an installed app by that id, so that is the folder name you will have and the name to use in | rest queries.
Splunkbase and the manifest name the app differently. The listing is titled Whisper Security Graph App for Splunk; the shipped manifest's info.title is Whisper Security Add-on for Splunk. The manifest title is what Splunk Web shows once the app is installed.
Splunkbase declares a platform range the package does not. The listing names Splunk 10.2 through 10.5. The manifest declares no floor at all — three earlier attempts to state one were rejected by Splunkbase's SLIM validator, which checks the declared floor against a bundled release list that stops well below 10.x. The real floor is carried instead by python.required = 3.13 in every extension point, which makes Splunk silently skip those extension points on an older release rather than fail the install.
One date differs by a day. The package changelog dates 0.17.0 to 2026-04-03; its tag was published 2026-04-02 UTC, which is 3 April in the release engineer's timezone. Every date on this page is the tag's publish date in UTC, so this page says 2026-04-02.
Two releases the package changelog does not record
v0.22.0 and v0.23.0 were tagged, had releases cut with full notes, and never got an entry in CHANGELOG.md — in both cases a version bump was reverted or rewound afterwards and the pending entries were lost with it. Their content is not recoverable from the package; it is recoverable from the release list, so it is published here.
0.22.0 — 2026-04-13. The app surface was cut back to enrichment, investigation and attack surface, and the Health input, the Multi-Tenant Attack Surface module and the DNSSEC module were removed. It shipped alongside a Whisper Security SOAR Connector at the same version. That connector was removed one release later and is not part of any published version.
0.23.0 — 2026-04-19. The release that made Splunk Cloud Victoria submission possible. default/indexes.conf was dropped from the package, requests and its transitive dependencies were vendored under package/bin/lib/, log output was namespaced under the add-on's own directory beneath $SPLUNK_HOME/var/log/splunk/, aarch64 wheels were bundled for grpcio, and .spl file permissions were normalised. AppInspect went to zero errors and zero failures across all five tag sets. Python 3.9 support was dropped, moving the floor to 3.11. The Investigation dashboard's panels were repaired so that shared-nameserver, WHOIS-pivot, ASN/BGP/prefix and directed web-link panels each returned what their titles claimed, and a TA Health supportability dashboard was added — the same dashboard removed again in 0.23.1.
Before 1.0.0
Every version below was tagged and had a release cut for it. None reached Splunkbase: the listing shows 1.0.0 and nothing else. There is no 0.1.0 tag and no release candidate; the history starts at 0.2.0.
Their release notes reference issue numbers in a repository that is not public, so the issue numbers are dropped here. The version, the date and what changed are not. If you are running one of these, 1.0.0 is the only version the rest of this documentation describes.
The pre-release tags
| Version | Tag published | What changed |
|---|---|---|
| 0.23.2 | 2026-04-29 | Logo image sizes corrected. The developer guide was made private and the in-repo release notes were dropped. |
| 0.23.1 | 2026-04-20 | Docs made private, the monitoring dashboard removed, CIM mappings audited. |
| 0.23.0 | 2026-04-19 | Absent from the package changelog. Splunk Cloud Victoria unblockers, Python 3.9 dropped, Investigation dashboard panels repaired, TA Health dashboard added. |
| 0.22.1 | 2026-04-14 | The SOAR app and every file related to it removed. Investigation panel rendering repaired on Splunk 10.0.5 Dashboard Studio v2; dashboard tokens and whisper.history columns fixed. |
| 0.22.0 | 2026-04-13 | Absent from the package changelog. App surface simplified; Health input, Multi-Tenant Attack Surface and DNSSEC modules removed. |
| 0.21.1 | 2026-04-08 | The watchlist input emits whisper:enrichment events; the dashboard queries that read them fixed. |
| 0.21.0 | 2026-04-08 | App structure aligned with Splunk's app anatomy spec and HTTPS-only enforced. A first-run setup wizard was added and reverted inside the same release. |
| 0.20.0 | 2026-04-07 | Event-based inputs, SSL enforcement, Cloud vetting preparation. |
| 0.19.2 | 2026-04-06 | Dashboard UX, enrichment pipeline, credential helper and documentation fixes. |
| 0.19.1 | 2026-04-06 | Setup-experience fixes; threat_level derived from threat_score; the risk trend chart rebuilt on bin+stats after timechart proved unreliable. |
| 0.19.0 | 2026-04-04 | MVP release: dashboard fixes, navigation, icons and bulletin messages, plus AppInspect, input and Splunkbase-readiness fixes across UI, config, logging and KV Store. |
| 0.18.0 | 2026-04-04 | All dashboards migrated to Dashboard Studio; RBA feed integration gained first-class risk scores; the connectivity test switched to CALL whisper.quota() and api_key became optional. |
| 0.17.0 | 2026-04-02 | Fifteen out-of-the-box detection searches; Splunk 10.x and UCC 6.x modernisation; searchbnf.conf for the search assistant; .conf.spec files; expanded whisperschema introspection. |
| 0.16.0 | 2026-03-28 | BGP prefix conflict detection; threat category booleans and ASN threat reputation exposed; expanded stats structure; the first real Splunk integration tests. |
| 0.15.2 | 2026-03-03 | The last outstanding AppInspect failure and its warnings resolved. |
| 0.15.1 | 2026-03-03 | Audit findings for the Splunkbase submission resolved. |
| 0.15.0 | 2026-03-03 | Configurable query depth added, and its fallback removed again before the release closed. |
| 0.14.0 | 2026-03-02 | Packaging, versioning, CIM and test audit findings resolved; official Whisper icons; credential lookup and restmap conflicts corrected for UCC. |
| 0.13.3 | 2026-03-02 | Missing input types exposed, the co-hosting search renamed, a connectivity test added. |
| 0.13.2 | 2026-03-02 | Splunk SDK wrappers for the search commands; branding assets for the docs build. |
| 0.13.1 | 2026-03-02 | User documentation added. |
| 0.13.0 | 2026-03-02 | AppInspect compliance validation wired into the build. |
| 0.12.0 | 2026-03-02 | Compliance dashboards. |
| 0.11.0 | 2026-03-02 | Attack surface monitoring. |
| 0.10.0 | 2026-03-02 | A SOAR connector with eight playbook actions. |
| 0.9.0 | 2026-03-02 | Correlation searches for infrastructure threat detection. |
| 0.8.0 | 2026-03-02 | Risk-based alerting with MITRE ATT&CK annotations. |
| 0.7.0 | 2026-03-02 | Enterprise Security threat intelligence and adaptive response. |
| 0.6.0 | 2026-03-02 | KV Store enrichment cache, pre-computed watchlist, automatic lookups. |
| 0.5.0 | 2026-03-01 | Ad-hoc Cypher query command with schema introspection. |
| 0.4.0 | 2026-03-01 | Real-time event enrichment. |
| 0.3.0 | 2026-03-01 | The API client foundation. |
| 0.2.0 | 2026-03-01 | CI pipeline with coverage, integration tests and dependency checks. |
Where these facts come from
- The add-on repository's
CHANGELOG.md— what changed in each version. It is authoritative for content and, as shown above, incomplete for versions. gh release list --repo whisper-sec/whisper-splunk— which tags exist and when each was published. This is the authority for version numbers and dates on this page, including the two releases the changelog omits.- The Splunkbase listing for app 8695 — what is actually published, and the compatibility the listing declares.
All three were read on 2026-08-10. Nothing on this page is carried over from prose elsewhere in this documentation.
Reporting a problem with a release
Give us the installed version and your Splunk version. The first comes from:
| rest /services/apps/local/TA-whisper-graph | table label version
Troubleshooting covers the failures that turn out not to be version-related.