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

Creating a program

"John Kotter has a book called Leading Change. At a meta level, all of the frameworks and processes for architecture boil down to the eight steps he outlines: create a sense of urgency, build a coalition, form a strategic vision, enlist others, enable action by removing barriers, generate short-term wins, sustain acceleration, and institute change. One of the primary sources of value for architecture is reducing technical debt. Stay focused on that: how can we make our lives easier in the future based on what we do today?"

– Adam Shostack, President, Shostack & Associates

You'll note that at this point, we still don't have any fully realized documentation for our goals, capabilities, or target state. We've done quite a bit of thinking about these things and maybe created some informal notes, but we have yet to put pen to paper to document this officially. To do that, we find it helpful to set up a structure within which we...

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