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

Virtuous cycles

“From my point of view, you need to align infrastructure and security design elements to the processes you have in place. For example, if your organization uses two-week scrums, align your architecture design and implementation process around that process. If you are using a different cycle or another approach, design around that instead. This is true both temporally as well as philosophically. Meaning, the cycle time should be aligned to best service their needs, but the design philosophy should be aligned as well: if the organization heavily leverages cloud, adapt – if it’s DevOps and CI/CD, integrate into that. You want to be in sync with the environment around you not just to get buy-in and acceptance but also as a practical matter.”

– Anand Sastry, Director Cyber Operations USA, Barclays

In the last chapter, we discussed the impact of change on the design process, both in dealing with unexpected change and issues that arise...