INFOSEC started with Ware Report defining issues and predicting requirements. Lots of CompSci and experimentation by military followed. MULTICS pentest and other landmark works happened. Most key activities that boost security were identified then included into standards like Orange Book. A niche market and CompSci field flourished studying and building systems that used every technique known to improve security with great results (on security anyway). U.S. government canceled mandate on high assurance to switch to COTS for features &amp; cost. Private market did same for similar reasons. High assurance market imploded with research going to a trickle.<p>PC and Internet eras were really getting going around that same time. Languages and approaches that introduce vulnerabilities one way or another became huge. INFOSEC research and products shifted toward all kinds of tactics for hardening, analyzing, monitoring, and recovering such inherently, insecure stuff. Revisionism kicked in where people forgot the old wisdom, starting to reinvent it slowly, plus how and why they got there in the first place. The products, both regular and security, had tons of vulnerabilities old methods and tools prevented. I call this the Modern Era of INFOSEC. It&#x27;s still running strong.<p>Good news is the Old Guard published tons of papers and experience reports telling us what to do, what not to do, and so on. There&#x27;s a steady stream of CompSci people and some in industry building on that. Keeps advancing. Even mainstream IT and INFOSEC adopted some of the strategies. Rust, &quot;side channels&quot; analysis, unikernels, trusted boot... all these are modern variations (sometimes improvements) on what was done in 70&#x27;s-early 90&#x27;s. So, it&#x27;s not dead but it&#x27;s mostly ignored and barely moving.<p>That&#x27;s what I&#x27;m thinking when I see another modern firewall or whatever with less security than the guards from the 80&#x27;s that predated them. You&#x27;d think they&#x27;d have learned something by now past just the features. The assurance activities were there for a reason. 
Guards, if you were wondering...
<a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Guard_%28information_security%29" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Guard_%28information_security%...</a><p>Good essay on security assurance from engineering rather than subjective point of view that development often takes:<p><a href="http:&#x2F;&#x2F;web.cecs.pdx.edu&#x2F;~hook&#x2F;cs491sp08&#x2F;AssuranceSp08.ppt" rel="nofollow">http:&#x2F;&#x2F;web.cecs.pdx.edu&#x2F;~hook&#x2F;cs491sp08&#x2F;AssuranceSp08.ppt</a>