<?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"
	>
<channel>
	<title>Comments on: Looks like it&#8217;s a good time to be talking about IM security</title>
	<atom:link href="http://www.mckeay.net/2006/10/31/looks-like-its-a-good-time-to-be-talking-about-im-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mckeay.net/2006/10/31/looks-like-its-a-good-time-to-be-talking-about-im-security/</link>
	<description>The views of one man on security, privacy and anything else that catches his attention</description>
	<pubDate>Sun, 20 Jul 2008 14:15:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: JB</title>
		<link>http://www.mckeay.net/2006/10/31/looks-like-its-a-good-time-to-be-talking-about-im-security/#comment-630</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Thu, 02 Nov 2006 17:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2006/10/31/looks-like-its-a-good-time-to-be-talking-about-im-security/#comment-630</guid>
		<description>We block all forms of IM at our firewalls, using ACLs, URL filtering (for web-based IM), and our IPS signatures.

IM was a tricky beast to lock down, but we finally managed to cover it with all those layers.

My concern with IM was its use as a vector for attack, as well as the ability to transfer sensitive files out of our network to another location.
</description>
		<content:encoded><![CDATA[<p>We block all forms of IM at our firewalls, using ACLs, URL filtering (for web-based IM), and our IPS signatures.</p>
<p>IM was a tricky beast to lock down, but we finally managed to cover it with all those layers.</p>
<p>My concern with IM was its use as a vector for attack, as well as the ability to transfer sensitive files out of our network to another location.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy</title>
		<link>http://www.mckeay.net/2006/10/31/looks-like-its-a-good-time-to-be-talking-about-im-security/#comment-629</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Wed, 01 Nov 2006 13:00:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2006/10/31/looks-like-its-a-good-time-to-be-talking-about-im-security/#comment-629</guid>
		<description>We installed an IRC server internally that employees can use to chat with one another (and fully disclose to them that everything they write is logged).  As for the popular IM services, we block the protocols and known website solutions as well as prevent end users from installing the software in the first place.
</description>
		<content:encoded><![CDATA[<p>We installed an IRC server internally that employees can use to chat with one another (and fully disclose to them that everything they write is logged).  As for the popular IM services, we block the protocols and known website solutions as well as prevent end users from installing the software in the first place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.mckeay.net/2006/10/31/looks-like-its-a-good-time-to-be-talking-about-im-security/#comment-628</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 31 Oct 2006 20:37:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2006/10/31/looks-like-its-a-good-time-to-be-talking-about-im-security/#comment-628</guid>
		<description>(A) We just installed our proxies  earlier this month, but only because our Compliance dept drove the requirement (Rule 17a-4). Past security warnings/requirements were ignored... but atleast we're protected.
</description>
		<content:encoded><![CDATA[<p>(A) We just installed our proxies  earlier this month, but only because our Compliance dept drove the requirement (Rule 17a-4). Past security warnings/requirements were ignored&#8230; but atleast we&#8217;re protected.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.347 seconds -->
