Secure by Design

11 Intermission: An insurance policy for free

This chapter covers

• A broken system where no parts were broken
• Context mapping to understand what’s going on
• Risk of myopic views of microservices

So far, we’ve covered lots of different ways to use design to make software more secure. We’ve collected designs from different areas, like cloud architecture, Domain-Driven Design (DDD), and reactive systems, where security wasn’t the original focus. The nice thing is that all these designs can be used in ways that increase security as a beneficial side effect. All in all, we’ve covered a lot of ground, and we’ll soon turn to applying these fundamentals to some different scenarios, such as legacy systems and microservices architectures. But before ...