Skip to Main Content

This policy explains the standard for creation of strong passwords, the protection of those passwords, and the frequency of change.

Password Complexity Policy

The main reason e-mail accounts get compromised is that people use easy to guess passwords. Unauthorized users then use your account to send out thousands of SPAM e-mail messages. This causes e-mail service providers to blacklist the College and prevent e-mail from being sent from or to College e-mail accounts. As a result, email services are interrupted, sometimes for several hours until the problem can be rectified. This is a very serious matter and it is very difficult to get removed from the blacklists.

Saint Rose Password Policy

I. Purpose:

Passwords are an important aspect of computer and network security. They are the front line of protection for user accounts. A poorly chosen password may result in the compromise of The College of Saint Rose’s (College) entire network or allow unauthorized access to systems or data. As such, all College personnel (including contractors and vendors with access to College systems) are responsible for taking the appropriate steps, as outlined below, to select and secure their passwords.

The purpose of this policy is to establish a standard for creation of strong passwords, the protection of those passwords, and the frequency of change. The objective of this policy is that all personnel who have or are responsible for an account (or any form of access that supports or requires a password) on any system that resides at any College facility, has access to the College network, or stores any non- public College information actively ensures that their passwords are strong enough to protect the College.

II. Definitions:

Terms                          Definitions
College                        The College of Saint Rose
ITS                               Information Technology Services

III. Policy:

A. Passwords must follow the password complexity requirements:
1. The password needs to be at least eight characters.
2. The password must include at least two of the following: a letter, a number or a special character (,!@#$%^&*()_+|~-=\`{}[]:”;'<>?,./)
3. Note additional password complexity suggestions under Guidelines below.
B. All user-level passwords (examples: e-mail, web, desktop computer, etc.) must be changed at least every 180 days. The recommended change interval is every 60 days.
C. The same password cannot be used within twelve password resets.
D. New passwords will need to age at least one day before they can be changed again.
E. If passwords are saved in written or printed format, they must be stored in a locked and secure location.
F. Passwords must not be posted in plain sight or hidden under a keyboard, under a desk blotter or in an unlocked desk drawer.
G. Whenever a password protected device or system is left unattended, it should be logged off either manually or automatically and require the user to log on again.
H. Passwords must not be inserted into e-mail messages or other forms of electronic communication.
I. Passwords are meant to be user specific so they must be kept confidential.
J. All user-level and system-level passwords must conform to the guidelines described below.
K. When possible and practical, systems will be set to disable an account after three unsuccessful attempts to log on. The account will be locked out for a minimum of fifteen minutes.
L. Passwords should never be embedded or hard-coded in applications, systems or hardware.
M. Users will be required to sign a statement prohibiting disclosure of passwords.

IV. Procedure:

A. General Password Construction Guidelines

Passwords are used for various purposes at the College. Some of the more common uses include: user level accounts, web accounts, e-mail accounts, screen saver protection, voicemail password, and local router logins.

Since very few systems have support for one-time tokens (example: dynamic passwords which are only used once), everyone should be aware of how to select strong passwords.

The College of Saint Rose password complexity requirements:
1. The password needs to be at least eight characters.
2. The password must include at least two of the following: a letter, a number or a special character (!@#$%^&*()_+|~-=\`{}[]:”;'<>?,./)

Password complexity suggestions:
1. The password should contain both lower and uppercase characters (examples: a-z, A-Z).
2. The password should not be based on personal information, names of family, pets, etc.
3. The words “The College of Saint Rose “, “strose”, “saintrose” or any derivation should not be used.
4. Try to create passwords that can be easily remembered. One way to do this is by creating a password based on a song title, affirmation, or other phrase. For example, the phrase might be: “This May Be One Way To Remember” and the password could be: “TmB1w2R!” or “Tmb1W>r~” or some other variation.

NOTE: Do not use either of these examples as passwords!

B. Password Protection Standards

1. Do not use the same password for College accounts as for other non-College access (examples: personal e-mail account, option trading, benefits, etc.).
2. Where possible, do not use the same password for various College access needs.
3. Do not share College passwords with anyone, including administrative assistants or secretaries. All passwords are to be treated as sensitive, confidential College information.

C. Passphrases

Passphrases are generally used for public/private key authentication. A public/private key system defines a mathematical relationship between the public key that is known by all, and the private key, that is known only to the user. Without the passphrase to “unlock” the private key, the user cannot gain access.

1. Passphrases are not the same as passwords.
2. A passphrase is a longer version of a password and is, therefore, more secure.
3. A passphrase is typically composed of multiple words. Because of this, a passphrase is more secure against “dictionary attacks.”
4. A good passphrase is relatively long and contains a combination of upper and lowercase letters and numeric and punctuation characters.
5. An example of a good passphrase: “The*?#>*@TrafficOnThe101Was*&#!#ThisMorning”
6. All of the rules above that apply to passwords apply to passphrases.

The following is a table of “do’s” and “don’ts” for passwords:

Change password once every six months
Change system-level passwords quarterly
Contact ITS if someone demands your password
Refer anyone demanding your password to this document
Report any suspected breach in your password security to ITS
If you believe your password has been compromised, change all passwords
Share a password with ANYONE including coworkers, friends or family members
Write passwords down and store them anywhere in your office without encryption or obfuscation.

Reveal a password over the phone to ANYONE, EVER!
Reveal a password in an e-mail
Reveal a password to your supervisor
Talk about a password in front of others
Hint at the format of a password (example: “my family name”)
Reveal a password on questionnaire or security form
Use the “remember password” feature of applications (examples: Eudora, Outlook, Netscape Messenger)
Store password in a file on ANY computer system (including Palm Pilots or similar devices) without encryption

NOTE: If ITS has reasonable cause to believe that a password or system has been compromised, it will change the password and/or otherwise disable the account.

Password cracking or guessing may be performed on a periodic or random basis by ITS or its delegates. If a password is guessed or cracked during one of these scans, the user will be required to change it.

D. Application Development Standards

Application developers must ensure their programs contain the following security precautions. Applications should:
1. support authentication of individual users, not groups.
2. not store passwords in clear text or in any easily reversible form.
3. provide for some sort of role management, such that one user can take over the functions of another without having to know the other’s password.
4. support TACACS+, RADIUS and/or X.509 with LDAP security retrieval, wherever possible.

V. Enforcement:

Failure to comply with this Policy will be addressed through the College’s Corrective Action process, as noted in the College’s employee handbooks and/or union contracts. If warranted, an employee’s failure to comply will result in disciplinary action up to and including termination of employment. Failure to comply may also be a violation of civil/criminal law and may cause the employee to be subject to applicable penalties.