Book
Designing Secure Software
A Guide for Developers
Loren Kohnfelder
Summary
Designing Secure Software, by Loren Kohnfelder, a co-developer of the STRIDE threat model, gathers more than 20 years of his experience into general methods for improving software security. STRIDE stands for Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege, and was developed at Microsoft in the late 1990s to classify threats. The book is aimed at everyone involved in a software product, from design and programming to marketing, and stresses early security in design and whole-team involvement. It has three parts: concepts, design, and implementation. Part 1 covers security and privacy basics, threat modeling, mitigations, design patterns, and cryptography. Part 2 covers security-minded software design and review. Part 3 covers vulnerabilities in code, from low-level flaws to input and web issues, and security testing.
Target Readers
- Engineers who want to establish threat modeling in their design process
- Developers who want to learn the whole secure development lifecycle systematically
- Everyone involved in a software product, from design and programming to marketing
Tags
Colophon
- Publisher
- Shuwa System
- ISBN
- 978-4-7980-6975-3
- Published
- Aug 2023
- List price
- ¥4,180incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
Secure by Design
Dan Bergh Johnsson, Daniel Deogun, Daniel Sawano
Reason: After grasping a robust, type-based design philosophy, advance to embedding it into the development process. STRIDE-based threat modeling systematically surfaces attack surfaces and trust boundaries, giving design reviews their backbone.
Next Books
- Related
Web Security Tantosha no Tame no Zeijakusei Shindan Start Guide, 2nd Edition (A Vulnerability Assessment Start Guide for Web Security Staff)
Sen Ueno Teaches New Techniques for Preventing Information Leaks
Sen Ueno
Reason: Once threat modeling has surfaced 'where the risks lie' at design time, confirm those assumptions through hands-on assessment. Matching design-level threats against actual behavior validates the effectiveness of your defenses.