Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

Setting architectural scope

"Be careful with setting scope. If you iterate too much on the scope of what you're trying to secure early on, you may never achieve the first milestone. However, the process and the model by which you create your architecture should absolutely be iterative and the scope will absolutely change. The architectural approaches and models we use need to be able to support these iterative approaches, but very few of the large, monolithic standards will do this "out of the box." This is where there is room for the individual architect to exercise their creativity and innovate, adapting their processes to fit their needs best."

– Steve Orrin, Federal CTO at Intel Corporation

Note right from the get-go that the outcome of this chapter is not about creating documentation. We will eventually document our design scope. This is an important part of the process and, eventually, we will fully document it – ideally, both...

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
Banner background image