The development of autonomous vehicles has been steadily progressing in recent years. From advances in collision avoidance systems to the development of self-driving technologies, automakers have been working to increase the automation of cars, leading to a reduction in the risk of car accidents, which are primarily caused by human error. Given the push towards developing self-driving technology in cars, the House of Representatives passed the Safety Ensuring Lives Future Development and Research in Vehicle Evolution (“SELF DRIVE”) Act, with the purpose of helping “ensure the safe and innovative development, testing, and deployment of self-driving cars across the country.”
The SELF DRIVE Act includes three major components. First, it prevents states from banning self-driving vehicles, and gives the National Highway Traffic Safety Administration (“NHTSA”) the authority to regulate self-driving vehicles as it does with “normal cars.” Second, it grants “exemptions to existing safety standards for a company’s first 100,000 vehicles,” to promote and speed up the process of developing self-driving cars and getting them to market. Finally, the SELF DRIVE Act mandates protections for consumer privacy and the prevention of cyberattacks on self-driving vehicles.
Cyberattacks on self-driving vehicles may lead to the hacking of the vehicle, potentially leading to dangerous situations in which the hacker controls the entirety of the car’s movements. To prevent this, the SELF DRIVE Act requires that automakers set up “a process for identifying and mitigating ‘reasonably foreseeable’ vulnerabilities,” and “have cybersecurity managers, training, and intrusion prevention and response systems in place.” Some claim that the cybersecurity requirements are overly vague and open to interpretation, leaving automakers to decide on their own what vulnerabilities are “reasonably foreseeable.” However, given the rapid pace of technological advancement, the broad regulatory language is apt, as it leaves room for new technical approaches and cybersecurity countermeasures to be implemented without requiring a change to the law.
Modern cars which lack self-driving capabilities are also susceptible to hacking. Not only is there a concern that hackers can take over the locking system, steering, and brakes of a car, but there is also an additional personal information security concern which exists with cars to which a smartphone is connected. When a smartphone is connected to a car, all of the personal information of the user which is recorded on the smartphone is accessible to hackers. Although there has not been significant regulation in relation to the cybersecurity of such cars, automakers have taken the issue seriously, and created the Automotive Information Sharing and Analysis Center (“Auto ISAC”) “to act as a clearinghouse for industry best practices” in relation to cybersecurity. Both Auto ISAC and the NHTSA have released publications which indicate best practices for automobile cybersecurity, and provide detailed practices and policies for automakers to adopt in order to prevent hacks or information leaks. With the transition to self-driving cars, whose cybersecurity risk is much higher, automakers will need to come up with “many dynamic solutions” and “multiple layers of security to make it as hard as possible for hackers to attack a car.”
Today’s evolving technology makes our day to day lives much easier, but comes with an increasing vulnerability to cyberattacks. With automakers working toward development of self-driving vehicles, many are worried about hackers accessing and taking control of these cars. To promote the development of self-driving vehicles, the SELF DRIVE Act gives broad guidelines for cybersecurity programs, allowing for advanced cybersecurity measures to be implemented as they are established. Given the broad language of the Act, automakers have the freedom to “create and test more [cybersecurity solutions]” and come to the “dynamic solutions” that will ensure our safety while autopilot enabled cars drive us.
See Bob Latta, Op-Ed: The Road Ahead for Self-Driving Car Legislation, Eno Center for Transportation (Nov. 13, 2017), https://www.enotrans.org/article/op-ed-road-ahead-self-driving-car-legislation/.
 See id. (discussing how 94% of car accidents are attributable to human error, and that the automation of cars reduces the risks of such accidents).
 Id.; see also Aarian Marshall, Congress Unites (Gasp) to Spread Self-Driving Cars Across America, Wired (Sept. 6, 2017, 4:33 PM), https://www.wired.com/story/congress-self-driving-car-law-bill/.
 See H.R. 3388: SELF DRIVE Act, GovTrack (Oct. 18, 2017), https://www.govtrack.us/congress/bills/115/hr3388/summary.
 See id.; Marshall, supra note 3.
 H.R. 3388: SELF DRIVE Act, supra note 4; see also Marshall, supra note 3.
 See H.R. 3388: SELF DRIVE Act, supra note 4; Marshall, supra note 3.
 Cyberattacks may also manifest as hackers simply tricking the vehicle into making driving errors. See Keith Laing, Carmakers Grapple with Robot-Car Hacking Fears, The Detroit News (Nov. 15, 2017, 12:02 AM), http://www.detroitnews.com/story/business/autos/mobility/2017/11/15/carmakers-stuggle-robot-car-hacking-fears/107696450/.
 Grant Gross, Self-Driving Car Bill Leaves Cybersecurity Rules Open to Interpretation, The Parallax (Sept. 18, 2017), https://www.the-parallax.com/2017/09/18/self-driving-car-bill-cybersecurity/.
 See id.
 See id. Furthermore, the NHTSA, with the regulatory power it received through the SELF DRIVE Act, can require that specific processes be implemented to ensure the cybersecurity of self-driving vehicles. See id.; Marshall, supra note 3. This will give carmakers the guidance that may be necessary to ensure consumer safety while maintaining the flexibility of agency regulation. See Gross, supra note 9; Marshall, supra note 3.
 See Caroline Mortimer, Hackers Now Able to Take Control of Cars to Cause Deliberate Accidents, Scientists Warn, Independent (Nov. 21, 2017), http://www.independent.co.uk/life-style/gadgets-and-tech/news/computer-hackers-control-car-deliberate-accidents-national-security-issue-a8066466.html; H.R. 3388: SELF DRIVE Act, supra note 4.
 See Mortimer, supra note 12.
 See Jamarlo Phillips, FBI: Car Hacking is Real and Dangerous, WearTV.com (Nov. 14, 2017), http://weartv.com/news/local/wear_112017_10p_hacking-cars.
 Though there have been proposals for cybersecurity regulation of the “Internet of Things,” which would presumably include such “connected cars.” See Stephen Edelstein, U.S. Senate’s New Cybersecurity Bill Could make Connected Cars Safer, The Drive (Aug. 1, 2017), http://www.thedrive.com/tech/13082/u-s-senates-new-cybersecurity-bill-could-make-connected-cars-safer.
 Chester Dawson, The Dangers of the Hackable Car, The Wall Street J. (Sept. 17, 2017, 10:08 PM), https://www.wsj.com/articles/the-dangers-of-the-hackable-car-1505700481; see also Connected Cars and Self-Driving Cars: Not on Auto Pilot in Terms of Legal Risks, Shearman & Sterling LLP (Jul. 11, 2016), http://www.shearman.com/~/media/Files/NewsInsights/Publications/2016/07/Connected-Cars-and-SelfDriving-Cars-Not-on-Auto-Pilot-in-Terms-of-Legal-Risks-PDP-071116.pdf.
 Chanley T. Howell, The Top Six Takeaways from Auto ISAC’s and NHTSA’s Cybersecurity Best Practices, Foley & Lardner LLP (Mar. 2, 2017), https://www.autoindustrylawblog.com/2017/03/02/the-top-six-takeaways-from-nhtsas-cybersecurity-best-practices/.
 Bridget Clerkin, How Will We Ensure Security in a Self-Driving World?, DMV.org (Sept. 21, 2017), https://www.dmv.org/articles/cybersecurity-and-self-driving-cars.
 See id.
 See id.; Laing, supra note 8.
 See Gross, supra note 9.
 See Clerkin, supra note 19.