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

Technical design

"Successful architecture needs both structure and agility. You need just enough structure to where that structure is useful, but anything beyond that is bad. The way I started thinking about security controls and applying them to the rest of the organization is through the lens of healthy friction versus unhealthy friction. Healthy friction is friction that makes the developer or IT person pause, ask, and genuinely answer a critical thinking question such as "should I be doing this differently?" or "can I do this better?". By contrast, if you get to the point where the security measures are onerous – for example, by adding thousands of false positives to a developer's queue or adding repetitive tasks to a user workflow– it becomes unhealthy friction. I view architecture the same way; introducing a process that makes people ask the right questions, talk to the right people, or do the right things is good. Adding structure...