Reviews the threat model when it is first written, at architecture approval, before the security review gate and after any significant change or new vulnerability class. The product security architect runs it with firmware, hardware security and validation reviewers.
MustThe material under review is a tagged version, and that version is named in the record.
MustReviewers received the material and this checklist early enough to prepare.
ShouldAt least one reviewer did not take part in the work under review.
ShouldThe scope of the review and anything excluded from it are stated at the start.
27 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.