Elastic Security now tracks every change to a detection rule and lets you roll back to any previous version with one click. The same history log gives compliance teams a timestamped audit trail that's immutable and append-only. Case data is queryable across 3 global indices (down from 12 per space), so SOC managers can build dashboards on closure rates, assignment load, and case volume without configuring anything. A rebuilt template system gives analysts structured, investigation-specific fields at case creation, so the data feeding those dashboards is consistent from the start.

Detection rule change history with one-click rollback

Detection rules change constantly. Analysts add exceptions, engineers tune them, detection logic shifts to adapt to new threats. Until now, that history was gone the moment it happened. If a reliable rule stopped firing, there was no built-in way to see what changed, who changed it, or when, which is a debugging problem and a compliance problem in one.

In 9.5, Detection Rules History Management ships as GA. A History section on the rule details page shows a complete, chronological log of every saved rule state: who made the change, when, and the revision number. From there, you can preview any historical revision, compare it to the previous version, and restore it with a single click.

The log is immutable and append-only, and it captures changes made through the UI or the API. Compliance teams get a defensible, timestamped audit trail for ISO 27001, SOC 2, and DORA standards without any manual export or configuration. Detection engineers get a real undo button: no custom scripts, no digging through audit logs.

See it in action. Kseniia Ignatovych demonstrates the rule history log, version comparison, and one-click rollback in the short video below.

SOC case management: templates and case analytics

Cases are where investigations land, but the data inside them has rarely been reliable enough to learn from. Custom fields were limited in type and count. The same fields appeared on every case regardless of what the analyst was investigating. Building dashboards required manual index configuration that most teams never completed, so case data stayed useful in the moment and hard to aggregate at scale.

In 9.5, we rebuilt the template system to fix how data goes in and made cases queryable out of the box for everything downstream.

Investigation-specific case templates with custom fields

Admins can now define templates for specific investigation types. A "Compromised Account" case collects different information than a "Service Outage" case. Admins build templates using a YAML editor with an Actions menu helper and a live preview panel. Analysts pick the right template for their investigation, see only the fields that apply, and fill in what's actually relevant.

YAML editor for a “Compromised Account” template

“Compromised Account” template applied to a case

The previous cap of 10 templates was a ceiling for enterprise SOCs managing phishing, malware, insider threat, compliance audits, and more. That limit is gone, along with the cap on custom fields. Seven new field types are also now available, including:

• Checkboxes
• Radio buttons
• A user picker
• A date/time picker

Any field can be marked required before case closure, so regulated teams can enforce that fields like "Root Cause" or "Closing Reason" get filled in before a case closes. A Field Library lets admins define reusable fields once and apply them across templates.

Queryable case analytics on every deployment

Cases as Data, Elastic Security's case analytics feature, exposes case activity in dedicated analytics indices so teams can build dashboards tracking case volume, closure rates, time to close, and assignment load, rather than relying on the case UI alone.

We shipped Cases as Data as a tech preview in 9.2, but it required manual configuration, wasn't available on Serverless, and had a complex index structure that wasn't ready for broad adoption. In 9.5, it's GA, on by default, and available across every deployment type including Serverless.

The architecture is simpler, too:

SOC managers, IR leads, and SRE teams can build case reporting on any deployment without manual index configuration.

Pre-built Cases Analytics Data View showing a snippet of case data available for analysis

Get started with detection rule history and case analytics

Detection engineers have been working without rule change history. SOC managers have been working without case data they can report on. Both change in 9.5.

Reliable change history and queryable case data are not the loudest features in a release. They are the groundwork the next wave of SOC automation depends on.

See the documentation for Detection rule change history, Case Templates, and Case Analytics to get started. Try the new capabilities on your deployment, or start a free trial. Connect with us on Elastic's community Slack to share feedback or tell us what you are building and how we can help.