liveBook · Manning

STRIDE

As explained in Grokking Software Architecture

STRIDE is a threat-modeling framework that classifies security threats as spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege.

STRIDE is a repeatable way to look for security threats while designing a system. Review the architecture before writing code, and use the framework whenever you examine a system diagram. section 11.6

Check the design against six threat categories:

  • Spoofing: could someone impersonate a user or service? section 11.6
  • Tampering: could someone modify data in transit or at rest? section 11.6
  • Repudiation: could someone deny an action because it was not recorded? section 11.6
  • Information disclosure, denial of service, and elevation of privilege. section 11.6

Spot the weak link

A rogue container might impersonate OrderService to send database commands. An attacker might alter an order’s shipping address, or an administrator might delete a table without leaving a record. STRIDE turns these into design questions to investigate before deployment. section 11.6

Figure 11.8 As the Risk Scout, Archie looks past the "Happy Path" to find the hidden cracks where an attacker might try to break the system.

The risk-scout illustration emphasizes looking beyond the happy path for places an attacker could exploit. section 11.6

How Grokking Software Architecture covers it

How deep it goes
Defines threat modeling, names six STRIDE categories, and works through identity, data-change, and audit-log risks with mitigations.
Examples
Uses a rogue container, an altered shipping address, and an unlogged database deletion as threat scenarios.
What you can do after
Evaluate system diagrams against six threat categories during architectural reviews.
How it connects
Connects threat modeling with architectural design and system-diagram reviews.

Also explained in

Compare how 2 books explain STRIDE →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.