ABSTRACT
Threat modeling is rarely that useful when performed exactly once, at a particular point in time. That’s because throughout development, things change regularly, sometimes constantly. When threat modeling is performed as a group activity, the analysis benefits from varying team member’s attack knowledge. Web attacks encapsulated within application messages were a cutting edge in the threat landscape. Presumably, assigning an experienced security architect who would both advance the state of the art against a changing threat landscape while also helping to build services resistant to the broader range of attacks that had become possible over the life of the legacy system proved worthwhile for the organization. There are couple of challenges that satellite programs will tend to encounter. The foremost is that as people go through the program, fulfill the role, they will be hired away into other organizations.
