<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[[SecurityRatty] tag: merchants]]></title>
    <link>http://securityratty.com/tag/merchants</link>
    <description></description>
    <pubDate>Mon, 23 Jun 2008 20:00:00 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[North America Recap]]></title>
      <link>http://securityratty.com/article/4c2bab97ffef28b37a1841c6d4902b75</link>
      <guid>http://securityratty.com/article/4c2bab97ffef28b37a1841c6d4902b75</guid>
      <description><![CDATA[I was one of the 650 attendees at the recent annual North American PCI Community Meeting . Held at the Omni Champions Gate resort in Orlando, it was great to speak with many of the merchants, banks...]]></description>
      <content:encoded><![CDATA[I was one of the 650 attendees at the recent annual <a href="https://www.pcisecuritystandards.org/pdfs/09-25-08.pdf" target="_blank">North American PCI Community Meeting</a>.  Held at the Omni Champions Gate resort in Orlando, it was great to speak with many of the merchants, banks and service providers in attendance about the challenges they are facing.]]></content:encoded>
      <pubDate>Thu, 09 Oct 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/service providers">service providers</category>
      <category domain="http://securityratty.com/tag/omni champions">omni champions</category>
      <category domain="http://securityratty.com/tag/orlando">orlando</category>
      <category domain="http://securityratty.com/tag/attendance">attendance</category>
      <category domain="http://securityratty.com/tag/challenges">challenges</category>
      <category domain="http://securityratty.com/tag/held">held</category>
      <category domain="http://securityratty.com/tag/attendees">attendees</category>
      <category domain="http://securityratty.com/tag/resort">resort</category>
      <category domain="http://securityratty.com/tag/banks">banks</category>
      <source url="http://www.rsa.com/blog/blog_entry.aspx?id=1363">North America Recap</source>
    </item>
    <item>
      <title><![CDATA["Catch Me, Yes YOU Can": Realized Threats at the Corner Store]]></title>
      <link>http://securityratty.com/article/cfe4e6883d78190bc8fc3d36305bf27f</link>
      <guid>http://securityratty.com/article/cfe4e6883d78190bc8fc3d36305bf27f</guid>
      <description><![CDATA[just returned from the Payment Card Industry's 2008 Members Council Meeting in Orlando, Florida. We had a blast despite the mood being somewhat dampened as a result of the uncertainty of the global...]]></description>
      <content:encoded><![CDATA[ just returned from the <a href="https://www.pcisecuritystandards.org/pdfs/pr_080930_PCIDSSv1-2.pdf" target="_blank">Payment Card Industry's</a> 2008 Members Council Meeting in Orlando, Florida.  We had a blast despite the mood being somewhat dampened as a result of the uncertainty of the global financial markets (heartfelt thanks to those wise souls who've been living outside of their means and taking undue personal and commercial financial risk...).  Anyhew, I met so many interesting people from both merchants and from the card brands like Visa, MasterCard, American Express, Discover & JCB International Co., Ltd.]]></content:encoded>
      <pubDate>Thu, 09 Oct 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/payment card industry">payment card industry</category>
      <category domain="http://securityratty.com/tag/commercial financial risk">commercial financial risk</category>
      <category domain="http://securityratty.com/tag/global financial markets">global financial markets</category>
      <category domain="http://securityratty.com/tag/wise souls">wise souls</category>
      <category domain="http://securityratty.com/tag/card brands">card brands</category>
      <category domain="http://securityratty.com/tag/american express">american express</category>
      <category domain="http://securityratty.com/tag/jcb international">jcb international</category>
      <category domain="http://securityratty.com/tag/undue personal">undue personal</category>
      <category domain="http://securityratty.com/tag/orlando">orlando</category>
      <source url="http://www.rsa.com/blog/blog_entry.aspx?id=1364">"Catch Me, Yes YOU Can": Realized Threats at the Corner Store</source>
    </item>
    <item>
      <title><![CDATA[McIrony: An unexpected response from McAfee]]></title>
      <link>http://securityratty.com/article/b7777c8973f62604f441965769aa7200</link>
      <guid>http://securityratty.com/article/b7777c8973f62604f441965769aa7200</guid>
      <description><![CDATA[Irony: incongruity between what might be expected and what actually occurs

Right before Black Hat, I put together what I believed was a pretty strong arguement against McAfee Secure - Hacker Safe, at...]]></description>
      <content:encoded><![CDATA[Irony: incongruity between what might be expected and what actually occurs.<br /><br />Right before Black Hat, I put together what I believed was a pretty strong  arguement against McAfee Secure - Hacker Safe, at a level heretofore unexplored. I believe it was more damaging than anything I've said to date, and as such, presented potential risk for me. So I ran it by some friends before publishing it. Then a most extraordinary thing happened. I had a long chat with <a href="http://blogs.zdnet.com/security/?p=1668" target="_blank">Nate McFeters</a>, who described an awakening he'd recently experienced. He shared with me the belief that a better approach to potentially negative security research might be to try to create a positive outcome, and worry less about press cycles or exposure, the 15 minutes of fame if you will. He pointed to people like <a href="http://blogs.zdnet.com/security/?p=1030" target="_blank">Mark Dowd</a> as an example of people who conduct crushingly good research, and steer clear of the petty, ego driven  bulls**t. <br />There I sat, repose like the thinking <a href="http://www.downshoredrift.com/photos/uncategorized/thinking_man.gif" target="_blank">man</a>, frozen for minutes. "Nate", I said, "I think you're right." <br />What do I aspire to as an information security professional; more readership or street cred than the next guy, or the respect of my peers for contributing to the greater <a href="http://holisticinfosec.org/content/view/21/31/" target="_blank">good</a>? Attention, press cycles, 15 minutes...it all has its allure, trust me on this. <br />But at the end of the day, I really do want to contribute to the greater good.<br />So I did something different. I sent my findings to McAfee and offered them an opportunity to respond, rather than publish first, ask questions later. <br />Here's the real kicker. <br />They responded.<br />I had a three hour lunch this past Thursday with two gentlemen from McAfee, who flew up from the Bay Area to Seattle to have a face to face with me. This, all by itself, speaks volumes to me. In addition to meeting with Kirk Lawrence, the new Director of Product Management for McAfee Secure, there I sat with, of all people, Joe Pierini, the very guy who has suffered more than his share of abuse, up to and including the <a href="http://pwnie-awards.org/2008/awards.html">Pwnie</a>.  As I have been a direct contributor and participant in heckling Joe, you can imagine our meeting could have been uncomfortable. It was not. <br />I have had expectations of McAfee and Scan Alert that to date have not been met, or my (your) perception has been that they have not been met.<br />This meeting was designed as an opportunity to voice some of these expectations, and see if McAfee, in turn, believed there was any merit to them.<br />Surprisingly, at least as spoken, we weren't all that far apart.<br />While, as a naive idealist, I believe that security should come before conversions, I am also grounded enough of a realize that the most attainable goal can be a marriage of both. This premise frames my expectations of McAfee. <br />Can they not be more of a "thought leader" for all the Ma & Pa websites who rely on McAfee Secure, first for a higher conversion rate, then security?<br />Can they not hold merchants to a higher standard, without alienating them and losing business?<br />Can they not embrace the security research community in a fashion that McAfee, the security community, the merchants, and consumers can all benefit from?<br />Can they not be more transparent in their approach, providing more details and feedback about their methods, their findings, and their vision?<br />I know McAfee Secure - Hacker Safe scans can find vulnerabilities.<br />I know they report the vulnerabilities to merchants.<br />What happens thereafter is where things begin to break down. <br />Can the scan engine be improved to find more vulns? Sure. That's really not that big a deal; technology can always be improved.<br />But, regarding holding merchants to a higher standard; therein is the whole point of this debate. <br />Anyone can throw a badge on a site. <br />But what happens when the site proves vulnerable is the key. I'll be candid here: I don't give a damn about the merchant at that point; it's the consumer who is at risk and needs something better from McAfee and their peers.<br />So, here begins a different approach. I know that making changes at a company the size of McAfee can be likened to the three miles it takes to turn around an aircraft carrier. I'm willing to work with them, and allow for a positive outcome.<br />I have been told that, in two or three weeks, we can expect a published standard, that clearly defines exactly what the McAfee Secure product offering adheres to, inclusive of their expectations for merchant remediation timelines, potential badge downgrades for unresolved vulnerabilities, and hopefully even a more clear stance on XSS.<br />I have been told that I will have the opportunity to discuss this standard, and invite feedback. Any <a href="http://holisticinfosec.org/content/view/19/29/" target="_blank">standard</a> is better than no standard. <br />I have also been told that this is just the beginning of changes that will lead to more of what I have hoped for in my expectations, over the next 6 months or so.<br />I am hopeful that we can take McAfee at their word, and even if slowly, see a positive outcome.<br /><br /><a href="http://del.icio.us/post?url=http://holisticinfosec.blogspot.com/2008/08/mcirony-unexpected-response-from-mcafee.html&title=McIrony:%20An%20unexpected%20response%20from%20McAfee " title="McIrony: An unexpected response from McAfee ">del.icio.us</a> | <a href="http://digg.com/submit?phase=2&amp;url=http://holisticinfosec.blogspot.com/2008/08/mcirony-unexpected-response-from-mcafee.html" title="McIrony: An unexpected response from McAfee ">digg</a>]]></content:encoded>
      <pubDate>Sat, 30 Aug 2008 09:04:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/mcafee">mcafee</category>
      <category domain="http://securityratty.com/tag/mcafee secure">mcafee secure</category>
      <category domain="http://securityratty.com/tag/negative security research">negative security research</category>
      <category domain="http://securityratty.com/tag/research">research</category>
      <category domain="http://securityratty.com/tag/mcafee secure product">mcafee secure product</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/security research community">security research community</category>
      <category domain="http://securityratty.com/tag/information security professional">information security professional</category>
      <category domain="http://securityratty.com/tag/positive outcome">positive outcome</category>
      <source url="http://holisticinfosec.blogspot.com/2008/08/mcirony-unexpected-response-from-mcafee.html">McIrony: An unexpected response from McAfee</source>
    </item>
    <item>
      <title><![CDATA[New security rules on tap for credit-card handlers]]></title>
      <link>http://securityratty.com/article/420bb9340c8954173cc94ee0bca0876e</link>
      <guid>http://securityratty.com/article/420bb9340c8954173cc94ee0bca0876e</guid>
      <description><![CDATA[The PCI Security Standards Council is set to release a revised version of its 12-part Payment Card Industry standard, which tackles systems related to storage and processing of credit and debit cards...]]></description>
      <content:encoded><![CDATA[The PCI Security Standards Council is set to release a revised version of its 12-part Payment Card Industry standard, which tackles systems related to storage and processing of credit and debit cards by merchants and service providers.]]></content:encoded>
      <pubDate>Wed, 27 Aug 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/tackles systems">tackles systems</category>
      <category domain="http://securityratty.com/tag/credit">credit</category>
      <category domain="http://securityratty.com/tag/service providers">service providers</category>
      <category domain="http://securityratty.com/tag/debit cards">debit cards</category>
      <category domain="http://securityratty.com/tag/version">version</category>
      <category domain="http://securityratty.com/tag/release">release</category>
      <category domain="http://securityratty.com/tag/merchants">merchants</category>
      <category domain="http://securityratty.com/tag/storage">storage</category>
      <category domain="http://securityratty.com/tag/set">set</category>
      <source url="http://www.networkworld.com/news/2008/082808-pci-security-standard-revised-version.html?fsrc=rss-security">New security rules on tap for credit-card handlers</source>
    </item>
    <item>
      <title><![CDATA[PCI Compliance: Reaction to the Summary of Changes]]></title>
      <link>http://securityratty.com/article/ddeefb896f6d234b28dddac20a55a9c5</link>
      <guid>http://securityratty.com/article/ddeefb896f6d234b28dddac20a55a9c5</guid>
      <description><![CDATA[On August 18 the PCI Security Standards Council formally announced ( http://www.pcisecuritystandards.org/pdfs/08-18-08 2.pdf ) forthcoming changes to the Payment Card Industry's Data Security Standard...]]></description>
      <content:encoded><![CDATA[On August 18 the PCI Security Standards Council formally announced (<a href="http://www.pcisecuritystandards.org/pdfs/08-18-08_2.pdf" target=_blank>http://www.pcisecuritystandards.org/pdfs/08-18-08_2.pdf</a>) forthcoming changes to the Payment Card Industry's Data Security Standard (PCI DSS) as it moves from version 1.1 to version 1.2 in October 2008.  The release represents the first major update since September 2006.
<P>
What's my take on the summary of changes? <B>Most merchants will be pleased to see that these are relatively minor changes...</b>]]></content:encoded>
      <pubDate>Mon, 18 Aug 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/payment card industry">payment card industry</category>
      <category domain="http://securityratty.com/tag/data security standard">data security standard</category>
      <category domain="http://securityratty.com/tag/release represents">release represents</category>
      <category domain="http://securityratty.com/tag/version">version</category>
      <category domain="http://securityratty.com/tag/pci dss">pci dss</category>
      <category domain="http://securityratty.com/tag/summary">summary</category>
      <category domain="http://securityratty.com/tag/october">october</category>
      <category domain="http://securityratty.com/tag/pdf">pdf</category>
      <category domain="http://securityratty.com/tag/minor">minor</category>
      <source url="http://www.rsa.com/blog/blog_entry.aspx?id=1330">PCI Compliance: Reaction to the Summary of Changes</source>
    </item>
    <item>
      <title><![CDATA[A new version?]]></title>
      <link>http://securityratty.com/article/e612020837731d9520e370baabf4378a</link>
      <guid>http://securityratty.com/article/e612020837731d9520e370baabf4378a</guid>
      <description><![CDATA[Yes folks, the PCI DSS's first major update since version 1.1 was announced in September 2006 is on the horizon. Unveiled in May by the PCI Security Standards Council, the new version, called 1.2, is...]]></description>
      <content:encoded><![CDATA[Yes folks, the PCI DSS's first major update since  version 1.1 was <a href="http://www.pcisecuritystandards.org/pdfs/09-07-06.pdf" target=_blank>announced in September 2006</a> is on the horizon.  <a href="http://www.pcisecuritystandards.org/pdfs/05-14-08.pdf" target=_blank>Unveiled in May</a> by the PCI Security Standards Council, the new version, called 1.2, is due out in October. <B>Over the past few weeks, I've received a myriad of inquiries from merchants and figured this would be a good forum to share some of them...</b>]]></content:encoded>
      <pubDate>Wed, 16 Jul 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/version">version</category>
      <category domain="http://securityratty.com/tag/pci dss">pci dss</category>
      <category domain="http://securityratty.com/tag/due">due</category>
      <category domain="http://securityratty.com/tag/horizon">horizon</category>
      <category domain="http://securityratty.com/tag/october">october</category>
      <category domain="http://securityratty.com/tag/forum">forum</category>
      <category domain="http://securityratty.com/tag/share">share</category>
      <category domain="http://securityratty.com/tag/merchants">merchants</category>
      <category domain="http://securityratty.com/tag/inquiries">inquiries</category>
      <source url="http://www.rsa.com/blog/blog_entry.aspx?id=1309">A new version?</source>
    </item>
    <item>
      <title><![CDATA[Finished? Where should I start?]]></title>
      <link>http://securityratty.com/article/8c822bb96c731d2d889f96c6023f538d</link>
      <guid>http://securityratty.com/article/8c822bb96c731d2d889f96c6023f538d</guid>
      <description><![CDATA[Many of the merchants I speak with are sharply focused on addressing specific PCI security requirements. While implementing the controls needed to meet the requirements is absolutely critical, I can't...]]></description>
      <content:encoded><![CDATA[Many of the merchants I speak with are sharply focused on addressing specific PCI security requirements.  While implementing the controls needed to meet the requirements is absolutely critical, I can't stress enough the importance of taking time to aim before firing. <P>

It's no secret that PCI compliance is focused on securing cardholder data and infrastructure.  Simply put, you can't secure what you don't manage and you can't manage what you don't know about. Before you go looking for all instances of cardholder data, you must be prepared to find more than expected.<P>

Most merchants are aware of the cardholder data in their database(s).  But what about payment applications or payment portals that temporarily store the data? <B>Or customer service reps e-mailing credit card information to confirm or dispute an order?...</b>]]></content:encoded>
      <pubDate>Mon, 30 Jun 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/cardholder data">cardholder data</category>
      <category domain="http://securityratty.com/tag/credit card information">credit card information</category>
      <category domain="http://securityratty.com/tag/customer service reps">customer service reps</category>
      <category domain="http://securityratty.com/tag/pci compliance">pci compliance</category>
      <category domain="http://securityratty.com/tag/payment applications">payment applications</category>
      <category domain="http://securityratty.com/tag/absolutely critical">absolutely critical</category>
      <category domain="http://securityratty.com/tag/temporarily store">temporarily store</category>
      <category domain="http://securityratty.com/tag/payment portals">payment portals</category>
      <source url="http://www.rsa.com/blog/blog_entry.aspx?id=1300">Finished? Where should I start?</source>
    </item>
    <item>
      <title><![CDATA[Montgomery Ward breached, no notification obligation?]]></title>
      <link>http://securityratty.com/article/d0a7010fb8fd83b7750424b96154c42b</link>
      <guid>http://securityratty.com/article/d0a7010fb8fd83b7750424b96154c42b</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/27/08

Organization
Direct Marketing Services Inc

Contractor/Consultant/Branch
Montgomery Ward
HomeVisions.com
SearsHomeCenter.com
SearsShowPlace.com...]]></description>
      <content:encoded><![CDATA[Technorati Tag: <a href="http://technorati.com/tag/security+breach" rel="tag">Security Breach</a><br><br>
<img src="http://breachblog.com/images/95781-88451/wards.jpg" width="200" align="right" height="50"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/27/08<br><br><span style="font-weight: bold;">Organization: </span><br>Direct Marketing Services Inc.<br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.wards.com/wards/default.asp">Montgomery Ward</a> <br><a href="http://www.homevisions.com/hvprod/Default.asp">HomeVisions.com</a> <br><a href="http://www.searshomecenter.com/homecenter/default.asp">SearsHomeCenter.com</a> <br><a href="http://www.searsshowplace.com/showplace/default.asp">SearsShowPlace.com</a> <br><a href="http://www.searsroomforkids.com/roomforkids/default.asp?partner=0">SearsRoomForKids.com</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>"at least 51,000 records"<br><br><span style="font-weight: bold;">Types of Data:</span><br>Names, addresses, phone numbers, card numbers, "security codes", and expiration dates<br><br><span style="font-weight: bold;">Breach Description:</span><br>"NEW YORK (AP) -- The parent company of Montgomery Ward is admitting that it was hit with a credit card hack, but it didn't inform the customers affected."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://ap.google.com/article/ALeqM5hMgFbRpfc74PW0CvbF3kFbWFkHsAD91IJCHG2">The Associated Press</a> <br><a href="http://www.wztv.com/template/inews_wire/wires.national/2c50aedd-www.fox17.com.shtml">The Associated Press via WZTV Channel 17 News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The Associated Press<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>At least 51,000 records were exposed in the breach at the parent company of Montgomery Ward.<br><br>The venerable Wards chain that began in 1872 went out of business in 2001, but in 2004 a catalog company, Direct Marketing Services Inc., bought the brand name out of bankruptcy.<br><br>Direct Marketing Services' CEO, David Milgrom, said the financial company Citigroup detected the computer invasion in December.<br><br>By going through HomeVisions.com, another Direct Marketing Services site, hackers had plundered the database that holds account information for all the company's retail properties.<br><span style="font-style: italic;">[Evan] The AP story names five of the six Direct Marketing Services retail properties (See Above).&nbsp; I don't know what the sixth is.</span><br style="font-style: italic;"><br>It now runs a Wards.com Web site along with six other sites, including three with Sears brands it has acquired: SearsHomeCenter.com, SearsShowplace.com and SearsRoomforKids.com<br><br>Milgrom said Direct Marketing Services immediately informed its payment processor and Visa and MasterCard.<br><br>Direct Marketing Services closely followed a set of guidelines, issued by Visa, on how to respond to a security breach.<br><span style="font-style: italic;">[Evan] This is sad.&nbsp; The Visa documentation regarding breach response is way too narrowly focused to be used as an organizational incident response.&nbsp; Every organization that creates, collects, uses, stores, and/or transfers confidential information should have an incident response policy and accompanying procedures.&nbsp; Take a look at the Visa "</span><a style="font-style: italic;" href="http://usa.visa.com/download/merchants/cisp_what_to_do_if_compromised.pdf?it=r%7C/merchants/risk_management/cisp_if_compromised.html%7CWhat%20to%20Do%20If%20Compromised">What To Do if Compromised</a><span style="font-style: italic;">" procedures, and judge for yourself.</span><br style="font-style: italic;"><br>That included a report to the U.S. Secret Service.<br><br>He said he believed by the end of December that Direct Marketing Services had met its obligations.<br><span style="font-style: italic;">[Evan] Mr. Milgrom is the president of the company.&nbsp; He really thought that his company had met all of its obligations with respect to this breach?&nbsp; It never occurred to him that he should notify customers, even if he weren't required to by law?&nbsp; Not only was the lack of notification illegal, but I think it is also unethical.</span><br style="font-style: italic;"><br>However, those guidelines from Visa are largely technical, and they do not cover a key additional step: that notification laws in nearly every state generally require organizations that have been hacked to come clean to the affected consumers, not just to the financial industry.<br><br>Companies that fail to comply can be hit with fines or be sued by affected customers, depending on the state<br><br>After being asked about those laws by The Associated Press, Milgrom said Direct Marketing Services now plans to contact consumers.<br><br>This hack might have stayed quiet except for online chatter detected in June by Affinion Group Inc.'s CardCops, a group of investigators who track payment-card theft for financial institutions.<br><br>In Internet chat rooms frequented by card thieves, CardCops spotted hackers touting the sale of 200,000 payment cards belonging to one merchant.<br><br>CardCops then intercepted several hundred of the records, along with the online handles belonging to hackers whose real names remain unknown.<br><br>Along with the card numbers, their three-digit "security codes" and expiration dates, the thieves had the cardholders' names, addresses and phone numbers.<br><br>The data had been organized in the same way, indicating the numbers likely came from the same database.<br><br>CardCops' president, Dan Clements, also noticed that the vast majority of the cardholders were women, a clue that the records came from a merchant catering to a certain demographic.<br><br>When he began calling them, the first eight said they had bought things online or through mail order from Montgomery Ward. At that point, Clements realized, "there's a high probability the entire database of Montgomery Ward was breached."<br><span style="font-style: italic;">[Evan] This is some good investigative work.</span><br><br>It is not clear to Clements, though, whether the hackers were inflating their claim when they offered 200,000 records or whether Milgrom's number of 51,000 is accurate.<br><span style="font-style: italic;">[Evan] According to the article, the "hackers" were able to compromise the information from all six Direct Marketing Services, Inc. properties.&nbsp; 51,000 may be Montgomery Wards customer accounts, and the remainder could be from the other five properties (just speculating).</span><br style="font-style: italic;"><br>A spokeswoman for Discover Financial Services LLC, Mai Lee Ua, said her company had addressed the problem by sending new cards to its cardholders who appeared in the compromised records.<br><br>Ua said they weren't told which merchant had been breached<br><br>Visa declined to comment.<br><span style="font-style: italic;">[Evan] Visa always declines to comment.&nbsp; No sense in even seeking one.</span><br><br>MasterCard issued a statement Friday acknowledging it was aware of the breach at Direct Marketing Services, and had notified the banks that issue MasterCards, telling them to monitor the accounts for suspicious charges.<br><span style="font-style: italic;">[Evan] Three different card companies, three entirely different responses.&nbsp; Of the three, I think I like the Discover one the best.</span><br style="font-style: italic;"><br>Such silence was the norm in the industry for years. But in response to fears of identity theft, 44 states have passed laws that generally require organizations holding consumer data to tell people when their information has leaked<br><br>Clements and other security analysts say that despite those laws, many breaches still are kept quiet, judging by the data being hawked in online black markets.<br><br>Avivah Litan, an analyst at Gartner Inc., believes unreported data breaches might still outnumber the ones that do get publicized.<br><span style="font-style: italic;">[Evan] I absolutely agree.&nbsp; You would be naïve to think that victim notifications go out in all breaches.&nbsp; Too many corporate leaders would rather not notify and hope that nobody notices.</span><br style="font-style: italic;"><br>Litan says it especially is the case with online merchants. She believes it happens because of a lack of pressure from credit card companies, which are not responsible for fraudulent charges in "card not present" transactions over the Web and mail order.<br><br>Until fraud actually appears on the card, they'd rather avoid the cost of voiding compromised cards and giving consumers new ones, she said.<br><br>"What it reveals is the convoluted banking system," she said. "If this had taken place at a grocery store, we all would have heard about it."<br><br>In fact, because of the silence that still sometimes follows data breaches, even people who have never been informed one of their records has leaked should assume their information is floating online, Litan said.<br><br>"Probably every one of our cards is up there somewhere now," she said.<br><span style="font-style: italic;">[Evan] I agree with all of the statements made by Avivah Litan except this one.&nbsp; This is a stretch.</span><br><br><span style="font-weight: bold;">On the Net:</span><br>Links to the <a href="http://www.ncsl.org/programs/lis/cip/priv/breachlaws.htm">44 state notification laws</a> <br><br><span style="font-weight: bold;">Commentary:</span><br>Is this a case of a company that was caught trying to cover up a breach, or was this a company that didn't know any better?&nbsp; </font><font size="2">I lean towards the former.&nbsp; </font><font size="2">Either way, is ignorance of the law any kind of valid excuse?&nbsp; <br><br>Let's assume for a second that company really didn't know that they were required to notify victims.&nbsp; If this were true, then this leads me to believe that the company doesn't govern information security well (due care?), probably has no formal information security program, lacks incident response policy and procedures, and doesn't manage risk well.<br><br>I could only guess how the "hack" took place.&nbsp; What vulnerability was exploited?&nbsp; Even in this, the company appears to have not detected the attack.&nbsp; </font><font size="2">Direct Marketing Services, Inc. had to be told of it by Citibank.&nbsp; </font><font size="2">Does this mean that the company did not use intrusion detection/prevention?&nbsp; <br><br>I could go on and on, but in the end I don't have much confidence here. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/27/wards.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Fri, 27 Jun 2008 19:45:03 +0000</pubDate>
      <category domain="http://securityratty.com/tag/card companies">card companies</category>
      <category domain="http://securityratty.com/tag/companies">companies</category>
      <category domain="http://securityratty.com/tag/services">services</category>
      <category domain="http://securityratty.com/tag/services closely">services closely</category>
      <category domain="http://securityratty.com/tag/credit card companies">credit card companies</category>
      <category domain="http://securityratty.com/tag/services retail properties">services retail properties</category>
      <category domain="http://securityratty.com/tag/financial company citigroup">financial company citigroup</category>
      <category domain="http://securityratty.com/tag/company">company</category>
      <category domain="http://securityratty.com/tag/montgomery ward">montgomery ward</category>
      <source url="http://breachblog.com/2008/06/27/wards.aspx">Montgomery Ward breached, no notification obligation?</source>
    </item>
    <item>
      <title><![CDATA[Security Briefing: June 26th]]></title>
      <link>http://securityratty.com/article/20cb5c5674bc648f3e21f47cde22b211</link>
      <guid>http://securityratty.com/article/20cb5c5674bc648f3e21f47cde22b211</guid>
      <description><![CDATA[OK, the database cluster is back up and playing nice after its petulant episode
Click here to subscribe to Liquidmatrix Security Digest
And now, the news
MoD implements new data security measures | PC...]]></description>
      <content:encoded><![CDATA[<p><center><img src='http://www.liquidmatrix.org/blog/wp-content/uploads/2007/09/newspapera.jpg' alt='newspapera.jpg' /></center></p>
<p>OK, the database cluster is back up and playing nice after its petulant episode. </p>
<p>Click here to <a href="http://feeds.feedburner.com/Liquidmatrix">subscribe to Liquidmatrix Security Digest!</a>. </p>
<p>And now, the news&#8230;</p>
<ol>
<li><a href="http://www.pcadvisor.co.uk/news/index.cfm?newsid=13532">MoD implements new data security measures</a> | PC Advisor</li>
<li><a href="http://lifestyle.hexus.net/content/item.php?item=14045">Do natural human traits make us more vulnerable to computer malware?</a> | Hexus</li>
<li><a href="http://www.networkworld.com/news/2008/062408-the-staff-the-thief-the.html">The staff, the thief, the device and its data</a> | Network World</li>
<li><a href="http://www.theaustralian.news.com.au/story/0,25197,23912352-643,00.html">Credit card firms wave stick at retailers</a> | The Australian</li>
<li><a href="http://www.theregister.co.uk/2008/06/24/pci_dss_compliance/">Merchants call credit card industry&#8217;s bluff on compliance</a> | The Register</li>
<li><a href="http://www.wyff4.com/news/16710144/detail.html">Chairman: Computer Hacking &#8216;Much More Widespread&#8217;</a> | WYFF 4</li>
<li><a href="http://www.chron.com/disp/story.mpl/headline/metro/5854484.html">Fired Houston organ bank worker accused of hacking into system</a> | Houston Chronicle</li>
<li><a href="http://www.vnunet.com/vnunet/news/2219820/pci-standard-lacking-secerno">PCI standard &#8216;ignores&#8217; insider threat</a> | vnunet</li>
<li><a href="http://www.stuff.co.nz/4596153a11.html">Student suspended after hacking emails</a> | Stuff NZ</li>
</ol>
<p> Tags: <a href="http://technorati.com/tag/News" rel="tag">News</a>, <a href="http://technorati.com/tag/Daily+Links" rel="tag"> Daily Links</a>, <a href="http://technorati.com/tag/Security+Blog" rel="tag"> Security Blog</a>, <a href="http://technorati.com/tag/Information+Security" rel="tag"> Information Security</a>, <a href="http://technorati.com/tag/Security+News" rel="tag"> Security News</a></p>

<p><a href="http://feeds.feedburner.com/~a/Liquidmatrix?a=wwo5bp"><img src="http://feeds.feedburner.com/~a/Liquidmatrix?i=wwo5bp" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=UaS03I"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=UaS03I" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=zVX34i"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=zVX34i" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=niEgni"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=niEgni" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=EO0ZZi"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=EO0ZZi" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=M1mXdi"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=M1mXdi" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/Liquidmatrix/~4/320513473" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 26 Jun 2008 09:11:27 +0000</pubDate>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/data security measures">data security measures</category>
      <category domain="http://securityratty.com/tag/security news">security news</category>
      <category domain="http://securityratty.com/tag/news">news</category>
      <category domain="http://securityratty.com/tag/natural human traits">natural human traits</category>
      <category domain="http://securityratty.com/tag/computer">computer</category>
      <category domain="http://securityratty.com/tag/computer malware">computer malware</category>
      <category domain="http://securityratty.com/tag/database cluster">database cluster</category>
      <category domain="http://securityratty.com/tag/security blog">security blog</category>
      <source url="http://feeds.feedburner.com/~r/Liquidmatrix/~3/320513473/">Security Briefing: June 26th</source>
    </item>
    <item>
      <title><![CDATA[The "E" word]]></title>
      <link>http://securityratty.com/article/9c24f7bdf82da05d57a6509c3af98480</link>
      <guid>http://securityratty.com/article/9c24f7bdf82da05d57a6509c3af98480</guid>
      <description><![CDATA[I met with a merchant this morning to talk PCI compliance. Like many of the conversations I've had with merchants, things got a bit more interesting when the discussion focused on cardholder data...]]></description>
      <content:encoded><![CDATA[I met with a merchant this morning to talk PCI compliance.  Like many of the conversations I've had with merchants, things got a bit more interesting when the discussion focused on cardholder data protection.
	
They joked that the new rev of the <a href="https://www.pcisecuritystandards.org/pdfs/05-14-08.pdf">PCI Standard, version 1.2</a> -- due out in October -- would eliminate the data protection requirements.  All joking aside, the truth is that data protection isn't going anywhere when it comes to the PCI DSS.  <b>While there are other alternatives, such as hashed indexes, truncation and...</b>]]></content:encoded>
      <pubDate>Mon, 23 Jun 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/data protection">data protection</category>
      <category domain="http://securityratty.com/tag/data protection requirements">data protection requirements</category>
      <category domain="http://securityratty.com/tag/cardholder data protection">cardholder data protection</category>
      <category domain="http://securityratty.com/tag/talk pci compliance">talk pci compliance</category>
      <category domain="http://securityratty.com/tag/pci dss">pci dss</category>
      <category domain="http://securityratty.com/tag/pci standard">pci standard</category>
      <category domain="http://securityratty.com/tag/october">october</category>
      <category domain="http://securityratty.com/tag/bit">bit</category>
      <category domain="http://securityratty.com/tag/merchant">merchant</category>
      <source url="http://www.rsa.com/blog/blog_entry.aspx?id=1294">The "E" word</source>
    </item>
  </channel>
</rss>
