Skip to main content
HIPAA Path
Category: Physical and Technical Safeguards

NIST SP 800-111

Also known as: SP 800-111, Guide to Storage Encryption Technologies for End User Devices, NIST Special Publication 800-111
Simply put

NIST SP 800-111 is a guidance document published by the U.S. National Institute of Standards and Technology in 2007 that explains how to use encryption to protect data stored on end user devices such as laptops, desktops, smartphones, and USB drives. It helps organizations understand the basics of storage encryption and how to apply it to secure information on these devices. It is a technical guide rather than a legal requirement, and it is not part of the HIPAA regulations themselves.

Formal definition

NIST SP 800-111, authored by K. Scarfone and published by NIST in 2007, is a Special Publication in the NIST 800 series that provides guidance on storage encryption technologies for end user devices, including full disk encryption, volume and virtual disk encryption, and file/folder encryption. Its scope is focused on end user devices such as laptops, desktops, smartphones, and removable media (e.g., USB drives) rather than server-side or cloud storage architectures. In a HIPAA context, this publication may be referenced as a technical resource supporting encryption of ePHI at rest under the Security Rule's technical safeguards; however, encryption is an addressable implementation specification under the Security Rule (addressable does not mean optional), and SP 800-111 is guidance, not a regulatory mandate. Adopting SP 800-111 does not by itself establish HIPAA compliance, and readers should verify current NIST guidance, applicable HHS OCR expectations, and any additional requirements imposed by state law or the HITECH Act. Note that as of the cited 2007 publication, its guidance is oriented to end user devices and does not address cloud storage.

Why it matters

For organizations handling electronic protected health information (ePHI), lost and stolen end user devices such as laptops, smartphones, and USB drives represent a persistent risk. NIST SP 800-111 matters because it provides practical guidance on the storage encryption technologies that can protect data at rest on exactly these kinds of devices. When ePHI is properly encrypted on a device that is later lost or stolen, the exposure of that information is generally mitigated, which is a significant consideration under the HIPAA Security Rule and the Breach Notification Rule.

In a HIPAA context, encryption of ePHI at rest is an addressable implementation specification under the Security Rule's technical safeguards. Addressable does not mean optional; it means a covered entity or business associate must implement the specification if reasonable and appropriate, or document why not and adopt an equivalent alternative where appropriate. SP 800-111 can serve as a technical reference to help organizations understand and evaluate storage encryption options as part of that analysis. It is important to stress, however, that SP 800-111 is guidance published by NIST, not a regulatory mandate, and following it does not by itself establish HIPAA compliance.

Organizations should also be aware of the document's limits. As a publication oriented to 2007-era end user devices, its guidance addresses laptops, desktops, smartphones, and removable media rather than server-side or cloud storage architectures. Readers should verify current NIST guidance and applicable HHS OCR expectations, and should account for any additional requirements imposed by state law or the HITECH Act.

Who it's relevant to

Security Officers and IT Security Teams
Those responsible for implementing the Security Rule's technical safeguards can use SP 800-111 as a reference when evaluating storage encryption options for end user devices holding ePHI. It supports, but does not replace, the risk analysis and documentation required when addressing encryption as an addressable implementation specification.
Covered Entities and Business Associates Managing Mobile and Portable Devices
Organizations that issue laptops, smartphones, and USB drives to workforce members face heightened loss and theft risk. SP 800-111 helps them understand full disk, volume, virtual disk, and file/folder encryption approaches for protecting data at rest on these devices, though it does not address cloud storage.
Compliance and Privacy Officers
Professionals overseeing HIPAA compliance should understand that SP 800-111 is technical guidance, not a legal requirement or part of the HIPAA regulations. Adopting it does not by itself establish compliance, and they should confirm current HHS OCR expectations and any additional state law or HITECH Act obligations.
Auditors and Risk Assessors
Those assessing an organization's encryption posture may reference SP 800-111 to benchmark end user device encryption practices. They should verify it against current NIST guidance and recognize its scope is limited to end user devices as of its 2007 publication.

Inside SP 800-111

Guide to Storage Encryption Technologies for End User Devices
NIST SP 800-111 is a National Institute of Standards and Technology special publication that provides guidance on encryption technologies for protecting data stored on end user devices such as laptops, desktops, removable media, and portable storage. It is a technical guidance document, not a regulation, and is issued by NIST rather than by HHS OCR.
Storage encryption categories
The publication generally addresses several approaches to at-rest encryption, including full disk encryption, volume and virtual disk encryption, and file/folder-level encryption. Each approach offers different protection characteristics and trade-offs regarding scope of protected data and usability.
Authentication and key management considerations
The guidance discusses the importance of authenticating users before granting access to encrypted data and of managing cryptographic keys throughout their lifecycle, since encryption strength depends heavily on how keys and credentials are protected and recovered.
Relationship to HIPAA Security Rule encryption
Encryption of ePHI is an addressable implementation specification under the technical safeguards of the HIPAA Security Rule. NIST SP 800-111 can serve as a reference practitioners consult when evaluating storage encryption for end user devices, but consulting it does not by itself establish HIPAA compliance. Addressable does not mean optional; a covered entity or business associate must implement the measure, adopt an equivalent alternative, or document why it is not reasonable and appropriate.
Connection to breach notification safe harbor concepts
Under HHS OCR guidance, ePHI that is rendered unusable, unreadable, or indecipherable through methods consistent with recognized standards may fall outside the definition of a reportable breach. NIST publications such as SP 800-111 are among the technical references commonly associated with encryption of data at rest, though readers should verify the specific methods and current guidance recognized by HHS.

Common questions

Answers to the questions practitioners most commonly ask about SP 800-111.

Is implementing NIST SP 800-111 required for HIPAA compliance?
No. NIST SP 800-111 is a guidance document on storage encryption technologies for end user devices, not a regulatory mandate. The HIPAA Security Rule does not require adherence to any specific NIST publication. Encryption itself is an addressable implementation specification under the Security Rule's technical safeguards, meaning a covered entity or business associate must assess whether it is reasonable and appropriate and, if not, document why and implement an equivalent alternative. Addressable does not mean optional. Organizations often reference NIST SP 800-111 as a recognized source of guidance, but doing so does not by itself establish HIPAA compliance, and readers should verify their obligations against the current regulatory text.
Does following NIST SP 800-111 guarantee that data will be secure or that a breach will be avoided?
No single measure guarantees security or prevents all breaches. NIST SP 800-111 addresses encryption of stored data on end user devices, which typically helps protect information at rest if a device is lost or stolen. It does not, on its own, address data in transit, access controls, key management failures, insider threats, or other risk areas. Encryption of ePHI consistent with recognized guidance may, in some cases, affect whether an incident is treated as a reportable breach under the Breach Notification Rule, but that determination depends on the specific facts and current HHS guidance, which readers should confirm.
How does NIST SP 800-111 relate to the HIPAA Security Rule's encryption provisions?
NIST SP 800-111 provides technical guidance on storage encryption for end user devices, which can inform how an organization implements the encryption and decryption addressable specification within the Security Rule's technical safeguards. The Security Rule applies to ePHI and requires a risk analysis to determine whether encryption is reasonable and appropriate. Guidance like NIST SP 800-111 can support that decision and its documentation, but the regulatory obligation flows from the Security Rule, not from the NIST document.
What types of devices and data does NIST SP 800-111 typically address?
The publication generally focuses on encryption of data at rest on end user devices such as laptops and other portable or removable media, along with related considerations for the encryption technologies used. It is oriented toward protecting stored information, particularly on devices that may be lost or stolen. It is not primarily focused on data in transit or on enterprise server or network-level protections, so organizations should consult additional guidance for those scenarios.
How should an organization document its decision when using NIST SP 800-111 as a reference?
Because encryption is an addressable specification, an organization should document the outcome of its risk analysis, the encryption approach it selected, and its rationale, including any recognized guidance such as NIST SP 800-111 that it consulted. If the organization determines full encryption is not reasonable and appropriate in a given context, it should document that determination and any equivalent alternative measures adopted. This documentation supports demonstrating a reasoned, risk-based approach, though readers should confirm current expectations against applicable regulatory text and HHS guidance.
Do business associates need to consider NIST SP 800-111 guidance as well?
Business associates that create, receive, maintain, or transmit ePHI are directly subject to the Security Rule and must address the same technical safeguards, including the encryption addressable specification. Their specific obligations are also shaped by the terms of the applicable business associate agreement. Guidance such as NIST SP 800-111 can inform a business associate's implementation choices for storage encryption on end user devices, but as with covered entities, referencing it does not by itself establish compliance, and state law or other frameworks may impose additional requirements that should be verified.

Common misconceptions

Following NIST SP 800-111 makes an organization HIPAA compliant.
NIST SP 800-111 is technical guidance from NIST, not a HIPAA regulation. HIPAA is enforced by HHS OCR. Using the guidance may support the encryption portion of the Security Rule's technical safeguards, but HIPAA compliance also requires administrative and physical safeguards, risk analysis, policies, and other obligations that this single document does not address.
Because encryption is an addressable specification, storage encryption is optional.
Addressable does not mean optional under the HIPAA Security Rule. A regulated entity must implement the specification if reasonable and appropriate, implement an equivalent alternative measure, or document the rationale for not doing so based on its risk analysis. NIST SP 800-111 informs how encryption might be implemented but does not change this addressable-versus-required framework.
Applying storage encryption per NIST SP 800-111 guarantees breach safe harbor and prevents all breaches.
Encryption generally reduces the risk that lost or stolen device data is accessible, and properly rendered ePHI may fall outside a reportable breach under HHS OCR guidance. However, no measure guarantees compliance or prevents all breaches; safe harbor depends on the specific method used, key protection, and current HHS guidance, which should be verified against the applicable regulatory text.

Best practices

Treat NIST SP 800-111 as a supporting technical reference within a broader HIPAA compliance program, and pair it with a documented risk analysis addressing administrative, physical, and technical safeguards for ePHI.
Document the decision-making for encryption as an addressable specification, recording whether the measure was implemented, an equivalent alternative was adopted, or a reasoned justification for not implementing it.
Select a storage encryption approach (full disk, volume, or file-level) appropriate to the sensitivity of the ePHI and the device's use case, recognizing the different protection scopes each provides.
Establish strong authentication and disciplined key management, including secure key storage and recovery, since the protective value of encryption depends on how keys and credentials are safeguarded.
Verify that the encryption methods used align with the methods currently recognized by HHS OCR guidance if relying on encryption to keep ePHI outside the definition of a reportable breach, and confirm details against current guidance.
Check for additional obligations under state law, the HITECH Act, or other frameworks, since these may impose requirements on end user device protection beyond what NIST SP 800-111 or the HIPAA Security Rule address.