Via Chad Loder.Read More Blaming the User
The response to my first Threat Model Thursday was almost uniformly positive. Thank you! I’m going to continue with the series, and have a second one ready. But as I think about how to maximize the value of the series, I want to try something. I want you to read the threat model without me,…Read More Threat Model Thursday: ARM Yourselves!
Eric Ries wrote the excellent book Lean Startup. In a recent interview with Firstround, he talks about how to integrate gatekeeping functions into a lean business. There is a tremendous amount of wisdom in there, and almost all of it applies to security. The core is that the gatekeeper has compassion for the work and…Read More Ries on Gatekeepers
There’s an increasing — and valuable — trend to publish sample threat models. These might be level sets for customers: “we care about these things.” They might be reassurance for customers: “we care about these things.” They might be marketing, they might serve some other purpose. All are fine motives, and whatever the motive, publishing…Read More Threat Model Thursday: Synopsys
I really enjoyed being part of this panel. I felt we had a good mix of experience and some really interesting conversations.Read More Threat Modeling Panel at APPSEC Cali 2018
There’s a long and important blog post from Matt Miller, “Mitigating speculative execution side channel hardware vulnerabilities.” What makes it important is that it’s a model of these flaws, and helps us understand their context and how else they might appear. It’s also nicely organized along threat modeling lines. What can go wrong? There’s a…Read More Speculative Execution Threat Model
Last week, in “Threat Modeling: Citizens Versus Systems,” I wrote: I think that was a right call for the first project, because the secondary data flows are a can of worms, and drawing them would, frankly, look like a can of worms. (and) Many organizations don’t disclose them beyond saying “we share your data to…Read More Citizen Threat Modeling and more data
Recently, we shared a privacy threat model which was centered on the people of Seattle, rather than on the technologies they use. Because of that, we had different scoping decisions than I’ve made previously. I’m working through what those scoping decisions mean. First, we cataloged how data is being gathered. We didn’t get to “what…Read More Threat Modeling: Citizens Versus Systems