A technical document about a breach would explain the mechanisms for the vulnerabilities and exploits involved, and discuss how systems could be architected and

A technical document about a breach would explain the mechanisms for the vulnerabilities and exploits involved, and discuss how systems could be architected and written differently to avoid them. This document walks up the abstraction chain several notches and attacks the org chart and security policy of the MS Word variety, not the way things were written or configured (except insofar as bad config stemmed from not enough teams of paper not enforced well enough). It is pitched at the kind of CIO/CTO who could just as easily be any other CxO, not at engineers.