Automotive Content

4 General Cybersecurity Best Practices

The automotive industry should follow the National Institute of Standards and Technology’s (NIST’s) documented Cybersecurity Framework, which is structured around the five principal functions, “Identify, Protect, Detect, Respond, and Recover,” to build a comprehensive and systematic approach to developing layered cybersecurity protections for vehicles.

4.1 Leadership Priority on Product Cybersecurity

Allocating dedicated resources within the organization focused on researching, investigating, implementing, testing, and validating product cybersecurity measures and vulnerabilities

4.1 Leadership Priority on Product Cybersecurity

Facilitating seamless and direct communication channels through organizational ranks related to product cybersecurity matters

4.1 Leadership Priority on Product Cybersecurity

Enabling an independent voice for vehicle cybersecurity-related considerations within the vehicle safety design process.

4.2.1 Process

The automotive industry should follow a robust product development process based on a systems-engineering approach with the goal of designing systems free of unreasonable safety risks, including those from potential cybersecurity threats and vulnerabilities.

4.2.2 Risk Assessment

This process should include a cybersecurity risk assessment step that is appropriate and reflects mitigation of risk for the full lifecycle of the vehicle.

4.2.2 Risk Assessment

Safety of vehicle occupants and other road users should be of primary consideration when assessing risks.

4.2.3 Sensor Vulnerability Risks

Manufacturers should consider the risks associated with sensor vulnerabilities and potential sensor signal manipulation efforts such as GPS spoofing, road sign modification, Lidar/Radar jamming and spoofing, camera blinding, and excitation of machine learning false positives.

4.2.4 Removal or Mitigation of Safety-Critical Risks

Any unreasonable risk to safety-critical systems should be removed or mitigated to acceptable levels through design, and any functionality that presents an unavoidable and unnecessary risk should be eliminated where possible.

4.2.5 Protections

For remaining functionality and underlying risks, layers of protection that are appropriate for the assessed risks should be designed and implemented.