Password Policies (Pro)

Version: 1.2.1 ProLast Updated: November 2025Difficulty: IntermediateTime Required: 30 minutes

Overview

Password Policies in Attributes User Access Pro enforce strong password requirements, expiration rules, and complexity standards to protect user accounts and meet compliance requirements.

Why Use Password Policies?

Security Benefits

✓ Prevent Weak Passwords

Stop users from using “password123” or other easily guessable passwords.

✓ Regulatory Compliance

Meet HIPAA, SOC 2, PCI-DSS, ISO 27001, and other compliance standards.

✓ Reduce Breaches

Strong passwords significantly reduce successful attack rates.

✓ Professional Standards

Demonstrate enterprise-grade security to clients and auditors.

Accessing Password Policy Settings

Navigate to settings:


WordPress Admin → Settings → Attributes User Access → Security → Password Policies

Password Complexity Requirements

Minimum Length

Configuration:

Minimum Password Length: [12] characters

Recommended lengths by security level:

Security Level Min Length Use Case
Low 8 characters Public content sites
Medium 12 characters Business websites
High 16+ characters Financial/Healthcare

Character Type Requirements

Available options:

☐ Require uppercase letters (A-Z)

☐ Require lowercase letters (a-z)

☐ Require numbers (0-9)

☐ Require special characters (!@#$%^&*)

☐ Block common passwords

☐ Block dictionary words

Example Password Configurations

Standard Business

✓ Minimum 12 characters

✓ Uppercase required

✓ Lowercase required

✓ Numbers required

✓ Special characters required

Example: MySecure2025Pass!

High Security (Healthcare/Finance)

✓ Minimum 16 characters

✓ All character types required

✓ Block common passwords

✓ Block dictionary words

✓ Password expiration: 90 days

Example: MyH0spit@l2025Secure!

User-Friendly (Basic Protection)

✓ Minimum 10 characters

✓ Uppercase required

✓ Numbers required

Special characters optional

Example: MyPassword2025

Password Expiration Rules

Force Regular Password Changes

Configuration:

Password Expiration: [90] days

Warning Period: [14] days

Grace Period: [7] days

How Expiration Works

Timeline:

Days 1-76:

Password valid, no warnings

User logs in normally

Days 77-90 (Warning Period):

User sees warning on login:

“Your password will expire in X days”

Can still log in

Prompted to change password

Days 91-97 (Grace Period):

“Your password has expired”

Can log in but forced to change password

Redirected to password change page

Day 98+ (Hard Expiration):

Cannot log in

Must contact administrator

Password reset required

Expiration Email Notifications

Automatic emails sent:

  • 14 days before: “Password expires soon”
  • 7 days before: “Password expires in 1 week”
  • 1 day before: “Password expires tomorrow”
  • On expiration: “Password has expired”
  • After grace period: “Account locked”

Recommended Expiration Periods

Industry/Type Expiration Rationale
Healthcare (HIPAA) 90 days Compliance requirement
Financial (PCI-DSS) 90 days Security standard
Corporate Business 90-180 days Industry best practice
E-Commerce 180 days Balance security/UX
Membership Sites Never User convenience

Password History Settings

Prevent Password Reuse

Configuration:

Remember Last: [5] passwords

How it works:

  • System stores hashed versions of previous passwords
  • User cannot reuse any stored passwords
  • Encourages creating new, unique passwords
  • Prevents password cycling (changing back and forth)

Example Scenario

User’s password history:

  • OldPassword2023! (oldest)
  • MySecure2024Pass
  • NewPassword2024!
  • UpdatedPass2025
  • CurrentP@ss2025 (current)

❌ Cannot reuse any of these 5 passwords

✅ Must create completely new password

Recommended History Sizes

Low security: 3 passwords

Standard business: 5 passwords

High security: 10 passwords

HIPAA/PCI compliance: 12+ passwords

Password Strength Meter

Real-Time Visual Feedback

Strength levels:

Weak ●○○○○ – Add more characters

Fair ●●○○○ – Add uppercase/numbers

Good ●●●○○ – Add special characters

Strong ●●●●○ – Excellent!

Very Strong ●●●●● – Outstanding security!

Configuration Options

Display settings:

☑ Show strength meter

☑ Show strength text

☑ Block weak passwords

☑ Require “Good” or better

Color coding:

Weak: Red (#dc3545)

Fair: Orange (#fd7e14)

Good: Yellow (#ffc107)

Strong: Light Green (#28a745)

Very Strong: Dark Green (#155724)

Compliance Templates

Pre-Configured Standards

Available templates:

  • HIPAA Compliance
  • SOC 2 Compliance
  • ISO 27001 Compliance
  • PCI-DSS Compliance

HIPAA Compliance Template

Health Insurance Portability and Accountability Act


Minimum Length: 12 characters
Character Requirements: All types required
Password Expiration: 90 days
Password History: 10 passwords
Account Lockout: 5 attempts
Session Timeout: 15 minutes
2FA: Required for administrative access

To apply:

  • Go to Password Policies
  • Click “Load Template”
  • Select “HIPAA Compliance”
  • Review settings
  • Click “Apply Template”
  • Save changes

SOC 2 Compliance Template

Service Organization Control 2


Minimum Length: 14 characters
Character Requirements: All types required
Password Expiration: 90 days
Password History: 12 passwords
Account Lockout: 3 attempts
Session Timeout: 30 minutes
2FA: Required for privileged users
Audit Logging: Comprehensive

PCI-DSS Compliance Template

Payment Card Industry Data Security Standard


Minimum Length: 12 characters
Character Requirements: All types required
Password Expiration: 90 days
Password History: 4 passwords
Account Lockout: 6 attempts
Inactivity Timeout: 15 minutes
2FA: Required for all access

ISO 27001 Compliance Template

Information Security Management


Minimum Length: 12 characters
Character Requirements: All types required
Password Expiration: 90 days
Password History: 8 passwords
Account Lockout: 5 attempts
Session Timeout: 20 minutes
2FA: Required for admin accounts
Regular Security Audits: Enabled

Implementation Strategy

Gradual Rollout Approach

Phase 1: Soft Launch (Week 1-2)

Enable password strength meter

Show recommendations

Don’t enforce requirements yet

Gather user feedback

Educate users

Phase 2: Warning Period (Week 3-4)

Display policy requirements

Show compliance status

Send notification emails

Allow grace period

Provide support resources

Phase 3: Full Enforcement (Week 5+)

Enforce all requirements

Block non-compliant passwords

Require password changes

Monitor compliance

Provide ongoing support

User Communication

Announcement Email Template

Subject: Important: New Password Requirements Effective [Date]

Dear [User Name],

To enhance the security of your account, we’re implementing

new password requirements starting [Date].

New Password Requirements:

✓ Minimum 12 characters

✓ At least one uppercase letter (A-Z)

✓ At least one lowercase letter (a-z)

✓ At least one number (0-9)

✓ At least one special character (!@#$%^&*)

What You Need to Do:

  • Log in to your account by [Date]
  • Go to Profile → Change Password
  • Create a new password meeting these requirements
  • Save your new password securely

Why This Change?

These requirements protect your account from unauthorized

access and help us meet security compliance standards.

Need Help?

• FAQ: [link]

• Video Tutorial: [link]

• Contact Support: [email/phone]

Thank you for helping us keep your account secure!

Best regards,

[Your Organization] Security Team

Best Practices

For Administrators

Test Before Enforcing

Enable policies on test accounts first. Verify no unexpected issues before site-wide rollout.

Communicate Early and Often

Notify users at least 2 weeks before enforcement. Provide clear instructions and support resources.

Monitor Compliance

Check audit logs regularly. High failure rates indicate user confusion or overly strict policies.

Balance Security and Usability

Don’t make requirements so complex that users write passwords down. Find reasonable middle ground.

For Users

Creating Strong Passwords:

Good strategies:

✓ Use passphrases: “MyDog Loves2Run inPark!”

✓ Substitute characters: “@” for “a”, “3” for “e”

✓ Combine random words: “Purple-Elephant-47-Moon”

✓ Use password manager to generate

Bad strategies:

❌ Simple substitutions: “P@ssw0rd”

❌ Sequential characters: “Abcd1234!”

❌ Personal information: “JohnSmith1980”

❌ Common patterns: “Qwerty123!”

Troubleshooting

Users Cannot Meet Requirements

Solutions:

    • Provide password examples that work
    • Create step-by-step tutorial with screenshots
    • Offer password manager recommendations
    • Provide IT support hotline
    • Consider temporarily relaxing requirements

High Support Ticket Volume

Solutions:

    • Create comprehensive FAQ page
    • Record video tutorial
    • Send proactive educational emails
    • Extend grace period
    • Improve error messages with examples

Password Expiration Causing Lockouts

Solutions:

    • Increase warning period (21-30 days)
    • Send more frequent reminder emails
    • Extend grace period (14 days)
    • Allow self-service password reset
    • Improve notification email visibility