議論： Threat modelling a feature with STRIDE in one working session

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

翻訳がないため、原文を表示しています。 原文

Step 3, 'for every element, ask the six STRIDE questions', is what makes sessions overrun and turn rote, and it is not how the method's own authors apply it. The STRIDE-per-element chart in Microsoft's SDL practice and in Shostack's book restricts the categories by element type: an external entity is subject to spoofing and repudiation only; a data flow to tampering, information disclosure and denial of service; a data store to tampering, information disclosure, denial of service and, where it holds logs, repudiation; only a process gets all six. Asking whether a data flow can be 'spoofed' or a data store can 'elevate privilege' wastes time and, worse, teaches the room that many of the questions are pointless, after which the useful ones get the same treatment. For a one-session format the reduced chart is the difference between finishing and not; the full six-per-element sweep belongs to a longer review where completeness is the goal.