// Comparison

Sécurité informatique vs Security Engineering: Which Should You Read?

Two cybersecurity books on Defensive, compared honestly: who each is for, what each does best, and which to read first.

Advanced

4/52013

Principes et méthodes à l'usage des DSI, RSSI et administrateurs

Laurent Bloch, Christophe Wolfhugel

A principles-first treatment of information security for DSI, RSSI and sysadmins — architecture, cryptography, network defence and security policy — from two veteran French practitioners.

Advanced

5/52020

Security Engineering

A Guide to Building Dependable Distributed Systems

Ross Anderson

Ross Anderson's comprehensive textbook on the design of secure systems, covering protocols, access control, side channels, economics of security, and policy.

Read this if

System administrators, architects and RSSI who want the reasoning behind security decisions: why a given architecture, protocol or policy holds or fails. Strong on the systems-and-network engineering view.

Anyone who builds, audits, or governs systems where failure has real-world consequences: banking, healthcare, voting, telecom, defence. The single most important security book ever written, and the rare textbook that improves with each edition.

Skip this if

Beginners wanting a gentle on-ramp, or readers chasing the latest tooling — the book is principles-oriented and predates much of the cloud-native era.

Readers looking for a hands-on tooling guide or a quick certification primer. Anderson works at the systems and policy layer; if you need to learn how to use Burp, this is not it. The 1,200 pages also reward patient readers, not skimmers.

Key takeaways

A rare French book that explains the why of security architecture rather than cataloguing tools.
Aimed squarely at the people who run infrastructure — admins, architects, RSSI — not at red teamers.
Principles age slowly, but check the network and crypto specifics against current cloud and identity practice.

Most production failures are economic and organisational, not cryptographic: incentives shape outcomes far more than primitives.
Threat models from one domain (banking, telecom, military) generalize to the next once you know what to look for, and Anderson is the best in the field at showing you.
Side channels, supply chains, and policy are first-class engineering concerns, not footnotes.

How they compare

We rate Security Engineering higher (5/5 against 4/5 for Sécurité informatique). For most readers, that means Security Engineering is the primary pick and Sécurité informatique is a useful follow-up.

Both books target advanced-level readers, so the choice is about topic, not difficulty.

Sécurité informatique and Security Engineering both cover Defensive, Security Architecture, so reading them in sequence reinforces the same material from different angles.

Keep reading

Sécurité informatique

→ Alternatives to Sécurité informatique → What to read after Sécurité informatique