Skip to content

Allow enforcing minimum password strength #29913

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
elasticmachine opened this issue Feb 10, 2017 · 8 comments
Open

Allow enforcing minimum password strength #29913

elasticmachine opened this issue Feb 10, 2017 · 8 comments
Labels
>enhancement :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team

Comments

@elasticmachine
Copy link
Collaborator

Original comment by @loekvangool:

We should allow administrators to add more requirements to passwords. We now (5.0.0) enforce a minimum length of 6 (at least in UI), but many enterprises require more.

Taking inspiration from Wikipedia, we could support:

  1. the use of both upper-case and lower-case letters (case sensitivity)
  2. inclusion of one or more numerical digits
  3. inclusion of special characters, such as @, #, $
  4. prohibition of words found in a password blacklist
  5. prohibition of words found in the user's personal information
  6. prohibition of use of company name or an abbreviation
  7. prohibition of passwords that match the format of calendar dates, license plate numbers, telephone numbers, or other common numbers

I'm proposing that out of these we at least add support for 1, 2, 3. Bonus kudos if we support LINK REDACTED, which basically means: if the password reaches a minimum length of, say, 20, drop the other rules.

@elasticmachine elasticmachine added :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) >enhancement labels Apr 25, 2018
@ylasri
Copy link

ylasri commented Jul 22, 2019

  1. Force user to change password after first login

@mmmichal
Copy link

mmmichal commented Oct 6, 2020

is there any due date for this?

@joej
Copy link

joej commented Sep 17, 2021

Is this coming (ever) for this security-conscious product from a security-savvy company?
The SSO Wall Of Shame still has elastic listed

@jerelrichardson
Copy link

Has this issue been resolved/fixed in the current release?

@bytebilly
Copy link
Contributor

For users that require password policies, the best solution is to rely on an external identity provider instead of using the native realm. The native realm is generally used to get started or for simple scenarios, and it's not optimal for enterprise environments.

For example, users can be managed via LDAP or via SSO, using identity providers that have password policy options that can be enforced.

@adrake07
Copy link

I have a use case where we have both a small number of locally configured user accounts and also have AD integration. But more importantly my customer requires from a compliance standpoint that we need the local accounts to have some level of password complexity as well as having the passwords expire after a period of time. This isn't for the built-in accounts but for anything that would be used by a local admin/user, these accounts exist in the event there is an issue with AD authentication.

@Gelios7
Copy link

Gelios7 commented Dec 10, 2024

The implementation of a password policy for users is currently a pressing need. It is especially relevant for the Elastic SIEM solution, as it directly impacts audit compliance.

We kindly request the addition of a feature to configure password policies for users.

@irs055
Copy link

irs055 commented Apr 30, 2025

Any Progress on Password Policy ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team
Projects
None yet
Development

No branches or pull requests

10 participants