---
title: "MFA in the Dealership: Every User, Every System That Holds Customer Data"
url: https://trnsfrm.tech/blog/dealership-mfa-every-user
description: "The FTC Safeguards Rule requires MFA for anyone accessing an information system."
lang: en
---

Back to blog (https://trnsfrm.tech/blog)
Image: MFA in the Dealership: Every User, Every System That Holds Customer Data (https://trnsfrm.tech/blog-covers/mfa-bypass.jpg)

By Jeff Dennis (https://www.linkedin.com/in/jefferydennis), Founder & CEO November 19, 2026

# MFA in the Dealership: Every User, Every System That Holds Customer Data

Auto Dealerships (https://trnsfrm.tech/blog?category=Auto+Dealerships)#ftc-safeguards #dealerships #mfa #access-control

A lot of dealerships have turned on multi factor authentication somewhere. Usually it is email, sometimes the DMS, often the bank. Then they assume the requirement is met. The FTC Safeguards Rule sets a broader standard than that, and the gaps tend to be in the same places from store to store.

## What the rule says

The requirement is in 16 CFR 314.4(c)(5). A covered financial institution must "implement multi-factor authentication for any individual accessing any information system, unless your Qualified Individual has approved in writing the use of reasonably equivalent or more secure access controls."

Two definitions in 314.2 shape what that means:

- **Information system** means a discrete set of electronic information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of electronic information containing customer information or connected to a system containing customer information. The definition expressly reaches specialized systems too, such as telephone switching and phone systems, industrial or process controls, and environmental controls, when they contain customer information or connect to a system that does.
- **Multi factor authentication** means verification of at least two types of factors: knowledge factors, such as a password; possession factors, such as a token; or inherence factors, such as biometric characteristics.

Read those together and the scope is wide. "Any individual" includes employees, managers, vendors, and the IT provider. "Any information system" includes systems that contain customer information and systems connected to them.

The rule allows one escape valve: the Qualified Individual (https://trnsfrm.tech/blog/ftc-safeguards-qualified-individual-dealerships) can approve in writing a reasonably equivalent or more secure access control. That approval should be specific, documented, and reviewed. It is not a blanket waiver.

## Where dealers usually have gaps

**The DMS.** Many dealer management systems now support MFA, but it is not always enforced for every user. Check whether it is required or optional, and whether any accounts have been exempted.

**Lender and credit portals.** F&I staff log in to multiple lender portals and credit bureaus. MFA availability varies by portal. Inventory them all and turn it on wherever it is offered.

**Windows logins.** Many stores have MFA on cloud services but not on the computers themselves. A salesperson's workstation is an information system connected to systems that hold customer information. Consider MFA at Windows sign in, at least for systems that can reach the DMS or store customer files locally.

**Remote access.** VPNs, remote desktop gateways, and remote support tools are frequent gaps, particularly those set up years ago by a previous provider.

**Vendor and IT provider access.** Your IT provider's remote management tools reach every computer in the store. Ask your provider to confirm MFA is enforced on their tools and accounts. The same goes for any vendor with remote access, such as a phone system provider or a camera vendor. Our post on DMS and vendor access (https://trnsfrm.tech/blog/dealership-dms-vendor-access) covers how to build and review that list.

**Administrator accounts.** Domain admin, Microsoft 365 global admin, firewall admin, and backup system admin accounts are the most powerful accounts in the store. They should be the first ones with MFA, not the last.

**Shared logins.** A login shared by the whole BDC or the whole parts counter usually cannot have MFA in any meaningful way. Replacing shared logins is often a prerequisite for meeting the MFA requirement. We cover how to do that in getting rid of shared accounts (https://trnsfrm.tech/blog/it-hygiene-shared-accounts).

**Email on personal phones.** If staff read company email on personal phones, check that MFA was required when the phone was set up and that the session is protected by your mobile device policy.

## Building the list

Start with a simple spreadsheet. List every system that holds customer information or connects to one. For each, record:

- Who logs in, including vendors
- Whether MFA is available
- Whether it is enforced for every user
- Exceptions, and whether the Qualified Individual approved them in writing

This list does double duty. It becomes part of your inventory under 314.4(c)(2), and it is the evidence you will want when your Qualified Individual reports on the program to the board or senior officer under 314.4(i). It also belongs alongside your written information security program (https://trnsfrm.tech/blog/dealership-written-information-security-program).

## Choosing the method

Not all MFA is equal. Text message codes are better than no MFA, but they can be intercepted or socially engineered. Authenticator app push notifications are better, especially with number matching turned on, which helps defeat push fatigue attacks. Phishing resistant methods, such as FIDO2 security keys or passkeys, are the strongest.

For most stores, a reasonable approach is:

- Phishing resistant methods for administrators and the IT provider
- Authenticator apps with number matching for most staff
- Text message codes only where a system offers nothing better, documented as such

## Rolling it out without disrupting the floor

Salespeople and service advisors are busy, and a confusing rollout will generate resistance. A few things help:

- Explain why in plain language at a sales meeting. Customers trust the store with their Social Security numbers and credit history.
- Enroll people in person, in small groups, with someone available to help.
- Turn on enforcement system by system, starting with email and the DMS.
- Have a clear process for lost phones and new phones so nobody is locked out on a Saturday.
- Use conditional access where available so trusted, managed devices in the store are not prompted constantly.

## Documenting exceptions

Some systems will not support MFA. An older lender portal, a piece of shop equipment, or a legacy application may only accept a password. For each one, the Qualified Individual should decide whether there is a reasonably equivalent control, such as limiting access to specific managed workstations on the store network, and approve it in writing. Record the reason, the compensating control, and a date to revisit. If the vendor adds MFA later, turn it on and close the exception.

## Next steps

If you are not sure where your store stands, start by listing every system that holds customer information and every way someone can log in to it. That list usually reveals the gaps quickly.

Our FTC Safeguards Rule overview (https://trnsfrm.tech/frameworks/ftc-safeguards) covers the full set of required elements, and our automotive page (https://trnsfrm.tech/industries/automotive) describes how we support dealerships. If you need a starting point for the policy side, see our access control policy guide (https://trnsfrm.tech/blog/policy-guide-access-control). If you want help building the list or planning the rollout, book your free risk review (https://trnsfrm.tech/book).

## Related articles

Auto Dealerships

### DMS Vendor Access: Who Can Get Into Your Dealer Management System

Your DMS holds more customer data than any other system in the store. How to list every vendor and integration that can reach it, cut what you do not need, and review it.

Read article
https://trnsfrm.tech/blog/dealership-dms-vendor-access

Auto Dealerships

### The Dealership Risk Assessment: Written Criteria, Not a Checklist

The Safeguards Rule requires a written risk assessment with criteria for evaluating risks. What that looks like for a dealership and how it drives the rest of the program.

Read article
https://trnsfrm.tech/blog/dealership-written-risk-assessment

Auto Dealerships

### Writing a Dealership WISP That Matches How the Store Runs

The FTC Safeguards Rule requires a written information security program. How to build one that describes your actual systems, people, and vendors instead of a downloaded template.

Read article
https://trnsfrm.tech/blog/dealership-written-information-security-program

Call (877) 777-6855: +18777776855

## Structured data

```json
[
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "TRNSFRM",
    "legalName": "Bitboyz LLC",
    "alternateName": [
      "TRNSFRM Technology",
      "Bitboyz",
      "Bitboyz LLC",
      "Bitboyz LLC DBA TRNSFRM"
    ],
    "url": "https://trnsfrm.tech",
    "logo": "https://trnsfrm.tech/wp-content/uploads/2021/11/trnsfrm-logo.svg",
    "image": "https://trnsfrm.tech/og-image.png",
    "description": "Cybersecurity, compliance, and managed IT services for manufacturers, construction, automotive, and healthcare organizations.",
    "foundingDate": "2008",
    "telephone": "+1-877-777-6855",
    "email": "info@trnsfrm.tech",
    "founder": {
      "@type": "Person",
      "name": "Jeff Dennis",
      "jobTitle": "Founder & CEO",
      "url": "https://trnsfrm.tech/",
      "sameAs": [
        "https://www.linkedin.com/in/jefferydennis"
      ]
    },
    "areaServed": [
      {
        "@type": "Country",
        "name": "United States"
      },
      {
        "@type": "City",
        "name": "Cleveland",
        "containedInPlace": {
          "@type": "State",
          "name": "Ohio"
        }
      },
      {
        "@type": "City",
        "name": "Columbus",
        "containedInPlace": {
          "@type": "State",
          "name": "Ohio"
        }
      }
    ],
    "address": [
      {
        "@type": "PostalAddress",
        "streetAddress": "10143 Royalton Rd Suite J",
        "addressLocality": "North Royalton",
        "addressRegion": "OH",
        "postalCode": "44133",
        "addressCountry": "US"
      },
      {
        "@type": "PostalAddress",
        "addressLocality": "Columbus",
        "addressRegion": "OH",
        "addressCountry": "US"
      }
    ],
    "contactPoint": {
      "@type": "ContactPoint",
      "contactType": "customer service",
      "telephone": "+1-877-777-6855",
      "email": "info@trnsfrm.tech",
      "areaServed": "US",
      "availableLanguage": "English"
    },
    "knowsAbout": [
      "CMMC",
      "NIST 800-171",
      "ISO 27001",
      "HIPAA",
      "FTC Safeguards",
      "ITAR",
      "Managed IT",
      "vCISO",
      "vCIO",
      "Cybersecurity",
      "Microsoft GCC High"
    ],
    "makesOffer": [
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Cybersecurity",
          "url": "https://trnsfrm.tech/cybersecurity",
          "provider": {
            "@type": "Organization",
            "name": "TRNSFRM"
          }
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Governance & Compliance",
          "url": "https://trnsfrm.tech/governance",
          "provider": {
            "@type": "Organization",
            "name": "TRNSFRM"
          }
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Managed IT",
          "url": "https://trnsfrm.tech/managed-it",
          "provider": {
            "@type": "Organization",
            "name": "TRNSFRM"
          }
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "vCISO",
          "url": "https://trnsfrm.tech/vciso",
          "provider": {
            "@type": "Organization",
            "name": "TRNSFRM"
          }
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "AI Integration & Implementation",
          "url": "https://trnsfrm.tech/services/ai",
          "provider": {
            "@type": "Organization",
            "name": "TRNSFRM"
          }
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Microsoft GCC / GCC High",
          "url": "https://trnsfrm.tech/services/microsoft-gcc",
          "provider": {
            "@type": "Organization",
            "name": "TRNSFRM"
          }
        }
      }
    ],
    "aggregateRating": {
      "@type": "AggregateRating",
      "ratingValue": "5.0",
      "reviewCount": "177",
      "bestRating": "5",
      "worstRating": "1"
    },
    "sameAs": [
      "https://www.linkedin.com/company/trnsfrmtech",
      "https://www.linkedin.com/in/jefferydennis",
      "https://clutch.co/profile/trnsfrm",
      "https://maps.google.com/?cid=0x8830ed5d3a6900c5:0xe344c24d13357f96",
      "https://www.goodfirms.co/company/trnsfrm",
      "https://www.bestitmsps.com/company/trnsfrm/"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "WebSite",
    "name": "TRNSFRM",
    "url": "https://trnsfrm.tech",
    "publisher": {
      "@type": "Organization",
      "name": "TRNSFRM"
    },
    "potentialAction": {
      "@type": "SearchAction",
      "target": "https://trnsfrm.tech/blog?q={search_term_string}",
      "query-input": "required name=search_term_string"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "ProfessionalService",
    "name": "TRNSFRM",
    "legalName": "Bitboyz LLC",
    "alternateName": [
      "TRNSFRM Technology",
      "Bitboyz",
      "Bitboyz LLC",
      "Bitboyz LLC DBA TRNSFRM"
    ],
    "url": "https://trnsfrm.tech",
    "image": "https://trnsfrm.tech/og-image.png",
    "telephone": "+1-877-777-6855",
    "email": "info@trnsfrm.tech",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "10143 Royalton Rd Suite J",
      "addressLocality": "North Royalton",
      "addressRegion": "OH",
      "postalCode": "44133",
      "addressCountry": "US"
    },
    "areaServed": [
      {
        "@type": "Country",
        "name": "United States"
      },
      {
        "@type": "City",
        "name": "Cleveland",
        "containedInPlace": {
          "@type": "State",
          "name": "Ohio"
        }
      },
      {
        "@type": "City",
        "name": "Columbus",
        "containedInPlace": {
          "@type": "State",
          "name": "Ohio"
        }
      }
    ],
    "priceRange": "$$",
    "sameAs": [
      "https://www.linkedin.com/company/trnsfrmtech",
      "https://www.linkedin.com/in/jefferydennis",
      "https://clutch.co/profile/trnsfrm",
      "https://maps.google.com/?cid=0x8830ed5d3a6900c5:0xe344c24d13357f96",
      "https://www.goodfirms.co/company/trnsfrm",
      "https://www.bestitmsps.com/company/trnsfrm/"
    ]
  },
  {
    "@context": "https://schema.org",
    "@graph": [
      {
        "@type": "BlogPosting",
        "headline": "MFA in the Dealership: Every User, Every System That Holds Customer Data",
        "description": "The FTC Safeguards Rule requires MFA for anyone accessing an information system. What that means for a dealership, where it gets hard, and how to handle exceptions in writing.",
        "author": {
          "@type": "Person",
          "name": "Jeff Dennis",
          "jobTitle": "Founder & CEO",
          "url": "https://www.linkedin.com/in/jefferydennis",
          "sameAs": [
            "https://www.linkedin.com/in/jefferydennis"
          ],
          "worksFor": {
            "@type": "Organization",
            "name": "TRNSFRM",
            "url": "https://trnsfrm.tech"
          }
        },
        "datePublished": "2026-11-19T12:47:29.512685+00:00",
        "publisher": {
          "@type": "Organization",
          "name": "TRNSFRM",
          "url": "https://trnsfrm.tech"
        },
        "image": "https://trnsfrm.tech/blog-covers/mfa-bypass.jpg"
      },
      {
        "@type": "BreadcrumbList",
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "name": "Home",
            "item": "https://trnsfrm.tech/"
          },
          {
            "@type": "ListItem",
            "position": 2,
            "name": "Blog",
            "item": "https://trnsfrm.tech/blog"
          },
          {
            "@type": "ListItem",
            "position": 3,
            "name": "MFA in the Dealership: Every User, Every System That Holds Customer Data",
            "item": "https://trnsfrm.tech/blog/dealership-mfa-every-user"
          }
        ]
      }
    ]
  }
]
```