Book
Grokking Web Application Security
Malcolm McDonald
Summary
Malcolm McDonald, a security engineer with two decades across investment banking, startups, and PayPal, wrote this to cover application security end to end without assuming a security background: the browser's sandboxing and same-origin policy, server-side input validation and defense in depth, and a development process that catches security bugs before release. Heavy on illustration, it walks through concrete attacks, cross-site scripting, CSRF, clickjacking, man-in-the-middle and DNS poisoning, authentication and authorization vulnerabilities, and injection attacks, explaining each from the attacker's side before the defense. It closes on incident response and third-party supply-chain risk, treating security as an ongoing practice rather than a checklist run once before launch.
Target Readers
- Developers with no security background who need a working mental model of browser and server-side threats before their first security review
- Teams that handle input validation ad hoc and want a systematic defense-in-depth process instead
- Engineers who understand common vulnerabilities individually but haven't connected them to a development process that prevents them
Tags
Colophon
- Publisher
- Mynavi Publishing
- ISBN
- 978-4-8399-9030-5
- Published
- Jan 2026
- List price
- ¥3,828incl. 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
Taikeiteki ni Manabu Anzen na Web Application no Tsukurikata, 2nd Edition (A Systematic Guide to Building Secure Web Applications)
How Vulnerabilities Arise and How to Counter Them in Practice
Hiroshi Tokumaru
Reason: Once Tokumaru's book has cemented the principles and root fixes, reinforce them with a modern, cross-layer view from browser to server. Widening the scope to supply chain and incident response raises the resolution of your defense.
Next Books
- Recommended
Hacking APIs
Breaking Web Application Programming Interfaces
Corey Ball
Reason: Once the principles of defense are solid, adopt the attacker's view. Learning API vulnerabilities (BOLA/IDOR, etc.) — now the main battleground for SPAs and microservices — from the offensive side lets you work backward to robust API design.
- Related
White Hacker Nyumon, 2nd Edition (An Introduction to Ethical Hacking)
Hiroki Abe
Reason: Once you hold the principles of web defense, widen your scope to attacks across networks and servers. Knowing the attacker's thought process brings insights for active defense that are not confined to the web app alone.