Standards List

This PAS gives recommendations for managing security risks that might lead to a compromise of safety in a connected automotive ecosystem.
The PAS covers both the entire connected automotive ecosystem and its constituent systems throughout their lifetimes (including manufacturing, supply chain and maintenance activities). The ecosystem includes vehicles (both those used on public roads, such as cars, and those used for off-road activities such as farming and mining), as well as road-side and other static infrastructure, communication channels between vehicles and infrastructure, servicing and repair facilities, digital services, data and information and other services that support the proper operation of road transport. All levels of vehicle automation and autonomy are in scope.
The PAS applies to risks that can affect a single system, a few systems, or are on a small scale. It also gives recommendations for managing systemic risks – wider risks which might appear small, but which become more significant when interdependencies are considered and where the vulnerability of a single or a few entities poses more widespread risk.
The PAS is intended to be used by manufacturers, operators and maintainers of products, systems and services used in a connected automotive ecosystem. This includes manufacturers of vehicle subsystems, vehicle manufacturers, maintenance organizations, infrastructure operators, owners of large vehicle fleets, and digital service providers.

NEMA TS 10-2020 (TS 10) is a Standard for the equipment deployed at roadside to support standardized over-the-air wireless messages, applications, and cybersecurity measures of communications with Connected Vehicles. This Standard describes physical and performance interfaces as well as functionality requirements as defined in Section 2.2.

This document provides the conventions used for the specification work as done by CAR 2 CAR Communication Consortium. It covers conventions on:
• Release types;
• Documents and
• Document content.

This SAE Information Report develops a concept of operations (ConOps) to evaluate a cooperative driving automation (CDA) Feature for occluded pedestrian collision avoidance using perception status sharing. It provides a test procedure to evaluate this CDA Feature, which is suitable for proof-of-concept testing in both virtual and test track settings.

This document specifies a generic position, velocity and time (PVT) service. It further specifies the PVT service within the ITS station (ITS-S) facilities layer (ISO 21217) and its interface to other functionalities in an ITS-S such as:
— ITS-S application processes (ITS-S-APs), defined in ISO 21217;
— the generic facilities service handler (FSH) functionality of the ITS station facilities layer, defined in ISO/TS 17429.
This document specifies:
— a PVT service which, dependent on a specific implementation, uses a variety of positioning-related sources such as global navigation satellite systems (GNSSs, e.g. GALILEO, GLONASS and GPS), roadside infrastructure, cellular infrastructure, kinematic state sensors, vision sensors;
— a PVT service which merges data from the above-mentioned positioning-related sources and provides the PVT output parameters (carrying the PVT information) including the associated quality (e.g. accuracy);
— how the PVT service is integrated as an ITS-S capability of the ITS station facilities layer;
— the interface function calls and responses (Service Access Point – service primitives) between the PVT ITS-S capability and other functionalities of the ITS station architecture;
— optionally, the PVT service as a capability of the ITS-S facilities layer; see ISO 24102-6;
— an ASN.1 module C-itsPvt, providing ASN.1 type and value definitions (in Annex A);
— an implementation conformance statement proforma (in Annex B), as a basis for assessment of conformity to this document.
NOTE It is outside the scope of this document to define the associated conformance evaluation test procedures.

This document provides guidance for organizations to address security threats and failures in artificial intelligence (AI) systems. The guidance in this document aims to provide information to organizations to help them better understand the consequences of security threats to AI systems, throughout their lifecycle, and descriptions of how to detect and mitigate such threats. This document is applicable to all types and sizes of organizations, including public and private companies, government entities, and not-for-profit organizations, that develop or use AI systems.

This document provides guidance for organizations to address privacy risks in artificial intelligence (AI) systems and machine learning (ML) models. The guidance in this document helps organizations identify privacy risks throughout the AI system lifecycle, and establishes mechanisms to evaluate the consequences of and treat such risks. This document is applicable to all types and sizes of organizations, including public and private companies, government entities, and not-for-profit organizations that develop or use AI systems.

This recommended practice provides guidance on vehicle Cybersecurity and was created based off of, and expanded on from, existing practices which are being implemented or reported in industry, government and conference papers. The best practices are intended to be flexible, pragmatic, and adaptable in their further application to the vehicle industry as well as to other cyber-physical vehicle systems (e.g., commercial and military vehicles, trucks, busses). Other proprietary Cybersecurity development processes and standards may have been established to support a specific manufacturer’s development processes, and may not be comprehensively represented in this document, however, information contained in this document may help refine existing in-house processes, methods, etc.
This recommended practice establishes a set of high-level guiding principles for Cybersecurity as it relates to cyber-physical vehicle systems. This includes:
Defining a complete lifecycle process framework that can be tailored and utilized within each organization’s development processes to incorporate Cybersecurity into cyber-physical vehicle systems from concept phase through production, operation, service, and decommissioning.
Providing information on some common existing tools and methods used when designing, verifying and validating cyber-physical vehicle systems.
Providing basic guiding principles on Cybersecurity for vehicle systems.
Providing the foundation for further standards development activities in vehicle Cybersecurity.
The appendices provide additional information to be aware of and may be used in helping improve Cybersecurity of feature designs. Much of the information identified in the appendices is available but some experts may not be aware of all of the available information. Therefore, the appendices provide an overview of some of this information to provide further guidance on building Cybersecurity into cyber-physical vehicle systems. The objective of the overviews is to encourage research to help improve designs and identify methods and tools for applying a company’s internal Cybersecurity process.

This SAE Standard serves as the guidance document for the J2945/x family of standards as illustrated in Figure 7. It contains cross-cutting material which applies to the other J2945/x standards, including recommended practice for the use of Systems Engineering (SE) and generic DSRC interface requirements content.
The scope for the DSRC system environment is to provide for the information exchange between a host vehicle and another DSRC enabled device, a device worn by or otherwise attached to a traveler, a roadside device, or a management center, to address safety, mobility, and environmental system needs.
The audience for this document includes the technical teams of developers of the J2945/x documents and the implementers of the applications which are based on the J2945/x documents.

This SAE Document specifies DSRC interface requirements for V2V Safety Awareness applications, including detailed Systems Engineering documentation (needs and requirements mapped to appropriate message exchanges). These applications include: Emergency Vehicle Alert, Roadside Alert, and Safety Awareness Alerts for Objects and Adverse Road Conditions. This document extends the V2V Communications capabilities defined in J2945/1 to support these applications, and the National ITS Architecture.
The purpose of this SAE Document is to enable interoperability for V2V Safety Awareness communications.