// What to read next
What to read after Building Secure and Reliable Systems
Where to go after Building Secure and Reliable Systems, picked from our catalog. The next step up from advanced level, weighted toward the topics this book covers.
01 · 2023
Security Chaos Engineering
Kelly Shortridge and Aaron Rinehart on treating security as a property of complex adaptive systems: instead of preventing failure, you continuously simulate it, and design the organization to learn from each result.
Advanced5/5Kelly Shortridge, Aaron Rinehart02 · 2020
Security Engineering
Ross Anderson's comprehensive textbook on the design of secure systems, covering protocols, access control, side channels, economics of security, and policy.
Advanced5/5Ross Anderson03 · 2024
Evasive Malware
Kyle Cucci on the anti-analysis arms race: sandbox detection, anti-debug, anti-VM, packing, and the analyst-side tooling and tradecraft that get past those layers.
Advanced4/5Kyle Cucci04 · 2007
Techniques virales avancées
Specialized follow-up to Filiol's Les virus informatiques. Dives into advanced malicious-code attack techniques and their defensive analysis.
Advanced4/5Éric Filiol05 · 2017
Attacking Network Protocols
James Forshaw, Project Zero veteran, on how to capture, parse, and break protocols from the wire up to the application layer, with a strong focus on building reusable analysis tooling.
Advanced5/5James Forshaw06 · 2009
Les virus informatiques : théorie, pratique et applications
Éric Filiol's reference French-language treatment of computer virology. Formal theory, infection mechanisms, offensive and defensive applications, with academic rigor rare on the topic.
Advanced5/5Éric Filiol07 · 2018
Practical Binary Analysis
Dennis Andriesse on the binary toolchain you can actually script: ELF internals, dynamic taint analysis, symbolic execution and instrumentation with concrete code-along examples.
Advanced5/5Dennis Andriesse08 · 2005
Silence on the Wire
Michal Zalewski's classic on the indirect attack surface: timing channels, protocol-stack fingerprinting, and the often-overlooked side data leaked by every layer of a stack.
Advanced5/5Michal Zalewski