<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Oil Change or Culture Change?</title><link>http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.aspx</link><description>Hello all... Dave here. I have worked on security and privacy initiatives at Microsoft for a number of years, but it wasn’t until I came to the Security Engineering group to work on the Security Development Lifecycle that I realized I don’t actually work</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Oil Change or Culture Change</title><link>http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.aspx#3017842</link><pubDate>Fri, 01 Jun 2007 07:10:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3017842</guid><dc:creator>Michael Howard's Web Log</dc:creator><description>&lt;p&gt;Dave Ladd has just posted a very interesting and thought provoking post over on the SDL blog: &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.asp"&gt;http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.asp&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Excellent point on culture change</title><link>http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.aspx#3022631</link><pubDate>Fri, 01 Jun 2007 13:52:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3022631</guid><dc:creator>Rory.Blog</dc:creator><description>&lt;p&gt;The Security Development Lifecycle : Oil Change or Culture Change? Really interesting point here on the Microsoft SDL blog about executive buy-in being critical to getting focus on security. I think that it actually applies to pretty much all security..&lt;/p&gt;
</description></item><item><title>re: Oil Change or Culture Change?</title><link>http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.aspx#3053819</link><pubDate>Sun, 03 Jun 2007 07:05:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3053819</guid><dc:creator>asteingruebl</dc:creator><description>&lt;p&gt;Dave,&lt;/p&gt;
&lt;p&gt;Great entry. &amp;nbsp;I've been thinking about this in my own job and how the vast majority of what I'm doing in building my own program in this area is affecting culture change.&lt;/p&gt;
&lt;p&gt;On the root causes of the problem I think I'll throw in a third and its the general culture of software development vs. software engineering. &amp;nbsp;I wrote a little more about it on my blog:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://securityretentive.blogspot.com/2007/06/more-thoughts-on-training.html"&gt;http://securityretentive.blogspot.com/2007/06/more-thoughts-on-training.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Oil Change or Culture Change?</title><link>http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.aspx#3237799</link><pubDate>Tue, 12 Jun 2007 02:21:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3237799</guid><dc:creator>mattmurphy531</dc:creator><description>&lt;p&gt;Not only does security awareness stop &amp;quot;cold&amp;quot; at the exec level, it's often like hitting a brick wall. &amp;nbsp;To say it stops doesn't do justice to the problem, because when it *does* stop, it can completely derail an otherwise very effective process. &amp;nbsp;If your priority and the CEO's priority conflict, your priority is functionally non-existent.&lt;/p&gt;
</description></item><item><title>MSDN FLASH IRELAND - INTERNATIONAL RESOURCES - 25 June 2007 </title><link>http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.aspx#3520382</link><pubDate>Mon, 25 Jun 2007 17:15:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3520382</guid><dc:creator>MSDN Ireland Blog</dc:creator><description>&lt;p&gt;a {color : #0033CC;} a:link {color: #0033CC;} a:visited.local {color: #0033CC;} a:visited {color : #800080;}&lt;/p&gt;
</description></item><item><title>Microsoft SDL Process – in detail</title><link>http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.aspx#8373347</link><pubDate>Thu, 10 Apr 2008 00:45:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8373347</guid><dc:creator>The Security Development Lifecycle</dc:creator><description>&lt;p&gt;Hello all – Dave here… I am currently at RSA and decided to take a few moments to blog about some updates&lt;/p&gt;
</description></item><item><title> “Walking” with the SDL – Part 2</title><link>http://blogs.msdn.com/sdl/archive/2007/05/31/oil-change-or-culture-change.aspx#8762040</link><pubDate>Mon, 21 Jul 2008 20:01:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8762040</guid><dc:creator>The Security Development Lifecycle</dc:creator><description>&lt;p&gt;Jeremy Dallman here with Part Two in my series on “Walking” with the SDL. In Part One , I provided a&lt;/p&gt;
</description></item></channel></rss>