claroty-risk-triage

Triages Claroty xDome alerts and vulnerabilities with blast-radius analysis and ITSM-gated write actions.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill claroty-risk-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claroty-risk-triage
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/claroty-risk-triage
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill claroty-risk-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security teams managing OT, IoT, and IoMT environments face a constant stream of Claroty xDome alerts and CVE findings that must be triaged, correlated, and dispositioned under change control. This Skill unifies alert and vulnerability triage into one workflow, computing blast radius, correlating with NVD CVE data, and enforcing ITSM gating on every write operation.

Core Features & Use Cases

  • Alert Triage & Investigation: List and filter alerts by severity, status, site, or assignee, and retrieve an alert together with every affected device in a single call.
  • Vulnerability Blast Radius: Filter CVE findings by CVSS score, list all devices affected by a specific vulnerability, and correlate with NVD for full CVSS vector decomposition.
  • ITSM-Gated Write Actions: Acknowledge alerts, apply labels, assign owners, and mark CVEs as not-relevant per device, all requiring a valid ServiceNow change request (CHG) number.
  • Use Case: During a ransomware hunt, an analyst lists open high-severity alerts at a warehouse site, labels them 'ransomware-candidate', assigns them to an investigator under CHG0013002, then pivots to the affected devices' CVE lists to assess combined risk.

Quick Start

Ask the agent to list all open high-severity Claroty alerts at a specific site and show every device each alert touches.

Frequently Asked Questions about claroty-risk-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage Claroty xDome alerts by severity?

Use the list_alerts tool with severity, status, site, or assignee filters to retrieve a severity-sorted alert table. For deeper investigation, get_alert_with_devices returns the alert plus every affected device in one call.

How do I find which devices are affected by a specific CVE in Claroty?

First call list_vulnerabilities with a cve_contains filter to get the xDome finding ID, then call get_vulnerable_devices with that ID to list all affected devices. You can correlate with the NVD for full CVSS vector details.

Does Claroty alert acknowledgment require a change request?

Yes, all write operations including acknowledge_alert, label_alerts, assign_alerts, and set_vulnerability_relevance require a CR number in CHG format validated against ServiceNow. The gate is bypassed only when NETCLAW_LAB_MODE is set to true.

Why does a Claroty write operation return applied false with a 403 error?

A 403 means the ITSM gate passed but the xDome API token lacks write scope on that resource type. Do not retry; escalate to whoever provisions xDome API tokens to grant the missing scope.

Can this skill quarantine a compromised endpoint directly?

No, quarantine actions are deliberately handed off to the ise-incident-response skill, which enforces a human decision point before any containment action. This skill only handles triage, labeling, assignment, and relevance marking.