Do collection agencies need a penetration test?
Yes, in practice. The FTC Safeguards Rule names collection agencies as a financial institution, and one way to meet its security-testing requirement is annual penetration testing plus vulnerability assessments every six months. You hold data from thousands of consumers who never chose to do business with you, which raises the sensitivity, not lowers it.
Your systems link a person's name, address and phone to a debt amount, the original creditor, and often the card or bank account they used to pay. A breach exposes not just contact details but the fact and size of someone's debt, which people treat as deeply private.
Grapefruit runs the test the rule points to: a real attack on your portal and systems, every finding proven, at a fixed price, with the report in about 10 days.
What does the FTC Safeguards Rule require?
The Safeguards Rule, at 16 CFR 314.4(d), lets you choose. You can continuously monitor your systems, or do both annual penetration testing and vulnerability assessments at least every six months, and again after any material change. For an agency juggling many client portfolios, the testing path produces a dated record your creditor clients can ask for.
At 16 CFR 314.2 the rule defines a penetration test as a method where testers try to defeat your security from outside or inside your systems. Grapefruit does that with authenticated testing, using test accounts you supply, so the attack reflects what a logged-in debtor or collector could reach.
- Annual penetration testing: one full Grapefruit test a year covers this half.
- Vulnerability assessments every six months: a Grapefruit maintenance plan re-tests weekly or monthly, well inside the line.
- After material changes: a plan re-tests after you onboard a new portfolio or payment processor.
- In force since June 9, 2023, so the expectation is current.
Are you a covered financial institution?
Almost certainly. The rule and FTC guidance describe financial institutions broadly and name collection agencies directly, alongside firms like non-bank lenders and finance companies. If you collect consumer debts and keep debtor records on a system, you are in scope. The definition sits at 16 CFR 314.2.
There is a narrow exemption. Under 16 CFR 314.6, a firm that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement. For a collection agency this threshold is usually met many times over, because each placed account is another consumer in your systems.
No certification is required to run the test. The rule asks for a competent tester, not a licensed one, because there is no federal penetration-testing license.
What does a collection agency breach look like?
The most common one lives in the debtor self-service portal. A consumer logs in to make a payment, and the page shows their balance from a web address that carries an account number. Change that number and a stranger's balance, original creditor and masked payment details load, because the portal never checked that the account belonged to the person signed in.
The larger exposure is an API that answers in bulk. A lookup endpoint behind the portal returns debtor names, phone numbers and balances for any ID an attacker feeds it, turning one weak check into a full export of a portfolio. Grapefruit hunts both the single-record and the bulk versions, and proves which ones respond.
- Balances and debtor details that load across accounts through a changeable ID.
- Payment pages that leak card or bank information entered by other consumers.
- Bulk API endpoints that return debtor records without the right authorization.
- Agent or admin screens reachable by an ordinary debtor login.
What does Grapefruit test for a collection agency?
Everything a debtor record touches, in one test. The debtor portal, the collector and admin tools, the APIs behind them, and any AI assistant you use for payment or intake conversations are attacked together, because a real attack chains across them. Findings are ranked critical, high, medium or low in an online portal.
Every finding arrives with the exact request and response that proves it. Your developer pastes the request, runs it, watches another debtor's balance or card data appear, then applies the fix and runs it again to watch the attack fail. That before and after is the evidence a creditor client or auditor wants.
- Authenticated testing with test accounts you supply, across debtor, collector and admin roles.
- Access-control testing across accounts, portfolios and client boundaries.
- API testing mapped to the OWASP API Security Top 10 2023.
- A downloadable report with the tested hostnames, the run date and proof for every finding.
| Debtor data | Attack that reaches it | What Grapefruit does |
|---|---|---|
| Balances and creditor | Changeable account ID in the portal | Attempts to load records across accounts |
| Card and bank details | Payment page or stored data leak | Tests whether payment data exposes to others |
| Bulk debtor records | Unprotected lookup API | Probes the API for mass data return |
| Client portfolios | Weak tenant separation | Tests boundaries between creditor clients |
How does one test a year plus a plan cover the rule?
The Safeguards Rule's two halves map onto Grapefruit's two offers. One full penetration test a year satisfies the annual testing requirement. A Grapefruit maintenance plan re-tests your verified domains every week or month, which sits inside the six-month vulnerability-assessment line and dates each run for your records.
So one full test a year plus a maintenance plan covers both halves of the rule, and gives you dated proof to show the creditors who place accounts with you. See pricing to configure a full test, or to start a plan.
How do you start?
Add your hostname, publish one DNS TXT record and sign the testing authorization online. It takes a few minutes. Testing without authorization is a federal crime under the Computer Fraud and Abuse Act, 18 U.S.C. 1030, which is why Grapefruit takes a signed authorization and a defined scope before any test.
Results land in your portal within hours of kickoff. Choose a full penetration test at a fixed quote, or a maintenance plan for weekly or monthly re-tests. This is a summary of public rules, not legal advice.
Questions
- Is penetration testing required for collection agencies?
- The FTC Safeguards Rule names collection agencies as financial institutions and, at 16 CFR 314.4(d), lets you meet its testing requirement with annual penetration testing plus vulnerability assessments every six months. Grapefruit runs that test at a fixed price with the report in about 10 days, and a plan keeps the six-month checks dated.
- Is my small agency exempt from the testing rule?
- Rarely. Under 16 CFR 314.6, a firm maintaining customer information on fewer than 5,000 consumers is exempt from the testing requirement. For collection work this threshold is usually crossed many times over, because every placed account is another consumer whose data sits in your systems.
- What debtor data is at risk?
- Debtor contact details, account balances, the original creditor, and the card or bank information people use to pay. A breach also reveals the fact and size of someone's debt, which consumers treat as highly private. Grapefruit tests whether any of it can be reached across accounts or exported through your APIs.
- Why do creditor clients care about our pentest?
- Creditors that place accounts with you are responsible for how their consumers' data is handled downstream, and many ask vendors for evidence of testing. A dated Grapefruit report, with proof behind each finding and a retest showing serious issues closed, is the kind of evidence a creditor's security team can accept.
- Do I need a certified tester?
- No. The Safeguards Rule asks for a competent tester, not a certified or licensed one, and there is no federal penetration-testing license. What matters to an examiner or a creditor client is a real test with evidence behind every finding, which is what a Grapefruit report provides.
- Can you test the payment portal without charging real cards?
- Yes. Testing uses the hostnames and test accounts you supply, so we work with controlled accounts rather than live debtor payments. You set the scope and window, and a maintenance plan re-tests on a schedule so coverage continues as you add portfolios or change payment processors.