<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>How to think like a hacker - Scott Culp's 10 Immutable Laws of Security</title><link>http://blogs.technet.com/steve_lamb/archive/2005/01/04/346400.aspx</link><description>Back in the year 2000 Scott Culp published a paper outlining the 10 Immutable Laws of Security . I've restated them here to be concise but strongly encourage you to read the original article as it develops each law to discuss each in turn. If you're new</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: How to think like a hacker - Scott Culp's 10 Immutable Laws of Security</title><link>http://blogs.technet.com/steve_lamb/archive/2005/01/04/346400.aspx#346650</link><pubDate>Wed, 05 Jan 2005 09:57:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:346650</guid><dc:creator>Julien Couvreur</dc:creator><description>Actually, Law #1 doesn't have to be that way.&lt;br&gt;&lt;br&gt;The reason why that law exists is the security model that is used in Unix and Windows: principals and access controls.&lt;br&gt;If each program only got the minimum authority that it needed, it could not do much damage. Also, if you manage to create protected components within a program and each component only gets the authority it needs, you can further improve the granularity level of security.&lt;br&gt;&lt;br&gt;This cannot be done with ACLs, because it becomes un-manageable.&lt;br&gt;Another security model: capability-based security, merges the security aspect into the design. It is authority-driven design.&lt;br&gt;&lt;br&gt;I can send you the draft of a paper I'm writing, that summarizes this approach.&lt;br&gt;More info at &lt;a target="_new" href="http://erights.org"&gt;http://erights.org&lt;/a&gt; (E language).</description></item><item><title>How to secure the Administrator account access to your environment</title><link>http://blogs.technet.com/steve_lamb/archive/2005/01/04/346400.aspx#406854</link><pubDate>Fri, 24 Jun 2005 20:15:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:406854</guid><dc:creator>Steve Lamb's Blog</dc:creator><description>The Administrator Accounts Security Planning Guide&amp;amp;amp;nbsp;has recently been posted to TechNet and hence...</description></item><item><title>Risk, Risk, Risk..do I sound like Steve Lamb yet?&amp;#8230; &amp;laquo; Forward, positively..</title><link>http://blogs.technet.com/steve_lamb/archive/2005/01/04/346400.aspx#3134920</link><pubDate>Fri, 10 Oct 2008 12:06:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3134920</guid><dc:creator>Risk, Risk, Risk..do I sound like Steve Lamb yet?&amp;#8230; &amp;laquo; Forward, positively..</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://thebestbrew.wordpress.com/2008/10/10/risk-risk-riskdo-i-sound-like-steve-lamb-yet/"&gt;http://thebestbrew.wordpress.com/2008/10/10/risk-risk-riskdo-i-sound-like-steve-lamb-yet/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>