Generated banner for Security Case Management
Generated logo for Security Case Management

Security Case Management

ElasticOfficialCreated by elastic

  • Skill
  • Tool integration
  • Security
  • Apache-2.0
  • Low risk
  • Has scripts

From the author

Create, search, update, and manage SOC cases via the Kibana Cases API. Use when tracking incidents, linking alerts to cases, adding investigation notes, or managing triage output.
— the description by elastic

AutoGineer summary

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

The security-case-management skill provides a command-line interface to interact with the Kibana Cases API, specifically for Elastic Security workflows. It enables security analysts to create, search, update, and manage incident cases without leaving their terminal. The skill supports attaching alerts to cases, adding investigation notes, and managing case metadata like severity and status, ensuring that incident response activities are synchronized with the Elastic Security solution.

What it does

  • Creates new SOC cases with custom titles, descriptions, and severity levels.
  • Searches for existing cases using tags, status, or free-text queries.
  • Attaches individual or batch alerts to specific cases for incident correlation.
  • Updates case status, severity, and tags to reflect investigation progress.
  • Adds investigation comments to existing cases.
  • Lists recent cases for review with configurable page sizes.

When to use it

  • When performing alert triage and needing to document findings in a formal case.
  • When correlating multiple alerts to a single security incident.
  • When updating the status or severity of an ongoing investigation.
  • When searching for historical cases related to a specific host or threat.

Advantages

  • Streamlines incident response by integrating case management into automated workflows.
  • Enforces structured metadata through standardized tag conventions.
  • Supports batch operations for attaching multiple alerts to a single case.
  • Provides direct access to the Kibana Cases API for programmatic incident tracking.

Usage examples

“Create a new high-severity case for the phishing alert I just triaged.”
The agent executes the create command with the provided details, returning the new case ID and confirmation.
“Find all open cases related to brute force attacks.”
The agent queries the Kibana API and lists the titles, severities, and IDs of all matching open cases.
“Add a comment to case abc-123 stating that the process tree analysis is complete.”
The agent updates the specified case with the provided investigation note.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/elastic/security-case-management/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip security-case-management.zip -d .agents/skills

Documentation by elastic

Case Management

Manage SOC cases through the Kibana Cases API. All cases are scoped to securitySolution — this skill operates exclusively within Elastic Security. Cases appear in Kibana Security and can be assigned to analysts, linked to alerts, and pushed to external incident management systems via connectors.

Prerequisites

Install dependencies before first use from the skills/security directory:

cd skills/security && npm install

Set the required environment variables (or add them to a .env file in the workspace root):

export KIBANA_URL="https://your-cluster.kb.cloud.example.com:443"
export KIBANA_API_KEY="your-kibana-api-key"

When to use

  • Creating a case after alert triage (classification, IOCs, findings)

  • Searching for existing cases to correlate related alerts

  • Adding investigation comments or attaching alerts to an existing case

  • Updating case status or severity

  • Listing recent cases for review

When NOT to use

  • Do not use this skill for Observability or Elasticsearch cases — it hardcodes owner: securitySolution

  • Do not use for cases outside the Security solution space

Execution rules

  • Start executing tools immediately — do not read SKILL.md, browse the workspace, or list files first.

  • Report tool output faithfully. Copy case IDs, titles, tags, severities, and counts exactly as returned by the API. Do not abbreviate case IDs, truncate titles, invent details, or round numbers.

  • When the API returns zero results, state that explicitly — do not guess at possible results.

  • When listing or finding cases, report the exact total count from the API response and present each case with its verbatim title, severity, and status.

Quick start

All commands run from the workspace root. All output is JSON. Call the tools directly — do not read the skill file or explore the workspace first. For attach-alert/attach-alerts, --rule-id and --rule-name are required by the Kibana API (use --rule-id unknown --rule-name unknown if unknown). Use attach-alerts for batch with automatic rate-limit retry and 2-second spacing between API calls.

Common multi-step workflows

TaskTools to call (in order)
Create a casecase_manager create (title, description, tags, severity)
Find cases for a hostcase_manager find --tags "agent_id:<id>" or find --search "<hostname>"
Attach alert to casecase_manager attach-alert (case-id, alert-id, alert-index, rule-id/name)
Add investigation notescase_manager add-comment (case-id, comment text)
List recent open casescase_manager list --status open --per-page <n>
Update casecase_manager update (case-id, status/severity/tags changes)

Finding cases for a host: Use find --search "<hostname>" to search by hostname across title, description, and comments. Alternatively use find --tags "agent_id:<agent_id>" if the agent ID is known. Always add --status open to filter to active cases only. Report the exact total count and each case title verbatim from the API response.

# Create (syncAlerts enabled by default; disable with --sync-alerts false)
node skills/security/case-management/scripts/case-manager.js create --title "Malicious DLL sideloading on host1" --description "Crypto clipper malware detected via DLL sideloading..." --tags "classification:malicious" "confidence:88" "mitre:T1574.002" --severity critical --yes

# Find, list, get
node skills/security/case-management/scripts/case-manager.js find --tags "agent_id:550888e5-357d-4bc1-a154-486eb7b4e076"
node skills/security/case-management/scripts/case-manager.js find --search "DLL sideloading" --status open
node skills/security/case-management/scripts/case-manager.js list --status open --per-page 10
node skills/security/case-management/scripts/case-manager.js get --case-id <case_id>

# Attach single alert
node skills/security/case-management/scripts/case-manager.js attach-alert --case-id <case_id> --alert-id <alert_doc_id> --alert-index .ds-.alerts-security.alerts-default-2025.12.01-000013 --rule-id <rule_uuid> --rule-name "Malware Detection Alert"

# Attach multiple alerts (batch)
node skills/security/case-management/scripts/case-manager.js attach-alerts --case-id <case_id> --alert-ids <id1> <id2> <id3> --alert-index .ds-.alerts-security.alerts-default-2026.02.16-000016 --rule-id <rule_uuid> --rule-name "Malware Detection Alert"

# Add comment, update (--tags merges with existing tags, does not replace)
node skills/security/case-management/scripts/case-manager.js add-comment --case-id <case_id> --comment "Process tree analysis shows..."
node skills/security/case-management/scripts/case-manager.js update --case-id <case_id> --status closed --severity low --yes

Write operations (create, update) prompt for confirmation by default. Pass --yes to skip the prompt (required when called by an agent).

Reporting list and find results

When reporting results from list or find:

  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 from the title field — 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 extra columns (alerts count, description, status) unless the user specifically requested them.

  4. Do not add information beyond what the API returned. If a field is null or missing, omit it.

  5. After presenting the results, stop. Do not add analysis, commentary, or observations about the cases.

Tag conventions

Use structured tags for machine-searchable metadata:

Tag patternExamplePurpose
classification:<value>classification:maliciousTriage classification (benign/unknown/malicious)
confidence:<score>confidence:85Confidence score 0-100
mitre:<technique>mitre:T1574.002MITRE ATT&CK technique IDs
agent_id:<id>agent_id:550888e5-...Elastic agent ID for correlation
rule:<name>rule:Malicious Behavior DetectionDetection rule name

Case severity mapping

ClassificationKibana severity
benign (score 0-19)low
unknown (score 20-60)medium
malicious (score 61-80)high
malicious (score 81-100)critical

Known limitations

syncAlerts is security-only

The syncAlerts setting (enabled by default) synchronizes case status with attached alert statuses. This feature is only available for Security Solution cases. Pass --sync-alerts false when creating a case if alert sync is not needed.

Rate limiting

The Kibana API enforces rate limits. When attaching multiple alerts, the attach-alerts batch command automatically handles 429 responses with retry. If using attach-alert one at a time, space calls ~10 seconds apart.

find --search on Serverless

The find --search parameter may return 500 errors on Kibana Serverless deployments. Use find --tags for filtering instead, or list to browse recent cases.

find --tags requires exact match

Tag searches are exact-match only. find --tags "agent_id:abc123" works, but partial matches do not.

Kibana Cases API reference

For detailed API endpoints, request/response formats, and examples, see references/kibana-cases-api.md.

Examples

  • "Create a case for the phishing alert I triaged with severity high"

  • "Search for open cases related to brute force attacks"

  • "Add the investigation findings as a comment to case ID abc-123"

Guidelines

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

  • Preserve identifiers from the request — use exact values the user provides in tool calls and responses.

  • Confirm actions concisely using the tool's return data.

  • Distinguish facts from inference — label conclusions beyond tool output as your assessment.

  • When presenting case lists or search results, copy the exact title from each case. Do not paraphrase, abbreviate, or summarize titles. Include the total count from the API total field.

  • Start executing tools immediately. Do not read SKILL.md, browse directories, or list files before acting.

Production use

  • Write operations (create, update) prompt for confirmation. Pass --yes or -y to skip when called by an agent.

  • Verify KIBANA_URL and KIBANA_API_KEY point to the intended cluster before running any command.

  • Cases are scoped to securitySolution — this skill does not affect Observability or other Kibana case owners.

Environment variables

VariableRequiredDescription
KIBANA_URLYesKibana base URL (e.g., https://my-kibana.kb.cloud.example.com)
KIBANA_API_KEYYesKibana API key for authentication

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.

Needs: Needs an API key, Needs Node.js

The author says: Requires Node.js 22+, network access to Kibana. Environment variables: KIBANA_URL, plus KIBANA_API_KEY or KIBANA_USERNAME/KIBANA_PASSWORD.

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

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/security/case-management · 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 or Elastic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download security-case-management.zip