<?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: merchant]]></title>
    <link>http://securityratty.com/tag/merchant</link>
    <description></description>
    <pubDate>Sat, 26 Apr 2008 20:22:24 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <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[Housing bill provision rattles privacy, small business groups]]></title>
      <link>http://securityratty.com/article/e9af5c65252322cbec352eff7740d7c3</link>
      <guid>http://securityratty.com/article/e9af5c65252322cbec352eff7740d7c3</guid>
      <description><![CDATA[A provision in a Senate housing bill calls for e-commerce companies and credit card companies to report merchant transactions to the IRS, raising privacy, financial issues for small...]]></description>
      <content:encoded><![CDATA[A provision in a Senate housing bill calls for e-commerce companies and credit card companies to report merchant transactions to the IRS, raising privacy, financial issues for small businesses.
<p><a href="http://feeds.computerworld.com/~a/Computerworld/Security/News?a=d7Kpdf"><img src="http://feeds.computerworld.com/~a/Computerworld/Security/News?i=d7Kpdf" border="0"></img></a></p><img src="http://feeds.computerworld.com/~r/Computerworld/Security/News/~4/320733264" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 26 Jun 2008 09:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/credit card companies">credit card companies</category>
      <category domain="http://securityratty.com/tag/report merchant transactions">report merchant transactions</category>
      <category domain="http://securityratty.com/tag/e-commerce companies">e-commerce companies</category>
      <category domain="http://securityratty.com/tag/provision">provision</category>
      <category domain="http://securityratty.com/tag/bill calls">bill calls</category>
      <category domain="http://securityratty.com/tag/financial issues">financial issues</category>
      <category domain="http://securityratty.com/tag/privacy">privacy</category>
      <category domain="http://securityratty.com/tag/businesses">businesses</category>
      <category domain="http://securityratty.com/tag/irs">irs</category>
      <source url="http://feeds.computerworld.com/~r/Computerworld/Security/News/~3/320733264/article.do">Housing bill provision rattles privacy, small business groups</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>
    <item>
      <title><![CDATA[Security Briefing: June 19th]]></title>
      <link>http://securityratty.com/article/fa3192f343c0f2e64009c0471a05b7d5</link>
      <guid>http://securityratty.com/article/fa3192f343c0f2e64009c0471a05b7d5</guid>
      <description><![CDATA[Making lists of things to remember as I scramble to keep my focus in the face of a lack of sleep. Next thing you know Ill be putting sticky notes on things. Coffee cup, Door, Advil and C-61 / bad...]]></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>Making lists of things to remember as I scramble to keep my focus in the face of a lack of sleep. Next thing you know I&#8217;ll be putting sticky notes on things. &#8220;Coffee cup&#8221;, &#8220;Door&#8221;, &#8220;Advil&#8221; and &#8220;C-61 / bad joke&#8221;. </p>
<p>You get the idea. </p>
<p>Click here to <a href="http://feeds.feedburner.com/Liquidmatrix">subscribe to Liquidmatrix Security Digest!</a>. Welcome to the new subscribers who joined us yesterday! Thanks!</p>
<p>And now, the news&#8230;</p>
<ol>
<li><a href="http://www.michaelgeist.ca/content/view/3026/159/">Copyright Bill&#8217;s Fine Print Makes For a Disturbing Read</a> | Michael Geist</li>
<li><a href="http://www.michaelgeist.ca/content/view/3046/125/">A Week in the Life of the Canadian DMCA: Part Two</a> | Michael Geist</li>
<li><a href="http://mangsbatpage.433rd.com/2008/06/dmc-eh-why-canadas-new-copyright-law-is.html">DMC-eh? Why Canada&#8217;s new Copyright law is a mistake</a> | Mang Bat</li>
<li><a href="http://www.npr.org/templates/story/story.php?storyId=91666556">E-Mail: To Encrypt or Not to Encrypt?</a> | NPR</li>
<li><a href="http://www.information-age.com/home/information-age-today/442761/hazel-blearss-stolen-laptop-was-not-encrypted.thtml">Hazel Blears&#8217;s stolen laptop was not encrypted</a> | Information Age</li>
<li><a href="http://www.darkreading.com/document.asp?doc_id=156738&amp;WT.svl=news2_1">Encryption: DLP&#8217;s Newest Ingredient</a> | Dark Reading</li>
<li><a href="http://www.rttnews.com/ArticleView.aspx?Id=634888&amp;SMap=1">Merchant Securities&#8217; stock broking firm fined for poor data security procedures</a> | RTT News</li>
<li><a href="http://cjonline.com/stories/061908/sta_292615657.shtml">State computers headed for sale had private information</a> | The Topeka Capital-Journal</li>
<li><a href="http://www.chron.com/disp/story.mpl/business/5845396.html">Fed slammed over internal controls</a> | Houston Chronicle</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=lW77MW"><img src="http://feeds.feedburner.com/~a/Liquidmatrix?i=lW77MW" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=4343GI"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=4343GI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=sXYPoi"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=sXYPoi" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=hC7jki"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=hC7jki" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=8poX7i"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=8poX7i" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=wufmoi"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=wufmoi" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/Liquidmatrix/~4/315350553" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 19 Jun 2008 07:17:24 +0000</pubDate>
      <category domain="http://securityratty.com/tag/rtt news">rtt news</category>
      <category domain="http://securityratty.com/tag/news">news</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/michael geist">michael geist</category>
      <category domain="http://securityratty.com/tag/security news">security news</category>
      <category domain="http://securityratty.com/tag/merchant securities stock">merchant securities stock</category>
      <category domain="http://securityratty.com/tag/information age">information age</category>
      <category domain="http://securityratty.com/tag/topeka capital-journal">topeka capital-journal</category>
      <source url="http://feeds.feedburner.com/~r/Liquidmatrix/~3/315350553/">Security Briefing: June 19th</source>
    </item>
    <item>
      <title><![CDATA[Altman Weil online store compromised]]></title>
      <link>http://securityratty.com/article/ea938b50d0e97fc94b9bb9b82e2b551b</link>
      <guid>http://securityratty.com/article/ea938b50d0e97fc94b9bb9b82e2b551b</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
5/27/08

Organization
Altman Weil, Inc

Contractor/Consultant/Branch
Unnamed web hosting vendor

Victims
Customers

Number Affected
Unknown

21 Maryland...]]></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/altman.jpg" align="right" height="55" width="200"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>5/27/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.altmanweil.com/">Altman Weil, Inc.</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>Unnamed web hosting vendor<br><br><span style="font-weight: bold;">Victims:</span><br>Customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown*<br><br><font size="1">*21 Maryland residents were affected</font><br><br><span style="font-weight: bold;">Types of Data:</span><br>"credit card information"<br><br><span style="font-weight: bold;">Breach Description:</span><br>On May 16, 2008, Altman Weil was notified by the company that hosts their on-line web store that credit card information belonging to Altman Weil customers was compromised through a "SQL virus" attack.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.oag.state.md.us/idtheft/Breach%20Notices/ITU-153059.pdf">Maryland State Attorney General breach notification</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The Maryland State Attorney General<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above:<br><br>On May 16, 2008, we were advised by the company that hosts our On-line Store website that an external virus (known as the SQL virus) access their server and may have attacked the credit card information of certain Altman Weil customers.<br><span style="font-style: italic;">[Evan] What is "the SQL virus"? Is this referring to an attack like that in this story "</span><a style="font-style: italic;" href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9080580">Huge Web hack attack infects 500,000 pages</a><span style="font-style: italic;">", an attack like the </span><a style="font-style: italic;" href="http://www.microsoft.com/technet/security/alerts/slammer.mspx">Slammer</a><span style="font-style: italic;"> worm (some would argue that this is the true "SQL virus") or just poor coding that led to a simple SQL injection attack?</span><br><br>Upon learning of this unauthorized breach and attack, on that same day, Altman Weil immediately authorized the hosting company to shut the site down so that access is no longer possible.<br><br>We were told by the hosting company that the server on which the On-line Store resider was password protected and had current firewalls and security protection, by we understand that the SQL virus may nonetheless have accessed credit card information<br><span style="font-style: italic;">[Evan] I doubt that the password protection or "current firewalls and security protection" would have had much effect against poor coding or missing patches.&nbsp; The term "current firewalls and security protection" is pretty subjective, so I can only speculate.</span><br><br>We are actively investigating this attack and are also addressing this incident to fully determine the extent to which credit card information of our customers may have been accessed.<br><br>We are looking for any help that your office or other state and/or federal agencies might be able to provide in assisting us to identify and pursue those responsible for this attack.<br><span style="font-style: italic;">[Evan] This is an interesting request.&nbsp; I think this is the first time that I have read where a company asks for assistance from the Attorney General.</span><br><br>Here are the steps we have taken to date, we:<br><br></font><ol><li><font size="2">On May 16, 2008, notified the Merchant Bank, Bryn Mawr Trust of the potential security breach</font></li><li>On May 16, 2008, learned that Bryn Mawr Trust outsources the actual credit card functions of the Merchant Bank to TransFirst.</li><li>On May 16, 2008, contacted TransFirst and notified it of the potential security breach and was informed that it would notify the three credit card companies, Visa, MasterCard and American Express.</li><li>On May 16, 2008, Altman Weil independently notified Visa, MasterCard, and American Express of the potential security breach.</li><li>On Saturday, May 24, 2008, notified all card holders whose cards were current (i.e. the expiration dates had not kicked in yet) by telephone calls placed.</li><li>Notified all card holders by letter of the situation and the possible risk</li><li>Notified the following law enforcement agencies:</li></ol><ol type="a"><li>Local police department located in Newton Square, Pennsylvania, where Altman Weil is located on May 23, 2008.</li><li>Secret Service's ECTF and Electronic Crimes Working Group on May 24, 2008.</li><li>Every state Attorney General in the states where potentially affected cardholders reside on May 27, 2008.</li><li>Federal Trade Commission on May 27, 2008.</li><li>Office of Thrift Supervision on May 27, 2008.</li><li>Office of the Comptroller of the Currency on May 27, 2008.</li><li>Federal Deposit Insurance Corporation on May 27, 2008.</li><li>Board of Governors of the Federal Reserve System on May 27, 2008</li></ol><ol start="8"><li>Assured that the hosting company has preserved logs and electronic evidence, has logged all actions taken, and has not altered or compromised the systems.</li><li>Retained forensic auditors at are [sic] own expense to undertake a thorough technical investigation of the cause and extent of the breach.</li><li>Committed to be back in touch with those customers who might be at risk with further information, once we have it.<br></li></ol><font size="2"><span style="font-style: italic;">[Evan] Whether I agree with the steps taken or not, I do appreciate the candid response.&nbsp; Without being close to the incident, it seems like Altman Weil did a good job.&nbsp; I presume from the structure that Altman Weil either has incident response procedures or they received good advice.</span><br style="font-style: italic;"><br>For more information contact Joann Miller, at Altman Weil, Inc. at 610-886-2006, or via email at: jamiller@altmanweil.com<br><br><b>Commentary:</b><br>This is an interesting breach although we are not really clear of the details due to the terminology used in the notification. <br><br><b>Past Breaches:</b><br>Unknown</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/16/altman.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Mon, 16 Jun 2008 11:27:28 +0000</pubDate>
      <category domain="http://securityratty.com/tag/altman weil">altman weil</category>
      <category domain="http://securityratty.com/tag/breach description">breach description</category>
      <category domain="http://securityratty.com/tag/breach">breach</category>
      <category domain="http://securityratty.com/tag/security breach">security breach</category>
      <category domain="http://securityratty.com/tag/altman weil immediately">altman weil immediately</category>
      <category domain="http://securityratty.com/tag/altman weil customers">altman weil customers</category>
      <category domain="http://securityratty.com/tag/credit card information">credit card information</category>
      <category domain="http://securityratty.com/tag/potential security breach">potential security breach</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <source url="http://breachblog.com/2008/06/16/altman.aspx">Altman Weil online store compromised</source>
    </item>
    <item>
      <title><![CDATA[Identity Management, Privacy, and Price Discrimination]]></title>
      <link>http://securityratty.com/article/ed9a5757e5816fc6433c9c57e4282201</link>
      <guid>http://securityratty.com/article/ed9a5757e5816fc6433c9c57e4282201</guid>
      <description><![CDATA[In the economics literature, privacy is usually discussed in the context of consumers' preferences and price discrimination: merchants are interested in finding out a consumer's preferences, because...]]></description>
      <content:encoded><![CDATA[In the economics literature, privacy is usually discussed in the context of consumers' preferences and price discrimination: merchants are interested in finding out a consumer's preferences, because from the latter they can infer the consumer's maximum willingness to pay for a good. However, economists also acknowledge that consumer privacy is not just about hiding the price you may pay for a good: during any economic transaction a consumer may rationally want to share with a merchant certain types of personal data while keeping others private. Identity management systems can support such selective information revelation strategies, allowing for economic transactions in which some level of information sharing is accompanied by some level of information hiding. In this paper we discuss what forms of privacy of personal data are compatible with merchants' interests in knowing more about their consumers and their preferences, and examine several ways in which identity management systems can protect certain types of information privacy while simultaneously enabling personalization and price discrimination.<br style="clear: both;"/>
      <a href="http://www.pheedo.com/click.phdo?s=d4befbae4ff080f49ae0cee434ffd06a"><img alt="" style="border: 0;" border="0" src="http://www.pheedo.com/img.phdo?s=d4befbae4ff080f49ae0cee434ffd06a"/></a>
  <img src="http://www.pheedo.com/feeds/tracker.php?i=d4befbae4ff080f49ae0cee434ffd06a" style="display: none;" border="0" height="1" width="1" alt=""/>]]></content:encoded>
      <pubDate>Thu, 22 May 2008 02:22:47 +0000</pubDate>
      <category domain="http://securityratty.com/tag/privacy">privacy</category>
      <category domain="http://securityratty.com/tag/price discrimination">price discrimination</category>
      <category domain="http://securityratty.com/tag/price">price</category>
      <category domain="http://securityratty.com/tag/information privacy">information privacy</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/consumer privacy">consumer privacy</category>
      <category domain="http://securityratty.com/tag/consumer">consumer</category>
      <category domain="http://securityratty.com/tag/identity management systems">identity management systems</category>
      <category domain="http://securityratty.com/tag/personal data">personal data</category>
      <source url="http://www.pheedo.com/click.phdo?i=d4befbae4ff080f49ae0cee434ffd06a">Identity Management, Privacy, and Price Discrimination</source>
    </item>
    <item>
      <title><![CDATA[Our Data, Ourselves]]></title>
      <link>http://securityratty.com/article/ef8c59c4320face3b8fee7b64a26bbdd</link>
      <guid>http://securityratty.com/article/ef8c59c4320face3b8fee7b64a26bbdd</guid>
      <description><![CDATA[In the information age, we all have a data shadow
We leave data everywhere we go. It's not just our bank accounts and stock portfolios, or our itemized bills, listing every credit card purchase and...]]></description>
      <content:encoded><![CDATA[<p>In the information age, we all have a data shadow. </p>

<p>We leave data everywhere we go. It's not just our bank accounts and stock portfolios, or our itemized bills, listing every credit card purchase and telephone call we make. It's automatic road-toll collection systems, supermarket affinity cards, ATMs and so on. </p>

<p>It's also our lives. Our love letters and friendly chat. Our personal e-mails and SMS messages. Our business plans, strategies and offhand conversations. Our political leanings and positions. And this is just the data we interact with. We all have shadow selves living in the data banks of hundreds of corporations' information brokers -- information about us that is both surprisingly personal and uncannily complete -- except for the errors that you can neither see nor correct. </p>

<p>What happens to our data happens to ourselves. </p>

<p>This shadow self doesn't just sit there: It's constantly touched. It's examined and judged. When we apply for a bank loan, it's our data that determines whether or not we get it. When we try to board an airplane, it's our data that determines how thoroughly we get searched -- or whether we get to board at all. If the government wants to investigate us, they're more likely to go through our data than they are to search our homes; for a lot of that data, they don't even need a warrant. </p>

<p>Who controls our data controls our lives. </p>

<p>It's true. Whoever controls our data can decide whether we can get a bank loan, on an airplane or into a country. Or what sort of discount we get from a merchant, or even how we're treated by customer support. A potential employer can, illegally in the U.S., examine our medical data and decide whether or not to offer us a job. The police can mine our data and decide whether or not we're a terrorist risk. If a criminal can get hold of enough of our data, he can open credit cards in our names, siphon money out of our investment accounts, even sell our property. Identity theft is the ultimate proof that control of our data means control of our life. </p>

<p>We need to take back our data. </p>

<p>Our data is a part of us. It's intimate and personal, and we have basic rights to it. It should be protected from unwanted touch. </p>

<p>We need a comprehensive data privacy law. This law should protect all information about us, and not be limited merely to financial or health information. It should limit others' ability to buy and sell our information without our knowledge and consent. It should allow us to see information about us held by others, and correct any inaccuracies we find. It should prevent the government from going after our information without judicial oversight. It should enforce data deletion, and limit data collection, where necessary. And we need more than token penalties for deliberate violations. </p>

<p>This is a tall order, and it will take years for us to get there. It's easy to do nothing and let the market take over. But as we see with things like grocery store club cards and click-through privacy policies on websites, most people either don't realize the extent their privacy is being violated or don't have any real choice. And businesses, of course, are more than happy to collect, buy, and sell our most intimate information. But the long-term effects of this on society are toxic; we give up control of ourselves.</p>

<p>This essay originally <a href="http://www.wired.com/politics/security/commentary/securitymatters/2008/05/securitymatters_0515">appeared</a> on Wired.com.</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=tqZPqH"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=tqZPqH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=EwZH3H"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=EwZH3H" border="0"></img></a>
</div>]]></content:encoded>
      <pubDate>Tue, 20 May 2008 09:10:55 +0000</pubDate>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/medical data">medical data</category>
      <category domain="http://securityratty.com/tag/enforce data deletion">enforce data deletion</category>
      <category domain="http://securityratty.com/tag/data shadow">data shadow</category>
      <category domain="http://securityratty.com/tag/limit data collection">limit data collection</category>
      <category domain="http://securityratty.com/tag/limit">limit</category>
      <category domain="http://securityratty.com/tag/data banks">data banks</category>
      <category domain="http://securityratty.com/tag/data controls">data controls</category>
      <category domain="http://securityratty.com/tag/information brokers">information brokers</category>
      <source url="http://www.schneier.com/blog/archives/2008/05/our_data_oursel.html">Our Data, Ourselves</source>
    </item>
    <item>
      <title><![CDATA[Our Data, Ourselves]]></title>
      <link>http://securityratty.com/article/256818069fd9ea50feeed730872906b9</link>
      <guid>http://securityratty.com/article/256818069fd9ea50feeed730872906b9</guid>
      <description><![CDATA[In the information age, we all have a data shadow
We leave data everywhere we go. It's not just our bank accounts and stock portfolios, or our itemized bills, listing every credit card purchase and...]]></description>
      <content:encoded><![CDATA[<p>
In the information age, we all have a data shadow.
</p>

<p>
We leave data everywhere we go. It's not just our bank accounts and stock portfolios, or our itemized bills, listing every credit card purchase and telephone call we make. It's automatic road-toll collection systems, supermarket affinity cards, ATMs and so on.
</p>

<p>
It's also our lives. Our love letters and friendly chat. Our personal e-mails and SMS messages. Our business plans, strategies and offhand conversations. Our political leanings and positions. And this is just the data we interact with. We all have shadow selves living in the data banks of hundreds of corporations' information brokers -- information about us that is both surprisingly personal and uncannily complete -- except for the errors that you can neither see nor correct.
</p>

<p>
What happens to our data happens to ourselves. 
</p>

<p>
This shadow self doesn't just sit there: It's constantly touched. It's examined and judged. When we apply for a bank loan, it's our data that determines whether or not we get it. When we try to board an airplane, it's our data that determines how thoroughly we get searched -- or whether we get to board at all. If the government wants to investigate us, they're more likely to go through our data than they are to search our homes; for a lot of that data, they don't even need a warrant.
</p>

<p>
Who controls our data controls our lives. 
</p>

<p>
It's true. Whoever controls our data can decide whether we can get a bank loan, on an airplane or into a country. Or what sort of discount we get from a merchant, or even how we're treated by customer support. A potential employer can, illegally in the U.S., examine our medical data and decide whether or not to offer us a job. The police can mine our data and decide whether or not we're a terrorist risk. If a criminal can get hold of enough of our data, he can open credit cards in our names, siphon money out of our investment accounts, even sell our property. Identity theft is the ultimate proof that control of our data means control of our life.
</p>

<p>
We need to take back our data.
</p>

<p>
Our data is a part of us. It's intimate and personal, and we have basic rights to it. It should be protected from unwanted touch. 
</p>

<p>
We need a comprehensive data privacy law. This law should protect all information about us, and not be limited merely to financial or health information. It should limit others' ability to buy and sell our information without our knowledge and consent. It should allow us to see information about us held by others, and correct any inaccuracies we find. It should prevent the government from going after our information without judicial oversight. It should enforce data deletion, and limit data collection, where necessary. And we need more than token penalties for deliberate violations.
</p>

<p>
This is a tall order, and it will take years for us to get there. It's easy to do nothing and let the market take over. But as we see with things like grocery store club cards and click-through privacy policies on websites, most people either don't realize the extent their privacy is being violated or don't have any real choice. And businesses, of course, are more than happy to collect, buy, and sell our most intimate information. But the long-term effects of this on society are toxic; we give up control of ourselves.
</p>
<p>
---
</p>
<p><cite>Bruce Schneier is Chief Security Technology Officer of BT, and author of </cite>Beyond Fear: Thinking Sensibly About Security in an Uncertain World<cite>.</cite>
</p><br style="clear: both;"/>
  <img alt="" style="border: 0; height:1px; width:1px;" border="0" src="http://www.pheedo.com/img.phdo?i=ce9167dfefe07eed4c03f59aaffb4bfc" height="1" width="1"/>
<img src="http://www.pheedo.com/feeds/tracker.php?i=ce9167dfefe07eed4c03f59aaffb4bfc" style="display: none;" border="0" height="1" width="1" alt=""/><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=kq7mhH"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=kq7mhH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=4Y4Vxh"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=4Y4Vxh" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=AFBTch"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=AFBTch" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=z1519H"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=z1519H" border="0"></img></a>
 <a href="http://feeds.wired.com/~f/wired/politics/security?a=UKA8xH"><img src="http://feeds.wired.com/~f/wired/politics/security?i=UKA8xH" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=Ge6U0h"><img src="http://feeds.wired.com/~f/wired/politics/security?i=Ge6U0h" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=TTzLlh"><img src="http://feeds.wired.com/~f/wired/politics/security?i=TTzLlh" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=jtHJ4H"><img src="http://feeds.wired.com/~f/wired/politics/security?i=jtHJ4H" border="0"></img></a> </div><img src="http://feeds.feedburner.com/~r/wired/politics/privacy/~4/291130235" height="1" width="1"/><img src="http://feeds.wired.com/~r/wired/politics/security/~4/291130242" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 15 May 2008 14:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/medical data">medical data</category>
      <category domain="http://securityratty.com/tag/enforce data deletion">enforce data deletion</category>
      <category domain="http://securityratty.com/tag/data shadow">data shadow</category>
      <category domain="http://securityratty.com/tag/limit data collection">limit data collection</category>
      <category domain="http://securityratty.com/tag/limit">limit</category>
      <category domain="http://securityratty.com/tag/data banks">data banks</category>
      <category domain="http://securityratty.com/tag/data controls">data controls</category>
      <category domain="http://securityratty.com/tag/information brokers">information brokers</category>
      <source url="http://feeds.wired.com/~r/wired/politics/security/~3/291130242/securitymatters_0515">Our Data, Ourselves</source>
    </item>
    <item>
      <title><![CDATA[Confidential information sent to PinPay.net and SoftCard.biz is exposed]]></title>
      <link>http://securityratty.com/article/27cbd575cc28534b9ca368f27ad75124</link>
      <guid>http://securityratty.com/article/27cbd575cc28534b9ca368f27ad75124</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
4/29/08

Organization
ACAP Security Inc

Contractor/Consultant/Branch
PinPay
SoftCard

Victims
Merchants, Agents and customers

Number Affected
Unknown
...]]></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/pinpay.jpg" align="right" height="200" width="178"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>4/29/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.acapsecurity.com">ACAP Security Inc.</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.pinpay.net/index.html">PinPay</a> <br><a href="http://www.softcard.biz/indexaa.html">SoftCard</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Merchants, Agents and customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>Name, mailing address, phone number, email address, date of birth, city of birth, sex, and one or more of the following (chosen from drop-down):<br><br></font><ul><li><font size="2">Passport</font></li><li>Voting ID card</li><li>PAN card</li><li>Driving License card</li><li>Government issued ID card</li><li>Social Security Card</li><li>Military ID card</li><li>Consular ID card</li><li>Postal ID card</li><li>Government Employee ID Card</li><li>Credit Card</li><li>Debit Card<br></li></ul><font size="2"><br><span style="font-weight: bold;">Breach Description:</span><br>ACAP Security and affiliated sites are actively marketing a "secure payment system that allows Internet-based businesses to accept secure PIN-debit card payments and transactions at their online store."&nbsp; The PinPay and SoftCard sign-up pages and account access pages are not adequately secured with encryption, potentially exposing extremely sensitive personal information.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.merchant911.org/blog/index.php/2008/05/05/softcard-vendor-exposing-card-numbers/">Merchant 911 Blog</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Tom Mahoney, the Founder and Director of Merchant 911<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above and my own cursory investigation:<br><br>Back in January, I had short email dialog with a Kip Long, who claimed to be one of the principles of a company called Softcard out of Huntington Beach, CA. They are not to be confused with SoftCard Systems in Athens, GA. As far as I know, SoftCard Systems is a legitimate company with a legitimate product.<br><br>Mr. Long was rather aggressively, but not very successfully, trying to impress me with their product - from what I can make of it, a virtual PIN based card.<br><br>The company uses PinPay - to process transactions and both companies are a part of ACAP Security, Inc.. <br><br>I reviewed their site for possible inclusion in our website’s resource pages, but promptly rejected them.<br><br>their insecure sign-up form - was requesting “Identity Card Numbers” and issue dates. <br><span style="font-style: italic;">[Evan] The sign-up forms at SoftCard.biz and PinPay.net are not secure.&nbsp; Neither are their respected login pages.</span><br><br>“Identity cards” are selectable from a drop down menu and include such ID information as Passport, Driver’s license, SSN, and Credit Card. <br><br>The form also requires a full name and DOB.<br><br>I tried using the HTTPS URL but it appears that they do not have a security certificate tied to their site.<br><br>The fact that Mr. Long used a hotmail address to pitch the company made me wonder too, given that at Merchant911 we try to instill in our members that a free email address from a customer is a fraud alert.<br><br>If a company official can’t use his company’s domain for email, I’m not going to talk to him.<br><br>I called their attention to the insecure web form in January. They still have the form up there, happily collecting this information with an insecure form.<br><span style="font-style: italic;">[Evan] I also sent emails and heard nothing in return.</span><br><br>I have to wonder how much information has already been sniffed or otherwise compromised. You probably don’t want to fill out this form.<br><span style="font-style: italic;">[Evan] My advice would be to <span style="font-weight: bold;">NOT </span>fill out the form and <span style="font-weight: bold;">NOT </span>conduct business with a company that has not demonstrated a willingness to secure your information.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>Tom informed me about this vulnerability (and potentially a breach for anyone that signed-up/in) a couple of weeks ago.&nbsp; I've been a little busy lately, but was finally able to check it out.&nbsp; Let me recap what I found.<br><br>First, let's go to <a href="http://www.softcard.biz.%C2%A0">www.softcard.biz.</a> This is the site that Tom originally pointed out to me.<br><br><img src="http://images.quickblogcast.com/95781-88451/softcardhome.jpg" border="0" width="485"><br><br>The flash home page forwards visitors to a static index (indexaa.html) page.&nbsp; The first paragraph on the page informs visitors about PinPay.<br><br>"The PINPAY SoftCard is a wise way to carry and transfer money. It gives you the ability to purchase products at participating stores throughout the world (as well as at online shopping malls), with the security of a PIN that travels the internet via private encrypted tunnels. It also allows you the ability to load money to your card, pay bills, transfer money to merchants, transfer money between cards, and withdraw cash from your card at the store."<br><br><img src="http://images.quickblogcast.com/95781-88451/registerforfree.jpg" border="0" width="574"><br><br>See where the page says, "Register for your FREE card HERE!!"?&nbsp; This is a link to the sign-up page that Tom was referring to.<br><br><img src="http://images.quickblogcast.com/95781-88451/signupurl.jpg" border="0" width="304"><br><br>No "https" in the URL.&nbsp; Tom was right on that.&nbsp; The sign-up form asks for a personal information ranging from name and address to identity card information (even information for a "Second Identity Card").<br><br><img src="http://images.quickblogcast.com/95781-88451/form.jpg" border="0" width="431"><br><br>The "Select Identity Card" drop down menu displays the choices for the prospective customer, including Passport, Voting ID card, PAN card, Drivers License card, Government issued ID card, Social Security card, Military ID card, Consular ID card, Postal ID card, Government Employee ID Card, Credit Card and Debit Card<br><br><img src="http://images.quickblogcast.com/95781-88451/dropdown.jpg" border="0" width="459"><br><br>SoftCard (or PinPay or ACAP Security) are asking for some very sensitive personal information!&nbsp; First, this is quite a bit more information than they need to approve a person for a "PINPAY SoftCard".&nbsp; Second, no encryption?!&nbsp; Third, who is ACAP/SoftCard/PinPay and what will they do to secure my information once they have it supposing it wasn't intercepted on the way to them?<br><br>Let's dig a little (public) information about ACAP Security.&nbsp; According to <a href="http://www.entrepreneur.com/tradejournals/article/120829630.html">Entreprenuer.com</a>, ACAP launched "Personal Private Network" (ppn) technology, commercially available under the trade name ppnPRO, which is described as a "highly secure, and highly private" personal private network.&nbsp; ppnPRO uses "Government approved AES encryption, with strong personalized 256-bit encryption keys, and encrypting all information- network addresses, applications and ports, as well as the confidential data content".&nbsp; Sounds impressive, but it also sounds like the company should know a thing or two about securing web site transactions with encryption.&nbsp; <br><br>I want to discuss the risk of sending confidential private information over a public network such as the internet without encryption, in particular.&nbsp; This is not a new topic, but I will take some time to demonstrate the risk.<br><br>In order for my information to be compromised, someone (or something) will need to capture the traffic.&nbsp; In order for someone to capture my traffic, they will need to tap into the communication somewhere between me (my computer) and the destination (the web server).&nbsp; My information doesn't travel directly from my computer to the server.&nbsp; There are intermediaries (routers, switches, firewalls, etc.) that have to get (or forward) my information from my computer to the server.<br><br><img src="http://images.quickblogcast.com/95781-88451/trace.jpg" border="0" width="575"><br><br>As you can see depicted in the graphic above, there are at least 16 routers (or hops) between this example source and <a href="http://www.softcard.biz.%C2%A0">www.softcard.biz.&nbsp;</a> The final few hops are not reported due to filtering.&nbsp; So where could my traffic be captured?&nbsp; At the very least:<br><br></font><ul><li><font size="2">Between my computer and my router (or firewall)</font></li><li>Between my firewall and the ISP hand-off</li><li>Between all the traversed devices within my ISP's network</li><li>Between all the traversed devices through the internet</li><li>Between all the traversed devices within the destination ISP's network</li><li>Between all the traversed devices within the destination organization's network and the server itself.<br></li></ul><font size="2">Anyone in the communication path can use a simple protocol analyzer like <a href="http://www.wireshark.org">Wireshark</a> and capture the sensitive information:<br><br>txtfname=Billy&amp;txtmname=J&amp;txtlname=Madison&amp;txtaddress=123+Main+Street&amp;txtcity=Anywhere&amp;<br>txtstate=MA&amp;txtzip=87451&amp;txtcountry=United+States&amp;mob_phone=NONE&amp;txtphone=18006218200&amp;<br>txtemail=billymadison@honky.com&amp;txtdob=04%2F20%2F1988&amp;txtbirthcity=Boston&amp;<br>txtbirthcountry=United+States&amp;txtgender=M&amp;identity1=Social+Security+Card&amp;txtcardno1=123-45-6789&amp;<br>txtissuedate1=04%2F20%2F1988&amp;identity2=Driving+License+card&amp;txtcardno2=M-1234567890&amp;<br>txtissuedate2=04%2F20%2F2006&amp;submit=Accept+Card+Agreement-Submit<br><br>This is a very simplistic demonstration about why it is important to encrypt sensitive information.&nbsp; If the communication had been encrypted, none of the data would have been visible without access to the private key.<br><br>We could go deeper into the server application and SQL, but I think that this is enough.<br><br>A Quote from the ACAP Security CEO:<br></font>“The right of privacy is a fundamental
          and very important right of American society. A right our Nation’s
          founders fought the American Revolution to obtain and a right many
          brave American soldiers have fought and continue to fight and die
          to preserve. As this Nation continues to advance into cyberspace, we
          have
          expanded the right of privacy to include the right to electronic privacy.
          The elements of cyber-crime and cyber-vulnerabilities have begun to
          seriously erode and destroy this important right of electronic privacy.”<br><font size="2"><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/05/08/pinpay.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Thu, 08 May 2008 09:26:03 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/drivers license card">drivers license card</category>
      <category domain="http://securityratty.com/tag/license card">license card</category>
      <category domain="http://securityratty.com/tag/card">card</category>
      <category domain="http://securityratty.com/tag/free card">free card</category>
      <category domain="http://securityratty.com/tag/social security card">social security card</category>
      <category domain="http://securityratty.com/tag/sensitive information">sensitive information</category>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/encrypt sensitive information">encrypt sensitive information</category>
      <source url="http://breachblog.com/2008/05/08/pinpay.aspx">Confidential information sent to PinPay.net and SoftCard.biz is exposed</source>
    </item>
    <item>
      <title><![CDATA[Online intruder makes off with SwimwearBoutique.com customer data]]></title>
      <link>http://securityratty.com/article/ce68ee3873573126adbe70597b391085</link>
      <guid>http://securityratty.com/article/ce68ee3873573126adbe70597b391085</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
4/16/08

Organization
Swimwear Boutique (&quot;SWB

Contractor/Consultant/Branch
None

Victims
Customers

Number Affected
Unknown

Types of Data
Name,...]]></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/swimwear.jpg" align="right" height="69" width="200"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>4/16/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.swimwearboutique.com/">Swimwear Boutique ("SWB")</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>Customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>Name, address, email address, SWB account password, and credit card information<br><br><span style="font-weight: bold;">Breach Description:</span><br>SwimwearBoutique.com "recently discovered that a person may have illegally gained unauthorized access to your personal information stored in your SWB account.&nbsp; We believe that this person unlawfully accessed the SWB Internet site between March 26, 2008 and March 28, 2008.&nbsp; The information accessed varied, but could have included your name, address, email address, SWB account password, and credit card account number"<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://doj.nh.gov/consumer/pdf/swimwear.pdf">New Hampshire State Attorney General breach notification</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The New Hampshire State Attorney General<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above:<br><br>I am writing to you on behalf of my client SwimwearBoutique.com ("SWB") because it determined on March 28, 2008 that it was the victim of an illegal intrusion into its systems.<br><br>Criminals unlawfully obtained access to certain databases containing various information, which could have included names, addresses, and credit card information of approximately 37 residents of New Hampshire, who were SWB customers.<br><span style="font-style: italic;">[Evan] 37 residents in New Hampshire alone.&nbsp; I assume that the number nation/worldwide would be much higher.</span><br><br>We believe that this person unlawfully accessed the SWB Internet site between March 26, 2008 and March 28, 2008.<br><br>These criminals also corrupted data maintained by SWB, rendering certain data unreadable and unusable.<br><span style="font-style: italic;">[Evan] Could this be the purpose behind the SWB note on their Sign In page?</span><br><br><img src="http://images.quickblogcast.com/95781-88451/swimwear2.jpg" border="0" width="497"><br><br>We reported this crime to the Dallas office of the United States Secret Service, and are assisting with the investigation.<br><br>We hope that the criminals responsible will be apprehended and prosecuted to the fullest extent of the law.<br><span style="font-style: italic;">[Evan] Geez.&nbsp; I think we all hope for this, but the reality is that online intruders are rarely caught and prosecuted.</span><br><br>SWB also worked with its existing Internet security provider, McAfee, to determine how these criminals gained access to this information and immediately implemented measures to counter such unlawful conduct.<br><br>We are monitoring the site for further attempts to break into the site and we continue to work with McAfee to maintain the security of the site.<br><span style="font-style: italic;">[Evan] Although I don't see the "Hacker Safe" seal anywhere on the site today, this is the McAfee service that SwimwearBoutique.com uses.&nbsp; In January, 2008 we reported the Geeks.com (also a Hacker Safe customer) </span><a style="font-style: italic;" href="http://breachblog.com/2008/01/07/geeks.aspx">breach</a><span style="font-style: italic;">.</span><br><br>We already have notified our merchant bank and are cooperating with it to provide a list of the affected individuals to it.<br><br>Notification letters will be sent out on April 23, 2008.<br><br>Affected customers also can contact us for more information at 1-866-SWIMWEAR.<br><br>In addition, to any affected customer requesting assistance from us, SWB will offer a year's subscription to the LoudSiren Identity Protection Network.<br><span style="font-style: italic;">[Evan] This statement is included in the letter to the New Hampshire State Attorney General.&nbsp; I did NOT see any reference to this in the letter that went to affected customers.&nbsp; Huh.</span><br><br>We are committed to helping our customers affected by these criminal acts.<br><br>We deeply regret that a valued customer like you may have been affected by the criminals.<br><br><span style="font-weight: bold;">Commentary:</span><br>People like simple solutions and quick fixes which often seem to lead to shortcuts and a false sense of security.&nbsp; Does a "Hacker Safe" seal or PCI compliance mean that your credit card information will be safe?&nbsp; No, it certainly doesn't.&nbsp; Understand these for what they are, a baseline level of security that only meets a certain number of requirements.&nbsp; There is a heckuva lot more to information security.&nbsp; Don't get me wrong, I think that requirements and baselines are important, but they are not more than a cog in a complex machine.<br><br>A tip for online consumers:<br>Check out <a href="http://www.paypal.com/cgi-bin/webscr?cmd=xpt/cps/account/VDCFrequentlyAskedQuestions-outside">PayPal's Virtual Debit Card</a>.&nbsp; "PayPal Virtual Debit Card generates a virtual card number each time you make a transaction online so you don't have to use your personal debit or credit card number."&nbsp; A one time credit card number.&nbsp; If your card number is compromised, it only affects the one transaction.&nbsp; Fraudsters are unable to rack up additional charges. Cool.<br><br><span style="font-weight: bold;">Past Breaches:</span><br>None</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/04/27/swimwear.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Sat, 26 Apr 2008 20:22:24 +0000</pubDate>
      <category domain="http://securityratty.com/tag/credit card account">credit card account</category>
      <category domain="http://securityratty.com/tag/credit card">credit card</category>
      <category domain="http://securityratty.com/tag/time credit card">time credit card</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/credit card information">credit card information</category>
      <category domain="http://securityratty.com/tag/customers">customers</category>
      <category domain="http://securityratty.com/tag/swb customers">swb customers</category>
      <source url="http://breachblog.com/2008/04/27/swimwear.aspx">Online intruder makes off with SwimwearBoutique.com customer data</source>
    </item>
  </channel>
</rss>
