{"id":1876,"date":"2008-05-29T11:22:00","date_gmt":"2008-05-29T11:22:00","guid":{"rendered":"http:\/\/marcbook.local\/wds\/playground\/cybertrust\/2008\/05\/29\/sdl-training\/"},"modified":"2023-05-15T23:09:05","modified_gmt":"2023-05-16T06:09:05","slug":"sdl-training","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2008\/05\/29\/sdl-training\/","title":{"rendered":"SDL Training"},"content":{"rendered":"
Hi everyone, Shawn Hernan here. Being a security guy is incredibly rewarding because you get to look at virtually any part of a product, from kernel drivers to web services to user education to sales and servicing. You have to do that because a failure in one of those areas can endanger the security of our customers. Microsoft’s SDL process reflects that reality. The process is structured so that you really do have to look at each piece before you can sign off. But sometimes when others want to emulate the success of the SDL, they want to skip steps. They try to boil the SDL down into its component parts, like training, or tooling, or security response. Maybe the most common form of that mistake is training, but you see that same thinking applied to code scanning, security response, and just about every phase of the SDL. “Let’s just train everyone, and all our security problems will go away<\/i>.” If only it were so easy. I’d like to take a few minutes to try to explain why it’s not really that easy from my own experience. <\/font><\/p>\n Have you ever sat in a corporate training? Some are good, some are bad, but did you ever say, “man I can’t wait<\/i> for training today.” What about mandatory training? What about mandatory training in a subject that you really don’t think is your area? What if you had to do it every year, and got harassed if you didn’t do it? What if you were, say, an audio engineer and were dragged into a security class? <\/p>\n <\/font><\/font><\/span><\/p>\n I ran the SDL training program at Microsoft for a long time, and developed and taught a big chunk of the training. I spent hundreds of hours in front of thousands of developers, testers, and program managers. I got some really good reviews (and a few bad ones) on the classes I offered. And I tried to do a lot of things to try to make the trainings interesting. I handed out dozens of fresh peaches in an early class on fuzz testing, for example. <\/span>The room smelled really nice after that, and there are probably still a few people around Microsoft who think of fuzz testing when they see a peach. <\/span><\/font><\/font><\/p>\n But even on my best day, I was under no illusion that the majority of the audience was excited to be there, and I was certain that they weren’t going to go back to their offices and spend weeks applying the lessons from the class, setting aside other <\/i>things that are causing present and immediate problems in favor of something that is far off into the future. <\/p>\n <\/font><\/font><\/span><\/p>\n You have to work at getting people’s attention – especially as it relates to security and privacy. From time to time, I would see people reading their mail in class, and I would point to them and ask them a question. That did not endear me to the audience as much as the peaches, but embarrassment is always fresh and in season. <\/span><\/font><\/span>J<\/span><\/span> <\/p>\n <\/font><\/span><\/font><\/p>\n