# Checklist: the FTC Safeguards Rule information security program, element by element

Fourteen steps for non-bank financial institutions under the FTC’s jurisdiction, from naming a Qualified Individual to the 30-day notice to the FTC when unencrypted information about 500 or more consumers is taken, each tied to 16 CFR 314.4.

Checklist · Financial Services · Platforms & Architecture. Published November 14, 2026. Last reviewed November 14, 2026.

## Who the rule reaches

Part 314 applies to the financial institutions over which the FTC has jurisdiction: businesses significantly engaged in activities that are financial in nature or incidental to them under section 4(k) of the Bank Holding Company Act [1]. The rule’s own examples include an automobile dealership that leases cars for longer than 90 days and a company acting as a finder between buyers and sellers. Section 314.3 requires a written information security program containing the elements of section 314.4, scaled to the institution’s size, complexity and the sensitivity of the information. The duty to notify the FTC in section 314.4(j) was added by an amendment published on November 13, 2023 and took effect on May 13, 2024 [1] [2].

## Using the steps

Each step names the element, who usually owns it and the paragraph of section 314.4 behind it. Section 314.6 exempts institutions that hold customer information about fewer than 5,000 consumers from four elements: the written risk assessment, the testing schedule, the written incident response plan and the annual report to the board [1]. Steps that are our suggestions are labeled. This page explains the rule; it is not legal advice.

## The checklist

1. **Confirm the business is a financial institution under the FTC’s jurisdiction, and count the consumers whose information it holds to see whether section 314.6 applies.** (General counsel or compliance lead) Section 314.1(b) and the definition in section 314.2(h) set the scope; section 314.6 sets the 5,000-consumer threshold [1].
2. **Designate a Qualified Individual to oversee, implement and enforce the program; if that person works for an affiliate or service provider, name a senior employee to direct and oversee them.** (Chief executive or board) Required by section 314.4(a). When the role is outsourced, the institution keeps responsibility for compliance and must require the provider or affiliate to maintain a program that protects it [1].
3. **Write the risk assessment with criteria for rating risks, criteria for assessing confidentiality, integrity and availability, and how each risk will be mitigated or accepted; then schedule the next one.** (Qualified Individual) Required by section 314.4(b)(1) and (2), which also call for periodic reassessment [1].
4. **Inventory the data, personnel, devices, systems and facilities the business runs on, ranked by importance.** (IT operations) Required by section 314.4(c)(2): identify and manage them in line with their relative importance to business objectives and the risk strategy [1].
5. **Restrict access to customer information to authorized users and to what each needs, review that access periodically, and require multi-factor authentication for any individual accessing any information system.** (Identity and access management) Section 314.4(c)(1) sets the access controls; section 314.4(c)(5) requires multi-factor authentication unless the Qualified Individual approves in writing reasonably equivalent or more secure controls [1].
6. **Encrypt customer information in transit over external networks and at rest, and record any compensating control the Qualified Individual approves where encryption is infeasible.** (Security engineering) Required by section 314.4(c)(3) [1].
7. **Adopt secure development practices for in-house applications that handle customer information, a way to assess externally developed ones, change management, and logging of authorized users’ activity.** (Engineering with the Qualified Individual) Required by section 314.4(c)(4), (7) and (8) [1].
8. **Set disposal procedures so customer information is disposed of no later than two years after it was last used to serve the customer, unless an exception applies, and review the retention policy periodically.** (Records management) Section 314.4(c)(6) lists the exceptions: information needed for business operations or other legitimate purposes, information other law requires to be kept, and cases where targeted disposal is not reasonably feasible [1].
9. **Choose continuous monitoring, or schedule annual penetration testing and vulnerability assessments at least every six months and after material changes.** (Security operations) Required by section 314.4(d)(1) and (2) [1].
10. **Run security awareness training, and make sure enough qualified security staff, in-house or outsourced, run the program and keep their knowledge current.** (Qualified Individual with HR) Required by section 314.4(e)(1) to (4) [1].
11. **Select service providers that can safeguard customer information, require safeguards by contract, and reassess providers periodically according to their risk.** (Procurement with the Qualified Individual) Required by section 314.4(f)(1) to (3) [1].
12. **Write the incident response plan with the seven areas the rule lists.** (Qualified Individual with legal) Section 314.4(h) lists goals; internal response processes; roles, responsibilities and decision authority; external and internal communications; remediation requirements; documentation and reporting; and revision of the plan after an event [1].
13. **Add the FTC notice to the incident plan: if a notification event involves information of at least 500 consumers, file on the FTC’s online form as soon as possible and no later than 30 days after discovery.** (Qualified Individual with legal) Section 314.4(j)(1) lists what the notice contains, including the types of information involved, the number of consumers affected and whether a law enforcement official has given a written determination that notifying the public would impede a criminal investigation or damage national security. A notification event is acquisition of unencrypted customer information without authorization, and unauthorized access is presumed to be acquisition without reliable evidence otherwise, under section 314.2(m). Under section 314.4(j)(2) the event counts as discovered on the first day any employee, officer or other agent (other than the person committing the breach) knows of it [1]. The FTC said in the 2023 amendment that it intends to put these reports in a publicly available database [2].
14. **Have the Qualified Individual report in writing to the board at least once a year, and adjust the program after testing, material business changes and new risk assessments.** (Qualified Individual and board) Section 314.4(i) sets the report’s contents, including the program’s overall status, risk decisions, service provider arrangements, test results and security events; section 314.4(g) requires the program to be evaluated and adjusted [1].

## Sources

1. Electronic Code of Federal Regulations. 16 CFR part 314, Standards for Safeguarding Customer Information (current text, checked November 14, 2026). <https://www.ecfr.gov/current/title-16/part-314> Checked November 14, 2026.
2. Federal Trade Commission, Federal Register (via GovInfo). Standards for Safeguarding Customer Information (final rule, 88 FR 77499, November 13, 2023). <https://www.govinfo.gov/content/pkg/FR-2023-11-13/html/2023-24412.htm> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-ftc-safeguards-rule-information-security-program>
Publisher: Moraph Insights
