<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The 8 Reasons to have a written Corporate IT Security Policy</title>
	<atom:link href="http://copiatech.com/the-8-reasons-to-have-a-written-corporate-it-security-policy/feed/" rel="self" type="application/rss+xml" />
	<link>http://copiatech.com/the-8-reasons-to-have-a-written-corporate-it-security-policy/</link>
	<description>Informative research on Anti Virus, Anti Spam, Anti Spyware, Adware and Encryption</description>
	<lastBuildDate>Tue, 18 Mar 2008 02:17:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: CopiaTech IT Security &#187; 76,560,425 Identity records exposed YTD; Where is encryption failing?</title>
		<link>http://copiatech.com/the-8-reasons-to-have-a-written-corporate-it-security-policy/comment-page-1/#comment-55</link>
		<dc:creator>CopiaTech IT Security &#187; 76,560,425 Identity records exposed YTD; Where is encryption failing?</dc:creator>
		<pubDate>Mon, 27 Aug 2007 19:25:27 +0000</pubDate>
		<guid isPermaLink="false">http://copiatech.com/2006/06/29/the-8-reasons-to-have-a-written-corporate-it-security-policy/#comment-55</guid>
		<description>[...] their office. A box is checked that software is purchased, but many do not incorporate into their Corporate Security Policy. Mike Fratto of Network Computing writes that there is a &#8216;lack of compelling business [...]</description>
		<content:encoded><![CDATA[<p>[...] their office. A box is checked that software is purchased, but many do not incorporate into their Corporate Security Policy. Mike Fratto of Network Computing writes that there is a &#8216;lack of compelling business [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
