<?xml version="1.0" ?>
<rss version="2.0">
	<channel>
		<title>BreakingPoint ATI Blog</title> 
		<link>http://www.breakingpointsystems.com</link> 
		<description>BreakingPoint Blog</description> 
		<webMaster>community@breakingpoint.com</webMaster>
		<generator>http://www.getmura.com</generator>
		<pubDate>Wed, 16 May 2012 20:53:44 -0400</pubDate> 
		<language>en-us</language>

		<item>
			<title>Massive-Scale Simulation &amp; Testing. Anywhere, Anytime.</title>	
			<link>http://www.breakingpointsystems.com/resources/blog/massive-scale-simulation-testing-anywhere-anytime/</link>
			<comments>http://www.breakingpointsystems.com/resources/blog/massive-scale-simulation-testing-anywhere-anytime/#comments</comments>
			<guid isPermaLink="false">27FCC14D-5056-9000-03D2F5703B934589</guid>
			<pubDate>2012-05-10T00:00:00 -0400</pubDate>
			<description><![CDATA[<p>Real-world massive-scale performance and security testing is always evolving, but some things always remain the same. Rack space, in many environments, is at a premium; companies need to perform testing in the field; and government and military organizations need to train cyber warriors all over the world. And yesterday BreakingPoint debuted the world&rsquo;s first 1U device capable of massive-scale performance and security simulation and testing.</p> ]]></description>
			
		</item>
		<item>
			<title>Spring Cleaning: Five Advanced Programming Issues</title>	
			<link>http://www.breakingpointsystems.com/resources/blog/advanced-programming-issues/</link>
			<comments>http://www.breakingpointsystems.com/resources/blog/advanced-programming-issues/#comments</comments>
			<guid isPermaLink="false">F81F21EF-5056-9000-036431393BA8AA03</guid>
			<pubDate>2012-05-07T00:00:00 -0400</pubDate>
			<description><![CDATA[<p>As a programmer, you already know about many programming issues and how to avoid them. But there are some that are more subtle yet every bit as dangerous when hackers are involved. In our roles at BreakingPoint, my colleagues and I get to think about the various problems that our customers have with their networks. We look at problems from multiple sides and help re-create known problems in order to mediate and to prevent bugs from getting into the wild. The ultimate goal is to stop hackers from disrupting networks.

</p> ]]></description>
			
		</item>
		<item>
			<title>Deep Packet Inspection, Viber, and You</title>	
			<link>http://www.breakingpointsystems.com/resources/blog/dpi-viber-testing/</link>
			<comments>http://www.breakingpointsystems.com/resources/blog/dpi-viber-testing/#comments</comments>
			<guid isPermaLink="false">BA0E2068-5056-9000-036EE9D495B70072</guid>
			<pubDate>2012-05-03T00:00:00 -0400</pubDate>
			<description><![CDATA[<p>DPI, or deep packet inspection, is an acronym you have probably heard more than a few times. It is used by a broad range of devices for an equally broad range of applications. For example:</p>
<ul>
	<li>Firewalls employ DPI to detect malicious traffic early, blocking attacks and malware before they ever enter the network. DPI can do this by detecting malformed, protocol-specific packets known to cause crashes or to carry malicious payloads.</li>
	<li>Routers and management hardware use DPI to classify traffic based on its hosts, the protocols used, and potentially fields within protocols. This knowledge allows administrators of large networks to identify and throttle large-bandwidth consumers, among other things.</li>
</ul> ]]></description>
			
		</item>
		<item>
			<title>No Public Exploit Available? No Worries: The Story of CVE-2012-0002</title>	
			<link>http://www.breakingpointsystems.com/resources/blog/no-public-exploit-available-no-worries-the-story-of-cve-2012-0002/</link>
			<comments>http://www.breakingpointsystems.com/resources/blog/no-public-exploit-available-no-worries-the-story-of-cve-2012-0002/#comments</comments>
			<guid isPermaLink="false">56C803B7-5056-9000-0330371617931B60</guid>
			<pubDate>2012-05-01T00:00:00 -0400</pubDate>
			<description><![CDATA[<p>Security professionals, like everyone, can often be misled by equivocation,&nbsp;semantic ambiguities&nbsp;aimed at creating meaningful logic from vague claims. We see these phrases all the time: &ldquo;no public exploit available&rdquo; or &ldquo;there are no known published exploits in circulation.&rdquo; Although worded differently depending on the security feed, these are simply oracular phrases that often lead to the false logic that if no public exploit exists, then nobody is exploiting it in the wild. Yet time and again those very exploits become subjects of late nights or weekends spent at work.</p> ]]></description>
			
		</item>
		<item>
			<title>Ready for DNSSEC?</title>	
			<link>http://www.breakingpointsystems.com/resources/blog/ready-for-dnssec/</link>
			<comments>http://www.breakingpointsystems.com/resources/blog/ready-for-dnssec/#comments</comments>
			<guid isPermaLink="false">58713567-D6F6-BA72-4BA1C1F51833B803</guid>
			<pubDate>2012-03-28T00:00:00 -0400</pubDate>
			<description><![CDATA[<p>Domain Name System Security Extensions (DNSSEC) is a system designed to guarantee the authenticity of data obtained from the domain name system (DNS). It is described by many Requests for Comments (RFCs), including but not limited to RFC 4033 (DNS Security Introduction and Requirements), RFC 4034 (Resource Records for the DNS Security Extensions) and RFC 4035 (Protocol Modifications for the DNS Security Extensions). DNSSEC uses resource records, flags within the DNS header and protocol extensions to make this authentication possible.</p> ]]></description>
			
		</item>
	</channel>
</rss> 
