One toggle, one open firewall rule or one account without MFA is all it takes. CloudMonitor checks for exposed storage, databases, ports and identity gaps across your environment, or your clients', in plain language with a link to the fix.
Exposure is usually an accident, not an attack plan: a storage container made public for a quick share, a database firewall opened to test something, a rule left at "any".
It is invisible from the console that created it. Everything works, and nothing warns you that the data is readable by anyone who finds the address.
Posture drifts. A setup that was right at launch is not right six months later, and each platform measures "right" differently.
Every platform CloudMonitor connects to, in the same order on every page, with what it checks for this problem today. Where nothing is checked yet, the table says so.
| Platform | What CloudMonitor checks for this problem | Status |
|---|---|---|
| Microsoft Azure | Storage accounts: Public access, waste Azure SQL, PostgreSQL, MySQL: Public access, TLS minimums Network security groups: Sensitive ports open to the internet Public IPs & gateways: Edge exposure on load balancers and App Gateway | Live |
| Microsoft 365 & Entra ID | Entra ID users: MFA gaps, stale and guest accounts Conditional Access: Policy gaps | Live |
| Amazon Web Services | S3: Public buckets, encryption RDS: Public access, backups, encryption Security groups: Open ingress | Beta |
| Google Cloud | Cloud Storage: Public buckets Cloud SQL: Public access, backups BigQuery: Dataset exposure VPC firewall: Sensitive ports open to the internet | Live |
| Kubernetes | Any cluster: OpenShift, k3s, Rancher, kubeadm — workloads, RBAC, quotas | Beta |
| Containers & registries | Docker Engine hosts: Privileged containers, restart loops, exposed ports, disk Docker Hub & GHCR: Publicly pullable images, critical CVEs | Live |
| On-prem servers & Exchange | Patch age, pending reboot and certificate checks only. No public-exposure check yet. | No check yet |
| MuleSoft Anypoint | CloudHub runtime: App status, unsupported runtime versions | Live |
| Domains, DNS & email | Email authentication: SPF, DKIM, DMARC, MTA-STS Security headers: HTTP header grade DNS watch: NS/MX drift, DNSSEC, CAA, blocklists | Live |
| Uptime & heartbeats | Not a posture check. Reachability and certificate days left only. | No check yet |
How deep each platform goes. Live means scheduled for every connected account; Beta means scheduled and verified against emulated APIs only. Azure is the most complete and is run against real accounts every day. The AWS and Google Cloud scanners have been verified against emulated APIs, not yet against live customer accounts. Kubernetes, MuleSoft and the on-prem collector are narrower still.
Access is read-only and least-privilege, and there are no agents to install on your cloud accounts.
Full setup guide: connectors.
Anything that makes a resource easier to reach or harder to defend than it should be: publicly readable storage, databases open to the internet, sensitive ports open to everyone, missing MFA, weak TLS settings and missing email authentication records. The table lists the checks per platform.
Exposure findings arrive within the hour of connecting a platform. The full scan repeats at least once a day.
No. CloudMonitor reads configuration through read-only access to what you connect, plus public data about your domains. It does not probe or attack anything.
No. Access is read-only. Findings link to the fix so you or your client can make the change.
No, and the table says so. Azure is the most complete and is run against real accounts every day; the AWS and Google Cloud scanners have been verified against emulated APIs, not yet against live customer accounts; other platforms are narrower.
No. CloudMonitor finds configuration gaps. It is not a certification or an audit, and no compliance outcome is implied.
14-day free trial. No credit card needed to start, and it never turns into a paid plan on its own.