Skip to main content

Vulnerability (CVE) Events

Mapped scans the devices in your org (controllers, supervisors, gateways, cameras, access panels, and the rest of the equipment that runs your airports, hospitals, factories, data centers, and offices) against published vulnerabilities (CVEs), using each device's make, model, and firmware. Every result is a finding: one CVE on one device. You track a finding's status with dispositions (acknowledged, in progress, remediated, and so on), and discuss them with comments.

These events let you feed findings into your ticketing, SIEM, or asset-management systems as they change, instead of polling.

Events​

typeSent when
mapped.security.cve.scan.v1.completedA scan of your org, or of one building, finished.
mapped.security.cve.identifiedCve.v1.createdA CVE was found on a device, by a scan or through the API.
mapped.security.cve.identifiedCve.v1.updatedA finding's details were edited through the API.
mapped.security.cve.identifiedCve.v1.deletedA user deleted a finding.
mapped.security.cve.disposition.v1.createdA finding's status changed: a user set a disposition, or a scan saw the device patched, regressed, or gone.
mapped.security.cve.disposition.v1.updatedA user edited a disposition's status or reason.
mapped.security.cve.disposition.v1.deletedA user deleted a disposition, so the finding's status went back to the one before.
mapped.security.cve.dispositionComment.v1.createdA user commented on a disposition.

Every Mapped security event type starts with mapped.security., so one filter can follow all of them as more are added.

AttributeValue
source//com.mapped/orgs/{orgId}/security/cve/scans for scan events, //com.mapped/orgs/{orgId}/security/cve/identifiedCves for the others
idUnique per event. A retry keeps the same id.
timeWhen the change happened.

Extensions​

These events carry extensions, so you can filter and route without reading data (empty values are left out):

ExtensionOnValue
cveidfinding and disposition eventsThe CVE, for example CVE-2024-12345.
identifiedcveidfinding and disposition eventsThe finding's ID.
severityfinding and disposition eventsSEVERITY_NONE, SEVERITY_LOW, SEVERITY_MEDIUM, SEVERITY_HIGH, or SEVERITY_CRITICAL.
deviceidfinding and disposition eventsThe thing the CVE was found on.
locationidfinding and disposition eventsThe building the device is in.
dispositionstatusdisposition eventsThe disposition's status (see Statuses).
scanidscan eventsThe scan's ID.
scanstatusscan eventsSCAN_STATUS_SUCCEEDED, SCAN_STATUS_PARTIAL, or SCAN_STATUS_FAILED.

Payloads​

Payloads follow the same field names and values as the CVE types in the GraphQL API: field names in lowerCamelCase, enum values as names (SEVERITY_HIGH), and 64-bit counts as strings ("412"). Fields without a value are left out.

Finding Events​

The identifiedCve.v1.* events and the disposition.v1.* events all have:

FieldDescription
orgIdYour org's ID.
identifiedCveIdThe finding's ID.
cveIdThe CVE, for example CVE-2024-12345.
identifiedCveThe finding as it is after the change (see below).
actorWho made the change: a user or client ID, or system for a change a scan made. Not set on findings a scan created.
truncatedtrue when the finding was too large to send whole; see Large Findings. Otherwise left out.

identifiedCve.v1.created adds origin: SCAN when a scan found it, or MANUAL when it was created through the API.

The main fields of identifiedCve:

FieldDescription
id, cveIdThe finding's ID and the CVE.
deviceId, deviceName, deviceTypeThe device the CVE was found on.
locationId, locationNameThe building it is in.
pointId, pointNameThe point that reported the device's firmware, when there is one.
gatewayId, connectorId, connectorType, protocolHow Mapped reaches the device.
make, model, firmwareWhat was matched against the CVE.
severity, cvssBaseScoreHow severe the CVE is.
knownExploitedtrue when the CVE is known to be exploited in the wild.
versionStateVULNERABILITY_STATE_VULNERABLE when the firmware is in the affected range, VULNERABILITY_STATE_UNVERIFIED_VERSION when the firmware could not be compared.
currentStatusThe finding's status: the status of its latest disposition.
dateIdentified, dateLastSeenWhen the CVE was first and last seen on the device.
dispositionsEvery disposition so far, oldest first, with their comments.
alertThe advisory: summary, advisoryUrl, vulnerableVersionRange, firstPatchedVersion, and so on.

mapped.security.cve.identifiedCve.v1.created, from a scan:

{
"orgId": "ORG4kFZ9ZGpdP3mYU3hF3ULdW",
"identifiedCveId": "ICVE6Yb1nqm2TKdUJd5W3mR2p",
"cveId": "CVE-2024-12345",
"origin": "SCAN",
"identifiedCve": {
"id": "ICVE6Yb1nqm2TKdUJd5W3mR2p",
"locationId": "BLDG5hJ2kQwR8nT3vX6zA1cDe",
"locationName": "Terminal B",
"deviceId": "THG8pL3mN6qR2sT5vW9xY1zAb",
"deviceName": "Supervisor 2",
"cveId": "CVE-2024-12345",
"make": "Acme Controls",
"model": "Supervisor 4",
"firmware": "4.10.1",
"severity": "SEVERITY_HIGH",
"cvssBaseScore": 8.1,
"versionState": "VULNERABILITY_STATE_VULNERABLE",
"currentStatus": "DISPOSITION_STATUS_NEW",
"dateIdentified": "2026-11-19T03:00:12Z",
"alert": {
"summary": "A crafted request can bypass authentication on the web interface.",
"advisoryUrl": "https://www.cve.org/CVERecord?id=CVE-2024-12345",
"vulnerableVersionRange": "< 4.12",
"firstPatchedVersion": "4.12"
}
}
}

Disposition Events​

The disposition.v1.* events add:

FieldDescription
dispositionThe disposition that was created, edited, or deleted: id, status, reason, date, actor, automated, and comments.
previousStatusThe finding's status before the change.
currentStatusThe finding's status after the change.
automatedtrue when a scan made the change, false when a user did.

A finding's status only ever changes through a disposition, so subscribing to disposition.v1.* gives you every status change: compare previousStatus with currentStatus. A comment written while setting a disposition comes in that disposition.v1.created event, not as a separate comment event.

mapped.security.cve.disposition.v1.created, when a scan sees that the device's firmware was upgraded:

{
"orgId": "ORG4kFZ9ZGpdP3mYU3hF3ULdW",
"identifiedCveId": "ICVE6Yb1nqm2TKdUJd5W3mR2p",
"cveId": "CVE-2024-12345",
"actor": "system",
"automated": true,
"previousStatus": "DISPOSITION_STATUS_NEW",
"currentStatus": "DISPOSITION_STATUS_REMEDIATED",
"disposition": {
"id": "DSP2xR7kM4nB9vC3qW6zT1yHe",
"status": "DISPOSITION_STATUS_REMEDIATED",
"reason": "firmware update observed; version no longer in affected range",
"date": "2026-11-20T03:00:40Z",
"actor": "system",
"automated": true
},
"identifiedCve": { "id": "ICVE6Yb1nqm2TKdUJd5W3mR2p", "currentStatus": "DISPOSITION_STATUS_REMEDIATED" }
}

(identifiedCve is shortened here; the event carries the whole finding, with this disposition at the end of dispositions.)

Comment Events​

dispositionComment.v1.created adds dispositionId, the disposition that was commented on, and comment, with the comment's id, author, comment text, and date.

Scan Events​

mapped.security.cve.scan.v1.completed:

{
"orgId": "ORG4kFZ9ZGpdP3mYU3hF3ULdW",
"newFindings": 3,
"reopenedFindings": 0,
"autoClosedFindings": 1,
"scan": {
"id": "SCN7tY2uI5oP8aS1dF4gH6jKl",
"status": "SCAN_STATUS_SUCCEEDED",
"lastScanStarted": "2026-11-20T03:00:00Z",
"lastScanCompleted": "2026-11-20T03:00:41Z",
"devicesScanned": "412",
"pointsScanned": "412",
"cvesIdentified": "3",
"autoDispositions": "1"
}
}
FieldDescription
newFindingsFindings this scan created. Each also has its own identifiedCve.v1.created event.
reopenedFindingsRemediated findings that came back, for example after a firmware downgrade.
autoClosedFindingsFindings the scan closed because the device was patched or is gone.
scan.statusSCAN_STATUS_SUCCEEDED; SCAN_STATUS_PARTIAL when some buildings or devices could not be scanned (findings are not closed after a partial scan); or SCAN_STATUS_FAILED.
scan.locationIdThe building scanned, or left out when the scan covered the whole org.
scan.devicesScanned, scan.pointsScanned, scan.cvesIdentified, scan.autoDispositionsWhat the scan covered and did.
scan.devicesUnidentifiedDevices in scope that could not be checked because their make and model are not known.

Statuses​

StatusMeaning
DISPOSITION_STATUS_NEWFound, not yet triaged.
DISPOSITION_STATUS_ACKNOWLEDGEDSomeone has seen it.
DISPOSITION_STATUS_IN_PROGRESSBeing worked on.
DISPOSITION_STATUS_REMEDIATEDFixed, by a user or because a scan saw patched firmware.
DISPOSITION_STATUS_ACCEPTED_RISKLeft as is on purpose.
DISPOSITION_STATUS_FALSE_POSITIVENot actually affected.

When They Are Not Sent​

  • A scan that only refreshes an existing finding (last seen, names, firmware) sends nothing for it.
  • A request that fails, or that changes nothing, sends nothing.

Large Findings​

When a finding is too large to send whole (a long disposition history, for example), the event drops identifiedCve.dispositions, shortens identifiedCve.alert to its summary and URL, and sets truncated: true. Read the whole finding with the identifiedCve query.

Using Them​

Every security event:

@.type =~ /^mapped\.security\./

Every status change on a high or critical finding:

@.type =~ /^mapped\.security\.cve\.disposition\./ && (@.attributes.severity.Attr.CeString == 'SEVERITY_HIGH' || @.attributes.severity.Attr.CeString == 'SEVERITY_CRITICAL')

New findings only:

@.type == 'mapped.security.cve.identifiedCve.v1.created'
  • De-duplicate on id and don't rely on order: use time, and the disposition's date, to apply changes in order.
  • Reconcile with the identifiedCves query (findings and their statuses) and cveScanStates (the latest scans).