The Red Flags Rule requires a dealership that qualifies as a creditor with covered accounts to keep a written Identity Theft Prevention Program: identify red flags, detect them, respond, and update the program periodically.
Last updated: November 16, 2026
A customer hands over a license on a Saturday afternoon, the photo matches the face, and the credit report comes back approved. Nothing looks wrong until somebody notices the address on the application isn’t the one the bureau has on file, and by then the truck is down the road. I’m making that scene up, but any dealer reading this can probably picture their own version. The rule’s own examples of red flags include a bureau notice of address discrepancy, and it expects you to have decided ahead of time what happens next.
Here’s my honest read before we get into it. The Red Flags Rule isn’t mostly an IT program. It’s a written program that senior management has to approve and oversee, and I’d be overstating our role if I told you otherwise. But the IT pieces are the ones that are hardest to show later, so this post covers who the rule reaches, what a program has to contain, and where the technology comes in. Our cybersecurity services for dealerships and compliance program pages cover the wider picture, and I’m not a lawyer, so none of this is legal advice.
Does the Red Flags Rule Apply to Your Dealership?
Coverage turns on what your store does, not what it sells. The FTC says whether any particular entity is covered “must be determined by that entity’s specific conduct,” such as regularly using consumer reports in credit deals, reporting to the bureaus, or advancing funds. Have your counsel confirm where you land.

Here’s how I’d think about it. When the FTC adopted the rule in 2007 it listed “automobile dealers” among the entities covered, and the rule’s own definition of a covered account names “automobile loan.” Congress narrowed the rule in 2010. The FTC’s 2012 notice says the change “generally limits the application of the Red Flags Rule to those ECOA creditors that regularly and in the ordinary course of business” do at least one of three things: obtain or use consumer reports in connection with a credit transaction, furnish information to consumer reporting agencies, or advance funds someone has to repay. It adds that there are no industry-wide exemptions, which is why I can’t tell you a dealer is in or out by label. The FTC’s Red Flags how-to guide asks the same thing in plain questions and says one thing dealers like hearing: “Just accepting credit cards as a form of payment does not make you a ‘creditor.'” The creditor definition itself sits in 16 CFR 681.1.
There’s a sibling rule. 16 CFR 641.1 is the address discrepancy rule, and it applies to users of consumer reports “that are motor vehicle dealers excluded from Consumer Financial Protection Bureau jurisdiction.” Neither one is the Safeguards Rule. If the alphabet soup has you tangled, our piece on GLBA and the FTC Safeguards Rule sorts out the other two, but the short version is that Safeguards protects the customer’s information and Red Flags is about spotting someone using a stolen identity.
What Does an Identity Theft Prevention Program Have to Include?
Four pieces: identify the red flags that fit your store, detect them, respond, and update the program over time. Around those, a senior person approves the written plan, staff get trained as needed, and you keep an eye on any service providers who touch covered accounts.

Walk that Saturday deal through the four pieces. The rule defines a red flag as “a pattern, practice, or specific activity that indicates the possible existence of identity theft,” and the appendix lists 26 examples, one of which is a bureau that “provides a notice of address discrepancy.”
Here’s the rule’s own list, so you can see the four pieces in its words.
The Program must include reasonable policies and procedures to: (i) Identify relevant Red Flags for the covered accounts that the financial institution or creditor offers or maintains, and incorporate those Red Flags into its Program; (ii) Detect Red Flags that have been incorporated into the Program of the financial institution or creditor; (iii) Respond appropriately to any Red Flags that are detected pursuant to paragraph (d)(2)(ii) of this section to prevent and mitigate identity theft; and (iv) Ensure the Program (including the Red Flags determined to be relevant) is updated periodically, to reflect changes in risks to customers and to the safety and soundness of the financial institution or creditor from identity theft. (16 CFR 681.1(d)(2))
- Somebody decided before that Saturday that an address mismatch counts. That’s the “Identify relevant Red Flags” step, and the appendix says a program “may consider incorporating” its examples, so not every one of the 26 has to fit your store.
- Then the store has to catch it. The rule says to “Detect Red Flags that have been incorporated into the Program,” and the appendix’s own examples of detecting include “Obtaining identifying information about, and verifying the identity of, a person opening a covered account.” In my scene, that’s a person checking the ID and a system putting the bureau’s notice in front of them.
- Then comes the response. I’d hold the deal and contact the customer before going any further. The guidelines list “Contacting the customer,” “Not opening a new covered account,” and “Notifying law enforcement,” and they also list “Determining that no response is warranted under the particular circumstances,” which is where I’d write down why.
- Afterward, ask what changed. The program has to be “updated periodically,” and the guidelines name “The experiences of the financial institution or creditor with identity theft” and changes in business arrangements, “including mergers, acquisitions, alliances, joint ventures, and service provider arrangements.”
Then there’s the administration. Here’s what the rule asks for.
(1) Obtain approval of the initial written Program from either its board of directors or an appropriate committee of the board of directors; (2) Involve the board of directors, an appropriate committee thereof, or a designated employee at the level of senior management in the oversight, development, implementation and administration of the Program; (3) Train staff, as necessary, to effectively implement the Program; and (4) Exercise appropriate and effective oversight of service provider arrangements. (16 CFR 681.1(e))
No board? For a creditor without one, the rule’s definition covers “a designated employee at the level of senior management,” so that person approves. The FTC’s guide suggests a contract provision requiring service providers to “have procedures in place to detect red flags and either report them to you or respond appropriately,” and it says whoever runs the program “should report at least annually” to the board or a designated senior manager. A program nobody approved is a draft.
Where Does IT Fit in a Red Flags Program?
On the IT side, the job I’d give you is making the program provable: who can pull credit, how identity documents are stored, which alerts reach a person, and what gets logged. The red flags and the responses are business decisions. The rule asks for “reasonable policies and procedures” and doesn’t mandate any particular system, so what follows is how I’d back it up.

I’m not telling you to turn the desk into an airport checkpoint. I’m telling you to match each kind of red flag to something a system can back up, and the rule’s own categories make that easy to do.
The appendix says what detecting can look like, and some of it touches your systems.
The Program’s policies and procedures should address the detection of Red Flags in connection with the opening of covered accounts and existing covered accounts, such as by: (a) Obtaining identifying information about, and verifying the identity of, a person opening a covered account . . . ; and (b) Authenticating customers, monitoring transactions, and verifying the validity of change of address requests, in the case of existing covered accounts. (16 CFR part 681, Appendix A, section III)
| Category in the rule’s Supplement A | An example, in the rule’s words | What I’d want IT to back up |
|---|---|---|
| Alerts from a consumer reporting agency | “A fraud or active duty alert is included with a consumer report.” | The alert reaches a person, and the pull ties to one named user |
| Suspicious documents | “Documents provided for identification appear to have been altered or forged.” | Stored ID scans with limited access and a retention rule |
| Suspicious personal identifying information | “The address on an application is fictitious, a mail drop, or a prison.” | Deal records you can search, so a repeat can be found |
| Notice from customers, victims, or law enforcement | “The financial institution or creditor is notified by a customer, a victim of identity theft, a law enforcement authority, or any other person that it has opened a fraudulent account for a person engaged in identity theft.” | A path to a named person, not a general voicemail |
Six IT jobs sit under that table. They’re my recommendations, not line items in the rule, except where I quote a rule.
- Everybody who pulls credit gets their own login with multifactor authentication on. The Safeguards Rule says to “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,” and a shared login makes “who pulled this?” hard to answer.
- Scans of driver’s licenses. The Red Flags Rule doesn’t tell you to keep them or not, so decide who can open them and how long they stay. The Safeguards Rule does ask for procedures for “the secure disposal of customer information in any format no later than two years after the last date the information is used in connection with the provision of a product or service to the customer to which it relates,” with listed exceptions.
- When a bureau’s notice of address discrepancy comes back, I’d want it in front of a person, because 16 CFR 641.1 requires policies for exactly that moment and a notice nobody sees can’t be acted on.
- Logs. The same Safeguards section asks for controls “designed to monitor and log the activity of authorized users and detect unauthorized access or use of, or tampering with, customer information by such users.” If your systems record who cleared a red flag and when, that record is also your evidence for the Red Flags program.
- Vendors touching the application. The appendix says a creditor “could require the service provider by contract to have policies and procedures to detect relevant Red Flags,” so ask your credit application and lead vendors what they do.
- The caller who says “I never bought that truck” needs a path to a named person. A notice from a customer or a victim is one of the appendix’s red flags, and a notice that lands in a general voicemail can’t be answered.
Who owns that? If F&I figures IT has it and IT figures F&I has it, then it’s nobody’s, and that’s the mess. We run security awareness training for dealership employees, and Red Flags training is part of it. The red flag list and the signature on the program belong to your store. The policy says what to do, and IT shows you did it.
How Do You Prove the Program Is Running?
I’d keep three records: what each red flag was and what you did about it, who got trained and when, and the annual report from the program’s owner to senior management. The first feeds that report, and the second shows the training duty was met.

I learned this one the hard way. Early on at Helion we ran the company on feel, with no real metrics, and it fell apart, because feel doesn’t scale and it doesn’t hold up as evidence either. A Red Flags program run on feel would look fine right up until somebody asked what happened on one particular deal. The guidelines spell out what the annual report should cover, and here’s the passage. It doesn’t need to be long. It does need to exist.
The report should address material matters related to the Program and evaluate issues such as: The effectiveness of the policies and procedures of the financial institution or creditor in addressing the risk of identity theft in connection with the opening of covered accounts and with respect to existing covered accounts; service provider arrangements; significant incidents involving identity theft and management’s response; and recommendations for material changes to the Program. (16 CFR part 681, Appendix A, section VI(b)(2))
Address mismatches get their own duty under 16 CFR 641.1, and here’s how it reads.
A user must develop and implement reasonable policies and procedures designed to enable the user to form a reasonable belief that a consumer report relates to the consumer about whom it has requested the report, when the user receives a notice of address discrepancy. (16 CFR 641.1(c)(1))
I’d want your log to show whether you got to that belief by comparing your own records or by verifying with the customer. Fraud doesn’t always arrive as a fake license, either. Sometimes it’s an email about a payoff, which I covered in business email compromise in the F&I office, and what the FTC actually did to dealerships in 2026 shows where its attention has been. A program nobody can prove was followed is a binder.
Questions I Get About the Red Flags Rule
Is the Red Flags Rule the same thing as the Safeguards Rule?
We don’t have a board. Who approves the program?
How often does the program need updating?
Does security awareness training cover Red Flags?
Name an Owner This Week
We work with 2,000-plus dealerships and have spent nearly 30 years on dealership technology and nothing else. If you want a second set of eyes on the IT side of this, the complimentary IT and cybersecurity assessment looks at your security posture, your technology setup, your vendor spend, and where you stand on the FTC Safeguards Rule. The findings come back in writing.
Name an owner, write the program, and keep the receipts.

