Skip to content

Consumer lender penetration testing

If you lend to consumers, the FTC Safeguards Rule puts penetration testing on your list. This page shows payday, installment and other non-bank lenders what the rule asks, where their borrower data is exposed, and how one yearly test plus a plan covers it.

Do consumer lenders need a penetration test?

Yes, in most cases. The FTC Safeguards Rule, 16 CFR 314.4(d), gives you a choice: monitor your systems continuously, or run annual penetration testing plus vulnerability assessments at least every six months. Payday, installment and other non-bank lenders are named financial institutions, so the clock has run since June 9, 2023.

The rule treats 'financial institution' broadly. The rule and FTC guidance name payday lenders, finance companies, other non-bank lenders and collection agencies among the businesses covered. If you take applications, pull credit and move money, you are inside the definition, whether you fund one product or ten.

Few lenders have the continuous monitoring program the either-or test wants, so most land on the testing path. That means a penetration test once a year and vulnerability assessments every six months, and a fresh look after any material change to your systems.

What borrower data makes a lender a target?

A consumer lender holds the full identity and finance picture of every applicant, approved or not. That is exactly what account takeover and synthetic fraud run on. An attacker who reaches your application store walks away with everything needed to impersonate a borrower or drain a linked account.

  • Loan applications with name, address, date of birth and Social Security number.
  • Income proof: pay stubs, employer details, stated and verified income.
  • Bank account and routing numbers for ACH disbursement and repayment.
  • Government ID images and selfies captured during identity checks.
  • Credit pulls, decision data and the reasons behind an approval or denial.

A breach scenario: one borrower reads another's file

The common failure in a lending portal is a missing ownership check. A borrower opens their application at a web address that ends in their application number. Change the number by one, and the page loads a stranger's file: their Social Security number, their bank account, their income. This is broken object level authorization, API1 in the OWASP API Security Top 10 2023.

It rarely stops at one record. The same gap usually sits on an API the mobile app calls, so a script can step through every application number in minutes and pull the whole book. No password is broken. The server simply answers for records that are not yours, because nobody checked who was asking.

Grapefruit proves the issue by exploiting it with a test account you supply, then captures the exact request and response. Your engineer pastes that request, watches it return a record it should not, ships the ownership check, and runs the same request again to watch it fail. The before and after is your evidence.

Are you exempt under the 5,000-consumer rule?

Maybe, if you are small. Under 16 CFR 314.6, a business that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement and a few other provisions. That count is cumulative across your records, not your active loans, so stored applications from past years still add up.

Most lenders pass 5,000 quickly. Every applicant you ever took in counts, funded or declined, which is why the exemption fits only the newest or smallest shops. If you are near the line, the simple move is to test anyway: the exposure is the same whether or not the rule names you.

What does the rule mean by a penetration test?

16 CFR 314.2 describes a penetration test as a method where testers try to defeat the security of a system from inside or outside it. The point is real attack, not a scan. The rule asks for a competent tester and names no certification, so what matters is whether the test actually breaks in and shows the path.

There is no US penetration-testing license to look for. Regulators and auditors want a qualified tester, not a licensed one. Testing a system without permission 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 work starts.

How does Grapefruit cover both halves of the rule?

One full test a year plus a Grapefruit maintenance plan covers both halves of the Safeguards Rule. The full penetration test is your annual requirement. The plan re-tests your verified domains every week or month, which lands well inside the six-month line and dates every run for your file.

Each run is kept in your portal with its date, the hostnames tested, and findings ranked critical, high, medium or low. When an examiner or a partner bank asks for proof of testing, you open a dated history instead of hunting for a year-old PDF.

Safeguards Rule 314.4(d)What it meansHow Grapefruit covers it
Annual penetration testA real intrusion attempt once a yearA full penetration test at a fixed quote, report in about 10 days
Vulnerability assessment every six monthsRecurring checks between the annual testsA maintenance plan that re-tests weekly or monthly, each run dated
After any material changeRe-test when systems changeThe next scheduled run covers new endpoints and features
Qualified testerA competent tester, no license requiredAuthorized testing under a signed scope
Evidence of testingSomething to show examiners and partnersA dated portal history with request and response proof

What should a consumer lender test cover?

Everything a borrower's data touches: the application website, the borrower portal, the mobile app APIs, and any lender, bureau or payment integrations behind them. Real attacks chain across these layers, so testing them in one pass finds the paths a single-surface test misses.

  • The online application flow and document upload, where identity data enters.
  • The borrower portal and its APIs, the usual home of ownership-check gaps.
  • ACH and card disbursement paths, where a flaw turns into moved money.
  • Credit-bureau and loan-origination integrations that pass data between systems.
  • Any AI feature, such as a loan chat assistant or an automated underwriting helper, tested in the same run.

How do you start?

Add your hostname, publish one DNS TXT record and sign the testing authorization online. It takes a few minutes. Pick a full penetration test at a fixed quote for your annual requirement, with the report in about 10 days, or a maintenance plan for weekly or monthly re-tests that keep you inside the six-month line.

Prices for the plans are on the page and checkout is by card, so there is no demo call to book. See pricing to choose a plan, or configure a full test to get your fixed quote. This is a summary of public rules, not legal advice.

Questions

Does the FTC Safeguards Rule apply to payday and installment lenders?
Yes. The rule and FTC guidance name payday lenders, finance companies and other non-bank lenders as financial institutions covered by the Safeguards Rule. Since June 9, 2023, that means annual penetration testing plus vulnerability assessments at least every six months, unless you run a qualifying continuous monitoring program instead.
We fund fewer than 5,000 people. Are we off the hook?
Possibly. Under 16 CFR 314.6, a lender maintaining information on fewer than 5,000 consumers is exempt from the testing requirement. The count is cumulative across every applicant you have stored, funded or declined, so most lenders cross 5,000 fast. Near the line, testing anyway is the safer call, since the data exposure is identical.
How much does consumer lender penetration testing cost?
Grapefruit quotes a full penetration test at a fixed price, with the report in about 10 days, and lists maintenance plan prices on the pricing page with card checkout. Traditional web application pentests commonly run 5,000 to 30,000 dollars, according to Astra's cost guide, and more for complex multi-role apps. See pricing for current figures.
Do we need a licensed or certified tester for the Safeguards Rule?
No. 16 CFR 314.2 asks for a competent tester and names no certification, and there is no US penetration-testing license. Regulators want a qualified tester who actually defeats your security and shows the path. Grapefruit tests under a signed authorization and a defined scope, because testing without permission is a crime under 18 U.S.C. 1030.
What is the difference between the test and the six-month assessments?
The annual penetration test is a real intrusion attempt against your systems. The six-month vulnerability assessments are the recurring checks between those tests. A Grapefruit maintenance plan re-tests your verified domains every week or month, which satisfies the six-month cadence and dates each run, so your file stays current between annual tests.
Will testing touch our live borrower data or disbursements?
Testing uses test accounts you supply, so coverage is authenticated without exposing real borrowers. Scope is defined and signed before any work starts. Findings arrive with the captured request and response, so your team can see exactly what an attacker could reach, fix it, and confirm the fix on the next run.

Standards and sources