Guide · FTC Safeguards Rule

The FTC Safeguards Rule for mortgage brokers and lenders

The FTC Safeguards Rule (16 CFR Part 314) names mortgage lenders and mortgage brokers among the financial institutions it covers, as long as another regulator doesn't oversee them under the Gramm-Leach-Bliley Act. If that's you, the rule requires a written information security program with specific parts: a Qualified Individual, a written risk assessment, safeguards, testing, training, vendor oversight, an incident response plan and a yearly written report to your board or owner.

Since May 13, 2024, it also requires you to notify the FTC no later than 30 days after you discover that unencrypted customer information on 500 or more consumers was acquired without authorization. Firms with customer information on fewer than 5,000 consumers are exempt from four specific requirements, but not from the rest of the rule and not from the FTC notice.

Who it covers

The scope section lists the kinds of companies the FTC means. Mortgage lenders, mortgage brokers and account servicers are on that list by name (314.1(b)). The rule applies to all customer information in your possession, including information other financial institutions give you about their customers.

The program has to be written, "in one or more readily accessible parts," and sized to you. The rule asks for safeguards "appropriate to your size and complexity, the nature and scope of your activities, and the sensitivity of any customer information at issue" (314.3(a)). A 12-person broker and a 300-person lender won't end up with the same program. They both need the same parts.

What the program has to include

Section 314.4 lists the elements. Here they are in the rule's order, in plain terms.

1. A Qualified Individual (314.4(a))

You designate one person to oversee, implement and enforce the program. That person can be your employee, or work for an affiliate or a service provider. If you use an outside person, you still keep responsibility for compliance, you name a senior member of your own staff to direct and oversee them, and you require the provider to keep a security program that protects you.

2. A written risk assessment (314.4(b))

The program has to be based on a risk assessment of the reasonably foreseeable internal and external risks to customer information. The written version must include criteria for rating the risks you find, criteria for assessing your systems and the controls you have, and how each risk will be reduced or accepted (314.4(b)(1)). You also have to repeat the assessment periodically (314.4(b)(2)).

3. Safeguards for the risks you found (314.4(c))

The rule names specific controls. Among them:

  • Access controls, so only authorized users get in and each one sees only what their job needs.
  • An inventory of the data, people, devices, systems and facilities your business runs on.
  • Encryption of customer information in transit over external networks and at rest. If that's infeasible, your Qualified Individual can review and approve effective compensating controls.
  • Secure development practices for apps you build, and a way to evaluate the outside apps you use.
  • Multi-factor authentication for anyone accessing any information system, unless your Qualified Individual approves equivalent or stronger controls in writing.
  • Secure disposal of customer information no later than 2 years after you last used it to serve that customer, unless you need it for business, the law requires you to keep it, or targeted disposal isn't reasonably feasible. You also review your retention policy periodically.
  • Change management procedures.
  • Monitoring and logging of what authorized users do, to catch unauthorized access or tampering.

4. Testing and monitoring (314.4(d))

You regularly test or monitor whether your key controls work. For information systems, that means continuous monitoring, or periodic penetration testing and vulnerability assessments. Without effective continuous monitoring, the rule calls for a penetration test every year and vulnerability assessments at least every 6 months and whenever your operations or business arrangements change materially (314.4(d)(2)). I scope that work and track the fixes. The testing itself comes from an independent firm.

5. Training and qualified people (314.4(e))

Staff get security awareness training that's updated for the risks your assessment found. You use qualified security personnel, your own or an affiliate's or a provider's, give them updates and training, and check that the key ones keep current on threats.

6. Service provider oversight (314.4(f))

Pick vendors that can protect the customer information they touch, require safeguards in the contract, and reassess them periodically based on the risk they present. For a lender, that list usually includes your LOS, POS, CRM, dialer, document storage and anyone else who handles borrower files.

7. Evaluate and adjust (314.4(g))

Update the program based on test results, new risk assessments, material changes to your business, or anything else you know could materially affect it.

8. A written incident response plan (314.4(h))

The plan has to cover seven areas: its goals; your internal response process; clear roles, responsibilities and decision authority; internal and external communications; fixing the weaknesses an event exposes; documenting and reporting events; and reviewing the plan after an event.

9. A yearly report to the board or owner (314.4(i))

Your Qualified Individual reports in writing, regularly and at least once a year, to your board or equivalent. With no board, the report goes to the senior officer responsible for the program. It covers the program's overall status and your compliance with the rule, plus material matters such as risk decisions, vendor arrangements, test results, security events and recommended changes.

The FTC notice: 500 consumers, 30 days

This part took effect May 13, 2024 (314.5). A "notification event" is the acquisition of unencrypted customer information without the authorization of the person it belongs to (314.2(m)). Two details matter:

  • Information counts as unencrypted if an unauthorized person got the encryption key.
  • Unauthorized access to unencrypted information is presumed to be acquisition, unless you have reliable evidence it wasn't, or couldn't reasonably have been, acquired.

If an event involves the information of at least 500 consumers, you notify the FTC as soon as possible and no later than 30 days after discovery, using the electronic form on ftc.gov (314.4(j)(1)). The notice covers who you are, what types of information were involved, the date or date range if you can tell, how many consumers were or may have been affected, a general description of the event, and whether law enforcement has told you in writing that public notice would impede a criminal investigation or harm national security.

The clock starts on the first day the event is known to you. It counts as known to you once any employee, officer or other agent knows about it, other than the person who committed the breach (314.4(j)(2)). That's a good reason for your incident response plan to say who decides whether an event is reportable and who files.

The small-firm exemption

Section 314.6 says four paragraphs don't apply to financial institutions that maintain customer information concerning fewer than 5,000 consumers:

  • 314.4(b)(1): the requirement that the risk assessment be written and include the listed criteria. Your program still has to be based on a risk assessment.
  • 314.4(d)(2): continuous monitoring, or the annual penetration test and 6-month vulnerability assessments. The general duty to test or monitor your controls in 314.4(d)(1) still applies.
  • 314.4(h): the written incident response plan.
  • 314.4(i): the Qualified Individual's yearly written report to the board or owner.

Everything else still applies, including the Qualified Individual, the safeguards, training, vendor oversight and the FTC notice. The test is how many consumers you maintain customer information about, not how many loans you closed this year.

Who asks to see it

The rule is the floor. In practice, lenders get asked for the same documents by several groups, each on their own form:

  • State examiners, who want to see the written program, the risk assessment and who owns it.
  • Warehouse lenders and investors, in their due-diligence questionnaires.
  • Cyber insurers at renewal, who ask about MFA, backups, training and your incident plan.
  • If you sell to lenders, your customers' vendor security reviews.

After the 2023 and 2024 cyberattacks on mortgage companies, those questions got more detailed. Building the evidence once, in one set of records, means you can answer each of them without starting over.

Where to start

If you're not sure where you stand, the 10-question Lender Security Snapshot maps quick yes/no questions to the elements above. If you're licensed in New York, read the NYDFS Part 500 guide too, since that regulation applies on top of this one.

I build and run the program the rule requires, sized to your shop: the written program, risk assessment, incident plan, vendor inventory, owner report and training. You can see how that works on the services page.

Sources

Educational, not legal advice. This guide summarizes 16 CFR Part 314 as published on eCFR, checked on November 15, 2026. Rules change, and how they apply depends on your business. Talk to your counsel about your obligations.

Book a 20-minute Safeguards check

Bring whatever you were asked for: the exam letter, the questionnaire or the renewal form. We'll go through where you stand against the rule and what to do first.