FTC Safeguards Rule checklist for MSPs
An FTC Safeguards Rule checklist for the MSP delivering compliance. All nine elements of 16 CFR 314.4 mapped to an owner, the stack component that covers each one and the evidence that survives an audit, plus the MFA and incident response plan requirements, the 5,000-consumer exemption and the 30-day FTC notice.
Updated: November 2026
The FTC Safeguards Rule (16 CFR Part 314) requires non-bank financial institutions such as tax preparers, mortgage brokers and auto dealers to run a written information security program with nine elements, a named Qualified Individual and an FTC report within 30 days of a breach involving 500 or more consumers. The legal obligation stays with the financial institution, while the technical work lands on whoever runs their IT. This checklist maps each element of 16 CFR 314.4 to an owner, the part of an MSP stack that covers it and the evidence an auditor will ask for.
TL;DR
- The checklist. The FTC Safeguards Rule has nine elements under 16 CFR 314.4: a Qualified Individual, risk assessment, eight technical safeguards, monitoring, training, provider oversight, program updates, an incident response plan, and an annual board report.
- Ownership. The financial institution stays accountable; the MSP executes and documents.
- Your exposure. Section 314.4(f) makes you a contracted service provider with written obligations.
- The clock. Breaches touching 500 or more consumers go to the FTC within 30 days.
Who the rule covers, and why your client probably qualifies
The Safeguards Rule applies to non-banking "financial institutions" under the Gramm-Leach-Bliley Act, and the FTC reads that phrase far more broadly than the phrase sounds. Tax preparers, CPA firms doing return work, mortgage brokers, auto dealers arranging financing, payday lenders, collection agencies, investment advisers not registered with the SEC, and career counselors serving finance clients all land inside it. The FTC's business guidance spells out the categories.
The practical test is simpler than the legal one. If your client collects a Social Security number, a bank account number, or income data in order to provide a financial product or service, they're in scope. Enforcement for the amended rule started June 9, 2023, so there's no grace period left to point at.
Two of your client verticals are worth flagging now. Accounting and tax firms hear the same requirement from the IRS: Publication 4557 tells tax professionals that the Safeguards Rule requires a written information security plan (WISP), and IRS Publication 5708 gives them a sample WISP to start from. If you already maintain a WISP for a tax client, map it to the 314.4 elements below before you write anything new. Auto dealerships are the other cluster, and the FTC publishes a separate Safeguards Rule FAQ for auto dealers.
The ownership split nobody writes down
The compliance argument between an MSP and a client starts from one unwritten assumption: each side thought the other had it. The rule itself is clear that accountability never transfers. The financial institution owns the program. You own execution and proof.
Here's the mapping, element by element.
| Element (16 CFR 314.4) | Who owns it | What satisfies it in the stack | Evidence artifact |
|---|---|---|---|
| (a) Qualified Individual | Client names the person, MSP supports | Named contact in the MSP agreement, defined escalation path | Board minutes or signed designation letter |
| (b) Written risk assessment | Client owns, MSP supplies technical input | Asset inventory from RMM, vulnerability scan output | Dated written assessment with criteria for scoring |
| (c)(1) Access controls | MSP | Identity provider, group policy, least-privilege review | Quarterly access review export |
| (c)(2) Data inventory | Shared | RMM and documentation platform, discovery scans | Living inventory of systems holding customer data |
| (c)(3) Encryption in transit and at rest | MSP | Disk encryption policy, TLS enforcement, mail encryption | Encryption status report per endpoint |
| (c)(4) Secure development | Client, only if they build apps | Code review and testing process | Written SDLC procedure |
| (c)(5) MFA | MSP | MFA for anyone accessing an information system, unless the Qualified Individual approves an equivalent control in writing | MFA coverage report plus the written exception approvals |
| (c)(6) Secure disposal | Shared | Retention schedule, certified wipe on decommission | Disposal certificates and retention policy |
| (c)(7) Change management | MSP | Ticketed change process in the PSA | Change log with approvals |
| (c)(8) Activity monitoring | MSP | SIEM or log aggregation with alerting on authorized-user activity | Log retention and alert history |
| (d) Testing | MSP delivers, client funds | Annual penetration test plus vulnerability assessments every six months, or continuous monitoring | Test reports with remediation tracking |
| (e) Training | Shared | Security awareness platform, role-based training for technical staff | Completion records and phishing simulation results |
| (f) Service provider oversight | Client owns, and you are the service provider | Contract clauses, vendor security reviews | Signed contracts with security obligations |
| (g) Program updates | Client owns, MSP triggers | Annual review tied to the risk assessment cycle | Version-controlled program document |
| (h) Incident response plan | MSP drafts, client approves | Written IR plan with roles, escalation, notification path | Tested plan plus tabletop exercise notes |
| (i) Annual board report | Client owns, MSP feeds data | Metrics pulled from the monitoring stack | Written report delivered to the board or equivalent |
Print that. Walk a client through it once, and the ambiguity that turns into a finger-pointing exercise after an incident disappears.
The qualified individual question you should answer carefully
Element (a) requires the client to designate a Qualified Individual to run the information security program. The rule permits that person to be an employee, an affiliate, or a service provider, which is why the question lands on MSP desks. No specific certification or title is required. What matters is relevant know-how for the size and complexity of the business.
Taking the designation looks like a revenue line. It's also a named-accountability role in a federal rule. When a service provider fills it, 314.4(a) still requires the client to retain responsibility for compliance, designate a senior member of their own staff to direct and oversee the Qualified Individual, and require the provider to maintain an information security program that protects them. If you accept it, the engagement needs to explicitly fund the time, define decision authority, and carry insurance that contemplates the role. If it doesn't, support the client's named individual instead and put that arrangement in writing. Either answer is defensible. Drifting into the role without a contract is not.
Where the written risk assessment falls apart
Element (b) is the hinge the rest of the program hangs on, and it fails in a predictable way: someone downloads a template, fills in generic threats, and files it. The rule asks for more than a document. It requires written criteria for evaluating and categorizing security risks, written criteria for assessing whether existing controls are adequate, and a written description of how identified risks will be mitigated or accepted.
Written criteria is the operative phrase. A risk rated "high" without a stated scale is a finding waiting to happen. The version that holds up names the systems in scope, scores each risk against a defined likelihood and impact scale, ties every mitigation to a specific control, and gets signed and dated by the Qualified Individual.
You supply the technical half: the asset inventory from the RMM, current scan results, and where patching and access stand today. A security posture assessment gathers most of that input in one pass. The client owns the risk decisions, especially the accepted ones, because accepting a risk is a business call and it needs their name on it.
The FTC MFA requirement in 314.4(c)(5)
Element (c)(5) reads broader than "MFA on email." It requires multi-factor authentication for any individual accessing any information system, and the rule's definition of an information system reaches any system that holds customer information or connects to one that does, including phone switches and environmental controls.
Multi-factor means verification through at least two of three factor types: something the user knows, such as a password; something they have, such as a token; or something they are, such as a fingerprint. A password plus a security question is one factor type used twice, so it doesn't count.
The one way around it is written approval. The Qualified Individual can approve reasonably equivalent or more secure access controls in writing, which is how a legacy line-of-business app or a shared service account stays compliant. Record each approval with the system name, the compensating control and a review date, and the MFA coverage report in your evidence pack becomes a list of approved exceptions instead of unexplained gaps.
Section 314.4(f) is the part that lands on you
This is the element that changes the conversation from "our client's compliance problem" to yours. Element (f) requires the financial institution to select service providers capable of maintaining appropriate safeguards, to contract with them to require those safeguards, and to periodically assess them based on risk.
You are that service provider. Every financial-services client you serve is obligated to push security requirements into your contract and then verify you're meeting them. That means the questionnaires, the attestation requests, and the evidence packages are the mechanism the rule prescribes.
Two things follow. First, build the answer once. A standing security overview covering your access controls, MFA enforcement on your own RMM and PSA, log retention, subcontractor list, and incident notification timeline turns a two-week scramble into an attachment. Second, run the same discipline downward, because your subcontractors and the tools holding client data inherit the same scrutiny. Our breakdown of the MSP security stack covers the tooling side of that in more depth.
The reason this matters more in 2026 than it did in 2023: compliance questionnaires now reach the MSP directly, and the firms sending them ask for artifacts rather than assurances. A SOC 2 report is one way to answer them all at once, and our guide to SOC 2 compliance for MSPs covers when it is worth the audit.
Testing cadence belongs in the contract
Element (d) gives two paths, and picking the wrong one quietly creates a budget fight later.
Path one is continuous monitoring of your systems and procedures to detect changes that could create vulnerabilities. Path two, for institutions without continuous monitoring, is annual penetration testing plus vulnerability assessments at least every six months, and additional assessments whenever there's a material change to operations or business arrangements.
The rule describes continuous monitoring as systems that detect, on an ongoing basis, changes in information systems that may create vulnerabilities. Write down how the client's tooling does that before you drop the annual penetration test.
This r/msp thread from a three-person MSP asks the element (d) question directly: can an MDR or SIEM service count as continuous monitoring, so the client can skip the annual penetration test?
Penetration testing here has a specific regulatory meaning: assessors attempt to circumvent or defeat security features by attempting penetration of databases or controls from outside or inside the systems. An automated vulnerability scan isn't a penetration test, and selling one as the other is the kind of gap that surfaces at exactly the wrong moment. Our guide to penetration testing services covers how to tell the two apart in a quote.
Decide which path each client is on during onboarding, write it into the agreement with the cadence and the funding, and put the reports where the Qualified Individual can reach them without asking you.
The 5,000 consumer exemption is narrower than it reads
Section 314.6 exempts institutions that maintain customer information on fewer than 5,000 consumers from exactly four paragraphs: 314.4(b)(1), the requirement that the risk assessment be written with stated criteria; 314.4(d)(2), the continuous monitoring or annual penetration test and six-month vulnerability assessment schedule; 314.4(h), the written incident response plan; and 314.4(i), the annual written report to the board.
Everything else stays in force. The written security program, the Qualified Individual, the risk assessment itself, the general duty in (d)(1) to test or monitor key controls, access controls, MFA, encryption, secure disposal, change management, activity monitoring, training, service provider oversight and the 30-day FTC notification all apply regardless of size.
The trap is the count. It covers all consumers whose information the firm maintains, not the active client list. A tax practice with 900 current clients and eleven years of retained returns clears 5,000 without noticing. Before you scope a small client as exempt, count the archive. That's a five-minute conversation that prevents a very expensive assumption.
The written incident response plan in 314.4(h)
Element (h) is the plan the 30-day clock tests. It has to be written, designed to respond to and recover from any security event that materially affects the confidentiality, integrity or availability of customer information in the client's control, and it has to address seven areas:
- The goals of the plan.
- The internal processes for responding to a security event.
- Clear roles, responsibilities and levels of decision-making authority.
- External and internal communications and information sharing.
- Requirements for fixing the weaknesses in systems and controls that an event exposes.
- Documentation and reporting of security events and the response to them.
- Evaluation and revision of the plan after a security event.
In practice the MSP drafts most of it and the client signs it, because areas 3 and 4 are the client's decisions: who can declare an incident, who calls the insurer and who files the FTC report. A client under the 5,000-consumer line can skip the written plan under 314.6, but it still has 30 days to report a notification event that involves 500 or more consumers. Our incident response guide has a plan structure small IT teams can run.
Breach notification in 30 days for 500 or more consumers
The notification amendment took effect May 13, 2024. Institutions must notify the FTC as soon as possible and no later than 30 days after discovering a notification event involving the information of at least 500 consumers, using the online form described in the FTC's notice on the requirement.
A notification event is unauthorized acquisition of unencrypted customer information. The report covers six things: who the institution is, the types of information involved, the date or date range if known, the number of consumers affected, a general description of the event, and whether law enforcement has determined in writing that public notice would impede an investigation or harm national security. When it adopted the amendment, the FTC said it intends to enter these reports into a publicly available database, so plan on the client's report becoming public.
Three details worth writing into every incident response plan you draft:
- Information counts as unencrypted if the encryption key was accessed by an unauthorized person, so key custody is part of the determination.
- There's no harm threshold to argue over. The trigger is unauthorized acquisition, and the rule presumes acquisition whenever there was unauthorized access unless you have reliable evidence that it didn't or couldn't have happened.
- The 30 days runs from discovery, which the rule sets as the first day any employee, officer or other agent of the institution, other than the person committing the breach, knows about the event. That puts the pressure on detection and on how fast your team can scope affected records.
That last point is the operational one. If it takes a week to determine which client systems held customer data and the number of consumers touched, you've spent a quarter of the window on inventory work that should have been standing. This is why element (c)(2), the data inventory, is worth more effort than its one line in the rule suggests.
As for penalties, in March 2019 testimony to Congress, the FTC backed a Government Accountability Office (GAO) recommendation to give it civil penalty authority for Safeguards Rule violations. Violating an FTC order, such as a consent order that settles a Safeguards case, carries civil penalties of up to $53,088 per violation, with each day of continued noncompliance counted separately. That is the 2025 level, and the FTC's September 2026 notice keeps it in place for 2026 because the 2026 inflation adjustment was cancelled.
The evidence pack that ends the argument
Auditors, insurers, and the client's own board ask the same questions in different formats. Assemble the answers once per client, refresh them on a schedule, and the annual review stops being a project.
- Signed designation of the Qualified Individual, the current written security program, and the dated risk assessment with its scoring criteria.
- Coverage reports for MFA, encryption, and patch status, each showing exceptions rather than a green checkmark, plus the current data inventory.
- Most recent penetration test or continuous monitoring summary, the last two vulnerability assessments, training completion records, the approved incident response plan with tabletop notes, and the signed service provider contracts including yours.
Exceptions matter more than totals. A report that says 98% MFA coverage with four named service accounts documented and compensating controls noted is stronger evidence of a working program than a dashboard claiming 100%. Regulators and underwriters both read the former as a program that's being managed and the latter as a program that isn't being checked.
What Safeguards Rule audit software has to produce
Audit and compliance software earns its place in this workflow only if it produces the artifacts above on a schedule. Before you buy a tool for a Safeguards Rule client, check it against four tests:
- It maps controls to 16 CFR 314.4 by paragraph, including (c)(1) through (c)(8), so a gap shows up as a missing artifact against a named requirement.
- It pulls evidence from the systems that hold it, such as the identity provider, the RMM and the log platform, instead of relying on uploaded screenshots.
- It records each exception with an owner and a written approval, which is what (c)(5) asks for when the Qualified Individual signs off on an MFA alternative.
- It exports a dated report the Qualified Individual can put in front of the board under 314.4(i).
No tool satisfies the rule by itself: the client still owns the program and the risk decisions. For evidence collection across frameworks, our comparison of compliance automation software covers the tools MSPs use.
If the client also needs risk registers and policy workflows, start with our GRC compliance software comparison.
For clients under more than one regime, the mapping exercise pays off twice. The overlap between the Safeguards Rule, CMMC, SOC 2, and the frameworks in our cybersecurity frameworks list is large enough that one well-built control set answers more than one questionnaire.
If you're working with defense-adjacent clients too, the CMMC compliance requirements share most of the same technical ground.
Running this across a book of clients
One financial-services client is a project. Fifteen is an operating model, and the difference shows up in three places.
Documentation has to be templated, because a risk assessment rewritten from scratch per client is where margin goes to die. Evidence collection has to be scheduled in the PSA as recurring work with real hours attached, not absorbed. And control drift has to be visible, because MFA coverage that was complete in March degrades quietly as new service accounts and integrations appear.
That last problem is a tooling problem. When endpoint data lives in the RMM, ticket history lives in the PSA, identity data lives somewhere else, and the compliance evidence lives in a spreadsheet a technician updates by hand, the drift is invisible until someone asks for proof. Pulling those into one platform is what makes the reporting cheap enough to sell at a sane price.
That's the case for consolidation on this specific workload. Flamingo, which publishes this guide, builds OpenFrame, open, AI-native infrastructure for IT and security in which help desk ticketing, RMM, remote access, MDM, SIEM and device inventory share one data model, at $1 per device a month with a 14-day free trial. It won't write the risk assessment or certify compliance. It can run one script across a client's devices and keep the output next to the tickets, which is the raw material for the MFA, encryption and patch coverage reports in the evidence pack.
What to do this week
Pull your client list and mark every account that touches tax preparation, lending, financing, accounting, or investment advice. For each one, answer two questions: who is the named Qualified Individual, and is there a signed contract clause covering your obligations under 314.4(f).
Where either answer is missing, you're carrying an unpriced liability until the contract says otherwise.
The firms that get audited lose points for controls nobody can prove existed on the day it mattered.

Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Frequently Asked Questions
/blog/ftc-safeguards-rule-checklist
Still deciding?
Ask Mingo answers from our docs and customer stories.