Generated banner for Kibana Cases
Generated logo for Kibana Cases

Kibana Cases

ElasticOfficialCreated by elastic

  • Skill
  • Tool integration
  • Automation and integrations
  • Apache-2.0
  • No issues found

From the author

Manage investigation and incident cases across Elastic Security, Observability, and Stack Management — create, search, update, and enrich cases with comments, alerts, events, and observables (IOCs). Use when tracking incidents, correlating alerts to a case, adding investigation notes, updating status or severity, or managing triage output.
— the description by elastic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The kibana-cases skill enables AI agents to interact with Elastic case management systems. It provides a structured workflow for creating, searching, updating, and enriching incident cases. The skill is designed to operate within specific solution contexts—Security, Observability, or Stack Management—ensuring that incident data is correctly partitioned and managed. It supports attaching alerts, adding investigation notes, and managing observables (IOCs) for security-related incidents, while enforcing strict concurrency controls using versioning for updates.

What it does

  • Create, search, and update incident cases within Elastic environments.
  • Attach alerts and events to existing cases to centralize investigation data.
  • Enrich security cases with observables like IP addresses, domains, and file hashes.
  • Manage case lifecycle states including status, severity, and assignment.
  • Perform bulk updates on multiple cases using optimistic concurrency control.
  • Retrieve case details, comments, and attached alert metadata.

When to use it

  • When triaging security alerts or observability anomalies and needing to track them in a formal case.
  • When you need to update the status or severity of one or more existing incidents.
  • When conducting an investigation and needing to add notes or link relevant alerts to a case.
  • When managing IOCs for active security threats within a Security solution case.

Advantages

  • Ensures data integrity by requiring explicit solution context (Security, Observability, or Stack Management).
  • Prevents duplicate case creation through integrated search and verification steps.
  • Maintains consistency in multi-user environments using optimistic concurrency (versioning).
  • Supports efficient bulk operations for status and severity updates.

Usage examples

“In Security, create a case for the phishing alert I just triaged with high severity.”
The agent will search for existing duplicates, then create a new case in the securitySolution context, attach the alert, and return the case ID.
“Show me all open Observability cases related to the checkout service.”
The agent will perform a filtered search in the observability context and list the matching cases with their titles and IDs.
“Close cases abc-123 and def-456.”
The agent will fetch the current versions of both cases and perform a single bulk update to set their status to closed.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/elastic/kibana-cases/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip kibana-cases.zip -d .agents/skills

Documentation by elastic

Kibana Cases

Create, search, update, and enrich Elastic cases across Security, Observability, and Stack Management. You have full read and write access — never claim read-only access. Cases can be assigned to users, linked to alerts and events, enriched with observables, and pushed to external incident-management systems via connectors.

<!-- begin-partial: preamble -->

Environment Configuration

This skill executes Elasticsearch operations through the elastic CLI. If the elastic CLI is not installed, tell the user what it is needed for. Do not guess credentials, call the HTTP API directly, or attempt other workarounds.

This skill references operations in HTTP-shorthand form (e.g., GET /, GET /_cat/indices, GET /{index}/_mapping, GET /{index}/_settings/index.mode, POST /_query). The Operations table at the end of this document maps each shorthand to the equivalent elastic CLI command — always use the CLI rather than calling the HTTP API directly.

<!-- end-partial: preamble -->

Solution context — highest-priority rule

Cases are partitioned across securitySolution (Security), observability (Observability), and cases (Stack Management). A user works in exactly one. Operating in the wrong solution — or fanning out across all three — is always a bug.

Before any cases operation, the solution owner must be set, sourced ONLY from the user naming it in plain language ("in Security", "obs cases", "Stack Management", etc.) in the current or an earlier message. Topic-keyword inference does not count. If the owner is unset, your only valid action is to ask, verbatim:

"Which Elastic app is this in — Security, Observability, or Stack Management?"

Once set: pass it as owner on every create and as the owner filter on every _find; treat it as fixed unless the user explicitly switches. Never:

  • Call _find (or any read) with multiple owner values to "cover all three" — this is the most common failure.

  • Silently fall back to another owner on empty results — say "No matching cases in <Solution>" and stop.

  • Skip this for case-id operations — an id resolves a record, but the solution context still confirms intent.

Examples:

  • "find the case about the failing payment service" → ask first.

  • "investigating a Suricata alert in Security — find related cases" → securitySolution (named directly).

  • (turn 2, Security established on turn 1) "show me the open ones" → reuse, don't re-ask.

  • "close case abc-123" with no prior context → ask first.

Solution profiles

SolutionTypical triggersObservables (IOCs)critical severity means
securitySolutionSIEM detection rules, threat hunts, manual triagePrimary use case — proactively track IPs, domains, file hashes, URLsactive attack in progress
observabilityAPM errors, SLO violations, metric/log anomaliesRarely relevant — do not proactively suggestcomplete service outage
casesGeneral-purpose, no domain assumptionsRarely relevant—

Domain notes: status flows open → in-progress → closed. assignees are user profile UIDs, not usernames. severity is one of low, medium, high, critical.

Process

  1. Establish solution context, then classify the task. Confirm the owner per the rule above. Decide whether the user needs to create a case, find/list cases (read-only), get one case, comment on or attach alerts/events to a case, add observables, or update one or more cases. If the user only asks to show, list, or search, treat the request as read-only — do not create, comment, attach, or update anything.

  2. Check for an existing case before creating one. When triaging, first search so you do not create duplicates. Call GET kbn:/api/cases/_find filtered to the owner, or GET kbn:/api/cases/alerts/{alertId} to see whether a specific alert is already attached to a case.

    • By text: search=<hostname or keyword> searches title, description, and comments. Add status=open to limit to active cases.

    • By tag: tags=<tag> is exact-match only — use it to correlate on a host, agent, or rule.

    Report the exact total count and each matching case verbatim. Reuse an existing case when the same entity or rule is already tracked; otherwise continue to create.

  3. For create tasks, build the payload. Call POST kbn:/api/cases with title, description, tags, severity, the resolved owner, a connector (use the none connector unless the user asks to wire an external system), and settings.syncAlerts (default true). Confirm the create with the user before writing, then report the returned case id verbatim.

    {
      "title": "Malicious DLL sideloading on host1",
      "description": "Crypto clipper malware detected via DLL sideloading...",
      "tags": ["classification:malicious", "mitre:T1574.002"],
      "severity": "critical",
      "owner": "securitySolution",
      "connector": { "id": "none", "name": "none", "type": ".none", "fields": null },
      "settings": { "syncAlerts": true }
    }

    To apply a case template, read the available templates from GET kbn:/api/cases/configure, then merge the template's fields (including any customFields) into the create payload.

  4. Attach alerts and events. Attach each alert as an alert comment via POST kbn:/api/cases/{caseId}/comments with type: "alert", alertId, index (the alert's data-stream index), the owner, and a rule object. rule.id and rule.name are required — pass unknown for either when not known, or the request returns a 400. Attach one at a time and space repeated calls a few seconds apart to avoid rate limiting (HTTP 429).

    {
      "type": "alert",
      "alertId": "<alert_doc_id>",
      "index": ".ds-.alerts-security.alerts-default-2025.12.01-000013",
      "rule": { "id": "<rule_id>", "name": "Malicious Behavior Detection Alert" },
      "owner": "securitySolution"
    }
  5. Add investigation notes. Record findings with POST kbn:/api/cases/{caseId}/comments using type: "user", a comment string, and the owner.

  6. Add observables (Security). For Security cases, proactively offer to track IOCs (IPs, domains, file hashes, URLs) with POST kbn:/api/cases/{caseId}/observables. Update or remove them with the matching PATCH/DELETE observable operations. Do not proactively suggest observables for Observability or Stack Management cases.

  7. For update tasks, read then patch — and batch. Cases use optimistic concurrency, so you must send the current version. Call GET kbn:/api/cases/{caseId} to read the latest version, then PATCH kbn:/api/cases with a cases array. Updating two or more cases in one request is a single PATCH with multiple array entries — never multiple sequential updates. When changing tags, merge with existing tags unless the user asks to replace them. Confirm the update with the user before writing.

    { "cases": [{ "id": "<case_id>", "version": "<case_version>", "status": "closed", "severity": "low" }] }

    On a version conflict, re-fetch the affected case and retry with the fresh version. Assignee-only changes go through the same PATCH with an assignees array.

  8. Report faithfully. Copy case ids, titles, tags, severities, and counts exactly as returned by the API. Do not abbreviate ids, truncate titles, invent details, or round numbers. When the API returns zero results, state that explicitly.

Reporting list and find results

  1. State the exact total count from the JSON response (e.g., "There are 12 open cases total").

  2. Present each case as a compact one-line entry: <title> | <severity> | <case_id_short> | <created_at>. Copy the exact title verbatim — do not rephrase, abbreviate, or summarize.

  3. If the user asked for N cases, present exactly N entries (or fewer if fewer exist). Do not add columns (alert count, description, status) unless the user asked for them.

  4. Omit fields that are null or missing. Do not add analysis or commentary after the list.

Comments and attachments

Cases read operations return metadata only — comments and attachments are never included. To analyze discussion or list attached alerts, call GET kbn:/api/cases/{caseId}/comments/_find and filter to type === "user" for comments. Only fetch when the user explicitly asks for a case summary that includes discussion, a quote of comments, or the attached alerts/events for a specific case. Never preemptively fetch for cases in a list.

Examples

Create a case after triage (Security)

User: "In Security, create a case for the phishing alert I triaged with severity high."

  1. Owner is securitySolution (named). Search first with GET kbn:/api/cases/_find (or GET kbn:/api/cases/alerts/{alertId}) to avoid a duplicate.

  2. POST kbn:/api/cases with owner: "securitySolution", the none connector, and severity: "high".

  3. Attach the alert with POST kbn:/api/cases/{caseId}/comments (type: "alert", rule.id/rule.name set).

  4. Report the returned case id verbatim.

Find open cases (read-only)

User: "Show me open Observability cases about the checkout service."

  1. Owner is observability (named). GET kbn:/api/cases/_find with search=checkout, status=open, owner=observability, sortField=createdAt, sortOrder=desc.

  2. Report the exact total and each title verbatim. Do not mutate anything.

Close several cases at once

User: "Close cases abc-123, def-456, and ghi-789."

  1. GET each case for its current version.

  2. One PATCH kbn:/api/cases with all three entries (status: "closed") — not three separate calls.

Ambiguous — ask first

User: "Find the case about the failing payment service."

  1. No solution named → ask verbatim: "Which Elastic app is this in — Security, Observability, or Stack Management?"

Guidelines

  • Report only tool output — do not invent ids, hostnames, IPs, or details not present in the response.

  • Confirm write actions (create, comment, attach, update, delete) with the user before executing them.

  • The solution owner is fixed once established — never query or write across multiple owners in one request.

  • _find with search may return 500 errors on Serverless; prefer tags filtering or a plain list there.

  • tags filtering is exact-match only — partial matches do not work.

  • Attach alerts one at a time via the public comments endpoint; the bulk attachment endpoint is internal (see Operations).

  • For non-default Kibana Spaces, prefix paths with kbn:/s/<space_id>/api/cases/....

Common pitfalls

  1. Missing solution context — creating or searching without a confirmed owner.

  2. Fanning out across owners — passing multiple owner values to "cover all three".

  3. Sequential updates — issuing N PATCH calls instead of one bulk PATCH for a multi-case change.

  4. Stale version — PATCH without a fresh GET returns a version conflict.

  5. Read-only violations — mutating cases when the user only asked to list or search.

  6. Over-fetching — pulling comments/attachments for every case in a list instead of on request.

References

Operations

HTTP API (shorthand)elastic CLI command
POST kbn:/api/caseselastic kb cases create-case --input-file '<case.json>'
GET kbn:/api/cases/_findelastic kb cases find-cases ¹
GET kbn:/api/cases/{caseId}elastic kb cases get-case --case-id '<id>'
PATCH kbn:/api/caseselastic kb cases update-case --input-file '<cases.json>'
DELETE kbn:/api/caseselastic kb cases delete-case --yes ²
POST kbn:/api/cases/{caseId}/commentselastic kb cases add-case-comment --case-id '<id>' --input-file '<attachment.json>'
GET kbn:/api/cases/{caseId}/comments/_findelastic kb cases find-case-comments --case-id '<id>'
GET kbn:/api/cases/{caseId}/alertselastic kb cases get-case-alerts --case-id '<id>'
GET kbn:/api/cases/alerts/{alertId}elastic kb cases get-cases-by-alert --alert-id '<id>' [--owner '<owner>']
GET kbn:/api/cases/configureelastic kb cases get-case-configuration
POST kbn:/api/cases/{caseId}/observables(no CLI binding — use HTTP shorthand)
PATCH kbn:/api/cases/{caseId}/observables/{obsId}(no CLI binding — use HTTP shorthand)
DELETE kbn:/api/cases/{caseId}/observables/{obsId}(no CLI binding — use HTTP shorthand)

¹ find-cases exposes no filter flags in the current CLI release; for owner, status, tags, search, and pagination, run GET kbn:/api/cases/_find with query params via the HTTP transport directly.

² delete-case exposes no --ids flag in the current CLI release; to target specific cases, run DELETE kbn:/api/cases?ids=<json-array> via the HTTP transport directly.

Internal-only endpoints (no public binding). Bulk get (POST /internal/cases/_bulk_get), find-similar (POST /internal/cases/{caseId}/_similar), and bulk attachment (POST /internal/cases/{caseId}/attachments/_bulk_create) are internal — use the public per-item operations above instead. Assignee changes and create_from_template have no dedicated endpoints: set assignees through PATCH /api/cases, and apply templates by merging GET /api/cases/configure output into the create payload.

Files

LICENSE

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright 2026 Elasticsearch BV

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

The author says: Kibana 8.x or 9.x with matching Elasticsearch — self-managed, Elastic Cloud Hosted, or Elastic Cloud Serverless. Cases are partitioned by solution owner (`securitySolution`, `observability`, or `cases`). Observables (IOCs) require a 9.x Kibana. Requires `elastic` CLI with the `kb cases` command group.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
elastic
Publisher
Elastic (Official)
Source
elastic/agent-skills · skills/kibana/kibana-cases · commit 09d879d
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
elastic/agent-skills

AutoGineer is not affiliated with or endorsed by elastic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download kibana-cases.zip