Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.
In the Ideas Portal, “Better Audit Logs” became one of the top-voted customer requests. Through surveys and Audit Beta sessions, you told us exactly where v1 fell short.
One security lead told us:
“Identity and access events aren’t optional—they’re the core of any compliance review. Without them, our auditors just shake their heads.” – Beta feedback, May 2025
Another noted how CIM alignment was critical:
“If it’s not CIM-compatible, we spend weeks normalizing data ourselves. That time is money.” – Audit Feedback Survey
We heard you. And every one of those insights shaped what became Audit Trail v2.
Audit Trail v2 is more than an upgrade. It’s a reset.
For the first time, audit logs are structured JSON—clean, parseable, and CIM-compatible out of the box – available for both Splunk Enterprise and Splunk Cloud Platform. We’ve added around 20 new events across IAM, server settings, and knowledge objects. And we finally cut out the redundant “capability checks” that made up more than half your v1 storage volume.
One admin summed it up in the beta:
“Audit logs used to be a chore. Now, they actually tell a story we can use.” – Security Admin, Fortune 500 Retailer
Audit Trail v2 transforms audit from a burden into a benefit.
No more “logs for the sake of logs.” Now, your auditors and security teams both get what they need.
Audit Trail v2 is the foundation. All new audit events will use this format. Existing v1 logs will migrate over time, ensuring continuity while building toward the future.
On the roadmap: long-term retention, process auditing, APIs, and side-by-side change visibility.
👉 This is just the beginning. More to come.
✨ From the valley of despair to clarity—Audit Trail v2 is here. And it’s only the start of the story.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.