Under the FTC Safeguards Rule, service provider oversight means a dealership must choose vendors able to protect customer information, require those safeguards in the contract, and reassess each vendor periodically based on the risk it presents.
Last updated: November 20, 2026
That’s the whole duty, written in 16 CFR 314.4(f). Three verbs. Select. Require. Reassess. At Helion Technologies, vendor risk assessment is part of our managed FTC Safeguards compliance program, run by the same team that delivers our managed IT and cybersecurity for dealerships. This piece walks through what the rule and the FTC’s own guidance actually say about vendors. Just that. No more, no less.
Count your vendors sometime. The DMS. The CRM. A digital retailing tool, an F&I menu, the marketing company that mails your service specials, the shredding company. Some of them are service providers under the rule. Some aren’t. It depends. The FTC gives dealers a simple test for telling them apart.
That test is where we start.

What Does the Safeguards Rule Say About Service Providers?
The rule defines a service provider as any person or entity that receives, maintains, processes, or otherwise is permitted access to customer information through services it provides directly to a financial institution covered by the rule. The FTC says the rule covers “most automobile dealers who finance or lease automobiles.” If that’s your store, the vendors that do work for you involving customer information are your service providers. Simple enough.
That coverage line comes from the FTC’s Automobile Dealers and the FTC’s Safeguards Rule: Frequently Asked Questions. If you’re not sure your store is covered, our post on whether the Safeguards Rule applies to your dealership works through it.
Here’s the text of 16 CFR 314.4(f), word for word. A dealership must “Oversee service providers, by: (1) Taking reasonable steps to select and retain service providers that are capable of maintaining appropriate safeguards for the customer information at issue; (2) Requiring your service providers by contract to implement and maintain such safeguards; and (3) Periodically assessing your service providers based on the risk they present and the continued adequacy of their safeguards.”
Read item 3 twice. Slowly. Then once more. “Periodically” and “continued” are the words I’d underline. The rule isn’t only asking whether a vendor was capable the day you signed. It’s asking you to keep assessing.
Small stores get no pass here. Section 314.6 of the rule exempts dealers that maintain customer information on fewer than 5,000 consumers from four requirements: the written risk assessment in 314.4(b)(1), the continuous monitoring or penetration testing and vulnerability assessments in 314.4(d)(2), the written incident response plan in 314.4(h), and the Qualified Individual’s report in 314.4(i). Service provider oversight, 314.4(f), isn’t one of them. Read that list again.
The FTC’s plain-language guide, FTC Safeguards Rule: What Your Business Needs to Know, sums it up in one heading: “Monitor your service providers.” It adds that your contracts must spell out your security expectations and build in ways to monitor the provider’s work. Our guide to the nine Safeguards Rule requirements covers the other elements.
Size doesn’t get you out of this one. Neither does a short vendor list.
Who Counts as a Service Provider at a Dealership?
The FTC’s dealer FAQ puts the test plainly: “to be a service provider under the Safeguards Rule, the other company must be providing you with a service that involves access to customer information.” Sharing information alone doesn’t make a company a service provider. Doing work for you that touches customer information does. That’s the line.
Run your list through that test. A few examples, starting with the ones the FTC names itself:
- A marketing company. The FAQ lists companies that “send out marketing materials” as possible service providers.
- The shredding company. Also named in the FAQ, because the paper it hauls away carries customer information.
- Companies that help you process transactions, which is the FAQ’s third example.
- Your DMS, CRM, digital retailing or F&I menu provider? If it stores, processes or can reach customer information to provide its service, it fits the definition.
- An outside IT company with access to your network. The FAQ says that when a provider has direct access to your system, oversight has to address the risk that access poses.
- Your OEM. Not automatically. Really. The FAQ says an OEM “will not be a service provider under the Safeguards Rule unless they are providing you with services.”
One more distinction from the same FAQ. If you share customer information with a company that isn’t your service provider, for example with the customer’s consent so they can get a rebate, the rule doesn’t give you an ongoing duty to oversee that company’s security. Different situation.
Write the list down. On paper. You can’t oversee a vendor you haven’t listed, and our dealership IT vendor inventory worksheet is a decent place to start it.

What Do the Three Oversight Duties Look Like in Practice?
The rule’s three duties land at different points in a vendor relationship. Selection comes before you sign, the contract duty comes at signing, and assessment keeps going for as long as the vendor has your customers’ information. The table puts the rule’s language next to what each duty asks of a dealership, using the FTC’s own explanation where it gives one.
| Duty in 314.4(f) | When it applies | What it asks of the dealership |
|---|---|---|
| (1) Select and retain capable providers | Before you sign, and whenever you decide to keep a vendor | Pick providers whose safeguards fit the customer information they’ll handle. The FTC’s dealer FAQ calls this “the flexibility to select service providers whose safeguards are appropriate.” |
| (2) Require safeguards by contract | At signing and renewal | The contract requires the vendor to implement and maintain those safeguards. The FTC’s business guide adds that contracts should spell out your security expectations and ways to monitor the work. |
| (3) Periodically assess, based on risk | For the life of the relationship | Reassess each provider based on the risk it presents. Separately, 314.4(g) has you adjust your program after any material change to your operations or business arrangements. |
Notice the word “retain” in duty 1. Keeping a vendor is a decision too. The rule treats it like one.
What Should You Ask a Vendor Before You Sign?
The rule doesn’t hand dealers a vendor questionnaire, and it doesn’t make every vendor meet every requirement you have. The FTC’s dealer FAQ says your oversight “does not mean that you have to get the service provider to agree to meet all of the Safeguards Rule requirements that apply to you.” What you ask depends on what the vendor will do.
These questions follow the FTC’s own reasoning, and each one points back to its source:
- What customer information will you receive, keep or be able to reach? That’s the definition in 314.2, and it decides whether the vendor is a service provider at all.
- Will anyone at your company have direct access to our network? If so, the FAQ says the provider “should be required to use multi-factor authentication for that access,” because 314.4(c)(5) covers anyone accessing your systems.
- Will you store or process our customers’ information? The FAQ says a provider doing that “should be required to encrypt that customer information as well,” tying back to 314.4(c)(3).
- Is your software something we’ll use to store, access or transmit customer information? Then 314.4(c)(4) asks you to have procedures for “evaluating, assessing, or testing the security of externally developed applications.”
- Will the contract require you to implement and maintain these safeguards? That’s 314.4(f)(2), in the vendor’s own signature.
Proportion matters. It’s in the FAQ. The FTC’s example: a marketing company with direct access to your systems needs its network security looked at, while a shredding company with no access to your network doesn’t, even though its handling of paper records is still a risk you have to address.
Ask about what the vendor actually touches. Then ask again later.

Why Doesn’t Vendor Oversight End at Signing?
The rule asks you to assess service providers periodically, based on the risk they present and the continued adequacy of their safeguards. A form filed at signing tells you about a vendor on one day. The rule asks about the continued adequacy of its safeguards.
The FTC’s dealer FAQ explains why the duty exists. Poor security at a service provider “could enable a bad actor to access your customer information on that service provider’s information system.” And if the provider has direct access to your network, its weak security could let an attacker straight into yours.
Erik Nachbahr, our founder and president, has put the access side bluntly: vendors have long pulled data out of dealer systems, often with elevated access rights, and in his view many still have far more access to dealer data than they need. That’s his read since he founded Helion in 1997. The rule’s answer is the periodic review. Not a one-time form.
Then there’s the news. In April 2026, The Record reported that Nissan confirmed a cyber incident at an undisclosed vendor earlier in the year. A hacking group had claimed it breached a file transfer system used by a company serving Nissan and Infiniti dealerships across North America, and Nissan said it found no indication its own systems were compromised. Those were the group’s claims, not confirmed facts. For a dealer, the takeaway isn’t fault. It isn’t panic either. It’s that a vendor’s systems can hold dealership data, so the vendor’s security is part of your risk. We covered a separate incident in our post on the VinSolutions data breach and what dealerships should do.
A few habits keep oversight current, and each one has a footing in the rule:
- Review vendor access on a set schedule. Section 314.4(c)(1) requires “periodically reviewing access controls,” and vendors with direct system access are the ones the FAQ singles out.
- Remove a vendor’s accounts when the relationship ends. The same paragraph limits access to authorized users.
- Revisit a vendor after a material change, such as a merger or a new integration. Section 314.4(g) has you adjust your program after material changes to your business arrangements, and a changed vendor relationship can be one.
- A vendor emails new bank details for its invoices? Our team’s advice: never send money without a phone call or some other verification first. Every time.
- Give the results to your Qualified Individual. The written report in 314.4(i) covers material matters “such as” risk assessment and “service provider arrangements,” unless your store falls under the 5,000-consumer exemption.
If you write that report, our Safeguards Rule board report template walks through what it covers.
Signing is the start of oversight. Not the end. Not even the middle.
What If a Vendor Won’t Tell You How It Handles Your Data?
Then you’ve learned something. Useful, too. The rule asks you to take reasonable steps to select and retain providers capable of maintaining appropriate safeguards, so a vendor that won’t explain its safeguards doesn’t get a pass by staying quiet. Write down what you asked, what you heard back, and what you decided. Your information security program has to be written anyway, under 314.3(a).
I ask myself one question when something isn’t going the way I want. What am I not doing? With vendors, the honest answer is sometimes that nobody asked. Fix that first.
The same rule reaches newer tools. AI apps you use to store, access or transmit customer information fall under the 314.4(c)(4) language on externally developed applications, and we’ve covered that in our AI vendor risk assessment for dealerships and our look at vibe coding security risks. When a contract ends, getting your data deleted by the vendor is its own step.
No answer is still an answer. Record it.

Where Helion Technologies Fits
We’ve worked only with automotive and heavy truck dealerships since 1997, and today we support 2,000-plus of them. Vendor risk assessment is part of our compliance program, evaluating the vendors already connected to a dealership’s systems. Compliance isn’t a separate contract with a separate team. It runs with the same team and system as our managed IT and cybersecurity.
We manage the technology so you can sell and service cars and heavy trucks. That’s the peace of mind part. It’s why we’re here.
Things Dealers Ask About Vendor Oversight
Does a small store really have to oversee its vendors?
Is my OEM a service provider just because I send it customer data?
How often counts as “periodically”?
Does every vendor have to meet all the rules my store does?
Who at the dealership should own vendor oversight?
You don’t have to sort this out alone. Start with a complimentary IT and cybersecurity assessment. It reviews your current technology, your security posture, your vendor spend, and where you stand against the FTC Safeguards Rule.

