*Drags soap box into the forum*
*Dusts it off, and steps up*
(pissed)
Ok how many here have to deal with the non-stop IT security protocol such as passwords and logins? How many here have to change their passwords every 2 weeks? On top of that the passwords cannot have any 2letter/digit combination that is the same as the previous 30? In addition it must contain caps and numbers PLUS a special character?
All right now that is just one routine for access the computers themselves. Keep in mind they store no secretive data, just standard office desktop applications.
Now we also have three other programs of which they follow the same login routine. That makes a total of 4 systems each with their own password routine.
Sure some maybe saying that it is helping to keep the systems secure. No it is not, and here is why I don't believe so.
In any environment you must take into account the fact that people are absent minded. As such you have to deal according. Though on the surface having such a security routine may sound safe, it actually leads breeches. As you force people to come up with new and drastically different passwords, they start getting out of their set routine. Pretty much people have a set pattern that they construct passwords from, or a list to use. By forcing them out of the pattern or in a sense going beyond the number of passwords they can remember; loopholes develop. In this instance users will start to write their passwords down, and store them around their desk.
Now in addition the user names have a new naming system; our employee ID.
*Looks up internal company guidelines*
Oh looky it says not to ever use your employee number for passwords or to share it with anyone.
Hmpf guess IT doesn't have to follow those rules in forcing us to do it. Now anyone can walk around and see what your employee number is. This confounds a pre-existing problem that deals with new systems. Any new systems that come up for users all have the same passwords. The security measure before was that each user had a user name that wasn't use for anything else. But now all user names are constructed around your employee ID. This ID is also used to fill out certain forms etc. This is the same problem that exist with your Social Security ID, a number which isn't suppose to be shared yet appears on every form you fill out. In fact the state of Virginia has caught on to that reality and is now issuing all drivers license with random license numbers instead of your Social.
Just irks me to no end what these IT people come up with here, to *try* and manage security systems.
Oh and am I an expert, No. All I have is an Associates in Network and Security before changing to Computer Science. So I don't try to be all mighty on this issue, but do look at it from a reality point of view. Realities that the more complex a system gets the more loopholes develop.
Hmm wait that phrase sounds familiar.....OHHH I know my professor for my entry level security class said it. Guess these IT admins missed that class.
Thank you for hearing my Rant.
Anyone else have similar IT silliness at his or her work place???
*Steps down from soap box*
*Dusts it off, and steps up*
(pissed)
Ok how many here have to deal with the non-stop IT security protocol such as passwords and logins? How many here have to change their passwords every 2 weeks? On top of that the passwords cannot have any 2letter/digit combination that is the same as the previous 30? In addition it must contain caps and numbers PLUS a special character?
All right now that is just one routine for access the computers themselves. Keep in mind they store no secretive data, just standard office desktop applications.
Now we also have three other programs of which they follow the same login routine. That makes a total of 4 systems each with their own password routine.
Sure some maybe saying that it is helping to keep the systems secure. No it is not, and here is why I don't believe so.
In any environment you must take into account the fact that people are absent minded. As such you have to deal according. Though on the surface having such a security routine may sound safe, it actually leads breeches. As you force people to come up with new and drastically different passwords, they start getting out of their set routine. Pretty much people have a set pattern that they construct passwords from, or a list to use. By forcing them out of the pattern or in a sense going beyond the number of passwords they can remember; loopholes develop. In this instance users will start to write their passwords down, and store them around their desk.
Now in addition the user names have a new naming system; our employee ID.
*Looks up internal company guidelines*
Oh looky it says not to ever use your employee number for passwords or to share it with anyone.
Hmpf guess IT doesn't have to follow those rules in forcing us to do it. Now anyone can walk around and see what your employee number is. This confounds a pre-existing problem that deals with new systems. Any new systems that come up for users all have the same passwords. The security measure before was that each user had a user name that wasn't use for anything else. But now all user names are constructed around your employee ID. This ID is also used to fill out certain forms etc. This is the same problem that exist with your Social Security ID, a number which isn't suppose to be shared yet appears on every form you fill out. In fact the state of Virginia has caught on to that reality and is now issuing all drivers license with random license numbers instead of your Social.

Just irks me to no end what these IT people come up with here, to *try* and manage security systems.
Oh and am I an expert, No. All I have is an Associates in Network and Security before changing to Computer Science. So I don't try to be all mighty on this issue, but do look at it from a reality point of view. Realities that the more complex a system gets the more loopholes develop.
Hmm wait that phrase sounds familiar.....OHHH I know my professor for my entry level security class said it. Guess these IT admins missed that class.
Thank you for hearing my Rant.
Anyone else have similar IT silliness at his or her work place???
*Steps down from soap box*
Last edited: