The FTC Safeguards Rule (16 CFR part 314) and its 500-consumer breach notice, explained

Financial institutions under the FTC’s jurisdiction must keep a written information security program with specific elements, and since May 13, 2024 must tell the FTC within 30 days of discovering a notification event that involves at least 500 consumers.

The Safeguards Rule sets standards for developing, implementing and maintaining reasonable administrative, technical and physical safeguards for customer information. It implements sections 501 and 505(b)(2) of the Gramm-Leach-Bliley Act and applies to the financial institutions over which the Federal Trade Commission has jurisdiction [1].

Who counts as a financial institution

An entity is a financial institution if its business is engaging in an activity that is financial in nature, or incidental to financial activities, as described in section 4(k) of the Bank Holding Company Act; an institution significantly engaged in such activities is covered [1]. The rule lists examples, including:

  • a retailer that extends credit by issuing its own credit card directly to consumers;
  • an automobile dealership that, as a usual part of its business, leases automobiles on a nonoperating basis for longer than 90 days;
  • a personal property or real estate appraiser;
  • a business that prints and sells checks for consumers [1].

The 2021 amendments widened the definition to include activities the Federal Reserve Board has found incidental to financial activities, which the FTC said brings “finders”, companies that bring together buyers and sellers of a product or service, within the rule [2].

The written information security program

Each institution must keep a comprehensive information security program, written in one or more readily accessible parts, with safeguards appropriate to its size and complexity, the nature and scope of its activities and the sensitivity of the customer information [1]. Section 314.4 lists the elements:

  1. A Qualified Individual who oversees and enforces the program. That person may work for the institution, an affiliate or a service provider; if the role is outsourced, the institution keeps responsibility, designates a senior staff member to direct and oversee the person, and requires the provider to protect it under the rule.
  2. A written risk assessment with criteria for evaluating and categorizing risks, criteria for assessing confidentiality, integrity and availability, and requirements for how risks will be mitigated or accepted, repeated periodically.
  3. Safeguards that include periodically reviewed access controls; identifying and managing the data, personnel, devices, systems and facilities the business relies on, by their importance to business objectives; encryption of customer information in transit over external networks and at rest, with compensating controls approved by the Qualified Individual where encryption is infeasible; secure development practices and testing of externally developed applications; multi-factor authentication for any individual accessing any information system, unless the Qualified Individual approves equivalent or more secure controls in writing; disposal of customer information no later than two years after it was last used for the customer, subject to listed exceptions; change management; and monitoring and logging of authorized users’ activity.
  4. Testing or monitoring of key controls. For information systems, this means continuous monitoring or, absent it, annual penetration testing and vulnerability assessments at least every six months and after material changes.
  5. Training and staffing: security awareness training, qualified security personnel, and steps to keep key staff current on threats.
  6. Service provider oversight: choosing capable providers, requiring safeguards by contract and periodically assessing them.
  7. Program adjustments in light of testing, business changes and new risk assessments.
  8. A written incident response plan covering its goals, internal response processes, roles and decision-making authority, communications and information sharing, remediation of identified weaknesses, documentation and reporting of security events, and revision of the plan after an event.
  9. A written report from the Qualified Individual to the board or equivalent governing body, regularly and at least annually, on the program’s overall status and material matters [1].

Under section 314.6, institutions that maintain customer information concerning fewer than 5,000 consumers are exempt from the written risk assessment in 314.4(b)(1), the monitoring and testing requirement in 314.4(d)(2), the incident response plan in 314.4(h) and the board report in 314.4(i) [1]. The other elements still apply to them.

The 2023 amendment: telling the FTC about notification events

The FTC published the notification amendment on November 13, 2023, effective May 13, 2024 [4]. It added section 314.4(j), and section 314.5 now states that 314.4(j) is effective as of May 13, 2024 [1].

What triggers it

A notification event is the acquisition of unencrypted customer information without the authorization of the individual it pertains to. Two details matter. Customer information counts as unencrypted if the encryption key was accessed by an unauthorized person. And unauthorized access to unencrypted customer information is presumed to be unauthorized acquisition unless the institution has reliable evidence that there has not been, or could not reasonably have been, acquisition [1].

The duty applies when a notification event involves the information of at least 500 consumers. The institution must notify the FTC as soon as possible and no later than 30 days after discovery [1]. An event is treated as discovered on the first day it is known to the institution, and the institution is deemed to know of it if any employee, officer or other agent, other than the person committing the breach, knows [1].

What the notice says

The notice is filed electronically on a form on the FTC’s website and includes:

  • the institution’s name and contact information;
  • the types of information involved;
  • the date or date range of the event, if possible to determine;
  • the number of consumers affected or potentially affected;
  • a general description of the event; and
  • whether a law enforcement official has determined in writing that public notice would impede a criminal investigation or damage national security, with a way for the FTC to contact that official [1].

A law enforcement official may request an initial delay of up to 30 days after notice to the FTC, extendable by up to 60 more days on a written request; further delay is possible only if FTC staff determine that public disclosure still threatens an investigation or national security [1]. In the final rule, the Commission said it intends to enter notification event reports into a publicly available database [4].

Section 314.4(j) is a notice to the Commission [1]. The Commission chose not to add a direct consumer notification requirement, saying that because all states have some form of consumer notification requirement, one in the Safeguards Rule would be largely duplicative of those state laws [4].

How the rule reached its current form

  • May 23, 2002: the original rule (67 FR 36493), per the eCFR source note [1].
  • December 9, 2021: the FTC published amendments that, among other things, added detailed program elements and the board report, exempted institutions with less customer information from some requirements and widened the definition of financial institution. They took effect January 10, 2022, with certain provisions set to apply from December 9, 2022 [2].
  • November 23, 2022: the FTC delayed those provisions to June 9, 2023, citing a reported shortage of qualified personnel and supply chain issues [3].
  • November 13, 2023: the notification amendment, effective May 13, 2024 [4].

We checked the eCFR version of part 314 dated November 1, 2026 on November 14, 2026; the sections described above read as summarized here [1].

This explainer describes the rule; it is not legal advice, and institutions should confirm with counsel whether and how it applies to them. The program elements are broken into steps in the companion FTC Safeguards Rule checklist.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • FTC
  • Safeguards Rule
  • 16 CFR part 314
  • Gramm-Leach-Bliley Act
  • breach notification
  • Qualified Individual
  • encryption