Set password policy windows server 2012

4sysops - The online community for SysAdmins and DevOps

  • This topic has 1 reply, 2 voices, and was last updated 5 years, 5 months ago by
    Set password policy windows server 2012
    Luc Fullenwarth.

  • Author

    Posts

    • Mon, Jun 26 2017 at 7:04 pm #178418

      Shan

      Participant

      Member Points: 143

      Hello All

      I am new to GPO and I was asked to setup the following in a Win Server 2012R2 envionment.

      This small company have like 10 users and need to setup a password policy like every 90 days passwords need to be changed for ALL users except for the CEO who is omitted from this rule.

      can anyone show me how to accomplish this ? what is the best solution here? is it GPO?

    • Mon, Jun 26 2017 at 9:39 pm #178427

  • Author

    Posts

  • You must be logged in to reply to this topic.

Create Account

Set password policy windows server 2012

What is fine-grained password policy? And how can I configure fine-grained password policy with the Active Directory Administrative Center (ADAC)?

Fine-grained password policy was introduced in Windows Server 2008 to overcome the limitation of only one password policy for a domain. Fine-grained password policies do exactly what they say on the tin, allowing system administrators to apply different password policies to groups of users in an Active Directory domain.

Configuring Fine-Grained Password Policy with the ADAC

Prior to Windows Server 2012, it was only possible to configure fine-grained password policies from the command line. Fortunately, a graphical user interface for fine-grained password policy is included in Windows Server 2012’s Active Directory Administrative Center (ADAC).

Before you can use fine-grained password policy, make sure that your domain is set at the Windows Server 2008 domain functional level or higher. For more information on setting domain and forest functional levels, see “Raising Windows Server 2008 Active Directory Domain and Forest Functional Levels” on the Petri IT Knowledgebase.

  • Login to a Windows Server 2012 domain controller as a domain administrator.
  • If it’s not already open, start Server Manager using the icon on the desktop taskbar or from the Start screen.
  • In Server Manager, select Active Directory Administrative Center from the Tools menu.
  • In the left pane of ADAC, click ad (local).
  • In the central pane, double-click the System container.
  • Now right-click Password Settings Container and select New > Password Settings from the menu.
  • Enter a name for the policy in the Create Password Settings dialog.

Set password policy windows server 2012

Enter a name for the policy in the Create Password Settings dialog.

  • Enter a number for the Precedence box. Policies with lower precedence index numbers take priority over those with higher numbers.
  • Now configure the remainder of the password policy settings as required.
  • When you’re done, click Add in the bottom right corner.
  • In the Select Users or Groups dialog, type the name of the group you want to apply the new policy to and click OK.
  • Now click OK in the Create Password Settings dialog.

If you double-click the Password Settings Container in ADAC, you’ll now see the new policy along with its precedence index.

With cyberattacks exploding around the world, it’s more important than ever for organizations to have a robust password policy. Hackers often gain access to corporate networks through legitimate user or admin credentials, leading to security incidents and compliance failures. In this article, we will explore how to create and maintain a strong and effective Active Directory password policy.

How Attackers Compromise Corporate Passwords

Adversaries use a variety of techniques to compromise corporate passwords, including the following:

  • Brute force attack — Hackers run programs that enter various potential passwords for a particular user account until they hit upon the right one.
  • Dictionary attack — This is a specific form of brute force attack that involves trying words found in the dictionary as possible passwords.
  • Password spraying attack — Adversaries try common passwords against multiple user accounts to see if they work.
  • Credential stuffing attack — Hackers use automated tools to enter lists of credentials against various company login portals.
  • Spidering — Adversaries collect as much information as possible about a hacking target and then try out passwords created using that data.?

How to View and Edit Active Directory Password Policy

To defend against these attacks, organizations need a strong Active Directory password policy. Password policies define rules for password creation, such as minimum length, complexity (like whether a special character is required) and the length of time the password lasts before it must be changed to a different one.

To configure a domain password policy, admins can use Default Domain Policy, a Group Policy object (GPO) that contains settings that affect all objects in the domain. To view or edit this GPO:

  1. Open the Group Policy Management Console (GPMC).
  2. Expand the Domains folder, choose the domain whose policy you want to access and choose Group Policy Objects.
  3. Right-click the Default Domain Policy folder and click Edit.
  4. Navigate to Computer Configuration à Policies à Windows Settings à Security Settingsà Account Policies à Password Policy.?

Alternatively, you can access your domain password policy by executing the following PowerShell command:

Get-ADDefaultDomainPasswordPolicy?

Remember, any changes you make to a domain’s default password policy apply to every account in that domain. You can create and manage fine-grained password policies using the Active Directory Management Center (ADAC) in Windows Server. ?

Understanding AD Password Policy Settings

Here are the six password policy settings and their default values:

  • Enforce password history — Default is 24. This setting specifies the number of unique passwords users must create before reusing an old password. Keeping the default value is recommended to reduce the risk of users having passwords that have been compromised.
  • Maximum password age — Default is 42. This setting establishes how long a password can exist before the system forces the user to change it. Users typically get a pop-up warning when they reach the end of their password expiration period. You can check this setting through PowerShell by executing the command net user USERNAME/domain. Keep in mind that forcing frequent password changes can lead to users writing their passwords down or simply appending the month to a stem word they reuse, practices that actually increase security risks. Setting “Maximum password age” to 0 means that passwords never expire (which is generally not recommended).
  • Minimum password age — Default is 1 day. This setting specifies how long a password must exist before the user is permitted to change it. Setting a minimum age keeps users from resetting their password repeatedly to circumvent the “Enforce password history” setting and reuse a favorite password immediately.
  • Minimum password length — Default is 7. This setting establishes the fewest number of characters a password can have. While shorter passwords are easier for hackers to crack, requiring really long passwords can lead to lockouts from mistyping and to security risks from users writing down their passwords. Best practices recommend a minimum password length of at least 8.
  • Complexity requirements — Default is Enabled. This setting details the types of characters a user must include in a password string. Best practices used to recommend leaving this setting enabled, but password length is now seen as a better strategy than complexity or frequent changes. Complexity requirements typically require the password to include a mix of:
    • Upper or lowercase letters (A through Z and a through z)
    • Numeric characters (0–9)
    • Non-alphanumeric characters like $, # or %
    • No more than two symbols from the user’s account name or display name
  • Store passwords using reversible encryption — Default is Disabled. This setting offers support for apps that require users to enter a password for authentication. Admins should keep this setting disabled because enabling it would allow attackers familiar with how break this encryption to log into the network once they compromise the account. As an exception, you can enable this setting when using Internet Authentication Services (IAS) or the Challenge Handshake Authentication Protocol (CHAP).

Fine-Grained Policy and How It’s Configured

Older versions of AD allowed the creation of just one password policy for each domain. The introduction of fine-grained password policies (FGPP) has made it possible for admins to create multiple password policies to better meet business needs. For example, you might want to require admin accounts to use more complex passwords than regular user accounts. It’s important that you define your organizational structure thoughtfully so it maps to your desired password policies.

While you define the default domain password policy within a GPO, FGPPs are set in password settings objects (PSOs). To set them up, open the ADAC, click on your domain, navigate to the System folder and then click on the Password Settings Container.

NIST SP 800-63 Password Guidelines

The National Institute of Standards (NIST) is a federal agency charged with issuing controls and requirements around managing digital identities. Special Publication 800-63B covers standards for passwords. Revision 3 of SP 800-63B, issued in 2017 and updated in 2019, is the current standard.

These guidelines provide organizations with a foundation for building a robust password security infrastructure. NIST recommendations include the following:

  • Require user-generated passwords to be at least 8 characters long (6 for machine-generated ones).
  • Allow users to create passwords up to 64 characters long.
  • Allow users to use any ASCII/Unicode characters in their passwords.
  • Disallow passwords with sequential (“12345” or “abcd”) or repeated (“kkkk”) characters.
  • Do not require frequent password changes. Although for years, many organizations have required users to change their passwords frequently, this policy often leads to users making incremental changes to a base password, writing their passwords down, or experiencing lockouts because they forget their new passwords. Accordingly, the latest NIST 800-63B standards call for using password expiration policies carefully. More recent research suggests that better alternatives include using banned password lists, using longer passphrases and enforcing multi-factor authentication (MFA) for additional security.

AD Password Policy Best Practices

Summary of Best Practices

  • Set a minimum password length of at least 8 characters.
  • Enforce a password history policy that looks back at the last 10 passwords of a user.
  • Make the minimum password age 3 days to keeps users from quickly rotating through historical passwords and setting a previous one.
  • Check proposed new passwords against banned password lists, lists of breached passwords and password dictionaries.
  • Reset local admin passwords every 180 days (consider using the free Netwrix Bulk Password Reset tool for that).
  • Reset device account passwords at least once per year.
  • Require passwords for domain admin accounts to be at least 15 characters long.
  • Set up email notifications to let users know passwords are about to expire (the free Netwrix Password Expiration Notifier tool can help).
  • Consider creating granular password policies to link with specific organizational units instead of editing the Default Domain Policy settings.
  • Consider using password management tools to store passwords.
  • Enable users them to change passwords via a web browser and help them pick compliant new passwords.
  • Set up account lockout policies to avoid brute force attacks.

For more information, read our password policy best practices for strong security in AD.

User Training

User training is as crucial as your password policy. Educate your users on the following rules of behavior:

  • Don’t write down passwords. Instead, pick strong passwords or passphrases you can recall easily, and use a password management tool.
  • Don’t type your password when anyone is watching.
  • Understand that URLs beginning with “HTTPS://” are more secure than those that begin with “HTTP://”.
  • Don’t use the same password for multiple websites that provide access to sensitive information.

FAQ

How do I find and edit my Active Directory password policy?

You can find your current AD password policy for a specific domain either by navigating to Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Account Policies -> Password Policy via the management console, or by using the PowerShell command Get-ADDefaultDomainPasswordPolicy.

Are passwords encrypted in Active Directory?

Yes. Passwords created by a user go through a hashing algorithm that encrypts them.

What is Active Directory password complexity?

Complexity requirements control the characters that cannot or cannot be included in a password. For example, users might be prevented from using sequential characters or digits, or required to include at least one number and one lowercase letter in the password.

What is Windows Server password policy?

Windows Server password policy controls passwords for accessing Windows servers.

How do I find, edit or disable a password policy in Windows Server?

Locate the GPO through the Group Policy Management Console and click Edit.

What is a good password policy?

Best practices include the following:

  • Make users create at least 10 new passwords before reusing an old one.
  • Compare proposed new passwords against lists of breached passwords and password dictionaries.
  • Apply a minimum password age of 3 days.
  • Make users create passwords that are at least 8 characters long.
  • Disable reversible encryption.

Set password policy windows server 2012

Jeff is a former Director of Global Solutions Engineering at Netwrix. He is a long-time Netwrix blogger, speaker, and presenter. In the Netwrix blog, Jeff shares lifehacks, tips and tricks that can dramatically improve your system administration experience.

Set password policy windows server 2012