performing-ot-vulnerability-scanning-safely
Perform vulnerability scanning in OT/ICS environments safely using passive monitoring, native protocol queries, and carefully controlled active scanning with Tenable OT Security to identify vulnerabilities without disrupting industrial processes or crashing legacy controllers.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- performing-ot-vulnerability-scanning-safely
- tags
- [ "ot-security", "ics", "vulnerability-scanning", "tenable", "nessus", "passive-scanning", "risk-management", "nist" ]
- author
- mahipal
- domain
- cybersecurity
- license
- Apache-2.0
- version
- 1.0
- nist_csf
- [ "PR.IR-01", "DE.CM-01", "ID.AM-05", "GV.OC-02" ]
- subdomain
- ot-ics-security
- description
- Perform vulnerability scanning in OT/ICS environments safely using passive monitoring, native protocol queries, and carefully controlled active scanning with Tenable OT Security to identify vulnerabilities without disrupting industrial processes or crashing legacy controllers.
- mitre_attack
- [ "T1078", "T1190", "T1059", "T1046", "T0816" ]
02 资源文件 3
- 许可证LICENSE11.0 KB
- 参考文档references/api-reference.md1.5 KB
- 脚本scripts/agent.py7.7 KB
03 SKILL.md 正文
Performing OT Vulnerability Scanning Safely
When to Use
- When conducting vulnerability assessments in OT environments with legacy controllers
- When implementing continuous vulnerability monitoring without impacting process availability
- When preparing for IEC 62443 or NERC CIP compliance audits requiring vulnerability data
- When evaluating risk-based patching priorities for OT assets
- When validating that compensating controls protect unpatched ICS devices
Do not use for aggressive active scanning of production PLCs (can crash legacy controllers), for IT vulnerability scanning using standard Nessus profiles on OT networks, or for penetration testing of live OT systems (see performing-ics-penetration-testing).
Prerequisites
- Tenable OT Security (formerly Tenable.ot/Indegy) or equivalent OT-safe scanning platform
- Passive monitoring sensor deployed on SPAN/TAP at OT network segments
- Lab-tested scanning profiles verified against each device type before production use
- Change management approval and maintenance window for any active scanning
- Vendor warranty verification to confirm scanning will not void support agreements
Workflow
Step 1: Deploy Passive Vulnerability Detection
Passive monitoring identifies vulnerabilities without sending any packets to OT devices.
#!/usr/bin/env python3
"""OT Safe Vulnerability Scanner Orchestrator.
Coordinates passive monitoring, native protocol queries, and carefully
controlled active scanning for OT vulnerability assessment without
disrupting industrial operations.
"""
import json
import csv
import sys
from datetime import datetime
from typing import Dict, List, Optional
try:
import requests
except ImportError:
print("Install requests: pip install requests")
sys.exit(1)
class OTVulnerabilityScanner:
"""Safe OT vulnerability scanning orchestrator."""
SCAN_SAFETY_LEVELS = {
"passive": {
"description": "Observe network traffic only, zero risk to devices",
"risk_level": "NONE",
"methods": ["traffic_fingerprinting", "protocol_analysis", "version_detection"],
"requires_window": False,
},
"native_query": {
"description": "Query devices using native industrial protocols",
"risk_level": "MINIMAL",
"methods": ["modbus_device_id", "s7_szl_read", "cip_identity", "bacnet_whois"],
"requires_window": True,
},
"controlled_active": {
"description": "Standard vulnerability checks with OT-safe profiles",
"risk_level": "LOW-MODERATE",
"methods": ["credentialed_scan", "banner_grab", "service_detection"],
"requires_window": True,
},
}
def __init__(self, tenable_url: str, api_key: str, verify_ssl: bool = True):
self.tenable_url = tenable_url.rstrip("/")
self.session = requests.Session()
self.session.headers.update({
"X-ApiKeys": f"accessKey={api_key}",
"Content-Type": "application/json",
})
self.session.verify = verify_ssl
self.findings = []
def check_safety_prerequisites(self, scan_level: str, target_subnet: str) -> dict:
"""Verify safety prerequisites before scanning."""
checks = {
"scan_level": scan_level,
"target": target_subnet,
"safety_level": self.SCAN_SAFETY_LEVELS[scan_level],
"checks_passed": [],
"checks_failed": [],
"approved": False,
}
prerequisites = [
{
"name": "Lab validation complete",
"description": "Scan profile tested against each device type in lab environment",
"required_for": ["native_query", "controlled_active"],
},
{
"name": "Vendor warranty verified",
"description": "Scanning will not void vendor support agreements",
"required_for": ["native_query", "controlled_active"],
},
{
"name": "Change management approved",
"description": "Change ticket approved for scanning activity",
"required_for": ["native_query", "controlled_active"],
},
{
"name": "Maintenance window confirmed",
"description": "Operations team confirms acceptable scanning window",
"required_for": ["controlled_active"],
},
{
"name": "Rollback plan documented",
"description": "Procedure to stop scan and recover if device becomes unresponsive",
"required_for": ["controlled_active"],
},
{
"name": "SIS excluded from scope",
"description": "Safety Instrumented Systems are never actively scanned",
"required_for": ["passive", "native_query", "controlled_active"],
},
]
for prereq in prerequisites:
if scan_level in prereq["required_for"]:
checks["checks_passed"].append(prereq["name"])
return checks
def run_passive_assessment(self, site_id: str):
"""Run passive vulnerability assessment using traffic analysis."""
print(f"[*] Running passive vulnerability assessment for site {site_id}")
print(f"[*] Safety Level: NONE - no packets sent to OT devices")
try:
resp = self.session.get(
f"{self.tenable_url}/api/v1/assets",
params={"site_id": site_id}
)
resp.raise_for_status()
assets = resp.json().get("assets", [])
for asset in assets:
asset_id = asset.get("id")
vuln_resp = self.session.get(
f"{self.tenable_url}/api/v1/assets/{asset_id}/vulnerabilities"
)
if vuln_resp.status_code == 200:
vulns = vuln_resp.json().get("vulnerabilities", [])
for vuln in vulns:
self.findings.append({
"asset": asset.get("name", "Unknown"),
"ip": asset.get("ip_address", ""),
"type": asset.get("type", ""),
"vendor": asset.get("vendor", ""),
"cve": vuln.get("cve_id", ""),
"severity": vuln.get("severity", ""),
"cvss": vuln.get("cvss_score", 0),
"description": vuln.get("description", ""),
"detection_method": "passive",
"remediation": vuln.get("remediation", ""),
})
print(f"[+] Passive assessment complete: {len(self.findings)} vulnerabilities found")
except requests.RequestException as e:
print(f"[!] API error: {e}")
def generate_prioritized_report(self, output_file: str):
"""Generate risk-prioritized vulnerability report for OT environment."""
self.findings.sort(key=lambda x: x.get("cvss", 0), reverse=True)
print(f"\n{'='*70}")
print("OT VULNERABILITY ASSESSMENT REPORT")
print(f"{'='*70}")
print(f"Date: {datetime.now().isoformat()}")
print(f"Total Findings: {len(self.findings)}")
severity_counts = {}
for f in self.findings:
sev = f.get("severity", "Unknown")
severity_counts[sev] = severity_counts.get(sev, 0) + 1
print(f"\nSeverity Distribution:")
for sev in ["Critical", "High", "Medium", "Low"]:
print(f" {sev}: {severity_counts.get(sev, 0)}")
# Risk-based prioritization considering OT context
print(f"\n--- RISK-PRIORITIZED FINDINGS ---")
print(f"(Prioritized by CVSS score and OT impact)")
for i, finding in enumerate(self.findings[:20], 1):
print(f"\n {i}. [{finding['severity']}] {finding['cve']}")
print(f" Asset: {finding['asset']} ({finding['ip']})")
print(f" Vendor: {finding['vendor']} | Type: {finding['type']}")
print(f" CVSS: {finding['cvss']}")
print(f" Detection: {finding['detection_method']}")
print(f" Description: {finding['description'][:100]}")
if finding.get("remediation"):
print(f" Remediation: {finding['remediation'][:100]}")
# Export to CSV
if output_file:
with open(output_file, "w", newline="") as f:
writer = csv.DictWriter(f, fieldnames=self.findings[0].keys())
writer.writeheader()
writer.writerows(self.findings)
print(f"\n[+] Report exported to {output_file}")
if __name__ == "__main__":
scanner = OTVulnerabilityScanner(
tenable_url="https://tenable-ot.plant.local",
api_key="your-api-key-here",
verify_ssl=True,
)
# Always start with passive assessment
safety_check = scanner.check_safety_prerequisites("passive", "10.10.0.0/16")
print(f"Safety prerequisites: {json.dumps(safety_check, indent=2)}")
scanner.run_passive_assessment(site_id="plant-01")
scanner.generate_prioritized_report("ot_vulnerabilities.csv")
Key Concepts
| Term | Definition |
|---|---|
| Passive Vulnerability Detection | Identifying vulnerabilities by analyzing mirrored traffic without sending any packets to OT devices |
| Native Protocol Query | Using industrial protocols (Modbus FC43, S7 SZL Read, CIP Get Attribute) to safely extract device information |
| OT-Safe Scan Profile | Vulnerability scanner configuration designed and lab-tested to avoid crashing industrial controllers |
| Compensating Control | Alternative security measure protecting an unpatched OT asset (firewall DPI, network isolation) |
| CVSS in OT Context | Standard CVSS scores adjusted for OT impact considering safety, availability, and physical consequences |
| Tenable OT Security | Purpose-built OT vulnerability management platform using passive and native protocol-based detection |
Output Format
OT VULNERABILITY ASSESSMENT REPORT
=====================================
Date: YYYY-MM-DD
Scope: [network segments]
Method: [Passive/Native Query/Controlled Active]
VULNERABILITY SUMMARY:
Critical: [count]
High: [count]
Medium: [count]
Low: [count]
TOP RISK FINDINGS:
1. [CVE] - [CVSS] - [Asset] - [Description]
UNPATACHABLE ASSETS REQUIRING COMPENSATING CONTROLS:
[Asset] - [Reason] - [Recommended Control]
PATCH PRIORITIZATION:
Immediate: [list]
Next Window: [list]
Acceptable Risk: [list with justification]
04 同仓库更多 Skills
runpodctl
Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.
runpod
Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.
runpod-usage
How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.
runpod-templates
Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.
runpod-migrate
Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.
runpod-mcp
Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.