Chapter 9. Architecture Patterns and Decisions
As a security architect, you won’t create a security architecture from a blank page; that would be a rather exceptional case. Luckily, there are a lot of sources of information you can reuse to create or update the security architecture you need. One of the artifacts you would be looking for most are security-related architecture patterns. These patterns will give you a kickstart when creating a security architecture. You should save valuable time when making use of such patterns, and you’ll get the assurance that the pattern will deliver the expected functionality because someone has tested it before.
In this chapter, we first take a closer look at the term “pattern” itself. What do we mean by the term pattern, and is there a definition for it? Next, we will review what kinds of security pattern types exist and direct you to or show you some examples. We’re then going to talk through layers of core security design patterns that demonstrate the need for patterns written as code for automation of the solution deployment using deployable architectures.
The next topic in this chapter is one that’s close to the authors’ hearts and fundamental to architectural thinking: architectural decisions. In general, IT architecture is created under time pressure. The shorter duration of development sprints for some projects doesn’t leave much time for solution architects and security architects to create detailed documentation. You’ll have to make ...
Get Security Architecture for Hybrid Cloud now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.