# Password Policies

Password policies are rules governing how passwords are created, used, changed, and protected within an identity system.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/password-policies

> Password policies establish requirements such as minimum length, prohibited passwords, reuse restrictions, and reset procedures to reduce unauthorized access. In cloud environments, their effectiveness depends on applying them to the correct identity source and combining them with multifactor authentication, secure credential storage, and appropriate access permissions.

Practice exams covering Password Policies: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate).

## 6 key aspects of Password Policies

Effective password policies combine usable strength requirements, clearly defined enforcement boundaries, secure lifecycle management, and complementary authentication protections.

1. **Password strength and uniqueness**: Require sufficient length and encourage unique, password-manager-generated passwords. Where the identity platform supports it, reject common and compromised passwords rather than relying only on character-composition rules.
2. **Correct enforcement scope**: Identify which identity store owns each password and configure requirements there. An account-level policy for local cloud users does not automatically govern root identities, federated users, databases, or application accounts.
3. **Lifecycle and recovery controls**: Define secure onboarding, password changes, compromise-driven resets, and recovery procedures. Use expiration and reuse restrictions where required, while accounting for support costs and predictable user workarounds.
4. **Separation of credential types**: Treat console passwords, access keys, temporary credentials, and application secrets as distinct credential types. Password policy changes do not rotate access keys; use roles and temporary credentials where possible.
5. **Appropriate credential storage**: Store operational secrets in an access-controlled secrets or encrypted configuration service rather than source code. For application-managed user authentication, store salted password hashes using an appropriate password-hashing algorithm.
6. **Layered authentication protection**: Combine password requirements with multifactor authentication, sign-in monitoring, and secure recovery. Keep permissions least-privileged because password strength does not limit an authenticated identity's authority.

## Cloud services for Password Policies

IAM enforces password requirements for IAM users, while AWS Config can check whether that account-level configuration meets organizational standards. Secrets Manager and Systems Manager Parameter Store address a separate concern: protecting credentials that applications or automation need to retrieve. Secrets Manager supports configured rotation workflows, whereas Parameter Store provides encrypted sensitive configuration without equivalent built-in credential rotation. These services complement rather than replace one another. Federated workforce password rules remain with the authenticating identity provider, and applications should use IAM roles and temporary credentials where possible instead of storing long-term AWS access keys.

- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: Secrets Manager stores and controls access to operational credentials such as database passwords and API secrets. It supports automatic rotation through supported integrations or configured rotation workflows, but does not enforce human sign-in password requirements.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Systems Manager Parameter Store can store sensitive configuration using SecureString parameters encrypted with AWS Key Management Service. It complements password policies by protecting stored credentials, but does not itself rotate the underlying credentials or enforce sign-in password rules.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config can evaluate the IAM account password policy against specified requirements using the iam-password-policy managed rule. This detects configuration noncompliance; it does not inspect individual passwords or replace IAM's enforcement.

## Password Policies exam questions

Real practice exam questions on Password Policies, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company has individual IAM users in one AWS account who sign in to the AWS Management Console. The company must centrally enforce a minimum password length of 14 characters and prevent users from reusing their five previous passwords when changing passwords. Which solution meets these requirements?

**Correct answer:** Configure the account's IAM password policy with a minimum length of 14 characters and password reuse prevention set to five previous passwords.

**Explanation:** An IAM account password policy centrally enforces requirements for IAM user console passwords, including minimum length and the number of previous passwords users cannot reuse.

### Question 2 (SOA-C03)

**Question:**

A company has an AWS account with IAM users who sign in directly to the AWS Management Console. The account currently uses the default IAM password policy. All users created their current passwords 7 days ago. A new security standard requires passwords to contain at least 14 characters and prevents reuse of the previous 24 passwords. Every existing user must choose a compliant password at the user's next console sign-in, and users must be able to complete the change without administrator assistance.

Which solution meets these requirements?

**Correct answer:** Configure an account password policy with a minimum length of 14 characters, prevention of reuse of the previous 24 passwords, and permission for users to change their own passwords. Set PasswordResetRequired to true on each existing user's login profile.

**Explanation:** The account password policy enforces the required length and password history. Setting PasswordResetRequired on each login profile forces existing users to change their passwords at their next console sign-in. Allowing users to change their own passwords enables self-service completion.

## Practice Password Policies in a full exam

Questions on Password Policies in each practice exam, with every answer option and an explanation for each:

- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 2 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 2 questions

## What is Password Policies

A password policy defines the requirements that passwords must satisfy and the procedures used to manage them throughout their lifecycle. Common controls include minimum length, character requirements, restrictions on previously used passwords, checks against compromised passwords, and secure recovery processes. Not every identity platform supports every control. Engineers must distinguish organizational requirements from the settings a particular platform can actually enforce.

Length and uniqueness are important because short passwords are easier to guess, while reused passwords expose accounts to credential-stuffing attacks after unrelated breaches. A practical policy encourages long, unique passwords generated and stored in an approved password manager. Where supported, rejecting common or known-compromised passwords helps prevent predictable choices. Character-composition rules alone do not guarantee strength: a predictable word with a number and symbol can satisfy complexity requirements while remaining easy to guess.

Cloud password policies apply at an identity boundary, not automatically across every resource in an organization. For example, an AWS Identity and Access Management account password policy governs passwords for IAM users in that AWS account. It does not govern the AWS account root user's password, federated workforce passwords, application user passwords, or database passwords. Organizations using federation normally manage workforce password requirements at the identity provider that authenticates those users. Each separate identity store needs its own appropriate controls.

Passwords must also be distinguished from access keys. An IAM user password supports interactive AWS Management Console sign-in. An AWS access key ID and secret access key support authenticated programmatic requests, such as requests made through an SDK or the AWS CLI. Changing a password policy does not rotate, expire, or otherwise secure access keys. For workloads, prefer IAM roles and temporary credentials over embedded long-term access keys; for workforce access, federation can similarly provide temporary credentials.

Expiration and reuse settings require deliberate trade-offs. Some compliance requirements mandate periodic password changes, and identity platforms may support configurable password age and password history. However, frequent forced changes can encourage predictable variations and increase support requests. Modern guidance generally favors strong, unique passwords and changes when compromise is suspected or confirmed rather than arbitrary periodic changes. Apply mandatory expiration where required, and document the rationale. Check how policy changes affect existing credentials rather than assuming every current password is immediately revalidated.

Secure credential storage complements password rules but solves a different problem. An application needing a database password can retrieve it from AWS Secrets Manager, which supports managed rotation for supported integrations and custom rotation workflows. AWS Systems Manager Parameter Store can hold sensitive configuration as encrypted SecureString parameters, but it does not provide the same built-in secret-rotation workflows. Neither service establishes the IAM account password policy. Applications that verify their own users' passwords should normally store salted, purpose-built password hashes rather than recoverable plaintext passwords.

Finally, password policies are only one layer of authentication security. Multifactor authentication reduces reliance on a password alone, while rate limiting, monitoring, and secure recovery processes address other attack paths. Authentication establishes identity; authorization determines what that identity may do. A strong password does not grant permissions or compensate for excessive privileges.

## Learn Password Policies in lessons

2 short lessons on Password Policies in 2 certification courses.

- CLF-C02: Password Policies: IAM account password rules (Premium), https://app.blowstack.com/lessons/password-policies-iam-account-password-rules-clf-c02
- SOA-C03: Password Policies: IAM account password controls (Premium), https://app.blowstack.com/lessons/password-policies-iam-account-password-controls-soa-c03
