Cloud Misconfiguration
A security-weakening setting left in an insecure or default state.
What it is
Any cloud setting that diverges from a secure baseline, such as disabled logging, public access, weak encryption, or absent guardrails. It is a configuration error rather than a code vulnerability.
Why it matters
Misconfiguration is consistently the dominant root cause of cloud incidents, which is why automated posture checks and configuration review feature so heavily in cloud defense and investigation.
In practice
A reviewer traces the breach to a single deployment that shipped with default credentials and public access both left on.
What to look for
- Public storage, open management ports or disabled encryption.
- Logging, MFA or key rotation left at default off.
- Drift between what infrastructure code says and what is deployed.
Common mistake
Fixing it in the console only. The next deploy from code puts the bad setting back.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Amazon GuardDuty Cloud service
AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.
-
Microsoft Defender for Cloud Commercial
Posture and threat protection for Azure, AWS and Google Cloud.
-
Wiz Commercial
Maps cloud resources, identities and exposures into one graph of risk.
-
Prowler Open source
An open source tool that checks cloud accounts against benchmarks such as CIS.
Read next
- Cloud Security Posture Management: Continuously checking cloud configuration against secure baselines.
- Misconfigured Storage Bucket: An object-storage container whose permissions expose data more broadly than intended.
- Infrastructure-as-Code Scanning: Checking infrastructure definitions for insecure settings before deployment.