Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Practical Cybersecurity Architecture
  • Table Of Contents Toc
  • Feedback & Rating feedback
Practical Cybersecurity Architecture

Practical Cybersecurity Architecture

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

Documenting your high-level approach

"In documenting your architecture, you need to have the consumer in mind. I don't mean end customers here—I mean the intended audience for the documentation itself. The CEO needs a different level of understanding about the architecture than a system administrator. The right way to approach this is to figure out what is the most useful format of the documentation for the audiences in the organization that need to consume it. To do this, you need to understand why they need it, how they will use it, and what their goals and interests are."

– Ted Ipsen, President and COO Positroniq, LLC

As we mentioned previously, in this section, we'll be putting together the initial documentation that will guide our work. We'll be creating this in two stages:

  • Phase 1: A high-level roadmap, which provides an abstract, business-facing view of the design.
  • Phase 2: An architecture definition, which provides a...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
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

Delete Note

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

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY