Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Practical Cybersecurity Architecture
  • Toc
  • feedback
Practical Cybersecurity Architecture

Practical Cybersecurity Architecture

By : Ed Moyle, Diana Kelley
4.2 (13)
close
Practical Cybersecurity Architecture

Practical Cybersecurity Architecture

4.2 (13)
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)
close
1
Section 1:Security Architecture
4
Section 2: Building an Architecture
9
Section 3:Execution

Virtuous cycles

"From my point of view, you need to align infrastructure and security design elements to the processes you have in place. For example, if your organization uses two-week scrums, align your architecture design and implementation process around that process. If you are using a different cycle or another approach, design around that instead. This is true both temporally as well as philosophically. Meaning, the cycle time should be aligned to best service their needs, but the design philosophy should be aligned as well: if the organization heavily leverages cloud, adapt – if it's DevOps and CI/CD, integrate into that. You want to be in sync with the environment around you not just to get buy in and acceptance but also as a practical matter."

– Anand Sastry, Director Cyber Operations USA, Barclays

In the last chapter, we discussed the impact of change on the design process, both in dealing with unexpected change and issues that arise during...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete