claroty-asset-inventory

Discover and classify OT, IoT, and IoMT assets via Claroty xDome with Purdue-level filtering and SoT reconciliation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OT and IoT environments often lack a reliable asset inventory, making it hard to know which devices exist at each site, how they map to Purdue Model layers, and whether the discovered inventory matches the source of truth. This Skill queries Claroty xDome to list, filter, and classify devices, and reconciles the results against Nautobot or NetBox to surface drift.

Core Features & Use Cases

  • Filtered Asset Discovery: List xDome-managed devices by site, Purdue level (0 through 4/5), device purpose (PLC, HMI, RTU, historian, medical device), or name substring with pagination controls.
  • ITSM-Gated Classification: Assign Purdue layers or set custom compliance attributes on devices, with every write validated against a ServiceNow change request before reaching xDome.
  • SoT Drift Detection: Cross-reference xDome's discovered inventory against Nautobot or NetBox records and flag IP drift, devices missing from the SoT, and devices missing from xDome.
  • Use Case: An OT security engineer needs to audit a warehouse site. They list all Purdue Level 1 devices, identify unclassified PLCs, assign Purdue layers under an approved change request, and diff the results against Nautobot to find undocumented devices.

Quick Start

Ask the agent to list all PLCs across every site in Claroty xDome and compare them against the Nautobot inventory to flag any devices missing from either side.

Frequently Asked Questions about claroty-asset-inventory

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

FAQPage Schema
How do I list OT devices by Purdue level in Claroty xDome?

Use the list_devices tool with the purdue_level parameter, optionally combined with site_id and limit. For example, filtering a site at Level 1 returns control-layer devices with names, vendors, and risk scores.

How do I find all PLCs across multiple sites?

Call list_devices with device_purpose set to PLC and a high max_items value such as 500. This returns every programmable logic controller managed by xDome regardless of site.

Can I change a device's Purdue level in Claroty xDome automatically?

Yes, via set_device_purdue_level, but the write is ITSM-gated. You must supply a ServiceNow change request matching CHG followed by digits in Implement state, unless NETCLAW_LAB_MODE is enabled.

How do I detect drift between Claroty xDome and NetBox or Nautobot?

Pull the xDome device set with list_devices for a site, then query Nautobot or NetBox for the same site's records. Diffing MAC, IP, and name fields surfaces IP drift and devices missing from either system.

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

A 403 after the ITSM gate passes means xDome rejected the request at RBAC. The API token lacks write scope on devices, so escalate to whoever provisions xDome API tokens rather than retrying.