• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 135
  • Last Modified:

Windows 2012 Domain - Password Sharing Issue - reluctant humans!

I have been looking at password complexity, expiry and all sorts of things best-practice-related and I have implemented a few additional policies on length, special characters, expiry etc..

...but I have a far more simple issue i would like to solve.... and i think it's a human one, but thought I'd check!

I have a department where the manager is insistent that it's easier for him to tell all his staff all to use the same password, Not the same user name, but same password for every user.  
Let's say that password does meet our complexity requirements, and as an example it's 1M4r1@UR!1  (That is example only, not one of my passwords).

In the manager's view, if  e.g. BOB is off sick, anyone else can log onto his PC and get to any work-in-progress, email etc,  as any other user would know that all they need to do is put in the user name and then the password that they all know.  

I can see his reasons, and I sympathise, but I don't agree with it.

In my view, this gives any user the chance to log on as anyone else and compromise their data and their email.  This might not (hopefully) include any existing member of staff, but you never know what drives people, and especially : what if someone leaves?  They may leave in anger, dispute, fired etc.  This then gives them the ability to log on from outside on Outlook Web and randomly delete any other user's email inbox.  This is especially easy in this manager's department as he insists on all staff using the same password, as I said above, but also when they change the password he merely adds a number sequence to the end of it, so for example 1M4r1@UR!1 becomes 1M4r1@UR!2, 1M4r1@UR!3 etc.

Yes, it's easier for his staff to remember BUT it's too easy for a disgruntled employee to guess/log on.

We are about to issue a company-wide policy on this but - just to check - can I enforce this in any way on Windows 2012?  I don't think it's possible for the system to know if two users have the same password?  It sounds more logical/secure that the system wouldn't be able to compare two users' passwords.

So, just to check before i send the written note out about this.

Over to you guys......
3 Solutions
Lee W, MVPTechnology and Business Process AdvisorCommented:
one way to pseudo enforce this is have a long (initially) minimum password age. Then force each user to change their password but at staggered times.  user1 on Monday, 2 on tuesday, etc.  with a minmum password age near the maximum password age, if they forget, they need to reset with IT but it prevents them from all changing to the same password.
Geert GOracle dbaCommented:
why not show this manager what could happen ...

login with his account and send an invitation to the whole company for a party ... and he's paying
David Johnson, CD, MVPOwnerCommented:
it is a human problem, you will have to go higher up the organization to fix this.  What is wrong with allowing a team member to  call the help desk and get the password reset when someone is sick, when the person comes back also do the password reset?
MalcAuthor Commented:
Thanks for confirming this is definitely a human policy issue, not an electronic one.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now