device_advisory_check
Checks scanned OT devices against a mounted advisory library and reports which fall inside an affected range, flagging unknown or unparsed firmware rather than declaring them safe.
Instructions
[READ][risk=low] Which scanned devices fall inside a mounted advisory's stated range.
`iaiops scan` already reads vendor / model / firmware / serial and then does
nothing with them. This closes that loop — and deliberately stops short of
where a vulnerability scanner would go.
**It reports that a device falls inside an advisory's stated range. Nothing
more.** Not "vulnerable", not "exploitable", no severity score. Whether a
published issue is reachable on a particular machine depends on
configuration, network position and compensating controls that a read-only
scan cannot see — and in OT most advisories against a protocol stack are not
findings at all, because the stack is not reachable from anywhere that
matters. A report full of red text that ignores that gets switched off by the
site, and then the real one is missed too.
**No database ships with this.** A bundled CVE feed is a maintenance
commitment this repo has not made, and a stale one that looks current is
worse than none — so the library is a file the site controls, which also
makes it work air-gapped. Every entry must carry a source, and one bad entry
refuses the whole file rather than half-mounting it.
Four verdicts, and the middle two are the point: `in_affected_range`,
`version_unknown` (model matches, no firmware read — neither a hit nor a
pass), `version_unparsed` (a firmware string it will not invent an ordering
for), `not_affected`. A device no advisory mentions is **absent** from the
findings, not reported clean: "nothing known" is not "nothing there".
Args:
devices: [{ip?, vendor, model, firmware?}] — e.g. the `hosts` of a scan.
library_path: Path to the advisory file (.yaml/.yml/.json) this site
mounted, under $IAIOPS_HOME, the config directory or a directory
the operator lists in IAIOPS_AGENT_READ_DIRS (other paths are refused unread);
entries are {id, vendor, model, source, affected_below|affected_from|
affected_versions, title?}.
Returns dict: {devices_checked, advisories_mounted, devices_with_findings,
summary:{in_affected_range, version_unparsed, version_unknown,
not_affected}, findings:[{ip, vendor, model, firmware, advisory_id, title,
source, status, detail}], truncated, advisory_note, note}.
Example: device_advisory_check(devices=[{"ip":"10.0.0.5","vendor":"Siemens",
"model":"S7-1500","firmware":"2.8.1"}], library_path="~/advisories.yaml").
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"devices": "<devices>",
"library_path": "<library_path>"
},
"name": "device_advisory_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| devices | Yes | ||
| library_path | Yes |