Discussion Locked

Should Techs know Users Passwords?

0 helpful
30 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are being told by out Director that we can no longer log onto a User's PC forr support reasons using the User's account/password. Remote assistance is ok, but if it requires a rebott and the user is nolonger around, we are boned. Any thoughts. How are other helpdesks doing this?

30 replies

by jdclyde

If you know the password and something bad happens, then they can blame you instead of taking the burn themselves.

This is one of the first things they teach in security as well, that you tell the users never to give their passwords out to anyone. If support can call and get a password, then you also have your social engineering to hack they company. The people are easier to hack than the systems are.

It is sometimes a pain, but this policy is there for a good reason.

Good luck.

by gralfus

Our techs all have admin rights on all PCs in the domain. Thus, we can do anything we want with the systems in question. Auditing requires that you not know their passwords, otherwise the company can be help up to legal difficulties in wrongful termination suits. "I didn't do that, someone logged in using my name and password. Everyone knows the techs have our passwords."

by gario

Not good security policy to give out passwords. Help Desk/Tech Support personnel should have Admin priviliges for remoting and logging onto workstations.

by maxwell edison

.
If they make that choice, then they suffer the potential consequences. If it's an inconvenience, let it be to them, not to you.

If, on the other hand, they want you to "be all" and "do all" at "all times", then they have to give-up a certain amount of privacy.

It's their choice, and you should make it clear what the repercussions of that choice really are -- then let them make it.

by jjdgraz001

We use a user account for troubleshooting problems. All of us have admin privileges on the network so if we try an application and it works, but it doesn?t work for a user. We have to troubleshoot it with user privileges. That is why we have a troubleshooting account. The users don?t have to give up there account credentials.

If the problem is Exchange related, Or if they have a problem with there e-mail that can?t be replicated unless the specific user is logged in, then we reset the user?s password to our default, troubleshoot / repair the problem, and force the user to change there password when they next log in.

Users have to have confidential passwords, and they have to have confidence that they are the only ones that have them. Even if we can get into see what they have saved on their desktops, or working folders.

by maxwell edison

.
In some companies, an employee might actually have an obligation to protect the privacy of some things on a computer. Other companies may not.

In my office, for example, we're pretty much an "open book" company (except accounting and payroll and such). Therefore, the company policy is that there is absolutely no expectation of privacy, and if a person is on vacation or out of the office, someone else might have to access his or her files -- or even his or her email -- to deal with a company issue that might arise.

So I suppose it depends on a lot of things.

by bfilmfan

Depending on your enviornment, you having a user's passwords could quickly run you into issues with SOX, HIPAA, etc.

I would recommend that a group with admin rights on the PC be created that has remote desktop management capabilities. That would resolve the issue, since admins in that group would have rights and could sign whatever applicable non-disclosure agreements were required.

by trockii

I am the IT director for the company i work for and I make everyone's passwords when i create their user acccounts. I have a default password I use and then force them to change it after initial login. There's no reason I need to know their password. I can do everything and more logging in as myself than as if I was to log on as them. With the right policies and domain admin accounts this wouldn't be an issue. If you feel you need more access then tell your boss what rights you need. Explain what is happening and he should be willing to listen and give you more rights. Just show you can be trusted with this priviledge and don't abuse it. It will make his and your job alot eaiser.

by teligence

My company's policy states basically that since these PCs are Company property the "Company" (i.e. IT) has blanket authorization to access any data on any device anywhere in the Company for any reason at any time.

Simply put - the Company paid for it, the Company has full right to any information on it or associated with it.

The users must sign they they have "read" and accept Company policies. (Yeah, right. Just like all of us read the entire license agreement for every software installation on every PC...) However, it is there and if the user chooses to accept it "blindly", then that's their choice.

As far as having access to their specific profile should the need arise for profile specific software installation or troubleshooting, as admins, we can always change the user's password to access their complete profile to assist them as needs arise.

Our old "mini-mainframe" had a very handy special feature - it allowed us to enter the username of an individual, but enter the admin password which allowed us to access the user's profile - just as they would. In addition it logged the port number, time, date, and the fact that the "admin" access was used for that particular session. This prevented a user from making any deflective statements and IT being a target. If Windows Server had that feature it would sure make my job that much easier - I mean, "It would allow me to support this Company resource that much more effectively" !!!

by tomsal

Here we are a 100 employee, privately held shop were for the last 7 out of 8 1/2 years I was the one who had all responsibilities for keeping any documentation that related to IT, as well as being tech support and the sole administrator. In my case there was no way around me having to know user's passwords. There is an encrypted and password protected file store on a network drive (that is backed up nightly) that only the admin group has rights too -- the passwords for ALL users (include from reception to the CEO) is stored in that file. I'm the one who maintains it when passwords are changed, employees leave or new hires come in.

Further more our work force (and I know this sounds judgmental but I'm just telling the truth, as people they are mostly very good people) is very low end computer users.

They forget passwords left and right like you won't believe. For a while we had a policy that each time they forgot a password a new one was assigned. Well some users forgot with such regularity that the admin overhead was just ridiculous (especially when you are the lone person supporting 100 users, plus all the "paper" and administrative duties of maintaining an IT department).

However, we are switching our policy as we upgrade systems from 98 SE to XP, the new policy will be like others said -- admin only rights for the techs no more using user passwords.

by scooterb

I am the sole person responsible at a public utility and have to serve all roles from SA all way the down to the help desk. I also provide all electrical engineering support. I had to make it real easy for me. I do have admin rights on all the PC's and servers, but I had to even generate their passwords for them and make them memorize them. They were wanting to use the simple and easily breakable dictionary type or else just their name. I have to keep my network locked down as inappropriate access could effect the publics access to their needed service. So I just try to keep my heartache down and provide them with one. I don't use them except when they come to me and do the ole "I can't log in anymore". Then I have to get out my log and go log in for them. Often times explaining for the third or fourth time that they are case sensitive. So I guess it would depend on your situation as to whether you have their passwords. It will be a matter of integrity as to whether you ever use them.

by gunnar klevedal

It is a pain remembering meaningless combinations of letters, numbers and special characters. And when I've found a god three-letter acronym that no one can guess, the next service provider requires six characters.
I am no admin. Rather I am a user among users, except that I do some local support.
We use Smart Cards with PIN codes. Every user has to remember his/her code, and the secret answers for two questions he construed himself.
I allways tell users - I don't want to know your pins or answers. Nevertheless they name their spouses,sons,daughters,pets,cars,movies etc. I've never used that information, and I tend to forget in the long run.
Users are different. Some guard the files on their home drive, and some do not know they have a home drive. Anyway I am convinced I have no right to access anyones files and folders, unless he gives me permission.

Tribute goes to John Socha

by zlitocook

We have an all XP workstation office, if you login as the user only you can access the programs that you need. Not even an administrator can access those programs because of SOX and other restrictions. So some times you have to have access to users logins and passwords to do upgrades or fix a problem. A user can change thier password any time they want so if I need to access a system they change the password after I am done. All departments are set up with thier own GPO and security settings, we have each user locked to one computer and let others to log into the computer but can not access any other user settings on that computer. So we do need a user login to fix, update or do other things for that user.

by ssteinberg

I have worked at companies with polar views on this. When I did have user passwords, I could configure a new pc for a user with little user interaction. Log in as user, configure Outlook/Printers and rest of profile. Deliver pc and good to go.
Meanwhile, without user passwords, I have to configure everything with the user logging in, and hanging out while I customize it. (Not that it takes long to do, but...)
At the company where I had user passwords, I also had full AD access, so I could reset their password anytime I wanted.
It comes down to security, and user inconvenience. Of course I believe I am trustworthy, but the next tech may not be. And thus not knowing the user password is frustrating for me because I have to wait on the user to complete my work. And again, I am not going to log in as them later to do malicious things.

by simon_mackay

Hi!

I am doing support work for a close friend of mine who is a professional art valuer who runs her business as a "one-person shop" -- i.e. a SOHO or SME job. This job has me responsible for two laptop computers and she has given me the OS password for one older unit and had me "key" the BIOS password for a new one that she just bought.

With this kind of work, I often notice that the SOHO type of user can treat their system password like their house's front-door key i.e. pass a copy of the key to a contractor or houseguest for the duration of their service or stay. They may retain the key and the householder won't often worry about whether that keyholder will revisit the premises after their tenure. This practice tends to happen more with people who aren't computer literate or simply don't have a full grasp of computing.

There should be some information on how a user can create a "contractor" password on their computer equipment, whether at OS level or BIOS level.

With regards,

Simon Mackay

by ecravens

We have found that often when trouble-shooting or working a node which is logged in as an administrator will not give the same errors or settings that the "User" would have. If we go to a workstation that has had the user password changed, we simply log on as administrator, change the password of the user to one we can use, then log on as the user.

If they have changed their network password, we just change it from the server.

Our philosophy is that the equipment and software are the property of the company, provided for the user to fulfil his or her task for the benefit of the company.

by mary.hoerr

I agree. I have all the user passwords. The network and admin passwords are all kept secure and never given out.

Like the other guy above, we are pretty open, and people expect others to have access to their computers and email when they're gone, except for accounting and personnel.

While in theory you ought to be able to log on as admin and do anything you need to, in my experience (with Windows 2000 and XP, at least) you can't be sure an install is going to run correctly until you log on as the user (unless the user has all admin rights). Also, you don't always get the same errors.

The security thing seems to be something of a red herring. After all, I can change the password anytime I want to, so I already have access to everything if I want it. True, if I change their password they'll know about it.

by awfernald

Because if you change their password for them, then the next time they try to log on, they are going to be calling you to "reset" their password. And when that happens, it logs it. Now, depending on the life cycle of your log, that may disappear before anything happens which would get people to "look" for that type of audit event. However, it's not quite as transparent as you make it seem.

Yes, you have access at any time you want, however, you do have to take an action which is "notable" to that end user, then convince them that for some odd reason their password changed on them without them doing it, or that they simply forgot the password that they had been using for the last 'x' number of months/years.

by lori wagoner

Our company has a policy that says you should never give out your password.

There have been times where it was necessary to set up profile items under the user's login and password (i.e. Outlook). At that time, I explain to the user that this can be done two ways. Either they log in and let me do the setups needed while they wait or they give me their password with the understanding that after I have set their profiles up, they must immediately change the password to something new.

When a user is new or forgets their password, we have one "system" password that is assigned to them. They must change this system password the first time they log in or understand that others could remember this password and use it to be malicious.

I agree with most commenting here that you can set up administrator groups to administrate the desktops, but when it comes to profiles, you must be logged in as the user.

by cp7212

We used to do that at our company and then the Sarbanes-Oxley Act reared it's ugly head. Now, under no circumstances whatsoever should we ask a user for their password. I accidentally asked for a password once and the user's supervisor tattled on me to my IT manager.

One day the sup was having a password problem. I came up to help her and found out she was logged on as someone else and using their account. So I narced on her. She tried to rationalize what she was doing. It didn't fly. Yes, it's immature but revenge is a dish best served cold......

I look at it this way. If I have to do something user-specific and I can't do it because of restrictions, I'm not the one who is boned.

by mikewbc

...I'll always need to have the user's passwords. You can reset the domain password at the server, but that doesn't get you logged onto the correct Win98 profile!! To do that you either have to go in, copy the profile to a new name, delete the original profile, copy the new profile to a second new profile using the original user name, give it the new domain password, Then delete the first new profile... or you can just delete all the .pwl files on the machine and when you log in the next time you enter the new password.

I don't know how many time's I've had a user say, my outlook doesn't work, or I can't get to my files, only to find out that they either typed their user name wrong or password wrong, and then created a new profile in Win98 that lets them use their local computer, but not get to the network. One user had more than 5 variations of their user name, each with different user profiles, only 1 of which would work on the network. With 50 of them and only one of me, I'd never get anything done but fix password problems or change passwords without my list.

by jjdgraz001

What kind of legetimate network still uses Win98 clients? There is NO security in FAT files systems. Nothing is protected from other users/hackers.

I suppose that if a seven year old operating system works, then there is no reason to upgrade. But how about service packs and hot fixes?

I thank my stars I don't have to deal with that problem any more.

by jessie

I've only ever worked for one company that DIDN'T have a policy about us knowing a user's password. If worst comes to worst, and it's an emergency that I get into a user's account, I can always talk to the Director of IT, get his/her approval for a password reset, reset the user's password, login, and force the user to change it at next logon.

For the most part, really, if you coordinate things with the users, it's never really a problem for me to NOT know their passwords. There's no need and it's WAY too un-secure. It would require writing down their password somewhere, as I know I can't remember over 400 users' passwords, which would make each user vulnerable to theft and cyber-backstabbing. It's just not a good idea really.

by plum

Those of us who work in the mindset of the Gatesian Universe (aka Windows), and have done so for a fair amount of time (on the order of decades), can shed some light on this matter of users' passwords.

It's easier to support a user in today's technology than in yesterday's technology... because Windows does a lot of quirky things inside of the user's profile area.

It has become so unweildy, in fact, that you will not be able to replicate a user's problem unless you are logged in as that user (in a Win2K or WinXP environment). With the advent of SP2 for WinXP, the challenges compound.

General... I agree with all who have said that the user's password should be private.

From a support perspective, however, it's becoming harder to support users as Windows "matures" due to the many "unpredicatable" and "unexplainable" occurences of "problems." It's nearly "impossible" to diagnose some problems, even knowing the user's passwords and working using their profiles. We see it... but we can't fix it. Sometimes we fix it by redo'ing their profiles... not really knowing what hosed their machines... and sometimes we opt for the 4 to 16 hour rebuild of their PCs.

The supertechs, of course, would argue that they can fix anything. Sure, I've seen those guys... and might even claim to be one... but seldom is it a resource-effective process... and I havn't really met too many supertechs... except those that are supertechs in tongue only...

by hal 9000

But here I'm thinking about a programs password not the computers password as there have been occasions when I've had to log on and out of a program for changes to take effect and it is just not piratical to have the user sitting there on the off chance that they might have to enter in their password. Actually when it all comes down it the nitty gritty I'm flat out remembering my own passwords let alone everyone else's so after I've finished a particular job I've effectively forgotten the password in question. I write these down for reference while I'm at the unit and shred then when I'm finished.

But it is amazing just how many people expect you to remember a password that they gave you 6 months ago. :)

Col ]:)

by smanches

I support a network of over 700 users to 2 techs - very seldom do I need to change a users password to fix a problem on their pc (even though I can since I have the permission to reset and create the users accounts) We have a password policy also, but most users would rather give me their password than have to come up with a new one (we change passwords every 45 days). I shred all passwords given to me once the job has been completed and I have never had any complaint on work that has been done as the user, except for uninstalling unapproved software from the pc. :-) I get the same thing about passwords - I just tell them all the passwords I have to remember to do my job, there is no way possible I can remember theirs.

by glen.cranston

I use administrator account to get into a pc if the user is out. Or change the password to get into the pc.

by doug m.

We start by not knowing anyone's passwords, but if we need to we will ask for one if we truly require it for that time. But we don't write them down or memorize them. Seems to work for us.

by duanedelima

Passwords should never be known by more than the intended user of that password. Passwords should be memorised and never written down or stored on the systems in a file.

The only case I would like to think this differs, is in the case of the system's current admin password... which should be known by the network administrator, and written on a paper, sealed in an envelope and locked in the company's safe. This may seem questionable. However, don't let security fears blind you from reality. Us techies can be hit by a bus and die. And with us, goes the entire network's primary control. They can get a replacement tech, but he would need to know the login password to resume work. No-one should know the password, but it should be accessible in absolute emergencies... thus... the safe...

Anyway, back to the question at hand... you should not know the user's password. In the case of requiring access to the user's account, you have two options...
1) have the user with you to log on himself/herself... this ensures you never need to enter the password yourself...
2) Reset the user's password to a randomly generated password, use that for your work, then inform the user of the password change... (do this personally) then have the user recreate a password once you're done with your work.

This discussion is closed to new replies.