What are common misconfigurations in cloud storage and how to mitigate them?

• A. Private buckets with no policies
• B. Public access controls and weak IAM; mitigate with proper bucket policies, access logging, encryption, and access reviews
• C. Only on-premises storage
• D. No encryption or logging needed

Answer: (B)

Misconfigurations in cloud storage often come from who can access the data and how that access is managed. When buckets end up public or when identities have more permissions than needed, data can be exposed unintentionally. The most effective mitigation focuses on tightening access, auditing activity, and protecting the data itself.

Explicit bucket policies and strict IAM controls are essential because they define exactly who can do what, under what conditions, and to which resources. This helps enforce least privilege and prevents broad, unintended access. Enabling access logging gives visibility into every access attempt and action, so you can spot unusual or unauthorized activity and respond quickly. Encrypting data at rest (and using capable key management) ensures that even if access is gained, the data remains protected. Finally, conducting regular access reviews keeps permissions aligned with current roles and removes stale or excessive rights over time.

Other options touch on different aspects (such as on-premises storage or omitting encryption or logging entirely), but they don’t address the most common cloud storage risks as directly as tightening access controls, visibility, encryption, and ongoing reviews do.