<?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 for ConfigBytes</title>
	<atom:link href="http://www.configbytes.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.configbytes.com</link>
	<description>Configuring it out... one byte at a time...</description>
	<lastBuildDate>Wed, 28 Jul 2010 14:35:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on How to prevent toll fraud on Cisco Gateways. by Ron Staples</title>
		<link>http://www.configbytes.com/2010/07/how-to-prevent-toll-fraud-on-cisco-gateways/comment-page-1/#comment-8</link>
		<dc:creator>Ron Staples</dc:creator>
		<pubDate>Wed, 28 Jul 2010 14:35:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.configbytes.com/?p=859#comment-8</guid>
		<description>Joe thanks for your comment.

You are absolutely correct that a Voice FW would be a better solution, however most &quot;mom and pop shops&quot; or even slight larger offices may not have that option in their  budget.  It&#039;s sad but true that allot of these are poorly misconfigued and throw up onto net with the notion if it works, leave it.  

Security does not become an issue until they are exposed, granted a simple access list will not protect you entirety but it will keep an honest person honest.  Think of putting a lock on a door, if someone really wants to get in they will.  

In summary any major corporation or government agency worth their salt is going have an elaborate security policy in place. Whether is be voice, data or physical.</description>
		<content:encoded><![CDATA[<p>Joe thanks for your comment.</p>
<p>You are absolutely correct that a Voice FW would be a better solution, however most &#8220;mom and pop shops&#8221; or even slight larger offices may not have that option in their  budget.  It&#8217;s sad but true that allot of these are poorly misconfigued and throw up onto net with the notion if it works, leave it.  </p>
<p>Security does not become an issue until they are exposed, granted a simple access list will not protect you entirety but it will keep an honest person honest.  Think of putting a lock on a door, if someone really wants to get in they will.  </p>
<p>In summary any major corporation or government agency worth their salt is going have an elaborate security policy in place. Whether is be voice, data or physical.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to prevent toll fraud on Cisco Gateways. by Joe ODonnell</title>
		<link>http://www.configbytes.com/2010/07/how-to-prevent-toll-fraud-on-cisco-gateways/comment-page-1/#comment-7</link>
		<dc:creator>Joe ODonnell</dc:creator>
		<pubDate>Tue, 27 Jul 2010 16:53:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.configbytes.com/?p=859#comment-7</guid>
		<description>The only way to prevent dial through fraud is to place a SecureLogix Voice FW on the PSTN connection. The issue is that PBX&#039;s, Gateways, VoiceMail systems, IVR,s modems, faxes, Dialers, Call Center Suites of all vintages, makes and models, IP or TDM as well as the carrier do not tell the enterprise what the wireline attributes of the individual calls are. Sure...they have databases but those cannot enforce policy and at best are rarely updated properly. Trust nothing is what we go by. You need attribute identification to build policies that give real time visibility and control into the &quot;PSTN Edge&quot;. We identify attributes such as Call Type(is that a modem, fax, human voice, STU, wideband video, Modem energy etc.  As well as source, destination, time of day, direction, action, etc. Very similar to a packet only FW. Once attributes are collected they can then fill out the various security and enforcement policies(FW, IPS/Fraud prevention, Usage manager, performance Manager, Policy based call recording) Dial through fraud is a multi-billon $ global issue. In some cases is actually tied to funding terrorist activities. We have 15 patents granted in this space and sit on more than 4 million lines. Many marquis enterprises and Federal Agencies depend on us. We are a Cisco Development Parter, A member of the Cisco SmartGrid Ecoystem as well as a feature in their channel programs.</description>
		<content:encoded><![CDATA[<p>The only way to prevent dial through fraud is to place a SecureLogix Voice FW on the PSTN connection. The issue is that PBX&#8217;s, Gateways, VoiceMail systems, IVR,s modems, faxes, Dialers, Call Center Suites of all vintages, makes and models, IP or TDM as well as the carrier do not tell the enterprise what the wireline attributes of the individual calls are. Sure&#8230;they have databases but those cannot enforce policy and at best are rarely updated properly. Trust nothing is what we go by. You need attribute identification to build policies that give real time visibility and control into the &#8220;PSTN Edge&#8221;. We identify attributes such as Call Type(is that a modem, fax, human voice, STU, wideband video, Modem energy etc.  As well as source, destination, time of day, direction, action, etc. Very similar to a packet only FW. Once attributes are collected they can then fill out the various security and enforcement policies(FW, IPS/Fraud prevention, Usage manager, performance Manager, Policy based call recording) Dial through fraud is a multi-billon $ global issue. In some cases is actually tied to funding terrorist activities. We have 15 patents granted in this space and sit on more than 4 million lines. Many marquis enterprises and Federal Agencies depend on us. We are a Cisco Development Parter, A member of the Cisco SmartGrid Ecoystem as well as a feature in their channel programs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ASA 5505 board repair and recovery by Mark Vice</title>
		<link>http://www.configbytes.com/2010/06/asa-5505-board-repair-and-recovery/comment-page-1/#comment-6</link>
		<dc:creator>Mark Vice</dc:creator>
		<pubDate>Sun, 13 Jun 2010 03:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.configbytes.com/?p=756#comment-6</guid>
		<description>I love it!</description>
		<content:encoded><![CDATA[<p>I love it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Last Subnet How2 Doc v3.0 by rstaples</title>
		<link>http://www.configbytes.com/2009/10/the-last-subnet-how2-doc/comment-page-1/#comment-3</link>
		<dc:creator>rstaples</dc:creator>
		<pubDate>Tue, 10 Nov 2009 17:19:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.configbytes.com/?p=37#comment-3</guid>
		<description>Ok The document has been rewritten for easy reading.  I hope that this will be the final version.  I apologize for any confusion.  Thanks to all who have downloaded and commented.   Your input is a valuable commodity and is greatly appreciated.</description>
		<content:encoded><![CDATA[<p>Ok The document has been rewritten for easy reading.  I hope that this will be the final version.  I apologize for any confusion.  Thanks to all who have downloaded and commented.   Your input is a valuable commodity and is greatly appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Last Subnet How2 Doc v3.0 by rstaples</title>
		<link>http://www.configbytes.com/2009/10/the-last-subnet-how2-doc/comment-page-1/#comment-2</link>
		<dc:creator>rstaples</dc:creator>
		<pubDate>Tue, 20 Oct 2009 18:37:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.configbytes.com/?p=37#comment-2</guid>
		<description>Just uploaded another version.  Corrected some minor typo&#039;s and spelling errors.

(I never claim to be an English professor)</description>
		<content:encoded><![CDATA[<p>Just uploaded another version.  Corrected some minor typo&#8217;s and spelling errors.</p>
<p>(I never claim to be an English professor)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
