Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical Cybersecurity Architecture

You're reading from   Practical Cybersecurity Architecture A guide to creating and implementing robust designs for cybersecurity architects

Arrow left icon
Product type Paperback
Published in Nov 2020
Publisher Packt
ISBN-13 9781838989927
Length 418 pages
Edition 1st Edition
Arrow right icon
Authors (2):
Arrow left icon
Diana Kelley Diana Kelley
Author Profile Icon Diana Kelley
Diana Kelley
Ed Moyle Ed Moyle
Author Profile Icon Ed Moyle
Ed Moyle
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Section 1:Security Architecture
2. Chapter 1: What is Cybersecurity Architecture? FREE CHAPTER 3. Chapter 2: The Core of Solution Building 4. Section 2: Building an Architecture
5. Chapter 3: Building an Architecture – Scope and Requirements 6. Chapter 4: Building an Architecture – Your Toolbox 7. Chapter 5: Building an Architecture – Developing Enterprise Blueprints 8. Chapter 6: Building an Architecture – Application Blueprints 9. Section 3:Execution
10. Chapter 7: Execution – Applying Architecture Models 11. Chapter 8: Execution – Future-Proofing 12. Chapter 9: Putting It All Together 13. Other Books You May Enjoy

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...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime