AuthLite Interactive Documentation
Quick Start: Install and protect Domain Admins AuthLite Features Supported Tokens Installation Configuration Administer tokens How to Log In
Fig. 1) Require 2-factor Authentication for Domain Admins
Fig. 1) Require 2-factor Authentication for Domain Admins
Fig. 2) Create an emergency recovery Administrator
Fig. 2) Create an emergency recovery Administrator

Properly securing Domain Admin credentials is an extra challenge: any attacker who gains a foothold as a domain admin might be able to alter any restrictions that have been placed onto their account.

Securing Domain Admin accounts

With AuthLite you can solve this problem by removing privileged groups from your domain admin accounts, and letting AuthLite grant the Domain Admins group SID temporarily when the user provides a 2-factor logon.  The DA SID is only included within the logon session token, and the static membership of the user object remains unprivileged.  See (Fig. 1) for a walk-through of changing Domain Admins to AuthLite-controlled "AuthLite Domain Admins".

Note: You should keep one Administrator account outside the control of AuthLite for emergency recovery purposes (see Fig. 2). Create and store a long random password for it and don't use that account (even for services).

Other administrative accounts

You can create additional group pairs and use the same strategy to control effective membership in other groups to which you've delegated power in the domain.

Service accounts

Services scheduled tasks are automated, and they must be able to log on without human interaction.  Therefore by necessity they store the credentials used to log themselves on.  If you have any service accounts that run as Domain Admin or other powerful group, that means any compromise of a system running that service can take over your whole domain! Run services and tasks as a lower privilege user if possible. Restrict allowed logon types and locations using group policy User Rights Assignment.

Auditing your power group membership

Through nested group membership, many organizations don't fully know which accounts have power over the domain.  In the AuthLite Admin Powershell, you can run the command Print-Users-In-Power-Groups to enumerate each powerful account in the domain, where it derives power, and some advice about mitigating risks.

Convert a user to be "AuthLite controlled"

In the AuthLite Admin Powershell, you can run the command Convert-User-Groups to pull a user out of their natural power groups and add them to whatever AuthLite equivalent groups you've defined in the AuthLite User Group Pairs dialog (i.e. AuthLite DA).  You can reverse the conversion by adding "-toAuthLite $false"