Skip to content

Auto dealer penetration testing

Car dealers that arrange financing or leasing are financial institutions under the FTC Safeguards Rule, which means penetration testing. This page shows dealerships what the rule requires, where credit-application data leaks, and how one yearly test plus a plan covers it.

Does the FTC Safeguards Rule apply to car dealers?

Yes, if you arrange financing or leasing. The rule and FTC guidance name auto dealers that finance or lease among the financial institutions covered by the Safeguards Rule. That brings 16 CFR 314.4(d) into your F and I office: annual penetration testing plus vulnerability assessments at least every six months, in force since June 9, 2023.

The trigger is the credit side of the sale, not the cars. The moment your store takes a credit application, pulls a bureau report and sends a deal to a lender, you are handling the customer financial information the rule protects. A cash-only lot sits outside it; almost no dealership is cash only.

The either-or in 314.4(d) lets you run continuous monitoring instead of testing, but few dealerships operate that kind of program. Most meet the rule with a penetration test once a year, vulnerability assessments every six months, and a fresh look after any material change, such as a new DMS or a new lead site.

What customer data sits in a dealership?

An F and I deal jacket is a complete identity theft kit. Between the credit application, the bureau pull and the funding packet, your systems hold everything a fraudster needs to open accounts in a buyer's name, and everything a Safeguards examiner expects you to protect.

  • Credit applications with Social Security number, date of birth and address history.
  • Income and employment details, pay stubs and references.
  • Driver's license scans and copies of insurance cards.
  • Bank references and down-payment or trade payoff account details.
  • Bureau reports and lender decisions pulled during the deal.

A breach scenario: the credit app that leaks down the lot

Most dealerships take credit applications through a website form that writes into a lead system or the DMS. The weak point is the status link a salesperson or customer uses to check a deal. If that link carries the deal number and the server does not confirm who is asking, stepping the number up or down loads the next customer's application: Social Security number, income, the lender decision. This is broken object level authorization, API1 in the OWASP API Security Top 10 2023.

The same gap usually sits on third-party integrations too. A credit-pull or lead vendor connected with a shared key can expose every deal that ever flowed through it, so one leaked credential opens the whole month of applications rather than a single record. Attackers automate the stepping and pull the book in minutes.

Grapefruit demonstrates the issue by exploiting it with a test account you supply, then captures the request and response that proves it. Your developer or your DMS vendor pastes the request, watches it return a deal it should not, adds the ownership check, and runs it again to confirm the leak is closed.

Does the 5,000-consumer exemption cover a dealership?

Rarely. Under 16 CFR 314.6, a business that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement. A dealership counts every financed buyer it has ever recorded, not just this year's, so even a single-rooftop store usually crossed 5,000 long ago.

The count is cumulative and includes declined applicants, co-signers and trade customers whose data you stored. Group dealers and anyone running a busy website lead funnel are well past the line. If your store is genuinely new and tiny, testing early is still the cheaper path than a breach of the data you already hold.

What does the rule mean by a penetration test, and who can run it?

16 CFR 314.2 describes a penetration test as a method where testers try to defeat a system's security from inside or outside. It is real attack, not a scan that lists theoretical issues. The rule asks for a competent tester and names no certification, so the test's worth is in whether it actually breaks in and shows the path.

There is no US penetration-testing license to require. Regulators and your lender partners want a qualified tester, not a licensed one. Testing a system without authorization is a federal crime under the Computer Fraud and Abuse Act, 18 U.S.C. 1030, so Grapefruit takes a signed authorization and a defined scope before touching anything.

How does Grapefruit satisfy the rule for a dealership?

One full test a year plus a Grapefruit maintenance plan covers both halves of the Safeguards Rule. The full penetration test meets your annual requirement with a fixed price and a report in about 10 days. The plan re-tests your verified domains every week or month, which clears the six-month line and dates every run for your records.

Each run lives in your portal with its date, the hostnames tested, and findings ranked critical, high, medium or low. When a lender audit or a Safeguards examiner asks for proof that you test, you open a dated history with the request-and-response evidence attached, rather than searching for last year's report.

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 annual testsA plan that re-tests weekly or monthly, each run dated
After any material changeRe-test after a new DMS, site or integrationThe next scheduled run covers the new surface
Qualified testerA competent tester, no license requiredAuthorized testing under a signed scope
Evidence of testingSomething to show lenders and examinersA dated portal history with replayable proof

What should an auto dealer's test cover?

Everything a credit application touches: the dealership website and its lead forms, the DMS and its web access, the F and I and credit-pull integrations, and any customer-facing app. Real attacks chain across these systems, so one combined test finds paths that checking a single site would miss.

  • Website credit-application and pre-qualification forms, where identity data enters.
  • The DMS web portal and the APIs your staff and vendors reach it through.
  • Credit-bureau and lender integrations connected with shared keys.
  • Customer status and deal-tracking links, the usual home of ownership-check gaps.
  • Any AI feature, such as a trade-in valuation chat or a website assistant, 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. Choose 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.

Plan prices are on the page and checkout is by card, so no demo call stands between you and a start date. See pricing to pick a plan, or configure a full test for your fixed quote. This is a summary of public rules, not legal advice.

Questions

Which car dealers are covered by the FTC Safeguards Rule?
Dealers that finance or lease vehicles are financial institutions under the rule and FTC guidance, so the Safeguards Rule applies to them. Once your store takes credit applications, pulls bureau reports and sends deals to lenders, you handle the customer financial information the rule protects, and the testing obligation under 16 CFR 314.4(d) has applied since June 9, 2023.
We are a small single-rooftop store. Are we exempt?
Probably not. 16 CFR 314.6 exempts a business maintaining information on fewer than 5,000 consumers from the testing requirement, but dealerships count every financed and declined applicant they have ever stored, not just current customers. Most single stores crossed 5,000 years ago. If you are genuinely new, testing early still beats a breach of the data you hold.
What does auto dealer 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. For comparison, traditional web application pentests commonly run 5,000 to 30,000 dollars, according to Astra's cost guide, and more for complex apps. See pricing for current figures.
Our DMS and lead forms are run by vendors. Can those be tested?
Yes. A dealer test should cover the systems your customer data actually flows through, including the DMS web portal and the lender and credit-bureau integrations your vendors run, within a scope you define and sign. Many real exposures sit in those integrations, where one shared key can open a whole month of credit applications.
Do we need a certified tester to meet the rule?
No. 16 CFR 314.2 asks for a competent tester and names no certification, and there is no US penetration-testing license. Your lenders and examiners want a qualified tester who actually defeats your security and shows the path. Grapefruit tests under a signed authorization and defined scope, since testing without permission is a crime under 18 U.S.C. 1030.
How do the six-month vulnerability assessments fit in?
The annual penetration test is a full intrusion attempt; the six-month 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. That keeps evidence current as you change your website, DMS or integrations.

Standards and sources