Chapter 12. Closing Thoughts

We’ve discussed a range of architectural thinking techniques and artifacts to use during the development of a hybrid cloud solution architecture. With a focus on artifacts rather than documents, the principles we went through apply to both traditional waterfall and Agile approaches to solution delivery.

There are other good practices that will help you on your journey to become proficient in architecting security into your solution architecture. We will take you through some of these guidelines as well as some thoughts around AI as our closing thoughts for the book. Let’s start with the basics.

Getting Started

You may be thinking this is all a bit overwhelming, and where do I start with something simple? We’ll discuss a few different perspectives to start with, including starting with some basic security controls, starting with a minimum set of artifacts, iterating to improve maturity, and getting the balance of risk right.

Don’t Forget the Basics

We talk about performing a comprehensive analysis with control compliance and threat modeling with assurance to provide confidence in your solution, but you can remove a large proportion of the risk rapidly by performing the basics, including:

Use supported software

Using supported software ensures the availability of security patches. This includes open source software that requires regression testing with all the different integrated components. Open source software isn’t free; it still needs support. ...

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.