|
Guy recommends :
Find out which of your VMs are a waste of space and which VMs need more resources.
|
Security Group Policies - Account Policies SettingsSecurity Group Policies - Account Policies Settings (Domain Level)Perhaps you are familiar with setting password length and account lockout
from your NT 4.0 days? This section will guide you through these and
many more security group policies for Active Directory Users. Do remember that the Account Policies on this page must be configured at the Domain level. If you try to set these polices for an OU, then you will be disappointed. This is because the Security Settings at the OU level have no affect on Domain Users. Security Group Policy TopicsUser Configuration Windows Settings Security Settings Account Policies ‡ Group Policy Security SettingsBefore you start experimenting, I urge you to take advantage of
Microsoft's built in templates. What I suggest is that you add the
Security Template snap-in to your MMC. Inside the template folder are half a dozen files with settings for each type of machine. The first task is to choose the nearest template to your situation, for example 'securedc' would be suitable for a domain controller. Once you have selected a template, then immediately right click, 'Save AS', and give it a new name, for example MyDomain. This technique will preserve the built-in settings so that you can always start again with a clean template. Your chosen template will act as a base for creating your own Security Settings. When you are happy with your policy, load your settings with the Security Configuration and Analysis snap-in (see diagram).
Security Settings -> Account Policies* Guy's Top Three Password Group PoliciesPassword PolicyThis password section really does come as a package, I will explain why you need to consider how these Group Policies interact as we go along. The first decision is, 'Minimum Password Length'; 8 letters is considered long enough by most security experts. To make it harder for hackers to guess passwords you can enforce - 'Passwords must meet complexity requirements'. This means that the word must contain 3 of these characteristics, UPPERCASE, lowercase, number or non-alphanumeric e.g. @ symbols. At first I thought that it would be too much to expect people to remember such complex passwords, but as time went on I realized, we humans are a most adaptable animal and we do learn to cope with passwords like P@ssw0rd or better a phrase like: B33r & sk1ttl3s. Once we set the length and complexity, the next decision is how often do users have to change their passwords? 60 days, 90 days - you decide. To prevent users just switching between two passwords, you can set * 'Enforce Password History'. Just when you think you have the users under control, some 'clever Dick' cycles through 24 passwords in their tea break and comes back to the original password. To stop them 'thumbing their nose' at you, fix the minimum password age at 1 day. If you set the 'Minimum Password Age' too long then that can create new problems. Specifically, if the user forgets their old password and they are given a new password which must be changed at first logon. No can do. They would either have to wait days to logon, or else the support staff would have to remove the tick next to 'Change Password at logon'.
Guy Recommends: Solarwinds' Log & Event Management Tool
| ||||
Custom Search
|
Guy Recommends:
|
|
Home Copyright © 1999-2012 Computer Performance LTD All rights reserved Please report a broken link, or an error. | |