A Cyberattack Can Expose Customer Data Without Stopping a Single Sale

Published on by Manpreet Singh · 6 min read

A Cyberattack Can Expose Customer Data Without Stopping a Single Sale
A cyber attack may expose data, but the dealership may just not notice it.

If your dealership keeps selling throughout a vendor's cyber incident, does that mean customer information stayed private? No. Someone can read or copy records without preventing your staff from using the system.

As a general manager at a U.S. dealership, you may want to avoid alarming customers before the vendor has established what happened. But uninterrupted operations cannot support reassurance about data exposure. Federal Safeguards Rule reporting and state customer-notification requirements address different questions, as California's rules illustrate.

A usable system can still disclose its records

NIST distinguishes availability from confidentiality: availability concerns whether authorized users can obtain and use information; confidentiality concerns restrictions on who may access or receive it. A service-status update addresses the first question, not necessarily the second.

Consider a simple illustration: an intruder uses a stolen login to open a credit application while your finance manager works in another record. The intruder reads the application without changing it or interrupting your manager. The system continues doing its job, but the information has reached someone who should not have it.

The absence of file-encrypting malware does not resolve that concern. In their joint ransomware guidance, CISA and its partners describe attacks in which criminals steal information for extortion without deploying ransomware. That establishes why data exposure and downtime need separate investigation, not what happened in any particular vendor incident.

The notice needs to identify your dealership's exposure

In its incident-response guidance, NIST calls for reconstructing events and identifying the resources involved. Applied to a dealership notice, that means separating what an intruder could access from what investigators found the intruder actually accessed or copied. Use these questions to evaluate the notice:

  • Was our dealership affected, excluded on evidence, or still under investigation? An announcement that relatively few dealerships were affected does not identify yours.
  • Which records and fields were involved? A reference to customer information should identify the fields involved, such as contact details versus Social Security numbers or finance documents. Account permissions alone do not establish that every accessible record was taken.
  • What was the unauthorized-access window? The vendor's discovery date is not necessarily the beginning of unauthorized activity; the access window helps establish which records might be involved.
  • What do the logs establish, and where are the gaps? If relevant activity was not logged, that gap cannot establish that copying never occurred.
  • Who is handling each required filing and customer notice? Confirm responsibility for each obligation so your dealership and the provider do not assume the other has handled it.

The provider's investigation does not replace your obligations

The Federal Trade Commission's auto-dealer guidance explains that dealerships arranging consumer auto financing fall within the Safeguards Rule. Covered dealerships must select and retain service providers capable of protecting customer information and require appropriate safeguards through their contracts. They must also reassess providers periodically according to risk.

Those duties matter when you receive an incident notice. The provider may control the forensic investigation, but its public statement does not replace your assessment of the information it handles for your dealership. Dealer-specific findings give your security lead and counsel something to evaluate beyond the vendor's description of its overall incident.

The FTC guidance also distinguishes an ordinary customer contact list from a list identifying people who financed vehicles. The latter can be protected customer information even without Social Security numbers. Consequently, a description such as contact information only may leave out an important fact: what the list reveals about the customer's financial relationship with your store.

Federal reporting and customer notice have different triggers

Under the FTC's Safeguards Rule guidance, covered institutions must report qualifying events involving at least 500 consumers to the FTC as soon as possible, with an outside deadline of 30 days after discovery. The trigger concerns unauthorized acquisition of unencrypted customer information, not lost sales or an outage.

The FTC treats information as unencrypted for this purpose if an unauthorized person accessed its encryption key.

Crucially, the FTC presumes acquisition when someone gains unauthorized access to unencrypted customer information. That presumption can be overcome with reliable evidence that acquisition did not happen or could not reasonably have happened. Missing proof of a download is therefore not, by itself, enough to dismiss the reporting question.

The FTC's rule text also ties discovery to knowledge of the notification event, including knowledge held by an employee, officer or other agent, except the perpetrator. You cannot assume the clock waits for the vendor's final forensic report.

Customer notification requires a separate analysis. The California attorney general explains that affected California residents must be notified when an unauthorized person obtained covered, unencrypted personal information, or the business reasonably believes that happened.

Under the California Legislature's SB 446, the rules in effect in 2026 generally require businesses to notify affected residents within 30 calendar days after discovering or being notified of the breach. The law permits delays for legitimate law-enforcement needs or when necessary to establish the breach's scope and restore the data system's reasonable integrity. When a single breach requires notices to more than 500 California residents, businesses must submit a sample notice to the attorney general within 15 calendar days after notifying affected consumers.

That California filing threshold is not a minimum for notifying customers. A smaller incident can require customer notices even when the federal reporting threshold is not met. Counsel needs the affected residents' states and the actual findings to determine applicable deadlines and exceptions, rather than treating an FTC filing as the entire notification obligation.

Customer updates must stop where the evidence stops

The FTC's breach-response guidance warns businesses against misleading statements and recommends explaining known facts alongside protective actions suited to the information exposed. For your dealership, that means a service-availability statement should never become a claim that customers' records are safe.

A holding response, if supported by the findings, could read: “The provider confirmed unauthorized access to our dealership account. Investigators are still determining which customer records were involved. We have not yet confirmed whether your information was involved.” That acknowledges the customer's question without inventing an answer.

Such an update is not a substitute for a legally required notice. It should identify a reliable contact for further information and describe the protective action supported by the findings. Where Social Security numbers were stolen, for instance, the FTC points consumers toward fraud alerts or credit freezes.

If advice is precautionary because findings remain incomplete, describe it that way. Recommending a precaution does not establish that theft occurred, just as an unfinished investigation does not establish that records stayed private.

The management question changes from “Are we still selling?” to “What does the evidence establish about our customers' records?” Keeping the store operating and deciding what those customers need to know are separate responsibilities.

Frequently asked questions

Can our vendor submit the FTC incident report for our dealership?

Yes. The FTC's reporting form permits service providers and other third parties to submit reports for affected financial institutions, including multiple institutions in one submission. Confirm that the submission actually covers your dealership; a vendor's statement that it contacted regulators does not establish that it reported on your behalf.

Your dealership, in one system

Dealersip brings inventory, your website, CRM, marketing and accounting into one system. Bella, its AI assistant, answers questions using your dealership's own data.

Book a demo