 




<?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: ChoicePoint CISO says breach not an information security issue</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/choicepoint-ciso-says-breach-not-an-information-security-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/choicepoint-ciso-says-breach-not-an-information-security-issue/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 00:24:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: infosafety</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/choicepoint-ciso-says-breach-not-an-information-security-issue/#comment-40248</link>
		<dc:creator>infosafety</dc:creator>
		<pubDate>Tue, 08 Mar 2005 19:10:38 +0000</pubDate>
		<guid isPermaLink="false">#comment-40248</guid>
		<description><![CDATA[This could get even more interesting, as it now involves a class action lawsuit.
http://www.righettilaw.com/cases/case.php?case=Choicepoint

Craig Herberg]]></description>
		<content:encoded><![CDATA[<p>This could get even more interesting, as it now involves a class action lawsuit.<br />
<a href="http://www.righettilaw.com/cases/case.php?case=Choicepoint" rel="nofollow">http://www.righettilaw.com/cases/case.php?case=Choicepoint</a></p>
<p>Craig Herberg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: imaginetsecurity</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/choicepoint-ciso-says-breach-not-an-information-security-issue/#comment-40249</link>
		<dc:creator>imaginetsecurity</dc:creator>
		<pubDate>Fri, 25 Feb 2005 11:26:27 +0000</pubDate>
		<guid isPermaLink="false">#comment-40249</guid>
		<description><![CDATA[This is a procedural breakdown of their entire process, not just as InfoSec is concerned.  A business process had holes in it that were exploited, not a network system or device that was exploited.  The violators came into the system appearing to be legitimate businesses, using social engineering to produce fraudulent business licenses and other documents.  These were not scrutinized well enough to prevent these persons from being given access as if they were any other legitimate customer.  

The CISO is no more culpable than the other executives in the company.  All of them have the responsibility to ensure that their business processes and network systems are protecting against and are frequently audited for just such procedural vulnerabilities.  This is not hacking but a business process and they applied their policies appropriately but we all see now that those policies were inadequate against fraudulent applications.  I am sure that their procedures and policies will be tightened down far more and will include background checks on all applicants, verification of legitimate business licenses and other documents, before a customer is granted access to the information.

Is a bank CIO/CISO responsible for the business procedures of accepting a new checking account application resulting in a fraudulent account that kites checks?  No.  Should that CIO/CISO have input into the processes to prevent social engineering?  Yes.]]></description>
		<content:encoded><![CDATA[<p>This is a procedural breakdown of their entire process, not just as InfoSec is concerned.  A business process had holes in it that were exploited, not a network system or device that was exploited.  The violators came into the system appearing to be legitimate businesses, using social engineering to produce fraudulent business licenses and other documents.  These were not scrutinized well enough to prevent these persons from being given access as if they were any other legitimate customer.  </p>
<p>The CISO is no more culpable than the other executives in the company.  All of them have the responsibility to ensure that their business processes and network systems are protecting against and are frequently audited for just such procedural vulnerabilities.  This is not hacking but a business process and they applied their policies appropriately but we all see now that those policies were inadequate against fraudulent applications.  I am sure that their procedures and policies will be tightened down far more and will include background checks on all applicants, verification of legitimate business licenses and other documents, before a customer is granted access to the information.</p>
<p>Is a bank CIO/CISO responsible for the business procedures of accepting a new checking account application resulting in a fraudulent account that kites checks?  No.  Should that CIO/CISO have input into the processes to prevent social engineering?  Yes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jonboy2001</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/choicepoint-ciso-says-breach-not-an-information-security-issue/#comment-40250</link>
		<dc:creator>jonboy2001</dc:creator>
		<pubDate>Fri, 25 Feb 2005 11:11:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-40250</guid>
		<description><![CDATA[Don&#039;t you think everyone in the organization should bear soome responsibility for fraud -- not just the security team. After all, there&#039;s a human element to securing systems. If people let fraud occur, the best laid policies won&#039;t work. 

I say everyone should back off this guy. People in glass houses shouldn&#039;t throw stones. ]]></description>
		<content:encoded><![CDATA[<p>Don&#8217;t you think everyone in the organization should bear soome responsibility for fraud &#8212; not just the security team. After all, there&#8217;s a human element to securing systems. If people let fraud occur, the best laid policies won&#8217;t work. </p>
<p>I say everyone should back off this guy. People in glass houses shouldn&#8217;t throw stones. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: merlot</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/choicepoint-ciso-says-breach-not-an-information-security-issue/#comment-40251</link>
		<dc:creator>merlot</dc:creator>
		<pubDate>Fri, 25 Feb 2005 10:24:29 +0000</pubDate>
		<guid isPermaLink="false">#comment-40251</guid>
		<description><![CDATA[Sounds like the CISO is whistling past the graveyard.]]></description>
		<content:encoded><![CDATA[<p>Sounds like the CISO is whistling past the graveyard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: infosafety</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/choicepoint-ciso-says-breach-not-an-information-security-issue/#comment-40252</link>
		<dc:creator>infosafety</dc:creator>
		<pubDate>Fri, 25 Feb 2005 08:36:44 +0000</pubDate>
		<guid isPermaLink="false">#comment-40252</guid>
		<description><![CDATA[Information security includes preventing unauthorized and/or inappropriate access.  Perhaps a review of their authorization policies along with a look at what they consider &quot;appropriate&quot; is in order. . .

Craig Herberg]]></description>
		<content:encoded><![CDATA[<p>Information security includes preventing unauthorized and/or inappropriate access.  Perhaps a review of their authorization policies along with a look at what they consider &#8220;appropriate&#8221; is in order. . .</p>
<p>Craig Herberg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sonotsky</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/choicepoint-ciso-says-breach-not-an-information-security-issue/#comment-40253</link>
		<dc:creator>sonotsky</dc:creator>
		<pubDate>Fri, 25 Feb 2005 07:40:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-40253</guid>
		<description><![CDATA[Theft of information from *any* system - paper, electronic, engraved on stone tablets - is a result of poor information security practices.

It&#039;s quite simple:  information - private customer data - was supposed to remain private and protected - there&#039;s the security part.  When the information was allowed outside of the secure environment, that&#039;s failure on InfoSec&#039;s part.

Sounds a lot like someone who knows they&#039;re in deep trouble and trying to spin the facts in order to keep their cushy job.

But that&#039;s just my opinion, and dammit, I&#039;m entitled to it.
]]></description>
		<content:encoded><![CDATA[<p>Theft of information from *any* system &#8211; paper, electronic, engraved on stone tablets &#8211; is a result of poor information security practices.</p>
<p>It&#8217;s quite simple:  information &#8211; private customer data &#8211; was supposed to remain private and protected &#8211; there&#8217;s the security part.  When the information was allowed outside of the secure environment, that&#8217;s failure on InfoSec&#8217;s part.</p>
<p>Sounds a lot like someone who knows they&#8217;re in deep trouble and trying to spin the facts in order to keep their cushy job.</p>
<p>But that&#8217;s just my opinion, and dammit, I&#8217;m entitled to it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.035 seconds using memcached
Object Caching 337/343 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-25 04:35:28 -->