Due to spams hit some mailboxes in our mail serves, because
of users weak passwords,
I want to update you that; in our Company network we
applied new password policies as follow;
The Passwords must meet complexity requirements policy setting determines whether passwords must meet
a series of guidelines that are considered important for a strong password.
Enabling this policy setting requires passwords to meet the following
requirements:
- Passwords may not contain the
user's samAccountName (Account Name) value or entire displayName (Full
Name value). Both checks are not case sensitive.
The samAccountName is checked in its entirety only to determine whether it is part of the password. If the samAccountName is less than three characters long, this check is skipped.
The displayName is parsed for delimiters: commas, periods, dashes or hyphens, underscores, spaces, pound signs, and tabs. If any of these delimiters are found, the displayName is split and all parsed sections (tokens) are confirmed to not be included in the password. Tokens that are less than three characters are ignored, and substrings of the tokens are not checked. For example, the name "Erin M. Hagens" is split into three tokens: "Erin", "M", and "Hagens". Because the second token is only one character long, it is ignored. Therefore, this user could not have a password that included either "erin" or "hagens" as a substring anywhere in the password. - The password contains characters
from three of the following categories:
- Uppercase
letters of European languages (A through Z, with diacritic marks, Greek
and Cyrillic characters)
- Lowercase
letters of European languages (a through z, sharp-s, with diacritic
marks, Greek and Cyrillic characters)
- Base
8 digits (0 through 7)
- Non-alphanumeric
characters (special characters) (for example, !, $, #, %)
- Any
Unicode character that is categorized as an alphabetic character but is
not uppercase or lowercase.
ΓΌ
This password policy it
should be apply for all Algosaibi network clients, no weak or easy password
anymore. At
user next login policy will be apply.
Example of complicated
password:
9870lock&runNOW
DAR*door@4652
I want from you
to help & guide users for easy change of their passwords.
No comments:
Post a Comment