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

Building blocks of secure design

Any discussion about the requisite tools in your design toolbox wouldn't be complete without some discussion of the actual security mechanisms that you'll employ as part of your design. These represent specific measures you might use—and specific objectives that you might target—as part of a broader, overarching security design.

It's important to understand what these controls are and are not. They are not implementations. Any given control can be implemented in a myriad of different ways. For example, you might have a control specifying that any administrative access to production systems (and system components) must be logged and recorded. However, this control doesn't outline how you'd do that; instead, context, circumstances, and the organization itself will dictate how. For example, if access to the production system happens via a terminal (that is, a user at the keyboard), you might use the native logging...

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