Book Image

Practical Cybersecurity Architecture

By : Ed Moyle, Diana Kelley
Book Image

Practical Cybersecurity Architecture

By: Ed Moyle, Diana Kelley

Overview of this book

Cybersecurity architects work with others to develop a comprehensive understanding of the business' requirements. They work with stakeholders to plan designs that are implementable, goal-based, and in keeping with the governance strategy of the organization. With this book, you'll explore the fundamentals of cybersecurity architecture: addressing and mitigating risks, designing secure solutions, and communicating with others about security designs. The book outlines strategies that will help you work with execution teams to make your vision a concrete reality, along with covering ways to keep designs relevant over time through ongoing monitoring, maintenance, and continuous improvement. As you progress, you'll also learn about recognized frameworks for building robust designs as well as strategies that you can adopt to create your own designs. By the end of this book, you will have the skills you need to be able to architect solutions with robust security components for your organization, whether they are infrastructure solutions, application solutions, or others.
Table of Contents (14 chapters)
Section 1:Security Architecture
Section 2: Building an Architecture
Section 3:Execution

Process for application security design

"On the technical side, one has to focus on the conceptual architecture. Cloud, for example, is a whole new concept with tremendous implications. At the detail level, there are many aspects of the cloud; you need people like that to know those details and do that work. But the really creative architecture work is at the higher level, the conceptual level: how businesses use the cloud, not how the cloud itself is implemented."

– John Sherwood, Chief Architect, Thought Leader and Co-Founder of The SABSA Institute

There are, of course, other approaches beyond the three software development methodologies and life cycle archetypes that we have highlighted here. However, hopefully, the integration strategies we've looked at that are associated with these different models has shown some of the logic behind where we've chosen to integrate. If not, that's OK: we will work through how and where the development model...