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

Application design considerations

“There are three kinds of security defects in the world. At the network level, most problems are just configuration errors: you set it up wrong, you didn’t block the right ports, you accidentally put your firewall behind the thing instead of in front of the thing. Those are configuration errors, the first generation of security problems, and the ones we’ve been dealing with the longest. The second kind of defects are bugs. These are implementation errors in code: you use the wrong system call in C or C++, or you used Java incorrectly and now you have a bug that can be tickled from outside by a smart attacker. The third kind of security defect has been generally-speaking ignored by everybody, which are design issues.

When you have a software architecture, you can do an analysis of it. Some people call this a threat model; others say it’s architecture risk analysis. The idea is let’s look for flaws in our design...