IAM Password Policy Non-Compliant
Weak or never-expiring passwords are permitted, which is precisely what makes credential-stuffing attacks work.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Strengthen the IAM password policy.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Any resource in the account
- The fix, by hand
- IAM Identity Center (or legacy IAM Users; IAM Identity Center is the AWS-recommended path now): review the current password policy.
- For legacy IAM users: IAM → Account settings → Edit → set min length 14, require upper / lower / number / symbol, max age 90 days, prevent reuse of last 24.
- For IAM Identity Center: open the directory → Password policies → tighten to the same baseline.
- Communicate the rotation window so users know to expect a prompt.
- Long-term: deprecate IAM users entirely in favour of IAM Identity Center + SSO + MFA.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1523- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.