Secure Software & Domain Driven Design
summary
Argues for treating security as an architectural concern and shows how Domain‑Driven Design (DDD) techniques produce concrete security improvements. Recommends using constructors and value objects to enforce invariants and immutability, applying fail‑fast validation, splitting shared classes (e.g. separate Address types for shipping vs orders) to avoid coupling, and validating inputs in sequence (origin, size, lexical/syntax, then semantic) with checks like IP validation, security groups, regex, and domain primitives.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:26Classic security concept
- 5:24Security as design aspect
- 7:12Domain model and DDD
- 12:39Code constructs for security
- 16:35Validations in secure development
- 21:34Basic building blocks
- 29:48Domain Primitives and conclusions
- 31:53Summary and Q&A
related talks
59mDomain-Driven Design - Where Rubber Meets the Road
52mSecure by Design, Revisited - Insights & Pitfalls
55mDomain-Driven Design: back to the roots
48mDomain-Driven Design tactically and practically
52mArm yourself with Domain Driven Security. It's time to slay some security trolls?
46mSecure Coding Patterns
01h 17mSecure by Design - Security Principles for the Working Architect
27mSecurity by Design