<

Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x

A concept for safe user support

Published on
11,980 Points
1,380 Views
6 Endorsements
Last Modified:
This is a guide to the following problem (not exclusive but here) on Windows:

Users need our support and we supporters often use global administrative accounts to do this. Using these accounts safely is a real challenge.

Any admin who takes security seriously fears attacks by his own colleagues. Thus he faces a small dilemma with user support: strictly speaking, each user PC is "enemy territory". We do not know if the user has evil intentions and might have prepared his already compromised machine, only waiting for us. How to authenticate there without running the risk that the user will somehow capture our password or hash?

Many questions arise:
  • Do we use remote assistance, remote desktop or TeamViewer?
  • Or walk over to the user and enter the password while he watches?
  • Or visit his computer (physically or from remote) "after hours"?
  • Do we use local Admins, or a/the domain admin or do we create an AD Group with delegated privileges? 
  • How do we maintain the passwords? Write lists, memorize, or set all to the same one?
  • Do we type that password in our own session only, or inside the user's session but only on the secure desktop of a UAC prompt, or may we use it with RunAs? Or would it be better to use 2-factor authentication?
  • Or shall we "surrender" and give all users admin rights so they can solve their problems alone? ;-)
You can find various recommendations also by Microsoft but I want to exhibit and recommend my own approach here. It comes without two-factor authentication, without additional software and is robust. I have been using it for more than a year now.

The main idea is: there is no need to use an account that is admin on more machines than the supported one! We are working on one (1) machine, so why should we use an account that is admin on all clients? The reason is convenience. And we pay for that laziness -- anyone familiar with mimikatz and similar exploitation tools will agree. I will show an alternate way that is secure and still convenient.

The usage scenario: User needs support, the problem has been identified: it is not a user profile problem so we will not need to work inside the user's session, but unfortunately, admin rights are needed to fix it. Still, the goal is to leave no exploitable credentials on the supported computer.

My intention is
  • to have one support admin account per computer
  • to have access to domain resources with this account 
  • to enable this account only for the period of the support case
  • not to create any password lists (I'll show that you do not even have to enter a password at all)
Now let's start:

Step 1: For each PC ("somePC") I automatically create a disabled user account "adminsomePC" with a random password that can log on nowhere. Therefore the parameter logonworkstations is set to some fantasy name (here: fantasynamehere). We can create a list.txt with all pc names inside and then run the following at the DC:
for /f %a in (list.txt) do net user /add admin%a /random /active:no /WORKSTATIONS:fantasynamehere

Open in new window

Step 2: These accounts will live in a their own OU, to which (weak) support employee accounts get delegated full rights (using the delegation of control wizard) in order to set those admin accounts active/inactive.

Step 3: A domain startup script makes the corresponding account member of the local admin group:

net localgroup /add administrators admin%computername% 

Open in new window

Step 4: If a supporter needs admin rights on somePC, he activates that somePCadmin account scripted (see below), lets the script set a new password and at the same time enter these credentials in the credential manager of his own computer and automatically set up a remote desktop connection to the PCxy. When he's done, the support account is disabled automatically.

The script itself is simple batch code, refined with a PowerShell script scripts.zip\Day6-PowerShell\GenerateRandomPassword.ps1 (public domain) from http://www.sans.org/windows-security/files/scripts.zip that generates random passwords (adjustable length, default: 15).

@echo off
set /p target=What machine?: %=%
for /f %%a in ('powershell \\server\share\GenerateRandomPassword.ps1') do net user admin%target% %%a /domain /active /workstations:%computername%,%target% & cmdkey /add:TERMSRV/%target% /user:netbiosdomainname\admin%target% /pass:%%a
start mstsc /v:%target%
pause
net user admin%target% /active:no /domain

Open in new window


The account can be used to help via RDP completely safely. If you correctly terminate the batch by pressing any key, that account will be deactivated immediately again. But just in case you should create a task that deactivates all support admins after working hours and schedule it to run on your DC. I had to minimally edit GenerateRandomPassword.ps1 to fit my needs. I commented out line 65:
#1..20 | foreach { Generate-RandomPassword -length $length } ; "`n"

Open in new window

and I added:

1 | foreach { Generate-RandomPassword -length $length } ; "`n"

Open in new window


That's it.
Certainly you can further refine this, my intent is to provide the base.
6
Comment
Author:McKnife
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 38

Expert Comment

by:Geert Gruwez
nice article, but why would a malicious user wait for you to come to him ?

what if the malicious user finds your account and tries  to login with it until it's locked because of n wrong passwords ...
the next level would be all supports accounts ...
0
 
LVL 56

Author Comment

by:McKnife
"what if the malicious user finds your account and tries  to login with it until it's locked because of n wrong passwords ... " - read it once more. That is not possible, because it is locked unless we activate it for the support rdp connection.
"nice article, but why would a malicious user wait for you to come to him ?" - if you have more questions, next time please ask them right at the article. Answer: to grab your password with mimikatz and extend his rights from admin@local to admin@allPCsThatAdminHasAccesto
0
 

Expert Comment

by:amstoots
Nice article, McKnife
0

Featured Post

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

Join & Write a Comment

This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Suggested Courses

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month