Cloud Hardening Cheat Sheets

Cloud Hardening Cheat Sheets

All eight pieces of SecBlog's Cloud Security & Hardening series in one place: six checklists and two essays on the reasoning behind them, plus the two open-source tools they lean on.

Each checklist is written from the provider's own documentation. It has a dated baseline, a note on which control numbers were verified and against which benchmark version, and a list of primary sources. Five of the six also have a "Worth flagging" section on one mistake the documentation describes but practitioners tend to miss.

Storage

AWS S3 Bucket Hardening Cheat Sheet19 items on access control, encryption, versioning and recovery, logging, and detection, mapped to CIS controls (v5.0.0). Baseline: September 2026. Azure Blob Storage Hardening Cheat Sheet26 items on access, network, encryption, recovery, and logging, mapped to Microsoft's cloud security benchmark where a control exists. Baseline: September 2026.Worth flagging: the static website gotcha. Google Cloud Storage Hardening Cheat Sheet20 items on access, encryption, recovery, network, and logging, mapped to the CIS Google Cloud Platform Foundation Benchmark (v1.2.0) where a control exists. Baseline: September 2026.Worth flagging: public access prevention masks a public grant instead of deleting it.
Where to startIf you run object storage, start with your provider's sheet. Then use the two access sheets below to check what can reach it: your own pipelines and your vendors.

Access to your cloud

GitHub Actions OIDC Hardening Cheat Sheet: AWS, Azure, and Google Cloud23 items on giving GitHub Actions workflows cloud access without long-lived keys, and on making sure only the right repository can use it. No CIS control numbers cited. Baseline: October 2026.Worth flagging: a trust policy that matches a repository by name trusts whoever owns that name next. Third-Party and Delegated Access Hardening Cheat Sheet: AWS, Azure, and Google Cloud26 items on giving a vendor, partner, or tool the access the job needs and no more, and on cutting it off quickly when the vendor is breached. No CIS control numbers cited. Baseline: October 2026.Worth flagging: Conditional Access for workload identities does not cover the vendor apps you most need it for.

Preparing for post-quantum

Post-Quantum Readiness Hardening Cheat Sheet: AWS, Azure, and Google Cloud26 items on a cryptographic inventory, key exchange in transit, keys, signatures, and certificates, crypto-agility, and logging, built around NIST IR 8547. No CIS control numbers cited. Baseline: November 2026.Worth flagging: post-quantum key exchange at the front door protects only the first hop.

The reasoning behind the checklists

IAM and Key Vaults: The Mandate, Not the SuggestionWhy identity and access management is the actual perimeter now, where secrets managers fit, and the tradeoffs of doing either properly. Encryption at Rest and in Transit: The Actual Case, and What It Costs YouWhat encryption does and doesn't protect against, and its tradeoffs: key management overhead, performance, and the false sense of security it can create.

Tools that automate the checks

OSS Spotlight: Cloud Custodian (c7n)An open-source policy engine that turns a recurring audit of public S3 buckets into a five-line YAML file. Each storage sheet explains how it covers that sheet's items. OSS Spotlight: GitleaksAn open-source secrets scanner that finds the long-lived credentials the OIDC sheet is meant to retire.

Keeping up

New sheets appear here as they are published. The full list is on the Cloud Security & Hardening tag page, and the site's RSS feed carries every post.

Marselis A. Reed

Marselis A. Reed

Information Security Engineer | CISSP Candidate | B.S. in Computer Science, with 10 years of production experience — including 5 years in healthcare information security.

Was this useful?

Discussion

Get the Next Issue

Cloud hardening, vendor watch, and OSS tooling — every week.