See latest writings mostly about software security and 日本語コンテンツ
Kohnfelder, Loren. Designing Secure Software: A Guide for Developers. No Starch Press, 2021.
Designing Secure Software consolidates more than twenty years of experience into a concise, elegant guide to improving the security of technology products. Written for a wide range of software professionals, it emphasizes building security into software design early and involving the entire team in the process.
The book begins with a discussion of core concepts, covering trust, threats, mitigation, secure design patterns, and cryptography. The second part, perhaps this book’s most unique and important contribution to the field, covers the process of designing and reviewing a software design with security considerations in mind. The final section details the most common coding flaws that create vulnerabilities, making copious use of code snippets written in C and Python to illustrate implementation vulnerabilities.
You’ll learn how to:
- Identify important assets, the attack surface, and the trust boundaries in a system
- Evaluate the effectiveness of various threat mitigation candidates
- Work with well-known mitigations and secure design patterns
- Understand and prevent vulnerabilities like XSS and CSRF, memory flaws, and more
- Use security testing to proactively identify vulnerabilities introduced into code
- Review a software design for security flaws effectively and without judgment
“The writing in this book is very clear and easy reading, and the examples used are both captivating and easy to understand. Kohnfelder does a great job of making a point that is easy to understand, and most of the chapters could stand alone for developers just working in that one particular area.” (read the full review)
Latest writings
-
Against the Leap Hour
I was very disappointed to read that our standards body would implement a leap hour. As I understand it the leap-second was an adjustment made everyone so many years to keep atomic…
-
August 2026
This linkdump post will be the last of the experimental series. I plan to revamp this website and consider better venues for my contributions to the public internet. Thanks to anyo…
-
Rate limiting legacy dependence
“AI” is already disrupting many institutions simply by extending the reach of digital technology faster and further than ever before. Of course, it is always going further, and the…
-
Questions about Collective action on cybersecurity
We are at an important inflection point with at least two fronts on the ongoing challenges of software security that AI is impacting at unprecedented speed. the rush to offload mo…
-
LLM Cyber defense
This is a quick solo effort of a few hours work with free tier Gemini … but surprisingly promising results right off the bat so I’m putting it out there on the off chance there is …
-
Threat modeling apps invoking LLMs
Currently all the talk is about how frontier models (e.g. Mythos) can be used offensively — and not talked about in polite company, probably most, if not virtually all, enterprise …
-
Anti-requirements in prompts
As we continue to see all the “AI goes rogue” in testing reports, I keep wondering if this isn’t the aptly named “genie effect” (hat tip: Bruce Schneier), and if so if anti-require…
-
Threat modeling post-quantum strategy
Racing to beat an unknowable deadline ahead of quantum computing breaking legacy cryptography, achieving the defenses we would wish to be in place in time, or to meet announced sta…
-
July 2026
AI continues to dominate the news, largely involving security, and not in a good way. Role confusion: one more reason we can’t trust LLMs AI agent parody? Threat modeling Duress c…
-
Role confusion: one more reason we can’t trust LLMs
Prompt Injection as Role Confusion is my new favorite paper about a very obvious threat in hindsight that’s hard for us humans to see because we anthropomorphize LLMs so naturally.…