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)
1
Section 1:Security Architecture
4
Section 2: Building an Architecture
9
Section 3:Execution

Requirements

If you've been following along, you'll have a few things already prepared:

  • Informal scope: You've spent some time thinking about the scope of your planning but you (purposefully) haven't documented it yet. In Chapter 3, Building an Architecture – Scope and Requirements, we went through the process of defining an informal scope. In this chapter, we will build on that to arrive at the actual recordable design scope.
  • Existing landscape: In the previous chapter, we talked about strategies to understand what you have in place now. This ideally includes an understanding of existing constraints that you'll need to account for and plan around (recall the gap analysis discussion from the previous chapter), as well as an understanding of what is in place already so that you can look for areas of efficiency during the implementation process. Some projects will start with a "blue ocean"—a completely new environment, application...