Used before Security architecture approved, to confirm the work of Security Architecture is done, its work products are at the right maturity and its decisions are recorded. Run by the stage leads and checked by the product security owner.
MustDone: choose the root of trust architecture.
a dedicated security subsystem, a security mode of the main processor with hardware isolation, or a separate secure element, and decide whether its IP is designed in-house or licensed, with the supplier's security evidence.
MustDone: design the secure boot chain.
boot sources, the order of verification from boot ROM to the operating system, anti-rollback and recovery, agreed with the firmware architecture.
MustDone: design key storage and the key hierarchy.
fuses, a physically unclonable function or protected memory as the root, how working keys are derived and how keys are revoked or replaced.
MustDone: define device lifecycle states and debug authentication.
what each state opens, how transitions are made one way or authenticated, and how returned parts can be analysed without exposing secrets.
MustDone: design isolation between trusted and untrusted software.
processor security states, bus and memory firewalls and access permissions per trust domain, described in machine-readable form shared with hardware and software.
MustDone: choose algorithms, key sizes, random number generation and the cryptographic accelerators, with a plan for crypto agility, and plan side-channel and fault countermeasures for each sensitive operation.
41 more items for registered members.
The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.