Skip to main content

FTC Safeguards Rule (16 CFR Part 314): Requirements and Checklist

The FTC Safeguards Rule is the Federal Trade Commission's regulation, at 16 CFR Part 314, that requires non-bank financial institutions under its jurisdiction to keep a written information security program protecting customer information. It implements the Gramm-Leach-Bliley Act (GLBA), which is why it is also searched for as the GLBA Safeguards Rule.

By · Last updated 21 November 2026

At a glance

Framework
FTC Safeguards Rule
Issuer
US Federal Trade Commission (FTC)
Current edition
16 CFR Part 314, as amended in December 2021 and November 2023, eCFR current to 19 November 2026; paragraph 314.4(j) effective 13 May 2024
Legal status
Regulation
Jurisdiction
United States; financial institutions over which the FTC has jurisdiction under the Gramm-Leach-Bliley Act
How it is assessed
The Rule defines no certificate or accreditation scheme; each covered institution is responsible for keeping its own written program
Scope
Handling of customer information by financial institutions over which the FTC has jurisdiction, meaning those not under another regulator's enforcement authority under GLBA section 505.

How it is structured

Section 314.3 requires a covered institution to “develop, implement, and maintain a comprehensive information security program” that is written in one or more readily accessible parts and contains administrative, technical and physical safeguards appropriate to its size and complexity, the nature and scope of its activities, and the sensitivity of the customer information it holds. Section 314.4 then sets out what that program must include, in paragraphs (a) to (j): ten elements in the eCFR text.

The FTC’s business guide gives the figure as nine and discusses FTC notification separately, so the eCFR’s ten paragraphs and the guide’s nine listed items cover the same text. Two later pieces of the Rule matter for scoping. Section 314.5 makes paragraph 314.4(j) effective from 13 May 2024. Section 314.6 removes four paragraphs for smaller institutions, described below.

Which of your clients it applies to

Section 314.1(b) applies the Rule to financial institutions over which the FTC has jurisdiction, which it describes as those not subject to another regulator’s enforcement authority under GLBA section 505. An entity is a financial institution if its business is an activity that is financial in nature or incidental to one, and an institution must be significantly engaged in such activities. The eCFR lists, among others, mortgage lenders, mortgage brokers, payday lenders, finance companies, account servicers, check cashers, collection agencies, credit counsellors and other financial advisers, tax preparation firms, and investment advisers that are not required to register with the SEC.

The definitions add examples that surprise MSP clients. An accountant or other tax preparation service that completes income tax returns is a financial institution. So is a retailer that issues its own credit card directly to consumers, and an automobile dealership that, as a usual part of its business, leases cars on a nonoperating basis for longer than 90 days, with respect to its leasing business. A retailer that only accepts cards issued by others is not. Whether a particular client is covered is a legal question; read the definitions in section 314.2 with the client, and confirm with counsel.

Section 314.6 gives one size-based relief: paragraphs 314.4(b)(1), 314.4(d)(2), 314.4(h) and 314.4(i) do not apply to institutions that maintain customer information concerning fewer than 5,000 consumers. That covers the written form of the risk assessment, the continuous monitoring or penetration testing and vulnerability assessment requirement, the written incident response plan, and the annual written report to the board. Section 314.6 does not list paragraph 314.4(j), and the other paragraphs still apply.

How an MSP delivers it

This is practitioner guidance, not text from the Rule. Section 314.4(a) lets the Qualified Individual be employed by the institution, an affiliate or a service provider, which is the opening for an MSP. Where a service provider or affiliate fills the role, the institution must retain responsibility for compliance, designate a senior member of its own personnel to direct and oversee the Qualified Individual, and require the provider to maintain an information security program that protects the institution as the Rule requires. Put those three duties in the contract.

  1. Confirm coverage and the size test. Record why the client is a financial institution, and whether it maintains customer information concerning fewer than 5,000 consumers, so you know which paragraphs apply.
  2. Name the Qualified Individual and the internal overseer. Agree who holds the role, who supervises them at the client, and who answers for compliance.
  3. Write the risk assessment. Where the exception does not apply, it must be written and include the criteria in 314.4(b)(1). Plan the periodic reassessment that paragraph (b)(2) requires.
  4. Build the written program from the checklist below. Start from the free WISP template and replace every placeholder with the client’s own systems, owners and decisions.
  5. Implement and evidence the safeguards. Access control, data inventory, encryption, multi-factor authentication, disposal, change management and logging usually map onto an MSP’s existing stack; the work is recording them against the risk assessment.
  6. Set the testing and review cycle. Choose continuous monitoring or the penetration testing and vulnerability assessment cadence in paragraph (d), then book the annual report and the evaluation under paragraph (g).
  7. Write the incident runbook with the FTC decision in it. Include how a notification event is recognised, who decides whether 500 consumers are affected, and who files.
  8. Run it as governance. Treat the program as a living document; the Rule asks for periodic reassessment, evaluation after material changes and an annual report, so a one-off build goes stale.

Split responsibilities in writing: the client keeps the decisions on risk and compliance, and the MSP operates the technical safeguards and prepares the paperwork.

Requirements checklist

The first two columns follow section 314.4 of the eCFR text, paraphrased. The third column is a working example of the evidence an MSP typically prepares for each paragraph; it is not text from the Rule, and a regulator or counsel may ask for different material.

314.4 paragraph What the Rule requires Evidence an MSP typically prepares
(a) Qualified Individual Designate a Qualified Individual to oversee, implement and enforce the program; a service provider may fill the role if the institution keeps responsibility and oversees it Written appointment, named senior overseer, service provider contract clauses
(b) Risk assessment Base the program on a risk assessment of foreseeable internal and external risks; written, with evaluation criteria and risk treatment, unless 314.6 applies; reassess periodically Written risk assessment, risk criteria, treatment decisions, reassessment dates
(c) Safeguards Design and implement safeguards for the identified risks: access controls, data and system inventory, encryption in transit and at rest, secure development, multi-factor authentication, disposal, change management, and activity logging Access reviews, asset and data inventory, encryption settings, MFA coverage, disposal procedure, change records, log retention settings
(d) Testing and monitoring Regularly test or monitor key controls; continuous monitoring, or annual penetration testing and vulnerability assessments at least every six months, unless 314.6 applies Monitoring configuration or penetration test report, vulnerability scan history
(e) People Provide security awareness training updated for the risks found, use qualified security personnel, and keep them trained and current Training records, role descriptions, personnel development records
(f) Service providers Select and retain capable service providers, require safeguards by contract, and assess them periodically based on risk Provider list, contract clauses, periodic assessment records
(g) Evaluation and adjustment Adjust the program after testing, material changes to operations, risk assessments, or other known circumstances Program change log, review minutes
(h) Incident response plan Written plan covering goals, internal processes, roles and decision authority, communications, remediation, documentation and reporting, and revision after an event; not required under 314.6 Written plan, contact list, exercise or review record
(i) Report to the board Qualified Individual reports in writing, at least annually, to the board or equivalent, or to a senior officer; not required under 314.6 Annual written report, delivery record
(j) FTC notification Notify the FTC as soon as possible, and no later than 30 days after discovery, of a notification event involving at least 500 consumers Decision record, notification form copy, runbook step

Section 314.2 defines a notification event as acquisition of unencrypted customer information without the authorisation of the individual it pertains to; information counts as unencrypted if the encryption key was accessed by an unauthorised person. The notice is made electronically on a form on the FTC’s website and includes the institution’s name and contact details, the types of information involved, the date or date range if known, the number of consumers affected, a general description, and whether law enforcement has asked for a delay. The Rule lets a law enforcement official request an initial delay of up to 30 days, and further delay only on the terms in paragraph 314.4(j)(1)(vi).

Overlap with other frameworks

The GLBA Privacy Rule is a separate regulation. 16 CFR Part 313 governs privacy notices and the conditions for sharing nonpublic personal information with third parties. By its own scope it applies only to information about individuals who obtain financial products or services primarily for personal, family or household purposes, and as the eCFR reads, the FTC’s rulemaking authority there covers motor vehicle dealers. The Safeguards Rule has a different job: it covers how customer information is protected, and applies to all customer information in the institution’s possession, including information about customers of other financial institutions.

The Rule does not require a particular security framework, and the FTC’s business guide does not mention NIST or any other. Whether a client maps its program to another framework is a client decision. Where it does, the frameworks list shows which others are covered, and how control mapping works explains how evidence is reused across them.

Common mistakes

  • Assuming the exception covers everything. Section 314.6 removes four paragraphs only. A client under 5,000 consumers still needs a written program, a Qualified Individual, safeguards, training, provider oversight and, where the facts arise, FTC notification.
  • Describing the exception backwards. It applies to institutions that maintain customer information concerning fewer than 5,000 consumers, not more.
  • Treating the program as a one-time document. The Rule asks for periodic reassessment, regular testing or monitoring, and evaluation after material changes.
  • Handing the provider the whole job. Under paragraph 314.4(a) the institution keeps responsibility for compliance and must designate a senior member of its own personnel to oversee the Qualified Individual.
  • Leaving the notification step out of the incident plan. Paragraph 314.4(j) applies from 13 May 2024 and has its own 500-consumer and 30-day tests, which the written plan should point to.
  • Assuming a client is out of scope without reading the definitions. Read the examples in section 314.2, including the leasing and own-credit-card examples, before you tell a client the Rule does not reach it.

Where GetCybr fits

FTC Safeguards Rule is in GetCybr's framework catalogue, one of the 39 compliance frameworks on the frameworks list. The control wording in GetCybr is the issuer's official text. It is cross-mapped through the Secure Controls Framework (SCF) crosswalk, so evidence gathered for one control can often support another.

The delivery sequence above is work any practice can run by hand. GetCybr's part is keeping it repeatable across clients: assessments can run as a conversation, where GetCybr's AI interview asks the questions and drafts control maturity, and nothing is saved until your reviewer applies it. See how control mapping works for the crosswalk.

Help Center

FAQs have moved to the Help Center

Find current answers for the topics covered on this page in our consolidated FAQ.

Sources

General information, not legal advice. Check the text of the regulation itself, or take legal advice, before relying on this page for a client obligation.

Delivering FTC Safeguards across several clients?

See how a practice runs assessments, evidence and client reporting in one workspace.