FTC Requires Non-Banking Financial Institutions to Report Data Security Breaches

February 12, 2024

Reading Time : 3 min

Beginning May 11, 2024, non-banking financial institutions regulated by the Federal Trade Commission (FTC) will be required to submit notifications of data breaches or other security events that impact 500+ consumers. The FTC issued a final rule (the Rule) amending its Safeguards Rule1 to impose this notification requirement. The FTC has indicated that such notices will be entered into a publicly available database. Below, we have outlined key requirements for non-banking financial institutions and next steps for compliance.

Key Requirements of the Revised Safeguard Rule

Who Needs to Report?

The Rule applies to all non-banking financial institutions regulated by the FTC, including exempt reporting advisers, state-registered advisers, technology companies, mortgage brokers, credit counselors, financial planners, credit reporting agencies and tax preparers, among others.

When Do You Need to Report?

The Rule requires covered entities to report a “notification event” that impacts at least 500 consumers to the FTC as soon as possible, but no later than 30 days following discovery. A “notification event” means acquisition of unencrypted “customer information” without the authorization of such customer. It is important to keep in mind that under the Safeguards Rule, “customer information” is defined broadly to mean any record containing nonpublic personal information about a customer. For example, such information may include information provided by the consumer to obtain a financial product or service and information collected through cookies on a website.2 The scope of noticeable information as defined in the Rule is much broader than most state data breach notification statutes.

Additionally, in defining a notification event, the FTC specifies that “customer information is considered unencrypted for this purpose if the encryption key was accessed by an unauthorized person.”

The Rule also specifies that a notification event is considered discovered as of the first day on which the notification event is known to any person (other than the person committing the breach) that is an employee, officer or agent of the financial institution.

How Do You Report?

Notice to the FTC must be made electronically through a form that will be made available on the FTC’s website.

What Do You Need to Report?

The notice to the FTC must include:

  • Name and contact information of the reporting institution.
  • A description of the types of information that were involved.
  • The date or date range of the notification event (if possible to determine).
  • Number of consumers affected.
  • A general description of the notification event.
  • If applicable, whether any law enforcement official has provided the financial institution with a written determination that notifying the public of the breach would impede a criminal investigation or cause damage to national security, and a means for the FTC to contact the law enforcement official.

Notably, though not an exception to reporting requirement, the Rule provides that a law enforcement official may request a delay in the notice of up to 30 days. The delay may be extended for an additional period of up to 60 days if the law enforcement official seeks such an extension in writing. Such additional delay may only be permitted if the FTC staff determines that public disclosure would continue to impede a criminal investigation or cause damage to national security.

When Will the Rule Go into Effect?

The Rule will take effect May 11, 2024, which is 180 days after the Rule was published the Federal Register (November 13, 2023).

Next Steps

Covered institutions should review existing incident response plans and related policies and procedures to ensure that notification requirements enable timely reporting under the Rule. Additionally, the Rule will likely lead to increased exposure for covered institutions and further affirms the FTC’s ongoing engagement in security and privacy enforcement. Such entities should review their privacy and security programs for compliance with the Safeguards Rule and other requirements and implement any measures needed to enhance such compliance.

We will continue to monitor developments in this space and are happy to assist with your assessment of the Rule and your compliance programs. Please contact a member of Akin’s cybersecurity, privacy and data protection team to learn more about how these incoming regulations may affect your company.


1 The Safeguards Rule took effect in 2003 and was recently updated in 2021 to specify what safeguards financial institutions must implement as part of a security program to protect their customer’s financial information. This updated did not include any breach notification requirements, which was the purpose of the Rule. For additional information on the 2021 updates to the Safeguards Rule, please see our previous blog post here.

2 Note that the Safeguards Rule provides that a “cookie” is an information collecting device from a web server. 16 C.F.R § 314(n)(2).

Share This Insight

Previous Entries

Data Dive

October 17, 2024

During the course of any lending transaction, lenders will conduct a due diligence review of the borrower, including reviewing any relevant “know-your-customer” information. In the context of a fund finance transaction, this due diligence is likely to include a review of fund organizational documents, subscription agreements and side letters, if any, from the fund’s investors. Providing this information to lenders is an essential and practical aspect of incurring any fund-level financing, and is often expressly permitted by a fund’s governing documentation. Especially in the context of a subscription credit facility, where investor commitments and the related right to collect capital contributions are the primary source of repayment for the loan, a lender will need to see information that could potentially include sensitive or confidential information about investors.

...

Read More

Data Dive

September 17, 2024

Following the publication of the European Union’s Artificial Intelligence Act (AI Act or Act) on 12 July 2024, there are now a series of steps that various EU bodies need to take towards implementation. One of the first key steps is in relation to the establishment of codes of practice to “contribute to the proper application” of the AI Act.

...

Read More

Data Dive

August 6, 2024

On July 30, 2024, the Senate passed the Kids Online Safety and Privacy Act (S. 2073) via an overwhelmingly bipartisan vote of 91-3 shortly before departing for the August recess.

...

Read More

Data Dive

July 18, 2024

On 12 July 2024, the European Union Artificial Intelligence Act (AI Act or Act) was published in the Official Journal of the European Union (EU), marking the final step in the AI Act’s legislative journey. Its publication triggers the timeline for the entry into force of the myriad obligations under the AI Act, along with the deadlines we set out below. The requirement to ensure a sufficient level of AI literacy of staff dealing with the operation and use of AI systems will, for example, apply to all providers and deployers on 2 February 2025.

...

Read More

Data Dive

July 18, 2024

On June 18, 2024, the United States Securities and Exchange Commission (SEC) announced a settlement with R.R. Donnelley & Sons Company (RRD) for alleged internal control and disclosure failures following a ransomware attack in 2021. Without admitting or denying the SEC’s findings, the business communications and marketing services provider agreed to pay a civil penalty of over $2.1 million to settle charges alleging violations of Section 13(b)(2)(B) of the Securities Exchange Act of 1934 (Exchange Act) and Exchange Act Rule 13a-15(a).1

...

Read More

Data Dive

June 11, 2024

In May, the National Institute of Standards and Technology (NIST) issued updated recommendations for security controls for controlled unclassified information (CUI) that is processed, stored or transmitted by nonfederal organizations using nonfederal systems, (NIST Special Publication 800-171 (SP 800-171), Revision 3). These security requirements are “intended for use by federal agencies in contractual vehicles or other agreements that are established between those agencies and nonfederal organizations.”1 While these new controls are only applicable to nonfederal entities that agree to comply with the new issuance, Revision 3 signals the next phase of expected security for government contractors.

...

Read More

Data Dive

May 31, 2024

On May 21, 2024, the European Union finalized the adoption of the groundbreaking EU Artificial Intelligence Act, a comprehensive and sector-agnostic legislation that extends globally. This 420-page Act aims to regulate the deployment and development of AI systems, categorizing them into high-risk and low-risk, and even banning certain types of AI. The Act emphasizes trust, transparency, and accountability in AI usage, promoting the safe integration of AI technologies. This legislation sets a potential global benchmark for AI regulation, although its complexity may pose interpretative and implementation challenges for stakeholders. We set out the key provisions below.

...

Read More

Data Dive

May 30, 2024

On May 17, 2024, Colorado Governor Jared Polis signed into law S.B. 205, a pioneering piece of legislation aimed at regulating high-risk AI systems. This new law, set to take effect on February 1, 2026, introduces stringent requirements for AI developers and deployers, focusing on risk management and the prevention of algorithmic discrimination. This legislation marks a significant step in state-level AI regulation, potentially setting a precedent similar to the impact of GDPR on privacy laws.

...

Read More

© 2024 Akin Gump Strauss Hauer & Feld LLP. All rights reserved. Attorney advertising. This document is distributed for informational use only; it does not constitute legal advice and should not be used as such. Prior results do not guarantee a similar outcome. Akin is the practicing name of Akin Gump LLP, a New York limited liability partnership authorized and regulated by the Solicitors Regulation Authority under number 267321. A list of the partners is available for inspection at Eighth Floor, Ten Bishops Square, London E1 6EG. For more information about Akin Gump LLP, Akin Gump Strauss Hauer & Feld LLP and other associated entities under which the Akin Gump network operates worldwide, please see our Legal Notices page.