Book description
Table of contents
- Cover
- Title Page
- Copyright Page
- Dedication
- Contents
- Foreword
- Acknowledgments
- Introduction
-
Part I What Do You Want?
-
Chapter 1 What’s the Problem?
- Overview
- 1.1 Baking in Trustworthiness: Design-Time
-
1.2 Operational Perspective: Basic Questions
- 1.2.1 Am I Under Attack?
- 1.2.2 What Is the Nature of the Attack?
- 1.2.3 What Is the Mission Impact So Far?
- 1.2.4 What Is the Potential Mission Impact?
- 1.2.5 When Did It Start?
- 1.2.6 Who Is Attacking?
- 1.2.7 What Are They Trying to Do?
- 1.2.8 What Is the Attacker’s Next Step?
- 1.2.9 What Can I Do About It?
- 1.2.10 What Are My Options and How Effective Will Each Option Be?
- 1.2.11 How Will My Mitigation Actions Affect Operation?
- 1.2.12 How Do I Better Defend Myself in the Future?
- 1.3 Asymmetry of Cyberspace Effects
- 1.4 The Cybersecurity Solution Landscape
- 1.5 Ounces of Prevention and Pounds of Cure
- Conclusion
- Questions
-
Chapter 2 Cybersecurity Right-Think
- Overview
- 2.1 It’s About Risk
- 2.2 The Cybersecurity Trade-off: Performance and Functionality
- 2.3 Theories of Security Come from Theories of Insecurity
- 2.4 They Come at You Through the Weeds
- 2.5 Top-Down Meets Bottom-Up
- 2.6 Cybersecurity Is a Live Orchestra, Not a Recorded Instrument
- Conclusion
- Questions
-
Chapter 3 Value and Mission: Know Thyself
- Overview
- 3.1 Focus on Mission and Value
- 3.2 Confidentiality: Value of Secrecy from Adversaries
- 3.3 Confidentiality: Beware the Tyranny of Secrecy
- 3.4 Confidentiality: Changing the Value Proposition
- 3.5 Integrity: The Root of All Trustworthiness Value
- 3.6 Availability: An Essential Yet Tenuous Value
- Conclusion
- Questions
- Chapter 4 Harm: Mission in Peril
-
Chapter 5 Approximating Reality
- Overview
- 5.1 The Complexity of State: Why Model?
- 5.2 Levels of Abstraction: At What Levels
- 5.3 What to Model and Why
- 5.4 Models Are Always Wrong, Sometimes Useful
- 5.5 Model Views
- 5.6 Defense Models Must Consider Failure Modes
- 5.7 Assume Adversaries Know Defender’s System
- 5.8 Assume Adversaries Are Inside Defender’s System
- Conclusion
- Questions
-
Chapter 1 What’s the Problem?
-
Part II What Could Go Wrong?
-
Chapter 6 Adversaries: Know Thy Enemy
- Overview
- 6.1 Know Your Adversaries
- 6.2 Assume Smart Adversaries
-
6.3 Assume Adversaries Don’t Play Fair
- 6.3.1 Going Around Security Controls
- 6.3.2 Going Beneath Security Controls
- 6.3.3 Attacking the Weakest Link
- 6.3.4 Violating a Design Assumption
- 6.3.5 Using Maintenance Modes
- 6.3.6 Using Social Engineering
- 6.3.7 Using Bribery and Blackmail to Subvert Insiders
- 6.3.8 Taking Advantage of Temporary Bypasses
- 6.3.9 Taking Advantage of Temporary Connections
- 6.3.10 Taking Advantage of Natural System Failure
- 6.3.11 Exploiting Bugs You Did Not Even Know You Had
- 6.3.12 Compromising External Systems that a System Trusts
- 6.4 Anticipate Attack Escalation
- 6.5 Red Teams
- 6.6 Cyberspace Exercises
- 6.7 Red Team Work Factor: Measuring Difficulty
- Conclusion
- Questions
-
Chapter 7 Forests of Attack Trees
- Overview
- 7.1 Attack Trees and Forests
- 7.2 System Failures Predict Cybersecurity Failures
- 7.3 Understanding Failure Is the Key to Success: The Five Whys
- 7.4 Forests Should Be Representative, Not Exhaustive
- 7.5 Drive Each Attack Tree Layer by Asking How
- 7.6 Go as Deep as Needed and No Deeper
- 7.7 Beware of External Dependencies
- Conclusion
- Questions
-
Chapter 6 Adversaries: Know Thy Enemy
-
Part III What Are the Building Blocks of Mitigating Risk?
-
Chapter 8 Countermeasures: Security Controls
- Overview
- 8.1 Countermeasures: Design to Purpose
- 8.2 Ensure Attack-Space Coverage (Defense in Breadth)
- 8.3 Defense in Depth and Breadth
- 8.4 Multilevel Security, Trusted Code, Security Kernels
- 8.5 Integrity and Type Enforcement
- 8.6 Cybersecurity Usability
- 8.7 Deploy Default Secure
- 8.8 Costs
- Conclusion
- Questions
- Chapter 9 Trustworthy Hardware: Bedrock
- Chapter 10 Cryptography: A Sharp and Fragile Tool
-
Chapter 11 Authentication
- Overview
- 11.1 Entity Identification: Phase 1 of Authentication
- 11.2 Identity Certification: Phase 2 of Authentication
- 11.3 Identity Resolution: Phase 3 of Authentication
- 11.4 Identity Assertion and Identity Proving: Phases 4 and 5 of Authentication
- 11.5 Identity Decertification: Phase 6 of Authentication
- 11.6 Machine-to-Machine Authentication Chaining
- Conclusion
- Questions
- Chapter 12 Authorization
-
Chapter 13 Detection Foundation
- Overview
- 13.1 The Role of Detection
- 13.2 How Detection Systems Work
- 13.3 Feature Selection
- 13.4 Feature Extraction
- 13.5 Event Selection
- 13.6 Event Detection
- 13.7 Attack Detection
- 13.8 Attack Classification
- 13.9 Attack Alarming
- 13.10 Know Operational Performance Characteristics for Sensors
- Conclusion
- Questions
- Chapter 14 Detection Systems
- Chapter 15 Detection Strategy
- Chapter 16 Deterrence and Adversarial Risk
-
Chapter 8 Countermeasures: Security Controls
-
Part IV How Do You Orchestrate Cybersecurity?
-
Chapter 17 Cybersecurity Risk Assessment
- Overview
- 17.1 A Case for Quantitative Risk Assessment
- 17.2 Risk as a Primary Metric
- 17.3 Why Measure?
- 17.4 Evaluate Defenses from an Attacker’s Value Perspective
- 17.5 The Role of Risk Assessment and Metrics in Design
-
17.6 Risk Assessment Analysis Elements
- 17.6.1 Develop Mission Model
- 17.6.2 Develop System Model
- 17.6.3 Develop Adversary Models
- 17.6.4 Choose Representative Strategic Attack Goals
- 17.6.5 Estimate Harm Using Wisdom of Crowds
- 17.6.6 Estimate Probability Using Wisdom of Crowds
- 17.6.7 Choose Representative Subset
- 17.6.8 Develop Deep Attack Trees
- 17.6.9 Estimate Leaf Probabilities and Compute Root
- 17.6.10 Refine Baseline Expected Harm
- 17.6.11 Harvest Attack Sequence Cut Sets => Risk Source
- 17.6.12 Infer Attack Mitigation Candidates from Attack Sequences
- 17.7 Attacker Cost and Risk of Detection
- Conclusion
- Questions
- Chapter 18 Risk Mitigation and Optimization
- Chapter 19 Engineering Fundamentals
- Chapter 20 Architecting Cybersecurity
- Chapter 21 Assuring Cybersecurity: Getting It Right
-
Chapter 22 Cyber Situation Understanding: What’s Going On
- Overview
- 22.1 Situation Understanding Interplay with Command and Control
- 22.2 Situation-Based Decision Making: The OODA Loop
- 22.3 Grasping the Nature of the Attack
- 22.4 The Implication to Mission
- 22.5 Assessing Attack Damages
- 22.6 Threat Assessment
- 22.7 The State of Defenses
- 22.8 Dynamic Defense Effectiveness
- Conclusion
- Questions
- Chapter 23 Command and Control: What to Do About Attacks
-
Chapter 17 Cybersecurity Risk Assessment
-
Part V Moving Cybersecurity Forward
- Chapter 24 Strategic Policy and Investment
- Chapter 25 Thoughts on the Future of Cybersecurity
- Part VI Appendix and Glossary
Product information
- Title: Engineering Trustworthy Systems: Get Cybersecurity Design Right the First Time
- Author(s):
- Release date: August 2018
- Publisher(s): McGraw-Hill
- ISBN: 9781260118186
You might also like
book
Cyber Security Engineering: A Practical Approach for Systems and Software Assurance
Cyber Security Engineering is the definitive modern reference and tutorial on the full range of capabilities …
book
Security Engineering: A Guide to Building Dependable Distributed Systems, Second Edition
The world has changed radically since the first edition of this book was published in 2001. …
book
The Cyber Security Handbook – Prepare for, respond to and recover from cyber attacks
This book is a comprehensive cyber security implementation manual which gives practical guidance on the individual …
book
Computer and Information Security Handbook, 3rd Edition
Computer and Information Security Handbook, Third Edition, provides the most current and complete reference on computer …