Book Image

Practical Cybersecurity Architecture

By : Ed Moyle, Diana Kelley
Book Image

Practical Cybersecurity Architecture

By: Ed Moyle, Diana Kelley

Overview of this book

Cybersecurity architects work with others to develop a comprehensive understanding of the business' requirements. They work with stakeholders to plan designs that are implementable, goal-based, and in keeping with the governance strategy of the organization. With this book, you'll explore the fundamentals of cybersecurity architecture: addressing and mitigating risks, designing secure solutions, and communicating with others about security designs. The book outlines strategies that will help you work with execution teams to make your vision a concrete reality, along with covering ways to keep designs relevant over time through ongoing monitoring, maintenance, and continuous improvement. As you progress, you'll also learn about recognized frameworks for building robust designs as well as strategies that you can adopt to create your own designs. By the end of this book, you will have the skills you need to be able to architect solutions with robust security components for your organization, whether they are infrastructure solutions, application solutions, or others.
Table of Contents (14 chapters)
Section 1:Security Architecture
Section 2: Building an Architecture
Section 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 have stressed this previously, but if you follow a disorganized, slipshod development process, you'll increase the likelihood of producing a disorganized, slipshod result. As...