This might be the best security book I've read. It reads like a suspense novel, but at the same time gives a fairly deep technical overview of how massive 'cyber-crimes' are accomplished. The book's suspense novel conceit is really useful as a way of communicating the concepts. I almost feel like this should be required reading for all developers. It's better than teaching security via endless boring Powerpoint slides. ("The elements of security are STRIDE. [next slide] S - Something. [next slide] T -TakeSecuritySeriously. [next slide] I - InfoSec. [next slide] D - DontGiveOutPassword [next slid] E - EvilHackers...")
The prose in this book is workman-like at best, but that's cos each chapter was written by a domain expert (i.e. a l33t or semi-l33t hacker). You can tell from the level of technical detail that this is the real deal. Surprisingly, though the writing isn't gonna win any awards, it's actually not that bad. Certainly no worse than what you'd see in a Tom Clancy book. This is basically a Tom Clancy novel, but with PHP exploits, nmap console logs, IDA debugger sessions, and other info-sec-porn in place of the usual war-nerdy stats about submarines, missile launchers, Apache gunships, etc.
Only real complaint w/ the book is that it's somewhat outdated. (god infosec moves so fast, I mean this is pre Snowden, pre Stuxnet, pre all the Russian bank robberies / ATM exploits / SWATTING attacks...) But really, most of it is still very applicable today. It's all chillingly plausible, and if anything, history has shown that this book was only scratching the surface of what's possible.