Skip to content
Password Generator Lab

Password requirements by platform, compared

Password rules side by side for NIST, Microsoft Entra ID, Active Directory, AWS IAM, Google Workspace, PCI DSS, GitHub, Apple, Salesforce and Oracle.

· 7 min read

Key takeaways

  • Minimum lengths differ: NIST SP 800-63B-4 asks for 15 characters when a password is the only factor, PCI DSS v4.0.1 for 12, and most vendor defaults for 8.
  • Microsoft Entra ID, Active Directory and AWS IAM require characters from 3 of 4 types; Apple requires an uppercase letter, a lowercase letter and a digit; NIST forbids composition rules.
  • Symbol support varies: AWS IAM accepts only 20 symbols, and Oracle's standard verify function rejects the double quotation mark.
  • Many limits are defaults that administrators can raise, so check your organization's own policy.
  • Our password policy generator creates a random password for any of these presets and checks it against each rule.

Last reviewed

Every platform has its own password rules, and they disagree. Some want a mix of character types, some forbid that requirement, and some reject symbols other systems accept. The table below compares the password requirements of 10 widely used standards and platforms. It uses the same rule data that our password policy generator enforces, checked against each vendor's documentation on 9 November 2026.

Password requirements at a glance

Platform or standardLengthCharacter rulesSymbols accepted
NIST SP 800-63B-4At least 15 charactersNo composition rulesAll 32 printable ASCII symbols
Microsoft Entra ID8–256 charactersCharacters from at least 3 of 4 types (upper, lower, digit, symbol)All 32 printable ASCII symbols
Active Directory (complexity on)Set by the administratorCharacters from at least 3 of 4 types (upper, lower, digit, symbol); Doesn't contain the account nameAll 32 printable ASCII symbols
AWS IAM users8–128 charactersCharacters from at least 3 of 4 types (upper, lower, digit, symbol)! @ # $ % ^ & * ( ) _ + - = [ ] { } | '
Google Workspace8–100 charactersNo composition rulesAll 32 printable ASCII symbols
PCI DSS v4.0.112–128 charactersContains both letters and digitsAll 32 printable ASCII symbols
GitHubAt least 15 characters, or at least 8 with a digit and a lowercase letterNo composition rulesAll 32 printable ASCII symbols
Apple AccountAt least 8 charactersContains an uppercase letter; Contains a lowercase letter; Contains a digit; No more than 2 identical characters in a rowAll 32 printable ASCII symbols
Salesforce (default org policy)At least 8 charactersContains both letters and digitsAll 32 printable ASCII symbols
Oracle Database (ora12c_verify_function)At least 8 charactersContains both letters and digits; Contains a special character; Doesn't contain a double quotation mark ("); Doesn't contain the word “oracle”; Isn't the user name or the user name reversed! # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

Lengths are the documented defaults or limits. Many of these systems let an administrator raise the minimum, so your organization's policy may be stricter. Each platform name links to its official documentation.

What each platform adds

Rules a generator can't check, such as history, lockout and banned-password lists, are listed here.

NIST SP 800-63B-4

U.S. federal guidance: length over complexity, no composition rules.

  • Applies to passwords used as the only authentication factor; 8 characters is the minimum when combined with another factor.
  • Services should accept at least 64 characters (we generate up to 64) and must not require mixes of character types or periodic changes.
  • Services must also screen passwords against lists of common or breached passwords.

Microsoft Entra ID

Microsoft 365 / Entra ID cloud accounts, including External ID tenants (fixed policy).

  • Entra doesn't accept Unicode characters (External ID tenants allow them only for some sign-up paths), so we use ASCII only. Spaces are allowed but we don't generate them.
  • Entra also rejects passwords on Microsoft's global and your tenant's custom banned-password lists — a random password won't match them.

Active Directory (complexity on)

On-premises Windows domains with “Password must meet complexity requirements” enabled.

  • Minimum length is a separate setting (the Default Domain Policy uses 7 characters) — check your domain's policy and set the length at least that long.
  • Backslash (\) and currency symbols don't count as special characters for this rule; our passwords always include upper, lower and digits, so they still pass.
  • Windows also rejects passwords containing any 3+ character part of the user's display name (split on spaces, commas, periods, hyphens, underscores and #); enter the account name above to check the obvious case.

AWS IAM users

AWS console passwords for IAM users (default policy).

  • Symbols are limited to ! @ # $ % ^ & * ( ) _ + - = [ ] { } | ' — the set AWS lists for IAM password policies.
  • The default policy also rejects a password identical to your AWS account name or email address.
  • Your account may use a custom policy with a longer minimum (CIS benchmarks recommend 14+); our default of 20 covers that.

Google Workspace

Google Workspace and Cloud Identity user accounts.

  • Admins choose a minimum and maximum between 8 and 100 characters and can require “strong” passwords, which Google checks itself against weak, patterned and breached passwords.

PCI DSS v4.0.1

Payment-card environments (requirement 8.3.6).

  • v4.0.1 is the only active version since v4.0 was retired on 31 December 2024; it didn't change 8.3.6.
  • Systems that can't support 12 characters may use 8; this has been mandatory since 31 March 2025.
  • Many systems in scope reject some symbols — if yours does, the generated password still meets 8.3.6 without them.

GitHub

GitHub personal account passwords.

  • GitHub also rejects passwords found in breach datasets such as Have I Been Pwned — a fresh random password won't be in them.
  • GitHub doesn't publish a maximum length; it recommends a password manager-generated password of at least 15 characters plus two-factor authentication.
  • Passwords only work for signing in on the web; Git and the API need a personal access token instead.

Apple Account

Apple Account (formerly Apple ID) passwords.

  • Apple also rejects commonly used passwords — a random password won't be one.
  • Apple doesn't publish a maximum length or a list of accepted symbols. If a long password or a symbol is refused, shorten it or regenerate.
  • Managed Apple Accounts (Apple Business Manager / School Manager) follow the policy your administrator sets instead.

Salesforce (default org policy)

Salesforce user passwords under a new org's default password policy.

  • These are the defaults for a new org; admins can raise the minimum length and complexity org-wide or per profile.
  • Only ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~ count as special characters for the stricter complexity options — exactly the symbols we generate.
  • By default the last 3 passwords can't be reused. Passwords can be up to 16,000 bytes; we generate up to 128 characters.

Oracle Database (ora12c_verify_function)

Oracle Database user passwords checked by the standard ora12c_verify_function.

  • No verify function is active until a DBA assigns one to a profile (for example by running utlpwdmg.sql, which uses ora12c_verify_function).
  • The function also requires the password to differ from the database name and from the previous password by at least 3 characters — check those yourself.
  • Passwords containing symbols must be enclosed in double quotes in SQL, e.g. ALTER USER app IDENTIFIED BY "…". Oracle Database 23ai accepts passwords up to 1,024 bytes; check older releases' limits.

Why the rules differ

Older policies tried to make passwords harder to guess by requiring a mix of uppercase, lowercase, digits and symbols. People respond to those rules predictably: a capital first letter, a digit and an exclamation mark at the end. Attackers' cracking rules try exactly those patterns first. Current guidance from NIST SP 800-63B-4 therefore drops composition rules and asks for length instead, plus screening against lists of common and breached passwords.

Vendors move more slowly. Their defaults often still include character-type rules for compatibility with older clients and audit checklists. Symbol restrictions usually come from legacy systems, command-line tools or forms that mishandle quotes, backslashes or angle brackets.

One password that meets every rule above

If you need a password that works on all of these platforms, combine the strictest settings in the table:

  • At least 15 characters. That is the longest minimum in the table; 20 is comfortably within every documented maximum.
  • All four character types: uppercase, lowercase, digits and at least one symbol.
  • Only symbols every platform accepts: ! # $ % & ' ( ) * + - = @ [ ] ^ _ { | }.
  • No part of your name or username, which Active Directory and Oracle reject, no character three times in a row (Apple), and not the word “oracle”.

A randomly generated password of 20 characters with these settings satisfies every rule listed and is far beyond what can be guessed. You can create one with the password generator by choosing the length and excluding the other symbols, or pick a preset in the password policy generator, which does this for you and checks the result against each rule.

Setting a policy for your organization

If you write the policy, start from the current standard rather than an old checklist: a long minimum length, no forced composition or scheduled changes, a banned-password list, and multi-factor authentication. Our guides on NIST password guidelines and how often to change passwords explain the reasoning, and how long a password should be covers the numbers. Compliance frameworks such as PCI DSS may still require specific rules for systems in scope.

Sources

Keep reading