<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: IDS and IPS systems and their effectiveness on reppelling penetration tests</title>
	<link>http://gsandahl.net/2007/11/14/ids-and-ips-systems-and-their-effectiveness-on-penetration-tests/</link>
	<description>Random rants on Defensive Security</description>
	<pubDate>Fri, 04 Jul 2008 14:13:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Intrusion Detection and Prevention as threat centric tools &#124; gsandahl.net</title>
		<link>http://gsandahl.net/2007/11/14/ids-and-ips-systems-and-their-effectiveness-on-penetration-tests/#comment-10037</link>
		<author>Intrusion Detection and Prevention as threat centric tools &#124; gsandahl.net</author>
		<pubDate>Mon, 17 Dec 2007 22:31:14 +0000</pubDate>
		<guid>http://gsandahl.net/2007/11/14/ids-and-ips-systems-and-their-effectiveness-on-penetration-tests/#comment-10037</guid>
		<description>[...] This kind of threat centric approach is what most Intrusion Prevention technologies lack. Common IPS:s functions as authentication systems without the threat centric part; They block individual attacks but passively lets the intruder keep trying until he crafts an exploit that slips through. Good examples are solutions that correlates alerts with vulnerability information of the target (which ISS does) in order to decide what to block. They forget to question whether the activity itself is acceptable. Just because the webserver runs Apache, all attempts at exploiting it as an IIS is ok? Or just because that perticular vulnerability isn&#8217;t present in this version of Apache, the activity is ok? This kind of thinking is, for example, what causes IPS implementation to fail at repelling penetration tests. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This kind of threat centric approach is what most Intrusion Prevention technologies lack. Common IPS:s functions as authentication systems without the threat centric part; They block individual attacks but passively lets the intruder keep trying until he crafts an exploit that slips through. Good examples are solutions that correlates alerts with vulnerability information of the target (which ISS does) in order to decide what to block. They forget to question whether the activity itself is acceptable. Just because the webserver runs Apache, all attempts at exploiting it as an IIS is ok? Or just because that perticular vulnerability isn&#8217;t present in this version of Apache, the activity is ok? This kind of thinking is, for example, what causes IPS implementation to fail at repelling penetration tests. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gsandahl.net &#187; Data Leak Prevention as protection from intentional theft or disclosure?</title>
		<link>http://gsandahl.net/2007/11/14/ids-and-ips-systems-and-their-effectiveness-on-penetration-tests/#comment-9237</link>
		<author>gsandahl.net &#187; Data Leak Prevention as protection from intentional theft or disclosure?</author>
		<pubDate>Wed, 21 Nov 2007 23:52:30 +0000</pubDate>
		<guid>http://gsandahl.net/2007/11/14/ids-and-ips-systems-and-their-effectiveness-on-penetration-tests/#comment-9237</guid>
		<description>[...] The failure to combat these is why some argue that DLP solutions are limited to preventing mistakes, rather than intentional leaks. I suppose issues with credit-card and identity theft is driving companies in investing in these solutions, and the belief that these systems will act as another layer when their intrusion prevention systems fails on them. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The failure to combat these is why some argue that DLP solutions are limited to preventing mistakes, rather than intentional leaks. I suppose issues with credit-card and identity theft is driving companies in investing in these solutions, and the belief that these systems will act as another layer when their intrusion prevention systems fails on them. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gsandahl.net &#187; IPS catch rates as identified by mu Security</title>
		<link>http://gsandahl.net/2007/11/14/ids-and-ips-systems-and-their-effectiveness-on-penetration-tests/#comment-9079</link>
		<author>gsandahl.net &#187; IPS catch rates as identified by mu Security</author>
		<pubDate>Thu, 15 Nov 2007 23:02:55 +0000</pubDate>
		<guid>http://gsandahl.net/2007/11/14/ids-and-ips-systems-and-their-effectiveness-on-penetration-tests/#comment-9079</guid>
		<description>[...] to yesterdays post entitled IDS and IPS systems and their effectiveness on reppelling penetration tests, Network World recently conducted a review of the prevention-ratio from of IPS:s whom are a part of [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] to yesterdays post entitled IDS and IPS systems and their effectiveness on reppelling penetration tests, Network World recently conducted a review of the prevention-ratio from of IPS:s whom are a part of [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
