Security Standards

The responsibility you can’t sign away

THE WORK MOVES — the responsibility stays. A copper arrow labeled “the work” runs from a glowing point labeled “you” and “the responsibility” to a small open circle labeled “the vendor.” The responsibility stays at the start of the arrow.

The contract moves the work. It does not move the responsibility.

A dealership’s security might run through an IT provider, a dealer management system provider and a string of software vendors. A software vendor’s might run through a cloud platform whose data centers it will never visit. Signing those contracts can feel like handing off the risk. It hands off the labor, and sometimes part of the cost. It does not hand off the obligation.

“The patch nobody was assigned” asked who patches each system: your team, your managed service provider or your software vendor. This is the harder half. Even when the answer is “the vendor,” the vendor owns the work and the promise. The responsibility is still yours.

Regulators say so in almost the same words. The FTC Safeguards Rule, 16 C.F.R. § 314.4, reaches dealers that finance or facilitate the financing of vehicles, or lease them for longer than 90 days.1 It requires a dealer to oversee the service providers that can reach its customer information: taking reasonable steps to select capable ones, requiring safeguards “by contract,” and “periodically assessing” them “based on the risk they present.”2 The FTC’s own examples are unglamorous: a marketing company with direct access to customer records, a shredding company handling paper ones.1 And where the person running the dealer’s security program works for a service provider, the rule says it outright: the dealer must “retain responsibility for compliance” and name a senior member of its own staff to direct and oversee that person.2

This is not one rule’s quirk. In 2023, the Federal Reserve, the FDIC and the OCC reminded banks that they must operate safely and lawfully whether work is done in-house or by a third party, and that “a banking organization’s use of third parties does not diminish its responsibility to meet these requirements to the same extent as if its activities were performed by the banking organization in-house.”3 In the European Union, the Digital Operational Resilience Act, which has applied since January 17, 2025, says financial firms that contract for technology services “shall, at all times, remain fully responsible for compliance” with their obligations.4

Vendors meet the same pattern from the other side. Amazon Web Services puts it plainly: “Security and Compliance is a shared responsibility between AWS and the customer.” AWS secures the infrastructure; the customer’s share depends on the services it chooses. On a virtual server, that includes the operating system and its patches. On storage, it includes the data, encryption choices and access permissions.5 Even a model built to split responsibility leaves the customer a share that stays the customer’s.

Delegation is a fine management technique. Try delegating the apology letter.

None of this argues against outsourcing. A specialist may do the work better than you would. It argues for knowing what you kept, and the rule’s three verbs are a good place to start: select, require, assess.

For a dealer, that means one page. List the providers that touch customer financing information. For each, write down what it handles, who it relies on, what the contract requires, including how fast it must tell you about an incident, and when someone last checked. If your IT company runs your security program, put the name of the senior person inside the dealership who oversees it at the top. Your controller can start it this week. It is a starting point, not the whole rule.

For a vendor, it means the same page one level down, and something more. To your customers, you are the third party, and the questionnaire in your inbox may be a dealer doing exactly what the rule asks. Answer it before it arrives: publish a plain responsibility matrix saying who handles user accounts, multifactor authentication, backups and patching, you or the customer.

For any company, it means the same page for whoever runs your email, payroll, customer data and cloud. A contract is a promise from someone else. Oversight is how you find out whether it is being kept.

If your most important vendor failed tomorrow, does the person who would answer for it know yet?

Notes

  1. Federal Trade Commission, “Automobile Dealers and the FTC’s Safeguards Rule: Frequently Asked Questions,” accessed October 21, 2026, www.ftc.gov/business-guidance/resources/automobile-dealers-ftcs-safeguards-rule-frequently-asked-questions. ↩a ↩b
  2. Standards for Safeguarding Customer Information, 16 C.F.R. §§ 314.2(r), 314.4(a), (f), www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314. ↩a ↩b
  3. Board of Governors of the Federal Reserve System, Federal Deposit Insurance Corporation, and Office of the Comptroller of the Currency, “Interagency Guidance on Third-Party Relationships: Risk Management,” 88 Fed. Reg. 37920, 37927 (June 9, 2023), www.federalregister.gov/documents/2023/06/09/2023-12340/interagency-guidance-on-third-party-relationships-risk-management. ↩
  4. Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on Digital Operational Resilience for the Financial Sector, arts. 28(1)(a), 64, 2022 O.J. (L 333) 1, eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022R2554. ↩
  5. Amazon Web Services, “Shared Responsibility Model,” accessed October 21, 2026, aws.amazon.com/compliance/shared-responsibility-model/. ↩

This post is general information, not legal advice.