<?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: Why your organization needs to do network auditing</title>
	<atom:link href="http://www.gfi.com/blog/network-auditing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gfi.com/blog/network-auditing/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=network-auditing</link>
	<description>Brought to you by GFI Software</description>
	<lastBuildDate>Fri, 09 Aug 2013 12:13:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Emmanuel Carabott</title>
		<link>http://www.gfi.com/blog/network-auditing/comment-page-1/#comment-29372</link>
		<dc:creator>Emmanuel Carabott</dc:creator>
		<pubDate>Thu, 14 Jul 2011 11:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3299#comment-29372</guid>
		<description><![CDATA[Hi Tana,

I can see such stories happening; most systems are automated nowadays - meaning they don&#039;t require maintenance to work. As such, if you ignore security you&#039;ll end up in situation were administrators leave and new ones are employed, and systems that do not cause any issues get forgotten. 

If existent systems are forgotten I think we can safely assume there is no way such companies will realize why foreign hardware is introduced, be it key loggers or wireless access points. 

A story comes to mind in which a post office suffered a break-in; an investigation found nothing missing, in fact there was an access point added! Investigators then found out this access point was meant to capture transactions and steal financial data.

I cannot stress enough how important it is for an administrator to know exactly what hardware there is on his/her network!]]></description>
		<content:encoded><![CDATA[<p>Hi Tana,</p>
<p>I can see such stories happening; most systems are automated nowadays &#8211; meaning they don&#8217;t require maintenance to work. As such, if you ignore security you&#8217;ll end up in situation were administrators leave and new ones are employed, and systems that do not cause any issues get forgotten. </p>
<p>If existent systems are forgotten I think we can safely assume there is no way such companies will realize why foreign hardware is introduced, be it key loggers or wireless access points. </p>
<p>A story comes to mind in which a post office suffered a break-in; an investigation found nothing missing, in fact there was an access point added! Investigators then found out this access point was meant to capture transactions and steal financial data.</p>
<p>I cannot stress enough how important it is for an administrator to know exactly what hardware there is on his/her network!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tana</title>
		<link>http://www.gfi.com/blog/network-auditing/comment-page-1/#comment-29354</link>
		<dc:creator>Tana</dc:creator>
		<pubDate>Sun, 10 Jul 2011 18:29:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3299#comment-29354</guid>
		<description><![CDATA[In one of the companies I used to work for (but for obvious reasons I won&#039;t name it), some of my colleagues in another office didn&#039;t know they had a server with a particular IP and when a guy from our office asked them to check if the server was down (because obviously it was down at least for us and we can distinguish a dead server from a running one, me thinks), this was such a shock for them because nobody knew where the damned thing was physically located. I suppose that the poor server might have run away from admins like them but since they had hardly ever done an audit, it was hard to tell where the server was hiding. 

I was really shocked by the fact that you can be totally ignorant about the devices in your network but after I spent some more time with the company and saw much more shocking things, this experience didn&#039;t look that shocking any more.]]></description>
		<content:encoded><![CDATA[<p>In one of the companies I used to work for (but for obvious reasons I won&#8217;t name it), some of my colleagues in another office didn&#8217;t know they had a server with a particular IP and when a guy from our office asked them to check if the server was down (because obviously it was down at least for us and we can distinguish a dead server from a running one, me thinks), this was such a shock for them because nobody knew where the damned thing was physically located. I suppose that the poor server might have run away from admins like them but since they had hardly ever done an audit, it was hard to tell where the server was hiding. </p>
<p>I was really shocked by the fact that you can be totally ignorant about the devices in your network but after I spent some more time with the company and saw much more shocking things, this experience didn&#8217;t look that shocking any more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @Furius_Geek</title>
		<link>http://www.gfi.com/blog/network-auditing/comment-page-1/#comment-29225</link>
		<dc:creator>@Furius_Geek</dc:creator>
		<pubDate>Mon, 06 Jun 2011 02:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3299#comment-29225</guid>
		<description><![CDATA[Usually, IT managers / administrators and CTOs are only concerned with software auditing. With so many software vendors increasing their auditing activities, we can&#039;t blame them. However, based on my experience as a network admin for an SME for more than five years, we should also not forget about network auditing. This system encompasses all IT-based management, such as software metering / auditing and license management.

Companies that are looking for more ways to save more financial resources should look into network auditing.]]></description>
		<content:encoded><![CDATA[<p>Usually, IT managers / administrators and CTOs are only concerned with software auditing. With so many software vendors increasing their auditing activities, we can&#8217;t blame them. However, based on my experience as a network admin for an SME for more than five years, we should also not forget about network auditing. This system encompasses all IT-based management, such as software metering / auditing and license management.</p>
<p>Companies that are looking for more ways to save more financial resources should look into network auditing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emmanuel Carabott</title>
		<link>http://www.gfi.com/blog/network-auditing/comment-page-1/#comment-29213</link>
		<dc:creator>Emmanuel Carabott</dc:creator>
		<pubDate>Fri, 03 Jun 2011 09:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3299#comment-29213</guid>
		<description><![CDATA[Thank you both for your kind words, I am glad you liked the article

Regarding monitoring of rogue laptops or other devices that might be connected for a brief time to the network and subsequently disconnected, scheduled base scanning can be a bit tricky as the scheduled scan needs to execute at a time when the rogue device is connected to the network.

However there are options; you could run an scanner that continuously monitors arp traffic and reports new mac addresses or, even though less reliable, you can monitor the dhcp leases.]]></description>
		<content:encoded><![CDATA[<p>Thank you both for your kind words, I am glad you liked the article</p>
<p>Regarding monitoring of rogue laptops or other devices that might be connected for a brief time to the network and subsequently disconnected, scheduled base scanning can be a bit tricky as the scheduled scan needs to execute at a time when the rogue device is connected to the network.</p>
<p>However there are options; you could run an scanner that continuously monitors arp traffic and reports new mac addresses or, even though less reliable, you can monitor the dhcp leases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Essex</title>
		<link>http://www.gfi.com/blog/network-auditing/comment-page-1/#comment-29212</link>
		<dc:creator>Gary Essex</dc:creator>
		<pubDate>Thu, 02 Jun 2011 16:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3299#comment-29212</guid>
		<description><![CDATA[Thanks for a great article. The human element is always the most uncontrollable. Now that laptops, netbooks, smart phones and tablets are becoming so prevalent employees, customers and visitors will always be bring devices onto the premises and they may connect them to the network.

@ Freddie James, I couldn&#039;t agree more about baselines... but I wonder if running the baseline comparison during the week would be better (than on Friday evening) as any rouge laptops etc will most likely be taken away at the weekend.]]></description>
		<content:encoded><![CDATA[<p>Thanks for a great article. The human element is always the most uncontrollable. Now that laptops, netbooks, smart phones and tablets are becoming so prevalent employees, customers and visitors will always be bring devices onto the premises and they may connect them to the network.</p>
<p>@ Freddie James, I couldn&#8217;t agree more about baselines&#8230; but I wonder if running the baseline comparison during the week would be better (than on Friday evening) as any rouge laptops etc will most likely be taken away at the weekend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Freddie James</title>
		<link>http://www.gfi.com/blog/network-auditing/comment-page-1/#comment-29209</link>
		<dc:creator>Freddie James</dc:creator>
		<pubDate>Thu, 02 Jun 2011 06:58:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3299#comment-29209</guid>
		<description><![CDATA[A fantastic point. How can you know how secure your network is if you can&#039;t compare its present incarnation to its initial setting and most secure state. Regular auditing of changes can give an administrator an absolute grip on what needs to be done in order to keep the network tidy and safe. Should be a totally regular practice.]]></description>
		<content:encoded><![CDATA[<p>A fantastic point. How can you know how secure your network is if you can&#8217;t compare its present incarnation to its initial setting and most secure state. Regular auditing of changes can give an administrator an absolute grip on what needs to be done in order to keep the network tidy and safe. Should be a totally regular practice.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: www.gfi.com @ 2013-08-12 14:21:06 by W3 Total Cache --