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
type | Sent when |
|---|---|
mapped.security.cve.scan.v1.completed | A scan of your org, or of one building, finished. |
mapped.security.cve.identifiedCve.v1.created | A CVE was found on a device, by a scan or through the API. |
mapped.security.cve.identifiedCve.v1.updated | A finding's details were edited through the API. |
mapped.security.cve.identifiedCve.v1.deleted | A user deleted a finding. |
mapped.security.cve.disposition.v1.created | A finding's status changed: a user set a disposition, or a scan saw the device patched, regressed, or gone. |
mapped.security.cve.disposition.v1.updated | A user edited a disposition's status or reason. |
mapped.security.cve.disposition.v1.deleted | A user deleted a disposition, so the finding's status went back to the one before. |
mapped.security.cve.dispositionComment.v1.created | A 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.
| Attribute | Value |
|---|---|
source | //com.mapped/orgs/{orgId}/security/cve/scans for scan events, //com.mapped/orgs/{orgId}/security/cve/identifiedCves for the others |
id | Unique per event. A retry keeps the same id. |
time | When the change happened. |
Extensions
These events carry extensions, so you can filter and route without reading data (empty values are left out):
| Extension | On | Value |
|---|---|---|
cveid | finding and disposition events | The CVE, for example CVE-2024-12345. |
identifiedcveid | finding and disposition events | The finding's ID. |
severity | finding and disposition events | SEVERITY_NONE, SEVERITY_LOW, SEVERITY_MEDIUM, SEVERITY_HIGH, or SEVERITY_CRITICAL. |
deviceid | finding and disposition events | The thing the CVE was found on. |
locationid | finding and disposition events | The building the device is in. |
dispositionstatus | disposition events | The disposition's status (see Statuses). |
scanid | scan events | The scan's ID. |
scanstatus | scan events | SCAN_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:
| Field | Description |
|---|---|
orgId | Your org's ID. |
identifiedCveId | The finding's ID. |
cveId | The CVE, for example CVE-2024-12345. |
identifiedCve | The finding as it is after the change (see below). |
actor | Who made the change: a user or client ID, or system for a change a scan made. Not set on findings a scan created. |
truncated | true 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:
| Field | Description |
|---|---|
id, cveId | The finding's ID and the CVE. |
deviceId, deviceName, deviceType | The device the CVE was found on. |
locationId, locationName | The building it is in. |
pointId, pointName | The point that reported the device's firmware, when there is one. |
gatewayId, connectorId, connectorType, protocol | How Mapped reaches the device. |
make, model, firmware | What was matched against the CVE. |
severity, cvssBaseScore | How severe the CVE is. |
knownExploited | true when the CVE is known to be exploited in the wild. |
versionState | VULNERABILITY_STATE_VULNERABLE when the firmware is in the affected range, VULNERABILITY_STATE_UNVERIFIED_VERSION when the firmware could not be compared. |
currentStatus | The finding's status: the status of its latest disposition. |
dateIdentified, dateLastSeen | When the CVE was first and last seen on the device. |
dispositions | Every disposition so far, oldest first, with their comments. |
alert | The 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:
| Field | Description |
|---|---|
disposition | The disposition that was created, edited, or deleted: id, status, reason, date, actor, automated, and comments. |
previousStatus | The finding's status before the change. |
currentStatus | The finding's status after the change. |
automated | true 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"
}
}
| Field | Description |
|---|---|
newFindings | Findings this scan created. Each also has its own identifiedCve.v1.created event. |
reopenedFindings | Remediated findings that came back, for example after a firmware downgrade. |
autoClosedFindings | Findings the scan closed because the device was patched or is gone. |
scan.status | SCAN_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.locationId | The building scanned, or left out when the scan covered the whole org. |
scan.devicesScanned, scan.pointsScanned, scan.cvesIdentified, scan.autoDispositions | What the scan covered and did. |
scan.devicesUnidentified | Devices in scope that could not be checked because their make and model are not known. |
Statuses
| Status | Meaning |
|---|---|
DISPOSITION_STATUS_NEW | Found, not yet triaged. |
DISPOSITION_STATUS_ACKNOWLEDGED | Someone has seen it. |
DISPOSITION_STATUS_IN_PROGRESS | Being worked on. |
DISPOSITION_STATUS_REMEDIATED | Fixed, by a user or because a scan saw patched firmware. |
DISPOSITION_STATUS_ACCEPTED_RISK | Left as is on purpose. |
DISPOSITION_STATUS_FALSE_POSITIVE | Not 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
idand don't rely on order: usetime, and the disposition'sdate, to apply changes in order. - Reconcile with the
identifiedCvesquery (findings and their statuses) andcveScanStates(the latest scans).