Password Construction Guidelines
Password Construction Guidelines
Password Construction Guidelines
1. Overview
Passwords are a critical component of information security. Passwords serve to protect user
accounts; however, a poorly constructed password may result in the compromise of individual
systems, data, or network. This guideline provides best practices for creating secure passwords.
2. Purpose
The purpose of this guidelines is to provide best practices for the created of strong passwords.
3. Scope
This guideline applies to employees, contractors, consultants, temporary and other workers,
including all personnel affiliated with third parties. This guideline applies to all passwords
including but not limited to user-level accounts, system-level accounts, web accounts, e-mail
accounts, screen saver protection, voicemail, and local router logins.
4. Statement of Guidelines
Strong passwords are long, the more characters you have the stronger the password. We
recommend a minimum of 14 characters in your password. In addition, we highly encourage the
use of passphrases, passwords made up of multiple words. Examples include “It’s time for
vacation” or “block-curious-sunny-leaves”. Passphrases are both easy to remember and type, yet
meet the strength requirements. Poor, or weak, passwords have the following characteristics:
In addition, every work account should have a different, unique password. To enable users to
maintain multiple passwords, we highly encourage the use of ‘password manager’ software that
is authorized and provided by the organization. Whenever possible, also enable the use of multi-
factor authentication.
5. Policy Compliance
5.1 Compliance Measurement
The Infosec team will verify compliance to this policy through various methods, including but
not limited to, periodic walk-thrus, video monitoring, business tool reports, internal and external
audits, and feedback to the policy owner.
5.2 Exceptions
Any exception to the policy must be approved by the Infosec team in advance.
5.3 Non-Compliance
An employee found to have violated this policy may be subject to disciplinary action, up to and
including termination of employment.
8 Revision History
June 2014 SANS Policy Team Separated out from the Password Policy and
converted to new format.
October, 2017 SANS Policy Team Updated to reflect changes in NIST SP800-63-3