- Cover
- Titlepage
- Copyright
- Dedication
- contents in brief
- contents
- foreword
- preface
- acknowledgments
- about this book
- about the authors
- about the cover illustration
- Part 1: Introduction
- Chapter 1: Why design matters for security
- Chapter 2: Intermission: The anti-Hamlet
- Part 2: Fundamentals
- Chapter 3: Core concepts of Domain-Driven Design
- Chapter 4: Code constructs promoting security
- Chapter 5: Domain primitives
- Chapter 6: Ensuring integrity of state
- 6.1 Managing state using entities
- 6.2 Consistent on creation
- 6.2.1 The perils of no-arg constructors
- 6.2.2 ORM frameworks and no-arg constructors
- 6.2.3 All mandatory fields as constructor arguments
- 6.2.4 Construction with a fluent interface
- 6.2.5 Catching advanced constraints in code
- 6.2.6 The builder pattern for upholding advanced constraints
- 6.2.7 ORM frameworks and advanced constraints
- 6.2.8 Which construction to use when
- 6.3 Integrity of entities
- Summary
- Chapter 7: Reducing complexity of state
- Chapter 8: Leveraging your delivery pipeline for security
- Chapter 9: Handling failures securely
- Chapter 10: Benefits of cloud thinking
- Chapter 11: Intermission: An insurance policy for free
- Part 3: Applying the fundamentals
- Chapter 12: Guidance in legacy code
- 12.1 Determining where to apply domain primitives in legacy code
- 12.2 Ambiguous parameter lists
- 12.3 Logging unchecked strings
- 12.4 Defensive code constructs
- 12.5 DRY misapplied—not focusing on ideas, but on text
- 12.6 Insufficient validation in domain types
- 12.7 Only testing the good enough
- 12.8 Partial domain primitives
- Summary
- Chapter 13: Guidance on microservices
- Chapter 14: A final word: Don’t forget about security!
- Chapter 12: Guidance in legacy code
- Index
- Lists of Figures
- List of Tables
- List of Listings
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.