Re: best practices: builtin administrator account in AD
From: ] (dlaflotte_at_criticalsites.com)
Date: 05/25/05
- Next message: Peter Foldes: "Re: Can Someone please explain"
- Previous message: MF: "Autoenrollment failed for Domain Controller"
- In reply to: mocity: "best practices: builtin administrator account in AD"
- Next in thread: Roger Abell: "Re: best practices: builtin administrator account in AD"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 25 May 2005 10:12:41 -0400
Mocity,
I'm the lead hacker in a corporate hacking division for a consulting
group. So I can tell you that renaming the account is a good first step but
will only stop the entry level hackers. The Administrative SID will always
be the same even if the account is renamed (and the SID can be used for many
devious things). I usually recommend you not disable the account but
instead use VERY strong passwords for this account. You are allowed a 127
character password (last byte is used for null termination). So I would say
you take an entire paragraph from a book with odd characters or just 127 odd
characters and make that the password. Then write this down and lock it in
a safe somewhere. At 127 characters there is no known array of computers
that would be able to crack that password in our lifetime. Keep in mind
that passwords that are under 14 characters are very bad (NTLM Hash is
stored under 14 chars and is easy to crack).
Hope this helps,
Duane Laflotte
MCSE, MCSD, MCDBA, MCSA, MCT, MCP+I
dlaflotte@criticalsites.com
http://www.criticalsites.com/dlaflotte
"mocity" <mocity@discussions.microsoft.com> wrote in message
news:EB7BFBE9-A467-4BC3-8F1F-6284EF9A3DE9@microsoft.com...
> Hi,
> I understand that renaming the builtin AD administrator account is a good
> idea, but is disabling this account and additional good security measure?
I
> would have no problem disabling this account, except for the fact if all
> other Domain Administrative accounts got locked out I would have no way of
> logging to the domain with admin privileges except through rebooting a DC
> into Safe Mode which enables the builtin administrator account---but this
> would be a hassle. (i'm sort of paranoid of a scenario where a malicious
user
> locked out all my admin accounts, and me having to do this).
> is having this account enabled a security risk, because it cannot be
locked
> and thus gives a person infinite attempts at cracking the password?
> thanks.
- Next message: Peter Foldes: "Re: Can Someone please explain"
- Previous message: MF: "Autoenrollment failed for Domain Controller"
- In reply to: mocity: "best practices: builtin administrator account in AD"
- Next in thread: Roger Abell: "Re: best practices: builtin administrator account in AD"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|