Module 08: Mutelist Mastery

Track 2 · Prowler Open Source CLI · Time: ~1h 15 min · Pass: 8/10

Scenario

Your first Cloudsmiths scan returned 1,200 findings. About 200 of those are known and accepted: public-facing buckets that are intentionally public for marketing assets, a deliberately permissive Lambda for the test harness, dev-only accounts you don't care about. The team is drowning in noise. You'll write a mutelist that suppresses the noise without hiding real risk.

Learning objectives

1. Distinguish between mutelist, suppression, allowlist, and policy.
2. Write a Prowler YAML mutelist with wildcards, exceptions, and tags.
3. Reason about blast radius before muting.
4. Track muted findings to keep accepted risk visible.