Security Alert Triage

ElasticOfficialCreated by elastic

Skill
Workflow
Security
Apache-2.0
No issues found

From the author

Prioritize and rank the Elastic Security alert queue by weighted risk — base risk score, MITRE tactic boost, entity risk, and asset criticality — then cluster alerts into entity groups. Use when an analyst asks what to focus on, which alerts are most urgent, or wants a ranked starting point across the queue before deeper investigation begins.

— the description by elastic

AutoGineer summary

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

This skill provides a structured approach to triaging the Elastic Security alert queue. It calculates a weighted risk score for alerts based on base risk, MITRE tactics, workflow status, entity risk, and asset criticality. By clustering alerts into entity groups, it helps security analysts identify the most urgent threats to focus on at the start of their shift or during active monitoring.

What it does

Calculates weighted risk scores for security alerts.
Clusters individual alerts into entity-based groups.
Applies boosts for MITRE tactics, entity risk, and asset criticality.
Adjusts scores based on alert workflow status (e.g., acknowledged or in a case).
Provides a ranked list of the top 10 entity groups for immediate attention.
Returns the top alert ID for each group to facilitate further investigation.

When to use it

When an analyst needs to know which alerts are most urgent.
When starting a shift and requiring a prioritized starting point.
When prioritizing a specific set of alert IDs.
When filtering the queue by a specific time window.

Advantages

Reduces noise by clustering related alerts into entity groups.
Provides a clear, data-driven rationale for alert prioritization.
Integrates contextual data like asset criticality and entity risk.
Maintains a read-only stance to prevent accidental state changes.
Offers a consistent scoring model across the security queue.

Usage examples

“What should I focus on right now?”: The agent analyzes the last 24 hours of open alerts, clusters them by entity, applies risk boosts, and returns a ranked list of the top 10 groups with their respective scores and top alert IDs.
“Prioritize these alerts: [alert_id_1, alert_id_2]”: The agent fetches the specific alerts provided, calculates their weighted risk scores, and presents them in a ranked order, ignoring standard time-window filters.
“Prioritize the queue. Include acknowledged alerts.”: The agent performs the standard triage process but expands the scope to include both open and acknowledged alerts in the final ranking.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/elastic/security-alert-triage/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip security-alert-triage.zip -d .agents/skills

Documentation by elastic

Alert Triage

Prioritize the Elastic Security alert queue by weighted risk and return ranked entity groups — a starting point before investigation begins, not an investigation itself.

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.

When to use this skill

Use this skill when:

An analyst asks "what should I focus on right now?" or "which alerts are most urgent?"
An analyst wants to prioritize the queue for a specific time window (for example, "last 8 hours")
An analyst provides a set of alert IDs and asks "which of these are most important?"
An analyst is starting a shift and needs a ranked starting point before investigation begins

Do not use this skill to investigate a single known alert — use the security-alert-analysis skill for that. This skill does not acknowledge alerts, create cases, or gather per-alert context. Those actions belong in the investigation phase.

Scoring model

The score for each alert is computed as:

alert_score = base_risk_score + mitre_boost + status_modifier
group_score = MAX(alert_score across group) + entity_risk_boost + asset_criticality_boost

The weights, mirroring the Kibana Agent Builder alert-triage skill, are:

Signal	Level	Boost
MITRE tactic	Exfiltration, Impact, Command and Control, Lateral Movement	+30
MITRE tactic	Credential Access, Privilege Escalation, Defense Evasion	+20
MITRE tactic	Persistence, Execution, Initial Access	+10
Workflow status	Alert is `acknowledged`	−5
Workflow status	Alert already attached to a case (`kibana.alert.case_ids` is non-empty)	−5
Entity Analytics risk	`Critical`	+25
Entity Analytics risk	`High`	+15
Entity Analytics risk	`Moderate`	+5
Asset criticality	`extreme_impact`	+20
Asset criticality	`high_impact`	+12
Asset criticality	`medium_impact`	+6

Status modifiers are additive: an acknowledged alert already in a case receives −10 total. Entity Analytics enrichment is best-effort; when the Risk Engine or asset criticality index is absent, both boosts are 0 and scoring continues normally.

Process

Step 1 — Establish scope

Decide:

Time window: default 24 hours, range 1–168 hours.
Workflow filter: "open" (default) or "open+acknowledged" to include acknowledged alerts.
Specific alert IDs: when the user supplies alert IDs, score exactly those and skip the time-window and workflow-status filters so a selected alert is never silently dropped regardless of age or status.

Data needed: time window or alert IDs; workflow scope.

Step 2 — Fetch and score the queue

Run one POST /_query with ES|QL. Elasticsearch computes every score field; no arithmetic is needed after the query returns.

Queue path (no explicit IDs):

FROM .alerts-security.alerts-* METADATA _id, _index
| WHERE kibana.alert.workflow_status == "open"
    AND @timestamp >= NOW() - 24 hours
    AND kibana.alert.building_block_type IS NULL
| EVAL tactics = COALESCE(MV_CONCAT(kibana.alert.rule.threat.tactic.name, "|"), "")
| EVAL mitre_boost = CASE(
    tactics LIKE "*Exfiltration*" OR tactics LIKE "*Impact*"
        OR tactics LIKE "*Command and Control*" OR tactics LIKE "*Lateral Movement*", 30,
    tactics LIKE "*Credential Access*" OR tactics LIKE "*Privilege Escalation*"
        OR tactics LIKE "*Defense Evasion*", 20,
    tactics LIKE "*Persistence*" OR tactics LIKE "*Execution*"
        OR tactics LIKE "*Initial Access*", 10,
    0)
| EVAL status_modifier = CASE(kibana.alert.workflow_status == "acknowledged", -5, 0)
                       + CASE(kibana.alert.case_ids IS NULL, 0, -5)
| EVAL alert_score = COALESCE(kibana.alert.risk_score, 0) + mitre_boost + status_modifier
| EVAL entity = CASE(
    host.name IS NOT NULL, CONCAT("host:", MV_FIRST(host.name)),
    user.name IS NOT NULL, CONCAT("user:", MV_FIRST(user.name)),
    CONCAT("ungrouped:", _id))
| KEEP _id, _index, @timestamp, entity, host.name, user.name, kibana.alert.rule.name,
       kibana.alert.severity, kibana.alert.workflow_status, kibana.alert.risk_score,
       mitre_boost, status_modifier, alert_score
| SORT alert_score DESC, @timestamp DESC
| LIMIT 100

For the explicit-IDs path, replace the WHERE clause with WHERE _id IN ("<id1>", "<id2>", ...) and keep all other stages, but raise LIMIT to the number of IDs (maximum 500) so a selected alert is never truncated. This path also drops the building-block exclusion on purpose: an alert the analyst selects explicitly is always scored, even if it is a building block. Kibana keeps that filter on both paths.

For "open+acknowledged" scope, change kibana.alert.workflow_status == "open" to kibana.alert.workflow_status IN ("open", "acknowledged").

Query design notes:

METADATA _id is required. The top alert _id per group is mandatory output — analysts use it to hand off to investigation or file a case directly.
kibana.alert.building_block_type IS NULL excludes building-block alerts (sub-components of parent alerts) the same way the Kibana skill does with must_not exists.
MV_FIRST on host.name / user.name gives a stable group key when a field has multiple values.
CASE tiers are ordered 30 → 20 → 10, so the first match wins. This reproduces Kibana's per-tactic maximum without an elementwise operation.
kibana.alert.rule.threat.tactic.name is a flat keyword field in the alerts mapping. MV_CONCAT collapses any multi-value results into one string that LIKE can match across all values.

Data needed: scored alert rows with entity key, top alert _id, and score breakdown.

Step 3 — Cluster into entity groups

Rows arrive sorted by alert_score descending. For each distinct entity value, the first row is the group's top alert and the row count is alert_count. Group by entity value.

Kibana uses a transitive union-find algorithm, so an alert that mentions both host A and user B merges both into one group. This skill keys on the primary entity (host first, then user) to match Kibana's primary-entity selection while keeping the ES|QL approach simple. Groups may differ from Kibana's on alerts that bridge a host and a user; document this if analysts report discrepancies.

Kibana also applies entity risk and asset criticality boosts to every group before it takes the top 10. This skill selects the top 10 by base score and then enriches only those, so a group ranked 11th or lower on base score can't surface through enrichment boosts. Document this if analysts report a missing high-criticality group.

Return at most 10 ranked groups — the long tail is not useful at the prioritization stage.

Data needed: per-entity group with alert_count, top alert _id, top rule name, severity, and alert_score breakdown (base + MITRE boost + status modifier).

Step 4 — Enrich the top groups (best-effort)

Before querying Entity Analytics, preflight each index with GET /_resolve/index/{pattern}. If either index is absent or returns no results, skip the corresponding boost (set to 0) and continue.

When the Risk Engine is available, look up the primary entity of each of the top 10 groups:

FROM risk-score.risk-score-latest-*
| WHERE host.name IN ("<host1>", "<host2>") OR user.name IN ("<user1>", "<user2>")
| KEEP host.name, host.risk.calculated_level, host.risk.calculated_score_norm,
       user.name, user.risk.calculated_level, user.risk.calculated_score_norm
| LIMIT 50

When asset criticality is available:

FROM .asset-criticality.asset-criticality-*
| WHERE (id_field == "host.name" AND id_value IN ("<host1>", "<host2>"))
     OR (id_field == "user.name" AND id_value IN ("<user1>", "<user2>"))
| KEEP id_field, id_value, criticality_level
| LIMIT 50

Add the entity risk boost and asset criticality boost to each group's score using the weight table above. Re-sort the ten groups by updated group_score.

When an entity enrichment re-ranks a group above a higher base-score peer, explain why: cite the entity risk level and asset criticality boost explicitly.

Data needed: entity risk level and asset criticality for the primary entity of each top group.

Step 5 — Rank and report

Sort the ten groups by group_score descending. Summarize the top 2–3 groups in detail; list the remaining groups briefly.

For each top group, report:

The entity or context (for example, "4 alerts on host WIN-SRV01")
The group score and what drove it (base risk + MITRE boost + entity risk + asset criticality)
The primary entity's risk level and asset criticality when present (copy values verbatim, for example Critical, extreme_impact)
Whether any alerts are acknowledged or already in a case (with the score modifier noted)
The top alert rule names in the group
The top alert _id verbatim — this is mandatory, not optional

End with a brief summary of the total alerts assessed and the number of groups identified.

Recommend the security-alert-analysis skill by name as the next step for any group the analyst wants to investigate further.

Guidelines

This skill is read-only. Do not acknowledge alerts, create cases, or run investigation queries. All writes belong in security-alert-analysis.
Do not deep-investigate. Prioritization is the output; investigation is the next step.
Copy identifiers verbatim. entityRiskLevel, assetCriticality, entityName, and alert _ids must be copied exactly from tool output. Do not paraphrase level names or abbreviate IDs.
Explain re-rankings. When entity enrichment lifts a group above a peer with a higher base score, explain why — cite the specific boost components.
Acknowledged alerts are deprioritized, not hidden. Flag the −5 modifier and surface the group.
Building-block alerts are excluded automatically by the kibana.alert.building_block_type IS NULL filter.
If the queue is empty, tell the analyst no open alerts match the criteria and suggest widening the time window or changing the workflow scope.

Examples

Query: "What should I focus on right now?"

Scope: { timeWindowHours: 24, workflowStatus: "open" }. Run the queue path, cluster, enrich, and return the top 10 groups.

Query: "Prioritize alerts from the last 8 hours"

Scope: { timeWindowHours: 8, workflowStatus: "open" }. Adjust the @timestamp filter to >= NOW() - 8 hours.

Query: "Which of these alerts should I look at first?" (with alert IDs)

Scope: { alertIds: ["<id1>", "<id2>", ...] }. Use the explicit-IDs path so a selected alert that is acknowledged or old is never silently dropped.

Query: "Prioritize the queue. Include acknowledged alerts."

Scope: { timeWindowHours: 24, workflowStatus: "open+acknowledged" }. Adjust the workflow filter in the ES|QL WHERE clause.

Response format

Present results as ranked groups. The top alert _id is required in every group — analysts use it to hand off to investigation directly.

**Group 1 — [entity or context]** (score: N)
- Alerts: N alerts | Top rule: [rule name] | Severity: critical/high
- Score drivers: base risk [N] + MITRE tactic boost [+N, tactic name] + entity risk [+N, level] + asset criticality [+N, level]
- Entity signals: risk level [Critical/High/…], asset criticality [extreme_impact/…] (omit if unavailable)
- Status: [N acknowledged (−5 each), N in a case (−5 each)] (omit if none)
- **Top alert ID: [exact _id from the query result]**
- Recommended next step: investigate with security-alert-analysis

**Group 2 — [entity or context]** (score: N)
…

End with: "Total alerts assessed: N across M groups."

References

Operations

HTTP API (shorthand)	`elastic` CLI command
`POST /_query`	`elastic es esql query --format tsv --query '<esql>'`
`GET /_resolve/index/{pattern}`	`elastic es indices resolve-index --name '<pattern>'`

This skill is read-only. Acknowledgement and case management operations are deliberately not bound here — use the security-alert-analysis skill for those operations.

Files

ATTRIBUTION.mdAdded by AutoGineer958 B
LICENSELicence file added by AutoGineer11.1 KiB
SKILL.md14.6 KiB

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. Read-only: no alerts are acknowledged, updated, or moved during this skill. Entity Analytics enrichment is optional and degrades cleanly when the Risk Engine or asset criticality data is unavailable. Requires the `elastic` CLI with `es` support.

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/security/alert-triage · commit 09d879d

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-08

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 security-alert-triage.zip