Re: protect admins account

Andrey

You really only need to ask a question once, and when someone
has time and info to share they will do so.

If your environment has lockout defined, then any account will
get lock it the thresholds are triggered. One does not exempt a
selection of accounts from the lockout policy. However, one
can look at alternatives, such as requiring those account to use
smartcard login.

Many now recommend not having a lockout policy as it can
cause denial problems and increase helpdesk costs.

The general recommendation for highly priv'd accounts is to
use a form of two-factor authentication (eg. smartcard) or if
using username/password then use long passphrases (such as
"This iS my 1 and only pwd!@#" or better yet, include some
alt key combos).

"Andrey Vasylenko" <Andrey Vasylenko@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:EF903990-890B-4EDE-8615-35EBD81F4C09@xxxxxxxxxxxxxxxx
Hi!
How can I protect admins account from lock out in case
of external intrusion?
What methods MS recommend to protect admins
password and accont?

Regards!



.

Relevant Pages

  • Re: Username Vulnerability???
    ... Open Server Manager> highlight the PDC ... Password Policy and Account Lockout Policy are both ...
    (microsoft.public.windows.server.general)
  • Re: OU group policy and how to use ldapsearch to find GPO settings
    ... The account is a domain account. ... Account Policies effective for all domain accounts. ... Your ldap query is seeing the settings that are in use for the domain. ... If I configure the account lockout policy in the default domain policy, ...
    (microsoft.public.windows.group_policy)
  • Re: Replication of password resets/unlocks
    ... Assuming that the reg key AvoidPDCOnWan isn't set passwords will be sent immediately out of band to the PDC when changed on a local machine. ... I haven't dug into the specifics but I believe that occasionally it will check with the PDC to see if the account has been unlocked but not for every auth attempt, this is so a PDC will not be overwhelmed by attempts to auth a locked account. ... The idea behind auto lockout is to prevent brute force systems from sending thousands of passwords an hour to crack a password, if that is the case, then setting the lockout policy to 25 bad attempts and locking the account out for say 5 minutes is just as good from a security perspective; it will seriously impact the ability for a brute force attack. ... From the usability standpoint, it will only lockout users who have really screwed up with their password and give them just enough time to realize they really screwed up but take less time than a call to the helpdesk for an unlock and replication of the unlock meaning that if they call the helpdesk for a rest, the only mechanism that comes into play is the one in the first paragraph above which works fine. ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 Server Client/Delegation and Data Issues
    ... "reveal" the read and write lockout time permissions. ... I have an account that I ... default - no mention of domain users. ...
    (microsoft.public.windows.server.active_directory)
  • Re: lockaccount flag in userAccountControl does not change
    ... Neither has explicit support for dealing with lockout though. ... The IADsUser interface in ADSI attempts to support it, ... checks to see if lockoutTime has a value or not and assumes the account is ... For more information on unlock, ...
    (microsoft.public.windows.server.active_directory)