Misconfig SweepCatch the risk. Choose the fix.
About Misconfig Sweep
Spot the risky line in fictional cloud, Kubernetes, Docker and CI configs, then choose the right fix. Watch for clean traps and build your combo in the daily sweep.
How it works
- Tap the risky line in a fictional configuration excerpt, or choose Looks safe for a clean trap. Then pick the best fix from three options.
- A run has 12 rounds drawn from 36 scenarios, rising through three difficulty levels. Each level includes one clean trap. Five missed full sweeps end the run; there is no countdown.
- Get both steps right for 200 points plus a streak bonus capped at 125. One correct step earns 50 points, but still costs a life. Every round ends with a short lesson and its official source.
- The daily deck and fix order use the UTC date. Random mode draws another deck. Best scores stay on your device; share your result or save an SVG score card, then restart instantly.
What you'll learn
- Reviewing storage public-access safeguards, encryption, remote administration rules, metadata tokens and audit logging across fictional cloud resources.
- Recognizing privileged Pods, host access, root identities, missing resource limits and mutable image references in Kubernetes excerpts.
- Choosing safer Docker build credentials, service users and artifact verification, plus safer GitHub Actions triggers and workflow permissions.
- Distinguishing directory-listing and version-disclosure hardening in nginx from authorization, and avoiding false positives by reading the stated scope.
FAQ
Is Misconfig Sweep free?
Yes. It runs in your browser without an account. No configuration is executed or deployed. Only local best scores are saved on your device.
Does Looks safe mean the deployment is secure?
No. It means the excerpt meets the specific review scope described in that round. The snippets are fictional teaching excerpts, not complete templates or a compliance assessment.
How is it different from Vuln Hunter?
Misconfig Sweep reviews cloud and deployment settings, then asks you to choose a remediation. Vuln Hunter focuses on application code bugs. The daily sweep also includes one clean configuration per difficulty level.
Keep going
References
The fictional excerpts teach provider best practices, not a compliance certification or a complete configuration audit. Each learned card links to its specific guidance. Syntax was checked against official documentation on November 16, 2026.
- AWS S3: Block Public Access
- AWS Security Hub: EC2 controls
- AWS EBS: encryption examples
- AWS RDS: encrypting resources
- Kubernetes: volumes and hostPath warnings
- AWS Security Hub: RDS controls
- AWS CloudTrail: security best practices
- Microsoft Learn: prevent anonymous blob access
- Microsoft Learn: network security best practices
- Google Cloud: public access prevention
- Kubernetes: Pod Security Standards
- Kubernetes: resource management
- Kubernetes: container images
- Docker: build best practices
- Docker: Dockerfile reference
- Docker: build secrets
- GitHub: secure use of Actions
- GitHub: pull_request_target warning
- GitHub: workflow permissions
- nginx: autoindex module
- nginx: server_tokens directive
Terraform attribute references
Continue with the Kubernetes security course, the AWS Security Specialty course, or the free website scanner. The website scanner does not inspect cloud accounts or Kubernetes clusters.