If you run a non-bank mortgage lender or brokerage, the FTC Safeguards Rule almost certainly applies to you. The FTC specifically lists mortgage lenders and mortgage brokers as examples of the financial institutions it covers.
The rule requires a written information security program built from nine elements. The language in the regulation can be dense, so here's each one in plain English, along with what it usually looks like in a smaller office.
1. Put a qualified person in charge
Someone has to be responsible for your information security program. It can be an employee, or someone at an outside company like your IT provider. If you use an outside company, a senior member of your own staff has to oversee them, the provider has to maintain its own security program that protects you, and your company remains responsible for compliance.
In a small office: an owner or operations lead is named as the responsible person, often working with the IT provider who handles the technical side.
2. Do a written risk assessment
You need to identify the reasonably foreseeable risks to customer information, internal and external, and judge how well your current safeguards handle them. This has to be written down, and you must repeat it periodically.
In a small office: a document that lists where borrower data lives (your loan origination system, email, file shares, laptops, scanners), what could go wrong with each, and what's in place to prevent it.
3. Put safeguards in place
This is the biggest element. Based on your risk assessment, the rule calls for specific controls, including:
- Access controls. People only get access to the customer information they need for their job.
- Know your data and systems. Keep track of the data, devices and systems you have and where they are.
- Encryption. Customer information is encrypted when it's stored and when it's sent over outside networks.
- Secure apps. Any software you build in-house is developed securely, and outside apps that handle customer information are evaluated for security.
- Multi-factor authentication. Required for anyone accessing your information systems.
- Secure disposal. Customer information is disposed of securely, generally no later than two years after you last used it to serve that customer, unless you need it for a business or legal reason.
- Change management. Changes to your systems are planned and controlled.
- Monitoring activity. You track what authorized users are doing and watch for unauthorized access.
In a small office: MFA on email and your LOS, encrypted laptops, unique logins for every person, access removed the day someone leaves, and a shredding and data retention routine.
4. Test and monitor your safeguards
You have to check that your safeguards actually work. The rule gives two paths: continuous monitoring, or annual penetration testing plus vulnerability assessments at least every six months. You also need to test after major changes to your business or systems.
In a small office: often the second path, an annual penetration test plus vulnerability scans at least every six months, with the reports kept on file. Ask your IT provider which path you're on. Security monitoring that watches for attacks is valuable, but it isn't automatically the same thing as the continuous monitoring the rule describes.
5. Train your staff
Everyone needs security awareness training, and the people who manage your security need training suited to that work.
In a small office: regular training on spotting phishing and wire fraud scams, with records of who completed it.
6. Oversee your service providers
Pick vendors that can protect your customer information, require them in your contracts to do so, and check on them periodically.
In a small office: a list of the vendors that touch borrower data, such as your LOS provider, IT company and document storage, with their security commitments on file.
7. Keep the program current
Update your program as your business changes. New systems, new locations, new threats and the results of your testing should all feed back into it.
In a small office: a set time each year to review the program, plus updates whenever something big changes.
8. Write an incident response plan
You need a written plan for responding to a security event. It should cover goals, roles and responsibilities, how you'll communicate, how you'll fix the problem, and how you'll document what happened and learn from it.
In a small office: a short, practical plan that says who to call, what to shut off, and how to notify the right people.
9. Report to your board or owners
At least once a year, your qualified person reports in writing to your board, or to a senior officer if you don't have a board. The report covers the overall status of the program and material issues.
In a small office: a short annual report to the owners.
The small-company exemption
If your company maintains customer information on fewer than 5,000 consumers, some requirements don't apply to you. Those are the written risk assessment, the continuous monitoring or penetration testing requirement, the written incident response plan and the annual report to the board.
The rest still applies, including the qualified person, the safeguards, training and vendor oversight. You also still have to base your program on a risk assessment and repeat it periodically. It just doesn't have to follow the written-assessment requirements. A written incident plan is still good practice.
Reporting a breach to the FTC
Since May 2024, the rule has also required you to notify the FTC as soon as possible, and no later than 30 days after you discover it, when unencrypted customer information involving at least 500 consumers is acquired without authorization. This applies even if you qualify for the small-company exemption. Planning for it is a good reason to keep an incident response plan current.
Common gaps
When mortgage offices look closely, the usual weak spots are MFA that covers email but not everything else, laptops that aren't encrypted, former employees who still have access, no written incident plan, and no record of staff training. Most of these can be fixed quickly once someone is looking.
Where to start
Begin with the risk assessment. It tells you where borrower data lives and which safeguards matter most, and everything else builds on it.
We help mortgage offices put the technical safeguards in place and keep the documentation ready for an examiner or investor. This checklist is a simplified summary, not legal advice. Your attorney or compliance officer can confirm how the rule applies to your business.