1. Purpose and scope
This is where most of the technical security decisions are made and where they are most expensive to change later. The concept is refined into a cybersecurity specification for each component and interface: the hardware trust anchor and its services, secure boot and software integrity, protection of in-vehicle and off-board communication, key management and provisioning, diagnostic access control, intrusion detection and logging, and the secure update path.
Chip and IP suppliers play a central role. The hardware security module or secure element, its key storage, its cryptographic services and its debug protection are specified here, and the integrator relies on the supplier's security manual and assumptions of use. Requirements to suppliers are flowed down formally so each supplier accepts what it must deliver.
In scope: the cybersecurity specification, hardware and software security specifications, the key management concept, the secure communication specification, the update concept, supplier cybersecurity requirements and the TARA refinement for the design. Out of scope: implementation and verification, which follow in Implementation & Integration Verification.
12 more sections for registered members.