@adamshostack@infosec.exchange
2026-09-24 21:50 UTC
In the second edition, I use the term model in two distinct ways: the first is ‘any representation,’ while the second is a formalized construct with technical properties.
(3/9)
Replies (1)
-
@adamshostack@infosec.exchange 2026-09-24 21:50
Diagrams are easy, fast, and customizable. You can put any shape you want in, you can break rules such as “no data sinks,” you can slap a boundary through the middle of a process, and ain’t no tooling gonna stop you. Models are harder to build: There are questions about the properties that you’re going to compute on later. You can’t fudge as easily. If you want traceability from model to code (or vice versa), you need to spend time connecting the two, and then maintain those connections. If your model breaks the rules, a model checker can warn you, the same way a compiler can (with the same pros and cons). (4/9)