There is no secret, and I've not read the CISSP manual. I just design for it before I start writing code. Also, I don't ask anyone to care about anything. Your app, your choice. You mention tornadoes. That's reactive. I'm suggesting being proactive, by asking what can be done before an event, not after.

I know absolute security is elusive. I still try to anticipate what might happen, however. As Covey says, begin with the end in mind.

And finally, as far as Matasano goes. Yes, they have a good reputation. Thomas has a lot of technical depth for sure (certainly more than I). It interests me however, that I've never heard mention of a Needham-Schroeder implementation from them. But I may just have missed it. To be clear, I have no delusions - I imagine Matasano's crew has a lot more brain than I do. That's cool. And yet I find myself wondering why we (and they) all talk about which algorithm is good for crypto function x or y, but never about which protocol you might use to securely exchange keys (for example).