Managing and Assuring Secure Systems
Stub. How to actually get a secure system built and trusted: managing the development process for security (not just bolting it on at the end), system evaluation and assurance methodologies (how a third party comes to trust a system's security claims), and a look at the bleeding edge — emerging threats and techniques the rest of the material hasn't caught up to yet.
Closes the security-engineering topic with the organizational and process questions that determine whether all the preceding mechanisms actually get deployed correctly. Managing the development of secure systems covers building security into the process (requirements, review, testing) rather than retrofitting it, and why retrofitted security reliably fails. System evaluation and assurance covers how an independent party can be convinced a system meets its security claims at all — from informal review up through formal evaluation criteria — which matters because most security failures in practice are failures of assurance (an unverified claim), not of any individual mechanism. The bleeding-edge chapter is a reminder that this whole topic area is a moving target, closing on emerging threats and techniques that outpace any fixed curriculum.
Outline (TODO — flesh out each)
- Managing the development of secure systems
- Why security needs to be built in, not bolted on
- System evaluation and assurance methodologies
- The bleeding edge — emerging threats and techniques