Performing Ics Asset Discovery With Claroty
Overview
Cybersecurity skill for performing ics asset discovery with claroty. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing ics asset discovery with claroty"
"Perform comprehensive ICS/OT asset discovery using Claroty xDome platform, lever"
When gaining initial visibility into an OT environment with unknown or poorly documented assets
When preparing for an IEC 62443 risk assessment requiring a complete asset inventory
When onboarding Claroty xDome into a brownfield industrial environment
When validating existing asset inventory against actual network communications
When identifying shadow OT devices or unauthorized connections in the control network
Do not use for IT-only asset discovery (use tools like Nessus or Qualys), for active scanning of sensitive PLC networks without vendor approval, or for environments where Claroty is not the deployed platform (see implementing-ot-network-traffic-analysis-with-nozomi).
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Claroty xDome SaaS subscription or on-premises deployment
- Network TAP or SPAN port configured at OT network boundaries (Levels 1-3 of Purdue Model)
- Claroty Edge collector deployed for safe active querying of hard-to-reach network segments
- Integration credentials for CMDB tools (ServiceNow, BMC) if used
- Network architecture diagram showing VLANs, switches, and firewall zones
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for ics asset discovery operations.
- Prepare Environment — Set up tools, access, and data sources required for ics asset discovery.
- Execute Core Workflow — Use claroty to perform ics asset discovery operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- claroty — Primary tool for this skill
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Design — Define interface, identify patterns, plan implementation
- Implement — Write code following existing conventions, add tests
- Verify — Run tests, check integration, validate behavior
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-ics-asset-discovery-with-claroty3description: Use when perform comprehensive ICS/OT asset discovery using Claroty xDome platform, leveraging passive monitoring, Claroty Edge active queries, and integration ecosystem to gain full visibility into industrial control system assets including PLCs, RTUs, HMIs, and network infrastructure across Purdue Model levels. . Use when working with performing ics asset discovery with claroty.4license: Apache-2.05---67# Performing Ics Asset Discovery With Claroty89## Overview1011Cybersecurity skill for performing ics asset discovery with claroty. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing ics asset discovery with claroty"16- "Perform comprehensive ICS/OT asset discovery using Claroty xDome platform, lever"171819- When gaining initial visibility into an OT environment with unknown or poorly documented assets20- When preparing for an IEC 62443 risk assessment requiring a complete asset inventory21- When onboarding Claroty xDome into a brownfield industrial environment22- When validating existing asset inventory against actual network communications23- When identifying shadow OT devices or unauthorized connections in the control network2425**Do not use** for IT-only asset discovery (use tools like Nessus or Qualys), for active scanning of sensitive PLC networks without vendor approval, or for environments where Claroty is not the deployed platform (see implementing-ot-network-traffic-analysis-with-nozomi).262728## When NOT to Use2930- When you lack proper authorization for testing31- For production systems without change management32- When the task requires legal or compliance expertise beyond technical scope333435## Prerequisites3637- Claroty xDome SaaS subscription or on-premises deployment38- Network TAP or SPAN port configured at OT network boundaries (Levels 1-3 of Purdue Model)39- Claroty Edge collector deployed for safe active querying of hard-to-reach network segments40- Integration credentials for CMDB tools (ServiceNow, BMC) if used41- Network architecture diagram showing VLANs, switches, and firewall zones4243## Workflow4445```python46# Example: IOC detection47import re4849IOC_PATTERNS = {50 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",51 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",52 "hash_md5": r"\b[a-f0-9]{32}\b",53 "hash_sha256": r"\b[a-f0-9]{64}\b",54}5556def extract_iocs(text: str) -> dict:57 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}58```59601. **Plan Operations** — Define objectives, scope, and success criteria for ics asset discovery operations.612. **Prepare Environment** — Set up tools, access, and data sources required for ics asset discovery.623. **Execute Core Workflow** — Use claroty to perform ics asset discovery operations following established procedures.634. **Validate Results** — Verify that results meet quality standards and objectives.645. **Report Findings** — Document results, observations, and recommendations.656. **Follow Up** — Track remediation actions and verify fixes where applicable.6667## Tools6869- **claroty** — Primary tool for this skill70- **Analysis Platform** — Data processing and visualization71- **Collaboration Tools** — Team coordination and knowledge sharing727374## Process75761. **Design** — Define interface, identify patterns, plan implementation771. **Implement** — Write code following existing conventions, add tests781. **Verify** — Run tests, check integration, validate behavior7980## Verification8182- [ ] All ics asset discovery procedures executed completely and documented83- [ ] Findings validated against multiple data sources84- [ ] False positives identified and filtered85- [ ] Results documented with evidence and timestamps86- [ ] Recommendations provided with risk-based prioritization8788## Anti-Rationalization Table8990| Rationalization | Reality |91|---|---|92| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |93| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |94| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |