DeepRead
Cover of Writing secure code

About the book

A practical guide to writing software that resists attack, aimed at developers and testers working on Windows and other C and C++ code bases. It covers how common security flaws arise in code, including buffer overflows, input validation errors, injection, and weak handling of data and privileges, along with the tools and review practices for finding them. The second edition, co-written with David LeBlanc, reflects Microsoft's security push after 2002. Security is a property that has to be designed and built in from the start, not added by testing or patching after release. Most exploitable vulnerabilities come from a small set of repeatable coding mistakes that developers can learn to recognise and avoid. The book makes the case for secure design principles such as least privilege, defence in depth, and failing securely, and for threat modelling as a routine part of development.

Written by Claude from what it knows of this book.

What Hacker News says 67% recommend · 0% critical

0122015201620182020202220232015 peak · 1
This bookAverage book in Cryptography and security engineering

In the commenters’ own words

What Open Library readers say

No Open Library reader has rated it yet.

Open Library’s page for the book

What critics say, via Wikipedia

No Wikipedia article about this book yet, so no critics to quote.

Reddit communities — coming later

Details

First published
2003
ISBN
9780735617223
Editions known
2 at Open Library
Open Library
OL12066727W

005.8Computer securityData encryption (Computer science)Data encryption (computer science)Qa76.9.a25 h698 2003

Explore in the mosaic

Read next: its neighbours on the mosaic