What does the FTC Safeguards Rule require for testing?
The rule gives you a choice. Under 16 CFR 314.4(d), a covered financial institution must either continuously monitor its systems, or do both annual penetration testing and vulnerability assessments at least every six months. Most firms that cannot run full continuous monitoring take the second path: one annual test plus recurring scans.
This part of the rule became enforceable on June 9, 2023. It sits inside a larger information security program the rule asks you to maintain, but the testing requirement is the piece that trips up firms who thought a password policy was enough.
The rule describes an outcome. It wants proof that your safeguards were tested by someone competent and that you acted on what they found. Grapefruit produces that proof at a fixed price, with the report in about 10 days.
What is the either-or in 314.4(d)?
You pick one of two paths. Path one is continuous monitoring: systems in place to detect changes and intrusions on an ongoing basis. Path two is periodic testing: an annual penetration test plus vulnerability assessments at least every six months, and after any material change to your operations or systems.
Continuous monitoring is a heavy, always-on program that smaller firms rarely run in full. For most covered businesses, path two is the realistic route, and it maps cleanly onto a yearly test and a recurring scan schedule you can evidence.
- Path one: continuous monitoring of your systems for changes and intrusions.
- Path two: an annual penetration test, plus vulnerability assessments at least every six months.
- Either path must also respond to material changes, so a new system or feature triggers fresh testing.
- Most non-bank firms choose path two, because it is a defined schedule rather than an always-on program.
What does the rule mean by a penetration test?
The rule defines it directly. Under 16 CFR 314.2, a penetration test is a method for finding ways to defeat the security controls of an information system by attempting to breach them, from outside or inside your systems. In plain terms, a tester tries to break in and get at data the way a real attacker would.
That is different from a vulnerability scan, which lists weaknesses without exploiting them. The rule asks for both: the annual test that proves real impact, and the recurring scan that keeps watch between tests. Grapefruit runs authenticated testing with real exploitation against your web app, your APIs and any AI features, then keeps re-testing on your plan.
Who has to comply with the Safeguards Rule?
The rule reaches a wide range of non-bank businesses. The term financial institution is defined broadly under 16 CFR 314.2(h), and the rule and FTC guidance name many everyday businesses that handle customer financial information. If you lend, finance, broker, prepare taxes, collect debts or move money, you are likely covered.
If any of the businesses below describe you, and you maintain customer information on 5,000 or more consumers, the testing requirement applies.
- Mortgage brokers and mortgage lenders.
- Auto dealers that finance or lease vehicles.
- Tax preparers.
- Payday, installment and other non-bank lenders, and finance companies.
- Collection agencies.
- Check cashers and money transmitters.
- Investment advisers and credit counselors.
Who is exempt under the 5,000-consumer rule?
Small firms get a partial exemption. Under 16 CFR 314.6, a business that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement, along with three other provisions. Cross 5,000 consumers and the annual-test-plus-scans requirement applies in full.
The count is the trap. Consumer information accumulates across years of files, not just this year's active clients. A tax preparer who has filed for a few thousand clients over several seasons, or a broker with years of closed loans on record, is probably over the line. When the number is close, treating testing as required is the safe call.
This exemption is FTC-only. New York sets different thresholds under its own rule, so a firm can be exempt here and still covered there.
How does Grapefruit cover both halves of the rule?
The rule has two halves on path two, and Grapefruit maps onto each. The annual penetration test is one Grapefruit full test a year. The six-month scanning half is a Grapefruit maintenance plan, which re-tests your verified domains every week or month, well inside the six-month line and dated for your file. One full test a year plus a Grapefruit maintenance plan covers both halves of the rule.
The table below lines up each requirement with what it means and how the service meets it.
- Web app, APIs and AI features are attacked together in one test, because real attacks chain across them.
- Findings are ranked critical, high, medium or low, each with the request and response that proves it.
- Replay a finding before the fix and after it to confirm the issue is closed.
- Every run is dated and downloadable, building the trail an examiner reviews.
| Requirement | What it means | How Grapefruit covers it |
|---|---|---|
| Annual penetration test, 314.4(d) | A real test, from inside or outside, that tries to defeat your controls once a year | One full penetration test at a fixed quote, report in about 10 days, with replayable evidence per finding |
| Vulnerability assessments every six months | Recurring checks for weaknesses between the annual tests | A maintenance plan re-testing verified domains weekly or monthly, well inside the six-month line |
| Testing after material changes | Fresh testing when you add or change a system | Weekly or monthly runs catch new endpoints and features on the next scheduled test |
| Evidence for an examiner | Proof the testing happened and findings were addressed | Dated runs in the portal showing new and fixed findings, each with captured request and response |
Do you need a licensed or certified tester?
No. The Safeguards Rule asks for a competent tester, not a licensed one. There is no US penetration-testing license and the rule names no certification. What it cares about is that the work is done well and that you act on the results.
Authorization is the real requirement. Testing a system without permission is a federal crime under the Computer Fraud and Abuse Act, 18 U.S.C. 1030, so Grapefruit takes a signed testing authorization and a defined scope before any test. You verify your domain, sign online, and the authorized test runs.
How do you start FTC Safeguards testing with Grapefruit?
Add your hostname, publish one DNS TXT record and sign the testing authorization online. It takes a few minutes. Testing starts right after, using test accounts you supply for authenticated coverage, and the report lands in about 10 days at a fixed price. No demo call, no scheduling.
Pick a full penetration test at a fixed quote for the annual half, and a maintenance plan for the six-month scanning half. Maintenance prices are public and checkout is by card. Not sure you are covered? Run the compliance check first, or see pricing to compare. This is a summary of public rules, not legal advice.
Questions
- Does the FTC Safeguards Rule actually require a penetration test?
- Under 16 CFR 314.4(d) a covered firm either continuously monitors its systems or does both annual penetration testing and vulnerability assessments at least every six months. Most non-bank firms cannot run full continuous monitoring, so the annual test plus recurring scans is the practical path. The requirement has been enforceable since June 9, 2023.
- What is the difference between the test and the six-month scans?
- The annual penetration test, defined in 16 CFR 314.2, tries to defeat your controls and prove real impact. The six-month vulnerability assessments are recurring checks for weaknesses between those tests. The rule asks for both on the periodic path. A Grapefruit full test covers the first and a maintenance plan covers the second.
- I serve fewer than 5,000 customers. Do I still need to test?
- Under 16 CFR 314.6, a firm that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement. The count adds up across years of files, not just active clients, so many firms that feel small are over the line. When you are close to 5,000, treating testing as required is the safe read.
- My business is not a bank. Why would this rule apply to me?
- The rule defines financial institution broadly under 16 CFR 314.2(h). The rule and FTC guidance name mortgage brokers, auto dealers that finance, tax preparers, collection agencies, non-bank lenders, money transmitters and more. Handling customer financial information is what pulls you in, not the word bank on your sign.
- Does the tester need a special certification?
- No. The Safeguards Rule asks for a competent tester and names no certification, and there is no US penetration-testing license. What the law does require is authorization: testing a system without permission is a crime under 18 U.S.C. 1030. Grapefruit takes a signed authorization and a defined scope before any test runs.
- How do I show an FTC examiner that I tested?
- Keep dated evidence. Each Grapefruit test and re-test is dated in your portal, with every finding ranked by severity and backed by a captured request and response. When a finding is fixed, a later run shows it gone. That dated record of testing and remediation is what an examiner looks for.