Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
cognito_user_pool_password_policy_numberProvider: AWS
Service:
cognitoSeverity: MEDIUM
Categories:
identity-accessResource type:
OtherWhat this check verifies
Amazon Cognito user pools are evaluated for a password policy that requires at least one number. The assessment checks whether the policy enforces a numeric character viaRequireNumbers and also identifies pools with no password policy configured.
Risk
Absent a numeric requirement-or any password policy-reduces password entropy, enabling brute force and credential stuffing. Successful account takeover grants valid tokens to protected APIs, risking data confidentiality, unauthorized actions affecting integrity, and resource abuse impacting availability.Recommendation
Enforce a strong password policy: require numbers (RequireNumbers=true), adequate length (e.g., >=8), and mixed case/symbols. Complement with MFA, login throttling/lockout, and password reuse limits for defense in depth. Apply least privilege to applications using tokens and monitor authentication activity.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-policies.html
- https://docs.aws.amazon.com/cognito/latest/developerguide/managing-users-passwords.html
- https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cognito-userpool-passwordpolicy.html
- https://support.icompaas.com/support/solutions/articles/62000233673-ensure-that-the-password-policy-for-your-user-pool-requires-a-number
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = cognito_user_pool_password_policy_number. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks