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

Building blocks of secure design

Any discussion about the requisite tools in your design toolbox wouldn’t be complete without some discussion of the actual security mechanisms that you’ll employ as part of your design. These represent specific measures you might use – and specific objectives that you might target – as part of a broader, overarching security design.

It’s important to understand what these controls are and what they are not. They are not implementations. Any given control can be implemented in a myriad of different ways. For example, you might have a control objective specifying that any administrative access to production systems (and system components) must be logged and recorded. However, this in itself doesn’t outline how you’d do that. Instead, context, circumstances, and the organization itself will dictate how you accomplish the result and how you implement that control within your organizational context. For...