Books › Application Security Engineer roadmap
Best books for Application Security Engineers
This list is about finding and preventing application flaws. It starts with the web attack classes you will meet in every review, moves to the design and development lifecycle that prevents them, and ends with the book that teaches you to judge whether a review or a program has covered what it should. Nothing here is a certificate syllabus; the labs and your own code reviews matter more than any book. The books assume you can read code in one language and read an HTTP request.
10 books in 3 stages, about 4,780 pages (at least 120 hours of reading). The notes are ours, with no ratings or sales claims.
See the full Application Security Engineer roadmap →Best courses for Application Security Engineers →
How to choose your books
A short method, so you read the right book for where you are instead of the longest list.
Find your stage
Getting started · 2 books
Web attack classes and an approachable introduction to secure coding. Read these alongside the labs until you can explain each flaw and its one-line fix.
Jump to this stage ↓Doing the job · 4 books
Design, API and lifecycle security. Read these when you start reviewing designs and services, not only single pages, and when you need to explain a control to the engineers who must build it.
Jump to this stage ↓Senior and leading · 4 books
Program design, risk and assessment method. These books help you run a review program and judge whether it covered what it claims to cover.
Jump to this stage ↓
If you are unsure, start one stage lower than you think. Books in a later stage assume the working knowledge the earlier ones give you.
Begin with one book
Our starting pick
The Web Application Hacker's Handbook: Finding and Exploiting Security Flaws
by Dafydd Stuttard, Marcus Pinto · 2007
It is the most complete hands-on guide to the attack classes behind most findings. Work through it with the labs, and write one sentence for each flaw that names its fix.
See the book ↓Then pick by your situation
Choose the next book by the problem in front of you, not by its place in the list.
If you are reviewing an API rather than a web page
read Hacking APIs (doing the job)
If you are running design reviews and need to reason about trust boundaries
read Designing Secure Software (senior and leading)
If you have been asked to build an application security program, not only review code
read Application Security Program Handbook (senior and leading)
Set a time budget
| Stage | Books | Pages | Reading | At 3 hrs a week |
|---|---|---|---|---|
| Getting started | 2 | 1,210 | 30 hrs | 10 wks |
| Doing the job | 4 | ≥ 1,060 | ≥ 27 hrs | ≥ 9 wks |
| Senior and leading | 4 | ≥ 2,510 | ≥ 63 hrs | ≥ 21 wks |
| All 3 stages | 10 | ≥ 4,780 | ≥ 120 hrs | ≥ 40 wks |
Treat this as a ceiling, not a target. Read one book at a time, apply it, then move on; read reference-style books in sections. Totals are approximate.
Judge any book before you buy it
Age
This list runs from 2001 (Security Engineering) to 2022 (Hacking APIs). Older books earn their place by teaching principles that do not change. For tools and platforms, buy the latest edition.
Level
Check the stage before the title. A book from a later stage will make sense only once you have faced the problems it solves.
Format
The longest book here, The Art of Software Security Assessment, runs about 1200 pages. Read very long books as references: pick the chapter that matches the problem you have.
Fit
Ask what you will do differently the week after you finish. If you cannot answer, the book is for a different moment. Come back to it when the situation arrives.
Getting started
Web attack classes and an approachable introduction to secure coding. Read these alongside the labs until you can explain each flaw and its one-line fix.
Start hereThe Web Application Hacker's Handbook: Finding and Exploiting Security Flaws
by Dafydd Stuttard, Marcus Pinto · 2007
~910 pages~23 hrs to read
The standard hands-on guide to finding authentication, session and injection flaws in web applications. Read it alongside the labs, and note which fix each attack class needs.
View book →
Alice and Bob Learn Application Security
by Tanya Janca · 2020
~300 pages~8 hrs to read
A friendly introduction to secure design, authentication and secure coding for developers. It is a good first book to give to an engineer you are about to work with.
View book →
Doing the job
Design, API and lifecycle security. Read these when you start reviewing designs and services, not only single pages, and when you need to explain a control to the engineers who must build it.
The Tangled Web: A Guide to Securing Modern Web Applications
by Michal Zalewski · 2011
~300 pages~8 hrs to read
Why browsers and web standards behave the way they do, and how that creates security problems. Useful when a finding depends on a browser quirk.
View book →
Hacking APIs: Breaking Web Application Programming Interfaces
by Corey J. Ball · 2022
API-specific attack classes such as broken object-level authorization and mass assignment. Read it when your review scope is an API rather than a web page.
View book →
Secure by Design
by Daniel Deogun, Dan Bergh Johnsson, Daniel Sawano · 2019
~410 pages~10 hrs to read
Design-level security: domain modeling, input handling and the principles that stop a whole class of bugs from being written. It is the design side of application security work.
View book →The Security Development Lifecycle
by Michael Howard, Steve Lipner · 2006
~350 pages~9 hrs to read
How Microsoft built security checkpoints into its development process. The book is dated in its tooling, but the lifecycle gates it describes are still the template most AppSec programs use.
View book →
Senior and leading
Program design, risk and assessment method. These books help you run a review program and judge whether it covered what it claims to cover.

Designing Secure Software: A Guide for Developers
by Loren Kohnfelder · 2021
~310 pages~8 hrs to read
How to reason about threats and trust boundaries when you design a system, written for the engineers who will build it. Read it when you are running design reviews rather than only code reviews.
View book →Security Engineering: A Guide to Building Dependable Distributed Systems
by Ross Anderson · 2001
~1000 pages~25 hrs to read
A systems-wide view of security: access control, cryptography, economics and failure. The third edition is the one to read, and it explains why controls fail in practice.
View book →The Art of Software Security Assessment: Identifying and Preventing Software Vulnerabilities
by Mark Dowd, John McDonald, Justin Schuh · 2006
~1200 pages~30 hrs to read
A methodical approach to auditing source code for vulnerabilities, with case studies from real products. It is the reference for judging whether a review actually covered a component.
View book →Application Security Program Handbook
by Derek Fisher · 2022
How to build and measure an application security program: policy, training, tooling and metrics. Read it when your job is to make the program work across many teams.
View book →
Book links go to Amazon and are affiliate links. As an Amazon Associate I earn from qualifying purchases.
Frequently asked questions
Which book should a Application Security Engineer read first?
The Web Application Hacker's Handbook: Finding and Exploiting Security Flaws by Dafydd Stuttard, Marcus Pinto. It is the most complete hands-on guide to the attack classes behind most findings. Work through it with the labs, and write one sentence for each flaw that names its fix.
Do I need to read all 10 books?
No. The list is a menu, not a syllabus. Find your stage (getting started: 2, doing the job: 4, senior and leading: 4), begin with one book (we suggest The Web Application Hacker's Handbook: Finding and Exploiting Security Flaws), then pick the next book by the problem you are facing at work. Come back to the others when the situation they cover arrives.
How long does it take to read these books?
The 8 books with a known page count add up to about 4,780 pages, roughly 120 hours at 1.5 minutes a page. At three hours a week that is about 40 weeks; at six hours a week, about 20. The list is meant to be read over time, one book at a time, not in one run.
Are these books up to date?
They range from 2001 (Security Engineering) to 2022 (Hacking APIs). Older titles are included because they teach principles that have not changed; for tools and platforms, we favor recent editions. Check the edition before you buy.
Related reading
Some links are affiliate links: we earn a small commission if you buy, at no cost to you. It does not change what we list.