Publications
July 19, 2023: URLs for CSRC publication details pages have changed. Legacy URLs should automatically redirect to the new URLs. However, links to the actual publications have NOT changed (e.g., DOIs and PDFs on nvlpubs.nist.gov). Please send inquiries to
csrc-inquiry@nist.gov.
Further development of this draft has ceased (April 01, 2016).
Guide to Enterprise Password Management
Documentation
Topics
Date Published: April 2009
Comments Due:
Email Questions to:
Planning Note (04/01/2016):
This draft publication has been retired.
Author(s)
Karen Scarfone (Scarfone Cybersecurity), Murugiah Souppaya (NIST)
Announcement
NIST announces that Draft Special Publication (SP) 800-118, Guide to Enterprise Password Management, has been released for public comment. SP 800-118 is intended to help organizations understand and mitigate common threats against their character-based passwords. The guide focuses on topics such as defining password policy requirements and selecting centralized and local password management solutions.
The public comment period closed on May 29, 2009.
SP 800-118 is intended to help organizations understand and mitigate common threats against their character-based passwords. The guide focuses on topics such as defining password policy requirements and selecting centralized and local password management solutions.
SP 800-118 is intended to help organizations understand and mitigate common threats against their character-based passwords. The guide focuses on topics such as defining password policy requirements and selecting centralized and local password management solutions.
Keywords
authentication; enterprise systems; password management; security
Control Families
Identification and Authentication; Planning; Risk Assessment; System and Communications Protection; System and Information Integrity
Documentation
Publication:
Draft SP 800-118 (pdf)
Supplemental Material:
None available
Document History:
04/21/09: SP 800-118 (Draft)
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
