Cloud Misconfiguration

A cloud misconfiguration is an insecure setting in a cloud service, such as public storage, missing MFA, overly broad permissions or disabled logging. Misconfigurations are among the most common causes of cloud data exposure.

IntermediateCategory: Cloud and software supply chain

Also called: cloud security misconfiguration, misconfigured cloud storage, public S3 bucket

What is a cloud misconfiguration?

Cloud services have hundreds of settings, and the defaults favor convenience. A cloud misconfiguration is any setting that leaves data or systems more exposed than intended. Under the shared responsibility model, configuration is the customer's job, and it's where many cloud breaches begin. They're a cloud-specific type of security misconfiguration.

Common examples

In AWS, Azure and Google Cloud:

  • Storage buckets or blobs open to the public internet
  • Databases, remote desktop or SSH reachable from anywhere
  • Overly broad identity roles, such as "admin on everything" for an app
  • Access keys that never expire, or that are embedded in code
  • Logging and alerting turned off
  • Unencrypted storage or snapshots shared publicly

In Microsoft 365 and Google Workspace:

  • MFA not enforced, or legacy authentication still allowed
  • Too many global admins
  • Anyone-with-the-link sharing on sensitive files
  • Automatic email forwarding to outside addresses allowed
  • Users able to grant third-party apps access to company data
  • Audit logging not enabled

Why it happens

Rapid changes without review, staff unfamiliar with cloud security, test resources that become permanent, inconsistent manual setup across accounts, and the belief that the provider handles security.

How to prevent and find misconfigurations

  1. Start from a secure baseline. CISA's free SCuBA baselines and its ScubaGear and ScubaGoggles tools check Microsoft 365 and Google Workspace settings. Cloud providers publish their own security benchmarks too.
  2. Use [CSPM](/glossary/cloud-security-posture-management/) tools, including the providers' built-in ones, such as Microsoft Defender for Cloud and AWS Security Hub, to scan continuously.
  3. Define infrastructure in code and scan it before deployment. See IaC security.
  4. Block public access at the account level where possible.
  5. Review admin roles and sharing regularly.

A penetration test or cloud configuration review can find misconfigurations before attackers do.

Related terms

Sources

  1. Secure Cloud Business Applications (SCuBA) Project (CISA)
  2. SP 800-144: Guidelines on Security and Privacy in Public Cloud Computing (NIST)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.