Overview
Passwords are an important aspect of computer security. A poorly chosen password may result in unauthorized access and/or exploitation of our resources. All staff, including contractors and vendors with access to Yellow Dog Software systems, are responsible for taking the appropriate steps, as outlined below, to select and secure their passwords.
Purpose
The purpose of this policy is to establish a standard for creation of strong passwords and the protection of those passwords.
Scope
The scope of this policy includes 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 Yellow Dog Software facility, has access to the Yellow Dog Software network, or stores any non-public Yellow Dog Software information.
Policy
Password Creation
All user-level and system-level passwords must conform to the Password Construction Guidelines.
Users must use a separate, unique password for each of their work related accounts. Users may not use any work related passwords for their own, personal accounts.
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 to access system-level privileges. In addition, it is highly recommend that some form of multi-factor authentication is used for any privileged accounts
Password Change
Passwords should be changed only when there is reason to believe a password has been compromised.
Password cracking or guessing may be performed on a periodic or random basis by the Yellow Dog Software Team or its delegates. If a password is guessed or cracked during one of these scans, the user will be required to change it to be in compliance with the Password Construction Guidelines.
Password Protection
Passwords must not be shared with anyone, including supervisors and coworkers. All passwords are to be treated as sensitive, Confidential Yellow Dog Software information. Corporate Information Security recognizes that legacy applications do not support proxy systems in place. Please refer to the technical reference for additional details.
Passwords must not be inserted into email messages, Alliance cases or other forms of electronic communication, nor revealed over the phone to anyone.
Passwords may be stored only in “password managers” authorized by the organization.
Do not use the "Remember Password" feature of applications (for example, web browsers).
Any user suspecting that his/her password may have been compromised must report the incident and change all passwords.