Cloud security

Read-only audits.
Real CIS controls.

Audit every cloud account with read-only keys that never leave your server. Each finding names the CIS control it fails, so your cloud team knows exactly what to change.

AWS production account
Read-only audit ยท eu-west-1, us-east-1
Completed
CIS controlCheckResult
1.4No access keys on the root userPass
1.10MFA for every console userFail
2.1.4Block public access on S3 bucketsFail
3.1CloudTrail enabled in all regionsPass
5.2No security group open to 0.0.0.0/0 on admin portsFail
CIS AWS Foundations Benchmark v3.0

What it does

What you get

  • Findings with the failing CIS control
  • A report per account
  • Posture history across scans
  • Findings in the same tracker as every other scan

Mapped to

  • CIS AWS Foundations
  • CIS Azure Foundations
  • CIS Google Cloud Foundations

How it works

  1. Grant read-only accessAn access key, a service principal or a service account key.
  2. Run the auditOne account at a time, as often as you like.
  3. Fix by controlEvery finding tells you the control and the change.

Documentation

Read the details

Setup, every option and the API, on docs.cerberon.dev.

Common questions

What access does a cloud audit need?
Read-only permissions. The audit sees only what the credential allows and never changes anything.
Where are my cloud keys stored?
On your server, encrypted with AES-256-GCM, and passed only to that scan's worker.

See it on your own systems.

A 30-minute demo on your targets, or install it yourself and start scanning this afternoon.

Search Cerberon