Skip to main content

​
Cloud Monitors

Cloud Monitors is the native cloud finding surface. Use it when you want the findings that already exist in the cloud provider ecosystem rather than a framework-mapped posture view or a repository scan result.

​
Current Provider Coverage

The current product surface is designed around:
  • AWS Security Hub
  • Azure Defender
Do not describe Cloud Monitors as a GCP workflow. The current implementation does not support that path.

​
How It Differs From Cloud Compliance

Use Cloud Monitors when you want:
  • Provider-native findings
  • A direct operational feed from AWS or Azure security tooling
  • A triage surface that starts from the cloud provider’s own detections
Use Cloud Compliance when you want:
  • Framework filtering
  • Requirement-oriented views
  • Audit-oriented exports and control coverage reporting

​
What You Need First

  • A connected AWS or Azure cloud integration
  • Enough access for the provider-specific findings flow to work

​
What To Expect

The cloud monitor experience is best treated as:
  • A live-state review surface
  • A triage queue
  • A starting point for follow-up remediation or agent work
It is not the best place to explain repository changes. For that, hand off to an AI DevOps session or a repository workflow.

Cloud Compliance

Move to a framework view when you need mapped control coverage.

Connect Cloud

Verify provider setup and access if monitor data is missing.