The core requirements are in 16 CFR 314.4, paragraphs (a) through (j). Here is what each one asks for and what it usually looks like at a dealership.
314.4(a)
Designate a Qualified Individual
One person oversees and enforces the program. It can be an employee or an outside provider. If you use an outside provider, the dealership keeps responsibility, must name a senior person to oversee the provider, and must require the provider to maintain a security program.
314.4(b)
Do a written risk assessment
Identify the risks to customer information (in the DMS, CRM, email, lender portals, paper deal jackets) and judge whether your current safeguards are enough. Repeat it periodically.
314.4(c)
Put safeguards in place
The rule names eight:
- Access controls, technical and physical, so people see only what they need
- An inventory of data, devices, systems, and facilities
- Encryption of customer information in transit and at rest
- Secure development practices for any in-house software
- Multi-factor authentication for anyone accessing any information system
- Secure disposal within two years of last use, with limited exceptions
- Change management procedures
- Monitoring and logging of user activity
314.4(d)
Test and monitor your safeguards
Regularly test whether your safeguards work. Without continuous monitoring, that means a penetration test every year and vulnerability assessments at least every six months, plus after material changes.
314.4(e)
Train your people
Give staff security awareness training that's updated as needed to reflect the risks in your risk assessment. Make sure the people running security are qualified and kept current.
Staff and leadership training →
314.4(f)
Oversee your service providers
Choose vendors that can protect customer information, require safeguards in their contracts, and periodically assess them. At a dealership, that usually means the DMS, CRM, lenders' portals, website and chat vendors, and IT support.
314.4(g)
Keep the program current
Adjust the program when testing turns up problems, when your operations change, or when anything else could materially affect it.
314.4(h)
Write an incident response plan
A written plan to respond to and recover from a security event. It must cover goals, roles and decision-making, internal processes, communications, fixing weaknesses, documentation, and updating the plan afterward.
314.4(i)
Report to leadership every year
The Qualified Individual reports in writing, at least once a year, to the board or a senior officer. The report covers the program's overall status and material matters like risks, test results, and incidents.
314.4(j)
Notify the FTC of certain breaches
If unencrypted customer information about 500 or more consumers is acquired without authorization, notify the FTC as soon as possible and no later than 30 days after you discover it.