First published on TechNet on Oct 31, 2017
Hello, Paul Bergson back again with today's topic of preventing your Domain Administrators and other privileged identities from logging into Tier 1 and Tier 2 devices. Credential theft protection is always an important step in protecting the enterprise. While your administrators are your most trusted employees within the IT enterprise, they may not always use good judgment when doing day to day tasks. ALL privileged users should have at least two accounts, one for daily tasks which need internet and e-mail access and one or more privileged accounts that are used to performed tasks which require elevated permissions and should have no access to internet or e-mail. In the case of Tier 0 accounts, they should only be authenticating to Tier 0 assets. Beyond the expectation that these elevated user accounts should not be used to log on to lower Tier assets, protection measures should be put in place to guard against administrators who want to take short cuts to get the job done quickly. What are Tier'd devices you ask? Well that is a very good question. Enterprises should define "Credential" layers where controls are put in place to control authentication to devices.
The reason to create credential Tier'ing is so that privileged accounts are never exposed to untrusted devices. Any device would be considered untrusted if it has ever been exposed to Internet browsing or e-mail access. These activities could compromise the user's device without their knowledge and credential harvesting could occur once a privileged user authenticates to this device.
So now that you have some background on the credential Tier model and understand why it is important to prevent privileged users from authenticating on untrusted devices, let's look at some of the ways enterprises can control Tier 0 accounts from logging onto lower Tier devices.
Just because you remove the DA from the Local Admins group, you are still NOT preventing that identity from authenticating onto the device. Looking at figure A, the domain admin has authenticated onto the device.
The administrator was not prevented from logging onto the machine and since the domain administrator is logged onto the machine the DA credential hash will still be cached on the device unless Credential/Remote Credential Guard is in place. But, as can be seen in Figure B the privileges are now reduced to a standard user. Figure A Figure B "Domain Admins are, by default, members of the local Administrators groups on all member servers and workstations in their respective domains. This default nesting should not be modified for supportability and disaster recovery purposes. If Domain Admins have been removed from the local Administrators groups on the member servers, the group should be added to the Administrators group on each member server and workstation in the domain." *1 If the Deny's as defined below for domain administrator's were put into place, it will prevent the identity from logging on. Deny Domain and Enterprise Administrators from authenticating to Tier 1 and Tier 2 assets via GPO:
When the deny measures above are put into place, this will also prevent the administrator from opening a cmd prompt via "RunAs" and thereby caching the elevated credentials on the local workstation. *2 If you have Tier 1 and Tier 2 privileged users who don't have a separate device (Privileged Access workstation *3 ) when they are using their elevated credentials and they are connecting to remote devices, it would be advised to protect their credentials via Remote Credential Guard or Restricted Admin mode. "Introduced in Windows 10, version 1607, Windows Defender Remote Credential Guard helps you protect your credentials over a Remote Desktop connection by redirecting Kerberos requests back to the device that's requesting the connection. It also provides single sign-on experiences for Remote Desktop sessions. Administrator credentials are highly privileged and must be protected. By using Windows Defender Remote Credential Guard to connect during Remote Desktop sessions, if the target device is compromised, your credentials are not exposed because both credential and credential derivatives are never passed over the network to the target device." *4 If your users are not using Windows 10 or there is the threat of gaining access to an open channel and create a session on the remote user's connection, we instead recommend utilizing /restrictedAdmin mode. "For helpdesk support scenarios, RDP connections should only be initiated using the /RestrictedAdmin switch. This helps ensure that credentials and other user resources are not exposed to compromised remote hosts." *4 The rdp option for RestrictedAdminMode was introduced in Windows 8.1/2012 R2 and was back ported via KB2871997 to Windows 7/Server 2008 R2. *5
Starting with Windows Server 2012 R2 a new feature was added to be able control accounts from logging onto specific devices utilizing Authentication Policies and Authentication Policy Silos. "Authentication policies and authentication policy silos are two of these new features and they help administrators define which user accounts can be restricted to log on to specific systems with those accounts. Administrators can configure these new Windows Server 2012 R2 features in the Active Directory Administrative Center or in PowerShell." *6 Authentication Policy Silo's define the accounts that are to be restricted from authenticating on devices. There is one account that cannot be Silo'd and that is the domain "Administrator" (DA). The DA can be added to the Silo, but it will not be blocked from logging onto any device. Similar to how removing the DA identity from the local "Administrators" group didn't prevent the DA from logging onto the device. Authentication Policies define access control to determine the Silo to use as well as Kerberos properties, including the Kerberos ticket lifetime. The ticket has a minimum lifetime of 15 minutes and a maximum lifetime of 4 hours once the ticket expires credentials are required to be re-entered, the ticket is not renewable. Part of the prerequisites to using "Silos" is that the DC's are running at least Windows Server 2012 R2, for a complete set of prerequisites and how to install, follow the guidance linked below. *6 How Silos work is that you need to need to enable claims on both the DC and the devices to control via Group Policy. Then you will define an Authentication Policy which will include ticket lifetime and the Silo related to the Policy. Obviously, this is a two-step process, since the Silo hasn't been created yet. You will then want to create a Silo and define the Privileged Accounts and the devices that they will be allowed to authenticate too. Each Silo can link to an unique "Authentication Policy" for Users, Managed Service Accounts (MSA) and Computers. If you notice in the picture below all the "Permitted" users have been added to the "Protected Users Group" (PUG). This isn't a requirement of Silo's but rather a recommendation. The PUG adds an additional layer of security to the users that belong to this group. Restrictions include while belonging to this group NTLM, CredSSP and WDigest protocols are blocked from being utilized. User accounts are not allowed to be "Delegated" and finally the Kerberos protocol will not use the weaker DES or RC4 encryption types in the pre-authentication process. There is a great Blog by Jerry Devore on PUG that can be found on this site. *7
Well there you have it. A couple of easy ways to protect your most prized credentials in the enterprise. You can then use these steps to start to prevent Tier 1 admins from authenticating to Tier 2 devices in a similar manner than was just presented. Hopefully you found this useful and can find the opportunity to deploy this simple credential theft protection. It is an easy win with a big payback, in that your privileged credentials are no longer exposed on untrusted devices. References:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.