Native findings and CVE detection
Fold your cloud providers' own scanner findings into one list, and detect known CVEs on end-of-life components.
Online version, always current: https://cloudvision360.com/docs/cloudvision360/native-findings-and-cve/
CloudVision360 does not replace your providers’ native scanners — it folds their findings in and adds the context they lack.
Native findings, ingested
Findings from the cloud providers’ own scanners are ingested and mapped into CloudVision findings, so you get one list and one severity scale:
- AWS Security Hub — GuardDuty and Inspector findings, live today.
- Microsoft Defender for Cloud and Google Security Command Center — next on the roadmap.
Once mapped, a native finding carries the same owner, risk score, ticketing and remediation options as any other finding.
Known CVEs on what you run
CloudVision360 detects known CVEs on end-of-life components it discovers — such as outdated database engines and Kubernetes versions — agentlessly, from the inventory it already builds. These are scored alongside posture findings so an exposed, out-of-support database competes for attention with everything else.
Why fold them in
Running each scanner in its own console means several severity scales, several queues and no shared business context. One mapped list means a single Fix first order, compliance evidence from the same data, and governed remediation regardless of which scanner raised the issue.
Set it up
Native ingestion turns on with the relevant cloud connection — Security Hub comes with the AWS connection. CVE detection runs as part of every scan with no extra configuration.