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

Life cycle models

“Start small. Don’t try to boil the ocean. Start with a small, manageable size and ‘follow the bit.' By this, I mean follow data from creation, through usage, to transmission, to storage, and ultimately to end of life. A good security architecture should be fluid; it needs to be a living document. If you try to make all decisions at once, they will tend to compete. Narrowing the focus is step one. Understanding the full life cycle is step two.”

– Steve Orrin, Federal CTO at Intel Corporation

Typically, the development model in use ties to the security architecture for a given application at a fundamental level. There are a few reasons for this. The first is that the way software is developed will likely influence the security of the result. We stressed this previously: if you follow a disorganized, slipshod development process, you’ll increase the likelihood of producing a disorganized, slipshod result. As a result...