Dealing with users gone bad…

We have all been there when someone that gets paid more than you do runs in and says “We need to remove User X from the network and lock them out of their PC to preserve evidence!!!”. If not, you will be.

So…aside from any 3rd party endpoint software you might have in that environment…what do you do? I have a list of steps, native Windows functions, that I have found helps eliminate avenues for User X’s continued use of ComputerX.

1. Disable User X’s Active Directory Account

This can be done in a number of ways but this post has a PowerShell tag so I recommend downloading Remote Server Administration Tools for your flavor of Windows if you don’t have it already. Then it is a simple matter of …

 Disable-ADAccount -Identity "UserX" 

2. Delete All Cached Credentials

$credential = Get-Credential -Credential "DOMAIN\adminacct"
Enter-PSSessio n -ComputerName ComputerX -Credential $credential
Set-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" -Name CachedLogonsCount -Value 0

This will set the number of cached creds Windows is storing to 0 and erase the previous creds.

3. Change their BitLocker Key Remotely

$BitLocker = Get-WmiObject -ComputerName ComputerX -Namespace "Root\cimv2\Security\MicrosoftVolumeEncryption" -Class "Win32_EncryptableVolume" -Filter "DriveLetter = 'C:'"
$VolumeKeyProtectorIDs = $BitLocker.GetKeyProtectors()|Select-Object VolumeKeyProtectorID
#Let's loop through all of the VolumeKeyProtectorIDs for the C Volume and delete them.
ForEach($ID in $VolumeKeyProtectorIDs){$BitLocker.DeleteKeyProtector($ID)}
#Now that all of the previous Protectors are gone, let's add our own.
#Let's add a new password that only the security team will need to know.
#As a backup, let's also add a couple of recovery keys just in case noone can find the sticky note with the password.
#Adding an additional optional recovery key might be helpful if you have more than one team that might need to gain access.

This is a fun one. This will delete the user’s BitLocker key and save a new one that the user doesn’t know so they can’t unlock the drive after a reboot.

4. Shut down the remote system using any number of methods.

#The nice way
Stop-Computer -computerName ComputerX -force
#Old school
shutdown -s -f -t 0 -m ComputerX
#The BSOD way
get-process -computername ComputerX| stop-process -force

This is not meant to be an exhaustive list but rather a collection of practical considerations. Lemme know if this helps or you have other suggestions.