RHODS / Threat Model Refresh

Email from Langley on next steps:

 
Further to the suggestion that was being bounced around in the RHODS meeting earlier today, I've checked with our Threat Modeling team on what can be done about refreshing the Threat Model.
 
Our program was designed to provide guidance and support to engineering for threat modeling activities.  Once the initial threat model is completed, it's understood that Engineering will retain ownership and update/make changes as needed as architecture and  implementation decisions change throughout the lifecycle.  
 
We can review any such changes following our pilot scheme process [1], taking capacity and conflicting priorities into consideration.
 
What I would like to suggest is that Engineering review the source gdoc [2] and update it to reflect the current state of ODS.  Once done, the TM team will be happy to have a look and we can take it from there.
 
Does that work for you?
 
Thanks,
Langley
Preview attachment Threat Model - RHODSThreat Model - RHODSShared in Drive