Stay secure · Security & Compliance

A security score you can actually move.

CloudMonitor runs configuration checks across your AWS, Azure and Google Cloud resources on every sync, grades the result from A to F and tells you exactly how to fix each finding.

AWS Azure Google Cloud Included in every plan
Security posture 3 open
  • high · −12IAM.1 · user without MFA
  • medium · −5IAM.2 · key older than 90 days
  • low · −2AZ-DSK-1 · unattached disk
01 What’s included

Security & Compliance, in detail.

A 0–100 posture score with prioritized findings. Here is exactly what CloudMonitor does — and where its coverage stops today.

AWS checks

S3 public access block and default encryption, unencrypted EBS, security groups open to the internet on SSH, RDP and database ports, public or unencrypted RDS, IAM users without MFA and access keys older than 90 days.

Azure checks

Storage accounts that allow public blob access or plain HTTP, unattached managed disks and allocated public IPs.

Google Cloud checks

Buckets without public access prevention, Cloud SQL instances with a public IP or without required SSL, and unattached disks.

Score and grade

Each finding subtracts from 100 by severity — critical 25, high 12, medium 5, low 2 — for an A–F grade overall and per cloud.

IAM review

Every AWS IAM user with MFA status, oldest key age and last password use, sortable and exportable.

A fix for every finding

Each finding carries remediation steps, with filters by severity, cloud, region, check and status.

02 How it works

Three steps, no agents to install.

1

Connect read-only access

The checks run against the configuration CloudMonitor already reads for the inventory.

2

Get a grade

A 0–100 score and A–F grade for the whole estate and for each cloud.

3

Work the findings

Critical items first, each with the exact fix. The score climbs as findings close.

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/0 or ::/0 on 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.

03 FAQ

Security & Compliance
questions.

Something else? Talk to us — a person replies.

Which security checks does CloudMonitor run?

On AWS: S3 public access block and default encryption, unencrypted EBS volumes, security groups open to 0.0.0.0/0 or ::/0 on SSH, RDP, MySQL, PostgreSQL, Redis or MongoDB ports (or on all ports), publicly accessible or unencrypted RDS, IAM users without MFA and access keys older than 90 days. On Azure: public blob access, HTTPS not enforced, unattached disks and public IPs. On Google Cloud: public access prevention, Cloud SQL public IPs and SSL, and unattached disks.

How is the security score calculated?

The score starts at 100 and each open finding subtracts points by severity: 25 for critical, 12 for high, 5 for medium and 2 for low. Grades run from A (90 and above) to F (below 60), for the whole workspace and for each cloud.

Is it mapped to the CIS Benchmarks?

The checks target many of the same misconfigurations the CIS Foundations Benchmarks focus on — public storage, open management ports, encryption, MFA and key rotation — but CloudMonitor does not claim formal CIS control mapping or certification.

Does CloudMonitor read Security Hub or GuardDuty?

No. Findings come from CloudMonitor’s own configuration checks against your inventory.

Turn on
the radar.

Create a workspace, connect your first account read-only and see what your clouds have been hiding.

FREE PLAN · NO CREDIT CARD · READ-ONLY ACCESS