Microsoft Corp. pours more money into software security than any other major vendor both because it has to and because it can. Yet for all the investments in security, the number of vulnerabilities discovered in the company's products has increased over the years, prompting questions over whether the company has reached the limits of its ability to debug software.
In an interview with Computerworld , Steve Lipner, senior director of security engineering at Microsoft's Trustworthy Computing Group, refuted that suggestion and insisted that the company's Security Development Lifecycle (SDL) approach is working as it was meant to. He said SDL has reduced the number of flaws in Microsoft's newer products while also making them harder to exploit.
Microsoft has invested a lot in security, but the number of flaws being discovered in its products has only been increasing. Why? There are a couple of things that are going on. Obviously, one of them is that security attacks and the security research environment are changing. Security vulnerabilities are actually worth money to the people who find them, so that intensifies the search for vulnerabilities in the outside world.
The second factor is that the SDL (Security Development Lifecycle) is not just about reducing the number of vulnerabilities but also about reducing the severity of the vulnerabilities through things like address space randomization and non-executable memory. We are making it harder to exploit vulnerabilities especially on the newer products. [But] we haven't yet taken the step of reducing the severity [rating] of vulnerabilities on our newer products even if it is too darn hard to exploit them.
Why haven't you done that? We are very conservative about severity ratings. Actually, I am sort of the guilty party who developed both of the severity rating systems we've used over the last 10 years at Microsoft. We haven't yet done any update to the severity rating system to reflect difficulty of exploitation because we want to be very sure that there isn't some way, somehow, that someone could still write a straightforward exploit and prove us wrong.
Some are suggesting that Microsoft might have reached an inherent limit in its ability to debug software with its SDL process. What's your response? Thirty years ago, I used to believe that you could reach perfection. Now, I don't think you are going to get that perfection. But we still have a lot of things that we are working on internal to Microsoft, internal to the security science team in terms of new techniques, new tools that we can apply to detect chances for vulnerabilities and remove them. The challenge for the science team is to make those techniques robust in the sense of low false-positive rates. There may be a theoretical limit at some point but we are not close to it yet. We are still innovating and we are still devising new techniques that we add to the SDL.
What's the SDL's biggest benefit been for Microsoft? I think the biggest gain has been the reduction in the prevalence of exploitable vulnerabilities [in Microsoft's newer products]. It really is the combination of making the code more secure and making the remaining vulnerabilities harder to exploit because the attack surface has been reduced.
Someone looking at the number of bulletins being issued by Microsoft these days would find it hard to believe that the number of exploitable vulnerabilities has actually been reduced. That is something you can fairly say we ought to do more with. Today, if a vulnerability is present in Windows 7 but is mitigated by address space randomization and data execute protection we are still going to issue a bulletin. Our practice today is not even to reduce the severity [of the vulnerability] based on those mitigations. So you can say we need to do a better job of analyzing the impact of the mitigations, but we are continuing to progress on that
Post new comment