Timely patching is critical to maintain the operational availability, confidentiality, and integrity of IT systems. However, failure to keep operating system and application software patched is the most common mistake made by information technology (IT) professionals. To help address this growing problem, this special publication recommends methods to help organizations have an explicit and documented patching and vulnerability policy and a systematic, accountable, and documented process for handling patches. This document also covers areas such as prioritizing patches, obtaining patches, testing patches, and applying patches.
Document Citations
Citations are generated automatically from bibliographic data
as a convenience and may not be complete or accurate.
Chicago
National Institute of Standards and Technology (NIST), Commerce Department. "Procedures for Handling Security Patches". Government. Commerce Department, January 1, 2002. https://www.govinfo.gov/app/details/GOVPUB-C13-e026e293cb814375e6f93ea18275bba7
APA
National Institute of Standards and Technology (NIST), Commerce Department. (2002, January 1). Procedures for Handling Security Patches. [Government]. Commerce Department. https://www.govinfo.gov/app/details/GOVPUB-C13-e026e293cb814375e6f93ea18275bba7
MLA
National Institute of Standards and Technology (NIST), Commerce Department. Procedures for Handling Security Patches. Commerce Department, (1 Jan 2002), https://www.govinfo.gov/app/details/GOVPUB-C13-e026e293cb814375e6f93ea18275bba7
Bluebook
National Institute of Standards and Technology (NIST), Commerce Department, Procedures for Handling Security Patches, GovInfo, (January 1, 2002), https://www.govinfo.gov/app/details/GOVPUB-C13-e026e293cb814375e6f93ea18275bba7
