- SOC 2 Readiness
- 24/7 incident line
- 24/7 security operations team
Checklist · Cloud Security
Cloud Security Baseline Checklist

Written for
Cloud and infrastructure engineers
Time needed
2 hours
Items
26 across 5 areas
Cloud breaches are usually configuration problems: an administrator without multi-factor authentication, storage open to the internet, keys that never expire, logs that were never turned on.
This baseline applies across the major providers and follows the CIS Benchmarks and each provider’s own guidance.
0 of 26 in place (0%)
Identity and access
The control that matters most.
Network exposure
What the internet can reach.
Data protection
Storage is where the damage happens.
Logging and detection
See what happens.
Governance
Keep it that way.
How to get the most from this list
- 01
Tick only what you can prove
If you could not show an auditor or your board the evidence today, leave it unticked. A lower honest score is more useful than a high hopeful one.
- 02
Give every gap an owner
For each unticked item, name one person and one date. Gaps without an owner are the ones still open next year.
- 03
Re-run it every quarter
Your environment changes faster than policy. Repeat the list each quarter and after any major change, and compare the scores.
Gaps we see most often
- Audit logging enabled in one region only
- Access keys several years old
- Storage made public for a one-off transfer and never closed
Take it with you
Download the checklist as a PDF
A designed 6-page version with tick boxes, the common gaps and the questions people ask. Useful for a team review or as audit evidence.
Want a second pair of eyes?
Bring your completed list to a risk review. We will check the items that matter most for your environment, confirm the evidence and turn the gaps into a short, prioritized plan.
Common questions
Is the cloud provider responsible for security?
The provider secures the platform. You are responsible for how you configure it, who can access it and what you store in it.
Which benchmark should we use?
The CIS Benchmark for your provider is the usual starting point and is built into most assessment tools.
How often should configuration be reviewed?
Continuously with automated tooling, with an independent assessment at least annually or after major change.



