# Encryption requirements at rest and in transit compared

**In short:** The FTC Safeguards Rule and the NYDFS Cybersecurity Regulation require encryption at rest and in transit over external networks, with approved compensating controls where encryption is infeasible (FTC: at rest or in transit; NYDFS: at rest only). The current HIPAA Security Rule makes encryption addressable rather than required, but breach notification applies only to unsecured data, so encryption that meets HHS guidance, with the key not breached, takes data outside it; the proposed update would require encryption but is not final as of 2026-11-14. FIPS 140-3 applies to federal agencies that use cryptography to protect sensitive information, and IRS Publication 1075 requires the latest FIPS 140 validated encryption for federal tax information; the CJIS Security Policy requires FIPS 140-3 certified modules or FIPS 197 (AES) for criminal justice information outside physically secure locations.

Cross-sector · Security & Resilience. Published November 13, 2026. Last reviewed November 14, 2026.

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. <https://creativecommons.org/licenses/by/4.0/>. Attribution: "Moraph Insights", <https://insights.moraph.com/compare/encryption-requirements>.

## The table

Each cell ends with the number of its source in "Sources". Cells were checked on November 14, 2026 unless the cell gives another date. Data: <https://insights.moraph.com/compare/encryption-requirements.csv> (CSV), <https://insights.moraph.com/compare/encryption-requirements.json> (JSON).

| Rule | Required or addressable | Standard named | Safe harbor | Citation |
|---|---|---|---|---|
| HIPAA Security Rule (current) [1] | Addressable, at rest and in transit: implement a mechanism to encrypt and decrypt ePHI, and to encrypt ePHI in transmission whenever deemed appropriate. Addressable means implement it if reasonable and appropriate, or document why not and use an equivalent alternative if reasonable and appropriate. [1] | None named in the rule. It defines encryption as an algorithmic process giving a low probability of assigning meaning without a confidential process or key (164.304). [1] | Yes. Breach notification applies only to unsecured PHI (45 CFR 164.402). HHS guidance names encryption consistent with NIST SP 800-111 for data at rest, and NIST SP 800-52, 800-77, 800-113 or FIPS 140-2 validated processes for data in motion, with the key not breached. [2] | 45 CFR 164.304, 164.306(d)(3), 164.312(a)(2)(iv), 164.312(e)(2)(ii) [1] |
| HIPAA Security Rule (proposed update) [3] | Proposed, not in force: encrypt all ePHI at rest and in transit, with listed exceptions. As of 2026-11-14 the Federal Register shows no final rule. [3] | Encryption that meets prevailing cryptographic standards [3] | The proposal does not amend the breach notification rule (45 CFR part 164, subpart D); it amends 45 CFR 160.103 and the Security Rule (subpart C) [3] | Proposed 45 CFR 164.312(b), 90 FR 898 [3] |
| FTC Safeguards Rule [4] | Required: encrypt all customer information held or transmitted, in transit over external networks and at rest. Where encryption is infeasible, effective alternative compensating controls reviewed and approved by the Qualified Individual. [4] | None named. Encryption must be consistent with current cryptographic standards and come with appropriate safeguards for key material. [5] | Yes, for FTC notification: a notification event is acquisition of unencrypted customer information. Data counts as unencrypted if the key was accessed. [5] | 16 CFR 314.4(c)(3); 314.2(f) and (m) [4] |
| NYDFS Cybersecurity Regulation [6] | Required: a written policy requiring encryption of nonpublic information in transit over external networks and at rest. If encryption at rest is infeasible, compensating controls approved in writing by the CISO; the CISO reviews feasibility and effectiveness at least annually. [6] | Encryption that meets industry standards [6] | None stated in 500.15 [6] | 23 NYCRR 500.15 [6] |
| FIPS 140-3 (federal agencies) [7] | Applies to all federal agencies that use cryptographic-based security systems to protect sensitive information; it shall be used in designing and implementing cryptographic modules that agencies operate or have operated for them under contract [7] | FIPS 140-3, four security levels for cryptographic modules [7] | None. The standard's requirements cover the design, implementation and operation of cryptographic modules, not breach notification. [7] | FIPS 140-3 (March 22, 2019) [7] |
| Executive Order 14028 [8] | Agencies shall adopt encryption for data at rest and in transit, to the maximum extent consistent with federal records laws and other applicable laws, within 180 days of May 12, 2021 [8] | None named in section 3(d) [8] | Not addressed in section 3(d) [8] | Executive Order 14028, sec. 3(d) [8] |
| IRS Publication 1075 [9] | Required for federal tax information: cryptographic protection in transit (SC-8) and at rest on end-user devices and portable storage (SC-28); in the cloud, encrypted in transit and at rest [9] | Latest FIPS 140 validated encryption; NIST SP 800-52 for TLS. SHA-1 for digital signatures is prohibited. [9] | None stated: the incident reporting section (1.8) has no exception for encrypted FTI. Separately, in the cloud, using FIPS 140 certified encryption at rest exempts third-party contractors from some protection requirements, such as training and background investigations. [9] | IRS Publication 1075, SC-8, SC-13, SC-28; section 1.8; cloud computing requirements [9] |
| CJIS Security Policy (version 6.1) [12] | Required for criminal justice information (CJI): cryptographic mechanisms to prevent unauthorized disclosure of CJI in transmission (SC-8(1)), and of CJI at rest on systems and digital media outside physically secure locations (SC-28(1)) [12] | FIPS 140-3 certified modules, or FIPS 197 (AES), with a symmetric key of at least 256 bits in transit and at rest (version 6.0 allowed 128 bits in transit and for FIPS 140-3 modules at rest). The policy says FIPS 140-2 certificates are not acceptable after September 21, 2026 [12] | Not addressed in SC-8, SC-13 or SC-28 [12] | CJIS Security Policy v6.1, SC-8(1), SC-13, SC-28 and SC-28(1) [12] |
| GLBA Interagency Guidelines Establishing Information Security Standards [10] | A measure each bank must consider and adopt if it concludes it is appropriate: encryption of electronic customer information, including in transit or in storage on networks or systems unauthorized people may access [10] | None named [10] | Not addressed in the guidelines' encryption measure [10] | 12 CFR part 30, appendix B, III.C.1.c (OCC text) [10] |
| FTC Health Breach Notification Rule [11] | No encryption requirement in the rule [11] | Refers to the HHS guidance on technologies and methods that secure information [11] | Yes. Notification applies to unsecured information: information not protected by a technology or method in the HHS guidance under section 13402(h)(2) of the 2009 Recovery Act. [11] | 16 CFR 318.2 (definition of unsecured) [11] |

## Method

We read each rule in its official source: the eCFR for federal regulations, the Federal Register for the executive order, the HIPAA proposal and HHS's 2009 encryption guidance, the NYDFS copy of Part 500, NIST's FIPS 140-3 page, the IRS's current Publication 1075 and the FBI's CJIS Security Policy version 6.1 PDF (dated 06/25/2026, opened on 2026-11-14; the FBI's CJIS resource center page blocks automated access, so whether a version later than 6.1 exists could not be checked). Version 6.1 raised the CJIS minimum symmetric key from 128 to 256 bits for CJI in transit and for FIPS 140-3 modules at rest. Cells were first checked on 2026-11-13 (the CJIS row on 2026-11-14), and every cell was re-checked on 2026-11-14 against its source. The HIPAA Security Rule is cited from the eCFR text of 45 CFR part 164, subpart C. Safe harbor means a rule where encrypted data falls outside a notification duty. Sources we could not open or cite were left out (see Omitted). This table explains the rules; it is not legal advice.

## Omitted

- **A row left out:** No single primary source summarizes state breach-law encryption safe harbors; a summary row would rest on secondary compilations.

## Notes

- The HHS guidance is cited from its 2009 Federal Register text; the HHS web page that carries the current guidance blocked automated access on 2026-11-13.
- The GLBA guidelines are shown in the OCC's text; the Federal Reserve and FDIC publish their own versions in their rules.
- NYDFS publishes the amended Part 500 on its website with a note that its copy is not an official version.

## Sources

1. U.S. Department of Health and Human Services. 45 CFR part 164, subpart C, Security Standards (HIPAA Security Rule): 164.304, 164.306(d) and 164.312. <https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C> Checked November 14, 2026.
2. U.S. Department of Health and Human Services. Breach Notification for Unsecured Protected Health Information, interim final rule with guidance on technologies that render PHI unusable (74 FR 42740). <https://www.federalregister.gov/documents/2009/08/24/E9-20169/breach-notification-for-unsecured-protected-health-information> Checked November 14, 2026.
3. U.S. Department of Health and Human Services. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule (90 FR 898). <https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information> Checked November 14, 2026.
4. Federal Trade Commission. 16 CFR 314.4(c)(3), Standards for Safeguarding Customer Information. <https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314/section-314.4> Checked November 14, 2026.
5. Federal Trade Commission. 16 CFR 314.2, Definitions (encryption; notification event). <https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314/section-314.2> Checked November 14, 2026.
6. New York State Department of Financial Services. 23 NYCRR 500.15, Second Amendment text (DFS copy; DFS notes it is not an official version). <https://www.dfs.ny.gov/system/files/documents/2026/10/NYCRR-part-500-Cybersecurity-Regulation_1.pdf> Checked November 14, 2026.
7. National Institute of Standards and Technology. FIPS 140-3, Security Requirements for Cryptographic Modules. <https://csrc.nist.gov/pubs/fips/140-3/final> Checked November 14, 2026.
8. Executive Office of the President (published by the Office of the Federal Register). Executive Order 14028, Improving the Nation's Cybersecurity, section 3(d) (86 FR 26633). <https://www.federalregister.gov/documents/2021/05/17/2021-10460/improving-the-nations-cybersecurity> Checked November 14, 2026.
9. Internal Revenue Service. IRS Publication 1075 (Rev. 11-2021), Tax Information Security Guidelines for Federal, State and Local Agencies, controls SC-8, SC-13, SC-28, section 1.8 and cloud requirements. <https://www.irs.gov/pub/irs-pdf/p1075.pdf> Checked November 14, 2026.
10. Office of the Comptroller of the Currency. 12 CFR part 30, appendix B, Interagency Guidelines Establishing Information Security Standards (OCC text). <https://www.ecfr.gov/current/title-12/chapter-I/part-30/appendix-Appendix%20B%20to%20Part%2030> Checked November 14, 2026.
11. Federal Trade Commission. 16 CFR 318.2, Health Breach Notification Rule definitions. <https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-318/section-318.2> Checked November 14, 2026.
12. Federal Bureau of Investigation, Criminal Justice Information Services Division. Criminal Justice Information Services (CJIS) Security Policy, Version 6.1 (06/25/2026), controls SC-8(1), SC-13 and SC-28(1). <https://le.fbi.gov/file-repository/cjis_security_policy_v6-1_20260625-1.pdf> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/compare/encryption-requirements>
Publisher: Moraph Insights
