Skip to main content

triggerCveScan

Mutation

Starts a CVE scan of your org, or of one building. A scan compares each device's make, model and firmware with the CVE catalog, records new findings, refreshes existing ones, records hardware changes, and may close findings automatically (e.g. after a firmware update) or reopen remediated ones that are vulnerable again. It runs in the background and can send notification emails (new findings, reopened findings, scan complete) as set in cveNotificationSettings. Triggering a scope that is already being scanned joins the running scan instead of starting another. Returns that scope's scan as RUNNING; follow its progress and results with cveScanStates.

triggerCveScan(locationId: String): CVEScanState

Arguments​

ArgumentTypeDefaultDescription
locationIdStringA building id, to scan only that building. Empty to scan the whole org.

Returns​

CVEScanState: The latest CVE scan of one scope of your org (the whole org, or one building), with what it covered.

Example​

Request
mutation TriggerCveScan {
triggerCveScan {
autoDispositions
cvesIdentified
devicesScanned
devicesUnidentified
id
lastScanCompleted
lastScanStarted
locationId
pointsScanned
status
subtendedDevicesUnidentified
}
}