The misconfigurations that actually cause incidents
Most cloud breaches don’t start with an exotic exploit. They start with a storage bucket left public, a database port open to the internet, a user without MFA or an access key nobody rotated. CloudMonitor checks for exactly these on every sync, across all three clouds.
The checks
AWS
- S3.1 / S3.2 — public access block not fully enabled; no default encryption.
- EC2.1 — unencrypted EBS volume.
- SG.1 / SG.2 — security group open to
0.0.0.0/0or::/0on SSH, RDP, MySQL, PostgreSQL, Redis or MongoDB ports, or on all ports (critical). - RDS.1 / RDS.2 — publicly accessible or unencrypted database.
- IAM.1 / IAM.2 — user without MFA; active access key older than 90 days.
Azure
- Storage accounts that allow public blob access or don’t enforce HTTPS; unattached managed disks; allocated public IPs (informational).
Google Cloud
- Buckets without public access prevention; Cloud SQL with a public IP or without required SSL; unattached disks.
How the score works
The score starts at 100. Every open finding subtracts points by severity — 25 for critical, 12 for high, 5 for medium, 2 for low — and the result maps to a grade from A (90+) to F (below 60), for the workspace and for each cloud. Because every finding counts, the score is strict: a large estate with many small issues will score low until they are cleaned up. That is deliberate. It makes progress visible and gives the team a number to defend.
From finding to fix
Every finding includes remediation text, and the findings view filters by severity, cloud, region, check and status. The IAM page lists each AWS user with MFA status, oldest key age and last password use. To decide what to tackle first across both security and cost, use the risk-adjusted worklist; to be told when something critical appears, turn on alerts.
The checks focus on many of the same areas as the CIS Foundations Benchmarks, but CloudMonitor doesn’t claim formal CIS mapping. Our AWS security checklist covers the wider practices worth adopting.