Findings & Data Model
Cloudaware normalizes vulnerabilities from multiple scanners into a common set of Salesforce objects.
This section describes how findings are stored, how severity and risk are calculated, and how ownership is derived from Cloudaware CMDB.
At a high level:
- Each vulnerability instance is represented as a Cloudaware Vulnerability Scan record, with a record type indicating the source (e.g., cloud‑native, Qualys, Rapid7, [Tenable], Snyk, etc.).
- CVEs and other identifiers are captured as fields on the scan record and, when applicable, as related Cloudaware Vulnerability Scan CVE records.
- Scan records are linked to assets (servers, containers, cloud resources), applications, and OUs in CMDB.
- Additional logic deduplicates, suppresses, and routes findings to the right teams.
Finding Schema
Understand the Cloudaware Vulnerability Scan record, core identifiers, source-specific fields, asset relationships, lifecycle fields, and status values. Use this guide as the starting point for building queries, dashboards, reports, or integrations on top of normalized vulnerability data.
Severity & Scoring
Understand how Cloudaware combines vendor severity, CVSS values, exploitability signals, business impact, and risk bands. Refer to it to define consistent prioritization logic for queues, SLAs, dashboards, and remediation planning.
Ownership & Routing
Understand how vulnerability findings inherit ownership from CMDB assets, applications, OUs, and teams. Ownership helps administrators route remediation tasks and ITSM tickets to the right owners while keeping escalation and reporting aligned.