Book Image

Practical Cybersecurity Architecture - Second Edition

By : Diana Kelley, Ed Moyle
Book Image

Practical Cybersecurity Architecture - Second Edition

By: Diana Kelley, Ed Moyle

Overview of this book

Cybersecurity architecture is the discipline of systematically ensuring that an organization is resilient against cybersecurity threats. Cybersecurity architects work in tandem with stakeholders to create a vision for security in the organization and create designs that are implementable, goal-based, and aligned with the organization’s governance strategy. Within this book, you'll learn the fundamentals of cybersecurity architecture as a practical discipline. These fundamentals are evergreen approaches that, once mastered, can be applied and adapted to new and emerging technologies like artificial intelligence and machine learning. You’ll learn how to address and mitigate risks, design secure solutions in a purposeful and repeatable way, communicate with others about security designs, and bring designs to fruition. This new edition outlines strategies to help you work with execution teams to make your vision a reality, along with ways of keeping designs relevant over time. As you progress, you'll also learn about well-known frameworks for building robust designs and strategies that you can adopt to create your own designs. By the end of this book, you’ll have the foundational skills required to build infrastructure, cloud, AI, and application solutions for today and well into the future with robust security components for your organization.
Table of Contents (15 chapters)
Part 1: Security Architecture
Part 2: Building an Architecture
Part 3: Execution

Documenting your high-level approach

“In documenting your architecture, you need to have the consumer in mind. I don’t mean end customers here—I mean the intended audience for the documentation itself. The CEO needs a different level of understanding about the architecture than a system administrator. The right way to approach this is to figure out what is the most useful format of the documentation for the audiences in the organization that need to consume it. To do this, you need to understand why they need it, how they will use it, and what their goals and interests are.”

– Ted Ipsen, President and COO at Positroniq, LLC

As we mentioned previously, in this section, we’ll be putting together the initial documentation that will guide our work. We’ll be creating this in two stages:

  • Phase 1: A high-level roadmap that provides an abstract, business-facing view of the design
  • Phase 2: An architecture definition that provides...