Used before Threat model baselined, to confirm the work of Threat Modelling & Attack Surface Analysis 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: describe the attackers.
remote attackers on a network, local software attackers, users with physical access, laboratory attackers with measurement and fault equipment, insiders in the supply chain. For each, record access, skill, time and equipment, since ratings depend on them.
MustDone: model the system.
draw the chip, its interfaces, software layers and trust boundaries, and add manufacturing, provisioning, field service and return paths. The model is the attack surface analysis and is reviewed with the architects who own each part.
MustDone: enumerate threats for each asset across each boundary using the method the security plan names, and check the list against public weakness catalogues such as the CWE hardware weakness view and published attacks on similar products.
MustDone: describe attack paths in enough detail to rate them.
the steps an attacker takes, what each step needs and which existing design features stand in the way.
MustDone: rate each risk for impact and feasibility with the agreed scale and record the rationale, so a later reviewer or laboratory can follow it.
29 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.