|
IV. AASU Policy on Passwords 4.0 Background and Purpose: This document represents the University-wide guidelines and responsibilities required to acceptable and proper use of passwords as they are used with computer resources and services. The intent of this policy is to educate users about their responsibilities regarding passwords while identifying certain unacceptable uses of passwords with AASU computing resources and services. 4.1 Overview Passwords are an important aspect
of computer security. They are the front line of protection for user
accounts. A poorly chosen password may result in the compromise of Armstrong
Atlantic State University's entire campus network. As such, all Armstrong Atlantic State University
employees (including contractors and vendors with access to Armstrong
Atlantic State University systems) are responsible for taking the appropriate
steps, as outlined below, to select and secure their passwords. 4.4.1 General 4.4.1.1. All system-level passwords (e.g., root, enable, NT admin, application administration accounts, etc.) must be changed on at least a quarterly basis. 4.4.1.2. All user-level passwords (e.g., email, web, desktop computer, etc.) must be changed at least every six months. The recommended change interval is every four months. 4.4.1.3. User accounts that have system-level privileges granted through group memberships or programs such as "sudo" must have a unique password from all other accounts held by that user. 4.4.1.4. Passwords must not be inserted into email messages or other forms of electronic communication. 4.4.1.5. Where SNMP is used, the community strings must be defined as something other than the standard defaults of "public," "private" and "system" and must be different from the passwords used to log in interactively. A keyed hash must be used where available (e.g., SNMPv2). 4.4.1.6. All user-level and system-level passwords must conform to the guidelines described below. 4.4.2.0. Guidelines 4.4.2.1. General Password Construction Guidelines 4.4.2.1.1. Passwords are used for various purposes at Armstrong Atlantic State University. Some of the more common uses include: user level accounts, web accounts, email accounts, screen saver protection, voicemail password, and local router logins. Since very few systems have support for one-time tokens (i.e., dynamic passwords which are only used once), everyone should be aware of how to select strong passwords. 4.4.2.1.2. Passwords should never be written down or stored on-line. Try to create passwords that can be easily remembered. One way to do this is create 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! 4.4.2.1.3. Poor, weak passwords have the following characteristics:
4.4.2.1.4. Strong passwords have the following characteristics:
4.4.2.2. Password Protection Standards 4.4.2.2.1. Do not use the same password for Armstrong Atlantic State University accounts as for other non-Armstrong Atlantic State University access (e.g., personal ISP account, option trading, benefits, etc.). 4.4.2.2.2. Do not share Armstrong
Atlantic State University passwords with anyone, including administrative
assistants, secretaries, or CIS personnel. All passwords are to be treated
as sensitive,
confidential Armstrong Atlantic State University information.
4.4.2.2.4. If someone demands a password, refer them to this document or have them call someone in the AASUSec. 4.4.2.2.5. Do not use the "Remember Password" feature of applications (e.g., Eudora, OutLook, Netscape Messenger). 4.4.2.2.6. Again, do not write passwords down and store them anywhere in your office. Do not store passwords in a file on ANY computer system (including Palm Pilots or similar devices) without encryption. 4.4.2.2.7. Change passwords at least once every six months (except system-level passwords which must be changed quarterly). The recommended change interval is every four months. 4.4.2.2.8. If an account or password is suspected to have been compromised, report the incident to AASUSec and change all passwords. 4.4.2.2.9. Password cracking or guessing may be performed on a periodic or random basis by AASUSec or its delegates. If a password is guessed or cracked during one of these scans, the user will be required to change it. 4.4.2.3. Application Development Standards 4.4.2.3.1. Application developers must ensure their programs contain the following security precautions.
4.5.0 Enforcement These policies and procedures are designed to ensure the integrity, security, and proper effective functioning of campus IT services. All policy and procedure violations will be subject to investigation and appropriate disciplinary action through established channels that may include, for serious violations, letters of reprimand and/or termination of employment.
|