 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Regulatory Reality &#187; network</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/regulatory-compliance/tag/network/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance</link>
	<description>A SearchFinancialSecurity.com blog</description>
	<lastBuildDate>Wed, 06 Mar 2013 17:19:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Credit Card Breaches: The times they need a changin&#8217;</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/credit-card-breaches-the-times-they-need-a-changin/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/credit-card-breaches-the-times-they-need-a-changin/#comments</comments>
		<pubDate>Sun, 29 Jul 2012 18:39:13 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[ATM]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[breach]]></category>
		<category><![CDATA[checking account]]></category>
		<category><![CDATA[community bank]]></category>
		<category><![CDATA[credit]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[cyber security]]></category>
		<category><![CDATA[data security]]></category>
		<category><![CDATA[evidence]]></category>
		<category><![CDATA[financial institutions]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[hacker]]></category>
		<category><![CDATA[hackers]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[id theft]]></category>
		<category><![CDATA[identity theft]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[oversight]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[personally identifiable informaiton]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[security breach]]></category>
		<category><![CDATA[theft]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=945</guid>
		<description><![CDATA[If my blogging about credit card breaches has a bit of a deja vu feel to it you&#8217;re not crazy, I last touched on it less than six months ago.  Sadly I was handed a new update this week in the form of my bank card being cancelled from right out underneath me again.   [...]]]></description>
				<content:encoded><![CDATA[<p>If my blogging about credit card breaches has a bit of a deja vu feel to it you&#8217;re not crazy, I last touched on it less than six months ago.  Sadly I was handed a new update this week in the form of my bank card being cancelled from right out underneath me again.   For those of you keeping score this would be the second time in 2012, a new personal record.</p>
<p>Here&#8217;s the sequence of events:</p>
<p>Wednesday morning I received an email alert from a company I use that my automatic monthly payment was declined.  Knowing full well it wasn&#8217;t a balance issue I assumed correctly that my bank had cancelled the card.  As I travel extensively and rely on the card exclusively I made my way to a local branch later that morning.  Along the way I called into the service center and confirmed my suspicions, that Visa informed the bank that my card was part of a range of numbers that was possibly exposed via a breach.  I asked if it was possible to learn the name of the offending vendor and was told (same as last time) that Visa doesn&#8217;t share that information.  As I am now a two-time victim it&#8217;s easy to spot the trend and hard to ignore the possibility that it might have involved the same vendor both times.  It wound up taking three visits to a branch to straighten me out and actually get a functioning card in my wallet.  The inconvenience is more than benign as I use the card in several places and will now need to make manual, one-off payments with the temporary card while awaiting the permanent card so that I can update the affected accounts.  By the time this is all said and done it will have resulted in my exhausting more than a half day of billable time trying to fix a problem I didn&#8217;t create.</p>
<p>A few things need to change.</p>
<ul>
<li>First, as part of the breach notification the card issuer needs to share with the cardholder the source of said breach.  I&#8217;ve been hit twice in six months, there&#8217;s a better than even chance that it involved the same vendor and/or processor and I deserve to know if that&#8217;s true.</li>
<li>Second, affected cardholders should receive status updates providing details about the breach including the suspected source, the techniques potentially used and a description of any follow-up actions including investigative and (hopefully) criminal prosecution.</li>
<li>Third, issuers need to have a better system in place to address breaches.  The fact that I have to overtly take action in order to replace the card is a joke.  I&#8217;m a billable resource and taking time out to wait to talk to a customer service representative results in loss of income; I&#8217;m being punished twice as a result.  I should have been offered the option to have a card overnighted to me or have been able to receive a card at any teller window and have it activated right there and then (I had to first activate at an ATM before I could use the temporary plastic).  The card replacement process needs to be streamlined.</li>
</ul>
<p>We collectively as an industry and a society need to accept that both identity and card theft is a mainstream occurrence and adjust accordingly.  Legislation is needed to further insulate the victims (like me) from any extended damage or inconvenience and ensure as smooth a process as possible to allow us to continue living our lives.  Because right now I don&#8217;t just feel like a victim, I feel like I&#8217;m being punished for being one and treated like I simply don&#8217;t matter.</p>
<p>Hey Washington, make the industry tell us what&#8217;s going on and to treat the consumers better!</p>
<p>Oh, and PCI Security Standards Council, how&#8217;s that framework working out for you?  I&#8217;m thinking the only one benefiting from your content are the practitioners making money by supporting it.</p>
<p>Seriously, something needs to change.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/credit-card-breaches-the-times-they-need-a-changin/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Should it be this easy to bypass network security?</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/should-it-be-this-easy-to-bypass-network-security/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/should-it-be-this-easy-to-bypass-network-security/#comments</comments>
		<pubDate>Thu, 17 Jun 2010 15:36:07 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[cyber security]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[penetration test]]></category>
		<category><![CDATA[penetration testing]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=398</guid>
		<description><![CDATA[My firm conducts basic penetration tests all the time and this is the sort of thing that would be flagged without much of an effort.  Why haven't they found it yet?  And if I've found it entirely by luck what about the hackers who go hunting for these sort of things? ]]></description>
				<content:encoded><![CDATA[<p>A few weeks back, I went online to pay my cable bill.  There&#8217;s a long story behind the struggles I&#8217;ve had in doing so since becoming a customer, but I&#8217;ll save that for another time.   Part of the longer story, though, involves my bookmarking the sign-on page where I can access my account and make payments.</p>
<p>I clicked on the link and instead of being directed to the desired page was instead routed through to a Websphere Administration panel.</p>
<p>But that&#8217;s not even the best part of the story.</p>
<p>After confirming that in fact I was somehow through their firewall security and at some point along the way into their infrastructure,  I decided to be a good citizen and let them know.  I tried calling their customer support department twice and both times, after being routed through some crazy series of automated menus, wound up being treated as someone who was simply having trouble accessing his online account.  One customer support representative had no clue what I was describing to them and the other one seemed to grasp what I was saying conceptually but didn&#8217;t have a page in his playbook to manage the call and so he defaulted to trying to help me pay my bill.</p>
<p>The funny thing is that once I navigated from their homepage through to the payment page it worked just fine, but if I selected the bookmark it deposited me right back at Websphere Central.  And as of 30 seconds ago it still does.</p>
<p>Now I know that bashing the local cable company is a popular thing to do and has fast become one of our nation&#8217;s favorite pastimes.  But I&#8217;m not so much picking on them as I&#8217;m amazed that they have such an obvious flaw in their network security.  My firm conducts basic penetration tests all the time and this is the sort of thing that would be flagged without much of an effort.  Why haven&#8217;t they found it yet?  And if I&#8217;ve found it entirely by chance what about the hackers who go hunting for these sort of things?  Or have they discovered it and are currently feeding large while it remains available?</p>
<p>It&#8217;s amazing any of us are ever willing to conduct business online, when you get right down to it.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/should-it-be-this-easy-to-bypass-network-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
