Monitoring
The API exposes the operational state of every device and site, so fleet health can be delivered to the systems your teams already operate, on a schedule you define, and combined with data held outside SecuriThings.
Scenarios
- NOC dashboards. Forward device and site state into the dashboards and monitoring stack your NOC already operates.
- Custom alerting. Evaluate conditions such as offline for longer than a set period, or a single probe down across an entire site, and raise them in your own alerting system.
- CMDB correlation. Join device state with records held outside SecuriThings, such as asset ownership, maintenance windows, or support contracts.
- SIEM ingestion. Deliver device state into your SIEM alongside your other security telemetry.
- Availability reporting. Responses describe current state, so recording them on a schedule produces the availability and trend reporting your organization requires.
- Automated response. Pair a detection with an executed task to remediate without manual intervention.
Device connectivity
status reports the connectivity of a device, and lastSeen reports the last time the device was
not offline, that is, the last time it was online or partial. Filter server-side rather than
retrieving the full inventory:
Code
Code
A status of partial indicates that some, but not all, of the device's probes are reporting. The
probe fields identify which component is affected, and each one is also available as a filter.
maintenanceMode identifies devices under planned work. Exclude them when generating alerts to
avoid reporting expected downtime.
Site connectivity
Sites expose their own status, so connectivity per location can be retrieved without paging
through every device:
Code
