<?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>Securing Your Infrastructure : organizational</title><link>http://blogs.technet.com/infrastructure_security/archive/tags/organizational/default.aspx</link><description>Tags: organizational</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Start Now</title><link>http://blogs.technet.com/infrastructure_security/archive/2008/01/31/start-now.aspx</link><pubDate>Thu, 31 Jan 2008 22:04:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2804978</guid><dc:creator>chrisr</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/infrastructure_security/comments/2804978.aspx</comments><wfw:commentRss>http://blogs.technet.com/infrastructure_security/commentrss.aspx?PostID=2804978</wfw:commentRss><description>&lt;P&gt;In talking security to various organizations, I often find varying opinions and methods of securing the environment.&amp;nbsp; One thing that does come across in a number of discussions is how security is veiwed.&amp;nbsp; Often security is veiwed a necessary evil that IT people avoid or ignore in the deployment of IT systems.&amp;nbsp; IT people outside the security organization often do not involve security because of the fear of security of stopping a project becasuse of security issue.&amp;nbsp; This thinking is often brought on by the security organization themselves.&amp;nbsp; The security organization views themselves as simply as a approving/disapproving organization.&amp;nbsp; If project does not meet certain published or in some cases unplublished standards, the project is blocked and is sent back to the drawing table.&amp;nbsp;This is a poor way of running security as it builds resistance between the groups and delays projects.&lt;/P&gt;
&lt;P&gt;My view of security has always been one of as enabler which I developed in my years in the military.&amp;nbsp; The "Start Now" title to my blog is how I feel security should be involved in a project.&amp;nbsp; Security should be a core part of the project from inception and every team member needs to take responsibility for developing/deploying a secure system.&amp;nbsp; By involving security from the start, the security team is better understand the project have input into the overall development rather than a simple barrier to pass.&amp;nbsp; Systems deployed with this type of security involvement are much more secure by the simple fact the system is designed as a secure system and not "patched up" at the end to pass the security "test".&lt;/P&gt;
&lt;P&gt;Now that you understand my view of security, my blogs will focus around how to securely build and deploy systems.&lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2804978" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/infrastructure_security/archive/tags/Security/default.aspx">Security</category><category domain="http://blogs.technet.com/infrastructure_security/archive/tags/organizational/default.aspx">organizational</category></item></channel></rss>