Understanding the US Department of Commerce ANPRM on Connected Vehicles, Supply Chain, & Cyber security

02 April 2024

By Josh Kolleda

What happened?

On 1 March 2024, the United States Department of Commerce's Bureau of Industry and Security (BIS) released an Advanced Notice of Proposed Rule Making (ANPRM) entitled, Securing Information and Communications Technology and Services Supply Chain: Connected Vehicles via the Federal Register.

Ultimately, the ANPRM outlines the concerns that the incorporation of technologies from foreign adversaries identified in Title 15 CFR 7.4 (i.e., Cuba, Iran, North Korea, Russia, the Venezuelan Maduro Regime), and specifically China) within the automotive supply chain may open the United States to malicious cyber activity and result in substantial risk to critical infrastructure. The ANPRM also signals the potential regulation of certain vehicle technologies and prohibition of those technologies originating from "foreign adversaries."

The timing of the ANPRM coincided with the White House Statement from President Biden Addressing National Security Risks to the US Auto Industry and FACT SHEET: Biden-⁠Harris Administration Takes Action to Address Risks of Autos from China and Other Countries of Concern summarizing the White House concerns.

The proposal falls within the purview of Executive Order (EO) 13873: Securing the Information and Communications Technology Services (ICTS) Supply Chain, which grants the Secretary of Commerce the authority to review and impose mitigation measures on or prohibit any ICTS transaction. This includes any acquisition, importation, transfer, installation, dealing in, or use of any ICTS by any person or concerning any property subject to US jurisdiction when the transaction involves any property in which a foreign country or national has any interest.

What is the purpose of the ANPRM, and who does it affect?

As a result of potential threats to the public and critical infrastructure, BIS is considering identifying vehicle operating systems, telematics systems, Advanced Driver Assistance Systems (ADAS), Automated Driving Systems (ADS), satellite or cellular telecommunication systems, and Battery Management Systems (BMS) as "most likely to present undue or unacceptable risks if exploited" by these foreign adversaries, along with considering "whether and how to regulate these software systems." Any response to the ANPRM must be submitted via the Federal Register on or before 30 April 2024.

The ANPRM specifically seeks comment on the following (which I've summarized from the questions posed in the ANPRM) to inform a later Notice of Proposed Rulemaking (NPRM)- the next stage in the rulemaking process:

  • Automotive ICTS supply chain ecosystem and prevalence of companies originating from foreign adversary geographies.
    • Role of companies from foreign adversary geographies within the CV ICTS supply chain within the US and how data from CVs is transmitted to these geographies
    • Effect of disrupting the supply of components from these entities on OEMs and suppliers in the US and whether there are alternative procurement sources
    • Relationships among OEMs and cloud service providers
    • Information sharing among OEMs, suppliers, and service providers (i.e., application source code, vulnerability information, etc.)
  • Connected Vehicle and component capabilities.
    • Data collection capabilities of CVs and who/what has access to that data
    • Remote access and firmware/software update capabilities that OEMs (and their suppliers) have to communicate with vehicles and individual ECUs
    • Linkage among sensors and components within the vehicle network
  • Regulations, standards, and best practices for:
    • Securing vehicle networks and electric vehicle charging infrastructure
    • Current practices for the vehicle software development lifecycle and SBOM verification
    • OEM supply chain security and vetting vendors
    • Verifying that vehicle and software components comply with OEM requirements
  • Authorization and mitigations for exceptions to the Rule
    • Instances where it would be necessary to grant temporary authorizations
    • Criteria in evaluating applications for a temporary authorization, such as specific standards and cyber security best practices
    • Existing US government models to consider in granting authorizations
  • Economic impact
    • Economic impact to US businesses and the public
    • Anticompetitive effects
    • New, implied due diligence, compliance, and record-keeping requirements

Responding to this ANPRM

Should I respond?

Cyber security standards and regulations are becoming more commonplace within the Transportation sector, and given the geopolitical landscape, the White House announcements and Commerce ANPRM shouldn't surprise most.

It's encouraging that the US government is actively working to understand the global nature of the automotive supply chain and the overall vehicle attack surface through the questions in the ANPRM. This is the chance for the industry to help educate and guide decision making to elevate the overall security posture of the automotive sector while also working toward a stable and diversified supply chain.

At a minimum, automotive OEMs and suppliers should review for awareness and evaluate the potential impacts of a rule on their supply chain and products.

However, it's important to note that this is an ANPRM, not an actual rule. If an actual rule ever materializes, it is likely a long way away, and the Department of Commerce should first issue an NPRM with another comment period. For example, on 20 November 2023, the National Highway Traffic Safety Administration (NHTSA) withdrew its V2V NPRM published on 12 January 2017, so there is no guarantee this will become a rule.

 

How do I respond?

Connected vehicles today present the risk of remote shutdown either as a part of 'security' capabilities, such as remote immobilization or as emergent behaviors that arise exploiting other intended functions, such as remote shell access (for diagnostics and logging). Many onboard technologies in use in vehicles today lack security controls that are commonplace in technologies that we are exposed to in our daily lives. For example, they often can lack authentication of important command and control messages and typically have less than optimal and less scrutinized cryptographic implementations for data encryption, authentication, and authorization.

Given the lack of understanding about the attack surface, this has been relatively unexplored and exploited until now. We've seen countless data breaches in other industries; vehicle-related cyber attacks are much less common to date and have typically been focused on an individual level instead of across a fleet.

However, security incidents related to the connected features of vehicles are increasing, as seen through released threat reports and security research. Those incidents often result from vulnerabilities within connected features or the supplier's back end rather than the automotive manufacturer or vehicle itself.

As those active in the automotive industry are already aware, most OEMs and suppliers are working toward compliance with standards such as ISO 21434 for vehicle cyber security engineering and ISO 24089 for vehicle software update engineering. Those outside the US are primarily subject to UN R155 for uniform provisions concerning the approval of vehicles regarding cyber security and R156 for vehicle software updates.

These same OEMs and suppliers are active within standards organizations such as SAE that are currently developing additional standards and best practices for vehicle systems and the networks and devices in which they communicate, such as Electric Vehicle Supply Equipment (EVSE) infrastructure.

If a rule moves forward to prohibit CV ICTS from 15 CFR 7.4 entities, particularly China, the US government should consider these standards and regulations as criteria to ensure cyber security assurance when considering exceptions and temporary authorizations. Regulatory approaches outside the US, such as UN R155, aim to encourage the adoption of Secure by Design/Cyber security Engineering, requiring OEMs to demonstrate they have considered and managed the risks to an acceptable level before passing Type Approval.

Importantly, this approach is not a prescriptive list of security controls to apply to a vehicle, which would quickly go out of date and not reflect the resultant threat landscape. Instead, these regulations require manufacturers to take a systems security engineering approach to justify their cyber security solutions and the accepted risk level. They typically start at the product concept and requirements stage, and, for vehicles, this can happen at a component level, feature/function level, or platform level. This leads to integrating security requirements, including considerations around test cases, and applying security controls to bring the cyber risk down to acceptable levels.

That directly opposes the common alternative, which is a long list of security controls that must be applied. Regulatory bodies should encourage maturity by setting the bar to demonstrate higher assurance over time.

Automotive OEMs and suppliers are also keenly aware that there are many companies headquartered in China or have a presence in China that supply ICTS to automakers that sell vehicles within the US Prohibiting Chinese-made components and software would likely further disrupt an industry that has already dealt with significant recent supply chain challenges as a result of the COVID pandemic.

That said, the industry should be looking at the features and functionality that are being introduced into vehicles, performing robust threat models, and encouraging the adoption of security controls that are likely to reduce residual risk. Many of the connected features/functions are sold to the consumer as 'convenience' but lack the notification around the potential risks they might possess if a capable threat actor targets the backend/cloud infrastructure.

How do I increase assurance while preparing for a potential rule?

The type of activities and level of effort will differ based on the organization, its role within the automotive supply chain, its geographic locations, and the geographies it sells into. However, any organization within the automotive supply chain would benefit from conducting these example activities to strengthen its security posture and exhibit security due diligence.

  • ISO 21434 and ISO 24089 Gap Assessments and Implementation:

(e.g., development and review of cyber security engineering work products) as these standards provide the frameworks for an overall vehicle cyber security program from security requirements and concept development to threat modeling to vehicle monitoring and security operations.

  • Supplier risk management programs and reviews:

Conduct a comprehensive review of your supplier program based on the current state – from full program buildout (process analysis and program design), current program assessment and targeted supplier assessments (reviewing or creating supplier risk profiles), to corrective action planning management (focused on remediating risk across suppliers)

  • Software escrow and source code audits of supplier components and applications:

Securely store software source code, firmware, binaries, and artifacts within physical or virtual vaults of a third party in line with the OEM and supplier's agreements. This also facilitates third-party verification of the code.

  • Third-party security assessments and penetration tests

These are based on risk but focused explicitly on the sub-systems and components mentioned within the ANPRM (e.g., ADAS, BMS, telematics), along with the backend supporting infrastructure.

  • Secure Development Lifecycle/Toolchain Gap Analysis:

Conduct a CI/CD pipeline audit and configuration review focused on safety-critical software and firmware development processes. This should include looking at how 3rd party code and tools make it into production code and build systems. Provide recommendations for process and tool changes/implementations.

  • Facility due diligence assessment for manufacturing sites:

Conduct an OT-focused assessment against best practices and standards such as IEC 62443 to understand IT/OT network segmentation posture and increase visibility of assets, vulnerabilities, and threats, along with prioritization of vulnerability remediation based on actual risk, all in an effort to ensure secure manufacturing and provisioning of components and vehicles.

  • Monitoring and detection:

Implement solutions to monitor for and detect vulnerabilities and threats throughout the business with special attention to the vehicle itself, connected services/telematics, and any third-party connectivity to vehicles.

  • Digital Forensics and Incident Response Retainers:

Obtain an IR retainer with a third party and conduct tabletop exercises, first responder trainings, and/or incident response capabilities assessments.

About NCC Group Transport Assurance

NCC Group is a global cyber and software resilience business operating across multiple sectors, geographies, and technologies. NCC Group has a decade of experience in supporting the global automotive industry, including some of the largest OEMs in the world, in all the services outlined above. We bring together cyber security professionals with deep knowledge of the transport sector, including consultants who have previous experience as cyber security engineers at OEMs and Tier 1s.

Our Automotive Practice comprises services to increase our clients' Cyber Security maturity. We identify the current maturity level and security posture and assess processes, products, people, and the supply chain, enabling our clients to mitigate risk, manage operational continuity, and respond by providing rapid access to cyber incident response.

With circa 2,400 colleagues, we have a significant market presence in the UK, Europe, and North America, as well as a growing footprint in Asia Pacific with offices in Australia, Japan, and Singapore.

Josh Kolleda

Josh Kolleda

Practice Director of Transport Assurance, NCC Group NA

Josh Kolleda brings 16 years of experience in the private, public, and defense sectors. He focuses on cyber security consulting capabilities across all of NCC Group’s services for companies in the transportation sector (automotive, maritime, aerospace, rail). He has worked with entities throughout the automotive and roadside infrastructure ecosystem, such as large OEMs, suppliers, standards bodies, infrastructure owner-operators, state and local governments, and federal regulators.

Josh's background as a former US Army officer specializing in transportation/logistics teams adds a unique perspective to his work. He also has a master’s degree in Transportation Policy, Operations, and Logistics and holds CISSP and PMP certifications.