// Comparison
Black Hat GraphQL vs Real-World Cryptography: Which Should You Read?
Two cybersecurity books on AppSec, compared honestly: who each is for, what each does best, and which to read first.
Aleks and Farhi on attacking GraphQL specifically: introspection abuse, batching, depth and complexity attacks, auth flaws, and the differences from REST that make GraphQL pentests their own discipline.
David Wong's hands-on tour of the cryptographic primitives, protocols and pitfalls that show up in actual production systems, with deliberate attention to TLS, Noise, modern AEAD, and post-quantum.
Read this if
Skip this if
Key takeaways
- Disabled introspection is not a security control; the book explains how to enumerate schemas without it and why that matters.
- Batching and aliasing attacks let one HTTP request do many things; classic rate-limit defenses fail unless GraphQL-aware.
- Depth and complexity attacks are the GraphQL equivalent of regex DoS, usually possible, often forgotten, sometimes catastrophic.
- Most crypto vulnerabilities are misuse, not broken primitives; Wong's framing of "what to use, what to avoid" is the cleanest in print.
- TLS 1.3, Noise, and Signal-style protocols compose primitives in patterns engineers should recognise on sight, this book teaches the patterns.
- Post-quantum cryptography is no longer optional reading; the book introduces the lattice and hash-based constructions you'll be deploying within a few years.
How they compare
We rate Real-World Cryptography higher (5/5 against 4/5 for Black Hat GraphQL). For most readers, that means Real-World Cryptography is the primary pick and Black Hat GraphQL is a useful follow-up.
Both books target intermediate-level readers, so the choice is about topic, not difficulty.
Black Hat GraphQL and Real-World Cryptography both cover AppSec, so reading them in sequence reinforces the same material from different angles.
Keep reading
Real-World Cryptography
→ Alternatives to Real-World Cryptography→ What to read after Real-World Cryptography