Welcome to MSDN Blogs Sign in | Join | Help

September 2007 - Posts

So for the past couple of posts , I've been walking through a psychic debugging experience I had over the weekend. As I presented the problem, there were three pieces of information needed to debug the problem. An interface: class IPsychicInterface { Read More...
As I mentioned yesterday , one of the other developers in my group had hit a sticky problem, and he asked me for my opinion on what was going wrong. There were 3 pieces of information that I needed to use to diagnose the problem, I gave you two of them Read More...
Over the weekend, one of the developers in my group sent me some mail - he was seeing one of the registers in his code getting corrupted across a procedure call. He was quite surprised to see this, and asked me for any suggestions. With the help of the Read More...
I wrote this piece up for our group as we entered the most recent round of threat models. I've cleaned it up a bit (removing some Microsoft-specific stuff), and there's stuff that's been talked about before, but the rest of the document is pretty relevant. Read More...
Yesterday I presented my version of the diagrams for Firefox's command line handler and the IE/URLMON's URL handler. To refresh, here they are again: Here's my version of Firefox's diagram: And my version of IE/URLMON's URL handler diagram: As I mentioned Read More...
I've been writing a LOT about threat modeling recently but one of the things I haven't talked about is the practical value of the threat modeling process. Here at Microsoft, we've totally drunk the threat modeling cool-aid. One of Adam Shostak's papers Read More...
It's been a long path, but we're finally at the point where I can finally present the threat model for PlaySound. None of the information in this post is new, all the information is pulled from previous posts. ---------------- PlaySound Threat Model The Read More...
So I've been writing a LOT of posts about the threat modeling process and how one goes about doing the threat model analysis for a component. The one thing I've not talked about is what a threat model actually is . A threat model is a specification, just Read More...
In my last post , I enumerated a bewildering array of threats that the PlaySound API is subject to, today I want to work through the analysis process for each of those threats. To refresh, here's the DFD and the list of threats: Application: External Read More...
I just wanted to take a quick break from threat modeling to point to a video that Valorie passed on to me that's nothing short of remarkable (from the blog of one of my favorite magazines, Mental Floss ): Advanced Tetris Gameplay : The magic happens about Read More...
Finally it's time to think about threat modeling the PlaySound API. Let's go back to the DFD that I included in my earlier post, since everything flows from the DFD. This dataflow diagram contains a number of elements, they are: Application: External Read More...
As I mentioned the other day , we had three huge big realizations as we've been doing more and more threat models. The first (which we've known all along) was that threats are permanent - the threats that apply to the elements of your component don't Read More...
In my last couple of posts , I've talked about the STRIDE categories. As I mentioned, STRIDE provides a convenient classification mechanism for threats, and threat modeling is all about trying to identify the threats to your feature/component/whatever. Read More...
I described the 6 STRIDE categories the other day . In that post, I mentioned that there are "well understood" mitigations for each of the STRIDE categories. Of course this list isn't exhaustive, many of these are obvious, and some don't apply, but when Read More...
As has been mentioned elsewhere , when we're threat modeling at Microsoft we classify threats using the acronym STRIDE. STRIDE stands for "Spoofing", "Tampering", "Repudiation", "Information disclosure", "Denial of service", and "Elevation of privilege". Read More...
 
Page view tracker