Password Policy
Written By Alistair
McDonald
|
|
|
Modern corporate life
means due diligence, adhering to legislation, and many other
distractions from the core business of an organisation.
Where computers are
concerned, there is potential for abuse of corporate systems,
infection of corporate systems with Viruses, Trojans and other
Malware, and damage to reputation through hacking and improper use
of resources by employees.
Download this page as a PDF file here:
password policy
|
Why you may need a password policy:
Every organization should have policies on use of
computers. These should include:
# An acceptable use policy, which describes how the firm’s
computers can be used.
# An email
policy, which defines how email can be used.
# A password
policy, where the use of passwords is defined.
The last item may be
unfamiliar to many, however, passwords can be the weak point in an
organization's security. They are often abused, decreasing their
strengths. It is worth educating users and defining the use of
passwords with a formal policy. The users should read the
password policy, understand it, and adhere to it.
It's important that
the password policy explains what the issues are, otherwise it may
be misinterpreted.
Rule 0: The password policy should be part
of every employee's Terms and Conditions.
So, what's wrong with
passwords? Typically, passwords are badly chosen. As a result, they
can be guessed easily and quickly. They are also more vulnerable to
brute-force attacks, where every possible password combination is
tried.
Choosing a good password is a skill, but it's an easily learned one.
The first thing is to not choose a very bad password. Firstly,
Passwords should not be a simple dictionary word or name - hacker
tools often include basic dictionaries, and these words will be
tested first. People's names, automobile models, sports teams, and
many other names are all used in passwords, and they are all
candidates for hackers to break quickly.
When a hacker is
attempting to break a password, his tools will test all of his
dictionary of words and names, and also use simple substitutions
such as changing the letter "I" for a number 1, "O" for zero, and so
on. They may also append a number to the end of the world.
Rule 1: Never base a password on a single
word.
The next step in choosing a good password is to make it long. A
password should be at least eight characters, and ideally 12 or
more. The longer a password, the less chance of a hacker breaking it
quickly. To join two words will create a longer word, but hacker
tools will search for this, and it is better to misspell one or both
of the words, so a straight dictionary approach will not work. If
you do choose to use this approach, DO NOT use two words that
someone will associate with you - choose them at random from a
newspaper, for example.
Rule 2: Use long passwords, including both upper and lower case,
numeric and quotation marks.
Using both upper and lower case will help too, if the application
supports it, some do not. If it does, then use the upper and lower
case at random, not just at the start of the password, again, this
will help.
The last tool I'm going to discuss for password security is adding
numbers and punctuation marks to the password. Knock out the
occasional letter and replace it with a number or a punctuation
mark. Some punctuation marks may not be allowed in some
applications, it's best to check, or to avoid greater than ">", less
than "<", the quotation marks """, "'" and "`", and the semicolon
and ampersand. I encourage you to try any unusual symbols on your
keyboard, for example"¬".
Rule 3: Never write passwords down in an easy to read form.
AND
Rule 4: Never leave passwords near the PC.
Now, there's a
temptation to write down difficult passwords. If you do write them
down, then disguise them. Hide them in a word search grid in your
diary - the answer will jump out at you, but a thief will struggle
to find the password. Never keep them in a desk drawer or on the
monitor. A better idea is to use a utility called Password Safe,
http://passwordsafe.sourceforge.net This keeps all your
passwords safe, using very strong encryption.
Rule 5: Never share accounts or give out
passwords.
There's another problem with passwords, they (and the accounts that
they are associated with) are often shared between several users.
This may be done only on certain occasions, for example when a key
employee takes vacation or is sick, or may be due to only one
account being shared within a team. When an account is shared, there
is no audit trail. This creates an opportunity for fraud. Each
person should have an account, and only use their own account. For
employees sick or on holiday, they should not be asked for their
password, but their password should be reset by the helpdesk, with
the new password given to the appropriate manager. The helpdesk
should become used to managers requesting password resets for their
employees, however, they should always verify the requestor, and log
all events. When the employee returns from vacation, they should get
their password reset again. Password resets should always be
used...
Rule 6: Never use a work password for leisure.
There is also a
danger when sharing a password on more than one system. It makes the
user's life easy if they only have to remember one password.
Single-sign-on systems can be very useful in the corporate
environment, but users should NOT use their work passwords for any
systems they use at home. Many web sites are poorly written, and
passwords may be available via techniques such as SQL injection, or
simply from fraud by the operators. There are many ways in which
a password can be learned. Once a password is known, a website
operator might trace site activity back to your company, and might
attempt to break in using the password.
Rule 7: Reset accounts as soon as employees
leave the firm.
The last point I wish to make is when employees leave the company.
Every account that they have access to should have its password
reset as soon as they leave the building. The manager can take
control of the accounts if required, but the passwords should be
reset as soon as possible. This is vitally important if
shared accounts are in use.
This concludes the article on email and passwords. I hope that it
help you to clarify what the policy for your organization should be.
Alistair McDonald is the author of SpamAssassin: A Practical Guide
to Configuration, Customization, and Integration.
You can read more
about Alistair's book here:
http://www.packtpub.com/book/spamassassin
Have you signed up for my FREE popular Windows XP
Newsletter? - Links at the top of the page on the left!
"Hey Marc! I signed up to your
newsletter on Fred Langa's recommendation.
After a quick lurk, I am glad I did - you appear to be doing us all a
big favour - for which I am grateful . . ."
Charlie - Carmel, Indiana
US
--------
I hope this article
on a password policy was useful... Enjoy the rest of site and
remember if you have a query about this site or a comment to make
then drop me a line at the
Contact Page
Kind Regards

Marc Liron -
Bio
Microsoft Digital Media MVP
Your Guide to using Windows XP
A Unique Windows XP Newsletter?
Sign Up Now!
- Make sure you get your
FREE tips and advice...
|