Telecommunications Board published its widely quoted Computers at Risk. [1]
This book included an entire chapter that described a programming
methodology for secure systems. In that chapter, the authors asked the
question, “What makes secure software different?” The authors then proceeded