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

Considerations for Waterfall projects

"For applications, you need to make sure that pieces align correctly and that the application itself is secure. The architecture process is there in part to ensure that developers don't do things that will wind up in the application being successfully attacked; for example, to ensure that logging is enabled, that authentication is in place, that secure session identifiers are in use, and so forth. Failure to do these things can often result in an attack because they weaken the application. The architect, seeing this, can design solutions that ensure the application's original goals are satisfied while at the same time closing these issues."

– John Kallil, Chief Information Security Officer

Nowadays, not many software projects are built using the traditional Waterfall development process. That being said, it is useful as a starting point because it is still sometimes used—notably for special-purpose software...