![Lead Image © ginasanders, 123RF.com Lead Image © ginasanders, 123RF.com](/var/ezflow_site/storage/images/archive/2021/62/protect-privileged-accounts-in-ad/po-24412-123rf-ginasanders_123rf-dokumentordner_mit_kette_und_schloss_und_verschlossen__resized.png/182266-1-eng-US/PO-24412-123RF-ginasanders_123RF-Dokumentordner_mit_Kette_und_Schloss_und_verschlossen__resized.png_medium.png)
Lead Image © ginasanders, 123RF.com
Protect privileged accounts in AD
Highly Confidential
In environments characterized by great complexity or the crucial importance of the connected systems, authentication must be clearly regulated. The need for protection is particularly great for privileged accounts such as domain or organization administrators. Active Directory (AD) offers, among other things, the Protected Users group and authentication policies for this purpose.
AD entered the market about 20 years ago with Windows 2000 Server. However, it was to be 13 years before Server 2012 R2 introduced one of the biggest security enhancements in the form of Kerberos authentication for highly privileged accounts. Part of the new functionality, the special treatment of the Protected Users group, was automatically introduced on upgrading the domain function level and caused irritation in some cases. Other features such as authentication policies are still unknown to many administrators.
Protecting Highly Privileged Accounts
For the normal user who logs on to their workstation or a shared computer without system admin rights to perform their tasks with the help of application programs, a standard login by Kerberos is quite good enough. The ticket-granting ticket (TGT) issued at login time is valid for 10 hours by default and is silently renewed when it expires. In principle, you can log in to any client system in the forest, provided the default configuration has not been changed. If older devices are in use, NT LAN Manager (NTLM) authentication is also possible, if necessary, and in most cases, perfectly acceptable.
However, the situation is different for a highly privileged account (Figure 1). "Highly privileged" does not necessarily mean a domain or schema admin. IT managers also need to protect an account adequately that has wide-ranging administrative and data access privileges on a system other than AD
...Buy this article as PDF
(incl. VAT)