Retention periods for records technology teams hold
| Record type | Period | Rule | Who it applies to |
|---|---|---|---|
| HIPAA Security Rule policies and procedures, and written records of actions, activities or assessments the Security Rule requires to be documented1 | Period6 years from the date of creation or the date it was last in effect, whichever is later1 | Rule45 CFR 164.316(b)(2)(i)1 | Who it applies toHIPAA covered entities and business associates1 |
| Hospital medical records for each inpatient and outpatient2 | PeriodAt least 5 years, in original or legally reproduced form2 | Rule42 CFR 482.24(b)(1)2 | Who it applies toHospitals subject to 42 CFR part 4822 |
| Records that the Bank Secrecy Act regulations (31 CFR chapter X) require financial institutions to retain3 | Period5 years. Records kept under an order issued under 31 CFR 1010.370: the period in the order, not more than 5 years. Records must be accessible within a reasonable period of time.3 | Rule31 CFR 1010.430(d)3 | Who it applies toFinancial institutions required to keep records under 31 CFR chapter X3 |
| Broker-dealer records made under Rule 17a-3(a)(1) through (3), (5), (21) and (22), and analogous records created under Rule 17a-3(e)4 | PeriodAt least 6 years, the first 2 years in an easily accessible place4 | Rule17 CFR 240.17a-4(a)4 | Who it applies toMembers, brokers and dealers subject to 17 CFR 240.17a-34 |
| Other broker-dealer records listed in Rule 17a-4(b), including originals of communications received and copies of communications sent relating to the business4 | PeriodAt least 3 years, the first 2 years in an easily accessible place4 | Rule17 CFR 240.17a-4(b)4 | Who it applies toMembers, brokers and dealers subject to 17 CFR 240.17a-34 |
| FINRA books and records for which FINRA rules and Exchange Act rules set no period5 | PeriodAt least 6 years, in a format and media that complies with SEA Rule 17a-45 | RuleFINRA Rule 4511(b) and (c)5 | Who it applies toFINRA member firms5 |
| Regulation S-P records: documentation of detected unauthorized access to or use of customer information and the response and recovery, and of the investigation and determination of whether notification is required, including any Attorney General delay documentation and a copy of any notice sent4 | Period3 years from the date the records were made, in an easily accessible place4 | Rule17 CFR 240.17a-4(e)(14)(ii) and (iii), for duties under 17 CFR 248.30(a)(3) and (a)(4)4 | Who it applies toMembers, brokers and dealers subject to 17 CFR 240.17a-34 |
| Regulation S-P written policies and procedures (required by 17 CFR 248.30(a)(1), (a)(5)(i) and (b)(2)), and written documentation of any contract or agreement entered into under 17 CFR 248.30(a)(5)4 | PeriodUntil 3 years after the policies and procedures stop being used, or 3 years after the contract or agreement ends, in an easily accessible place4 | Rule17 CFR 240.17a-4(e)(14)(i), (iv), (v) and (vi)4 | Who it applies toMembers, brokers and dealers subject to 17 CFR 240.17a-34 |
| Records from systems designed to reconstruct material financial transactions sufficient to support normal operations and obligations (systems kept to the extent applicable and based on the risk assessment)6 | PeriodNot fewer than 5 years6 | Rule23 NYCRR 500.6(a)(1) and (b)6 | Who it applies toNYDFS covered entities: persons operating under, or required to operate under, a license, registration, charter, certificate, permit, accreditation or similar authorization under the Banking Law, the Insurance Law or the Financial Services Law6 |
| Audit trails designed to detect and respond to cybersecurity events that have a reasonable likelihood of materially harming any material part of normal operations (systems kept to the extent applicable and based on the risk assessment)6 | PeriodNot fewer than 3 years6 | Rule23 NYCRR 500.6(a)(2) and (b)6 | Who it applies toNYDFS covered entities6 |
| Federal agency computer security incident handling, reporting and follow-up records7 | PeriodDestroy 3 years after all necessary follow-up actions have been completed; longer retention is authorized if required for business use7 | RuleNARA General Records Schedule 3.2, item 0207 | Who it applies toFederal agencies (NARA General Records Schedule; use of the GRS is mandatory unless an agency justifies an agency-specific schedule)9 |
| Federal agency system access records (user profiles, log-in files, password files, audit trail files) for systems requiring special accountability for access7 | PeriodDestroy 6 years after the password is altered or the user account is terminated; longer retention is authorized if required for business use7 | RuleNARA General Records Schedule 3.2, item 0317 | Who it applies toFederal agencies (NARA General Records Schedule; use of the GRS is mandatory unless an agency justifies an agency-specific schedule)9 |
| Federal agency logs kept for cybersecurity event monitoring and for threat hunting, investigation, response and forensics (OMB M-26-14, which rescinded OMB M-21-31 with immediate effect on May 22, 2026)11 | PeriodActively searchable for at least 6 months after creation and retrievable for a year after creation; agencies must still meet any longer period set by agency-specific or government-wide records schedules11 | RuleOMB Memorandum M-26-14, Appendix B, item 111 | Who it applies toFederal agencies; not national security systems or the Department of Defense and Intelligence Community systems described in 44 U.S.C. 3553(e)11 |
| Federal agency IT operations and maintenance records, such as IT asset inventories, requests for service, work orders, maintenance schedules and problem reports8 | PeriodDestroy 3 years after the agreement, control measures, procedures, project, activity or transaction is obsolete, completed, terminated or superseded; longer retention is authorized if required for business use8 | RuleNARA General Records Schedule 3.1, item 0208 | Who it applies toFederal agencies (NARA General Records Schedule; use of the GRS is mandatory unless an agency justifies an agency-specific schedule)9 |
| Customer information held by financial institutions under the FTC Safeguards Rule10 | PeriodA disposal deadline: securely dispose of customer information no later than 2 years after it was last used to provide a product or service to the customer, unless it is necessary for business operations or other legitimate business purposes, required by law or regulation to be kept, or targeted disposal is not reasonably feasible. The data retention policy must be reviewed periodically.10 | Rule16 CFR 314.4(c)(6)10 | Who it applies toFinancial institutions over which the FTC has jurisdiction under the Gramm-Leach-Bliley Act (16 CFR 314.1), such as mortgage lenders, payday lenders, finance companies, mortgage brokers, check cashers and wire transferors10 |
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Method
We read each retention rule in its own text: the eCFR for federal regulations, FINRA's rulebook, the NYDFS copy of Part 500, NARA's General Records Schedules 3.1 and 3.2 and OMB Memorandum M-26-14 (opened on whitehouse.gov on 2026-11-14, when it replaced the row that cited the rescinded M-21-31). Each cell was compared with its source on 2026-11-13 and again on 2026-11-14. Periods are worded as each rule states them ('at least', 'not fewer than' or a fixed period). Records kept under parallel rules for other firm types were not compared. This table explains the rules; it is not legal advice. Time-sensitive cells were re-checked against their sources on 2026-11-14.
Notes
- NARA schedules say when federal records may be destroyed, and authorize longer retention for business use; the FTC Safeguards Rule sets a disposal deadline rather than a retention period.
- FINRA Rule 4511(b) applies only to FINRA books and records for which FINRA rules and Exchange Act rules set no period.
- NARA's General Records Schedule 3.2 (Transmittal No. 33, January 2023), as published on 2026-11-14, still describes cybersecurity event logs as those required by OMB M-21-31 (item 036, destroy when 30 months old); OMB rescinded M-21-31 in M-26-14 on May 22, 2026, and M-26-14 says its retention minimums do not relieve agencies of records schedule obligations.
Sources
- U.S. Department of Health and Human Services. 45 CFR 164.316, Policies and procedures and documentation requirements. Checked .
- Centers for Medicare & Medicaid Services. 42 CFR 482.24, Condition of participation: Medical record services. Checked .
- Financial Crimes Enforcement Network, U.S. Department of the Treasury. 31 CFR 1010.430, Nature of records and retention period. Checked .
- U.S. Securities and Exchange Commission. 17 CFR 240.17a-4, Records to be preserved by certain exchange members, brokers and dealers. Checked .
- Financial Industry Regulatory Authority. FINRA Rule 4511, General Requirements (books and records). Checked .
- New York State Department of Financial Services. 23 NYCRR Part 500, Cybersecurity Requirements for Financial Services Companies, sections 500.1 and 500.6 (DFS copy; DFS notes it is not an official version). Checked .
- National Archives and Records Administration. General Records Schedule 3.2: Information Systems Security Records (Transmittal No. 33, January 2023). Checked .
- National Archives and Records Administration. General Records Schedule 3.1: General Technology Management Records (last updated in Transmittal No. 30, November 2019). Checked .
- National Archives and Records Administration. General Records Schedules (GRS). Checked .
- Federal Trade Commission. 16 CFR part 314, Standards for Safeguarding Customer Information (314.1 and 314.4). Checked .
- Office of Management and Budget, Executive Office of the President. OMB Memorandum M-26-14, Ensuring Effective and Efficient Agency Logging and Network Visibility to Defend Against Evolving Cyber Threats (May 22, 2026), pages 1, 2 and 6 (Appendix B, item 1). Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the table where needed.