<?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: tamper]]></title>
    <link>http://securityratty.com/tag/tamper</link>
    <description></description>
    <pubDate>Thu, 13 Mar 2008 06:44:00 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Red Hat Releases Critical OpenSSH Update After Detection Of Server Intrusion]]></title>
      <link>http://securityratty.com/article/9f3e955ac8d3e973bc65ce6f28510f3a</link>
      <guid>http://securityratty.com/article/9f3e955ac8d3e973bc65ce6f28510f3a</guid>
      <description><![CDATA[More than a week after a cryptic note hinted at a security breach at Fedora, the open-source group has finally agreed that two separate server intrusions compromised the security of Red Hats OpenSSH...]]></description>
      <content:encoded><![CDATA[More than a week after a cryptic note hinted at a security breach at Fedora, the open-source group has finally agreed that two separate server intrusions compromised the security of Red Hat’s OpenSSH packages. Red Hat has warned that hackers were able to commandeer its systems and tamper with code - but said that since [...]]]></content:encoded>
      <pubDate>Sun, 24 Aug 2008 12:32:40 +0000</pubDate>
      <category domain="http://securityratty.com/tag/red hat">red hat</category>
      <category domain="http://securityratty.com/tag/security breach">security breach</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/server intrusions">server intrusions</category>
      <category domain="http://securityratty.com/tag/cryptic note">cryptic note</category>
      <category domain="http://securityratty.com/tag/open-source">open-source</category>
      <category domain="http://securityratty.com/tag/fedora">fedora</category>
      <category domain="http://securityratty.com/tag/week">week</category>
      <category domain="http://securityratty.com/tag/tamper">tamper</category>
      <source url="http://cyberinsecure.com/red-hat-releases-critical-openssh-update-after-detection-of-server-intrusion/">Red Hat Releases Critical OpenSSH Update After Detection Of Server Intrusion</source>
    </item>
    <item>
      <title><![CDATA[Mailing error at the University of Maryland exposes student information]]></title>
      <link>http://securityratty.com/article/a51262d40f98a67474833c65ff29621e</link>
      <guid>http://securityratty.com/article/a51262d40f98a67474833c65ff29621e</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
7/17/08

Organization
University of Maryland

Contractor/Consultant/Branch
Department of Transportation Services

Victims
All students registered for...]]></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/umd.jpg" width="88" align="right" height="83"><font size="2"><b>Date Reported: </b><br>7/17/08<br><br><b>Organization: </b><br><a href="http://www.umd.edu/">University of Maryland</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.transportation.umd.edu/index.html">Department of Transportation Services</a> <br><br><span style="font-weight: bold;">Victims:</span><br>All students registered for Fall 2008 classes<br><br><span style="font-weight: bold;">Number Affected:</span><br>23,727<br><br><span style="font-weight: bold;">Types of Data:</span><br>Names, addresses, and Social Security numbers<br><br><span style="font-weight: bold;">Breach Description:</span><br>On July 1st, 2008, the University of Maryland Department of Transportation Services mailed an </font><font size="2">on-campus parking </font><font size="2">brochure to all students </font><font size="2">registered for Fall 2008 classes</font><font size="2"> as of June 15, 2008.&nbsp; Recipient Social Security numbers were inadvertently exposed on the mailing labels.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.transportation.umd.edu/parkingmailer/">University of Maryland</a> <br><a href="http://www.wjla.com/news/stories/0708/536794.html">ABC Channel 7 News</a> <br><a href="http://www.wtop.com/?sid=1442585&amp;nid=25">WTOP FM 103.5 News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>University of Maryland<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>On July 1st, 2008, the University of Maryland’s Department of Transportation Services sent all students registered at the time, by U.S. mail, a brochure with on-campus parking information.<br><br>On July 8, 2008, the University discovered that the labels on that mailing included the addressees’ Social Security numbers.<br><span style="font-style: italic;">[Evan] Sheesh, a fraudster doesn't even have to tamper with the mail if the Social Security number is on the label.</span><br><br>The error was discovered on the morning of July 8 when calls were made to the University.<br><br>This parking mailer was sent to all individuals registered for Fall 2008 classes at the University of Maryland as of June 15, 2008.<br><br>The mailing list numbered 23,727 individuals.<br><br>In our annual effort to provide parking and transportation information to the University community, the names and addresses of all registered students was requested internally at the Department of Transportation Services for the purpose of creating mailing labels for a brochure.<br><br>This information was generated by a computer query and included names, addresses and what was believed to be University identification numbers (UIDs).<br><span style="font-style: italic;">[Evan] When writing and executing database queries, isn't it a good idea to check the results and see if the information displayed is the information you were looking for?&nbsp; I wonder if UIDs are also nine digits long like Social Security numbers are.</span><br><br>Our normal process is to remove the University ID numbers prior to mailing.<br><span style="font-style: italic;">[Evan] Is it safe to assume that "normal process" was not followed in this instance?&nbsp; If so, then why not?&nbsp; There is no mention in the school's response.</span><br><br>It was not apparent to departmental staff that these numbers not only still existed within the file, but were Social Security numbers, and not University ID numbers.<br><span style="font-style: italic;">[Evan] Not apparent?&nbsp; They were on the labels!</span><br><br>The numbers were not identified as Social Security numbers and did not show the normal spacing between digits.<br><span style="font-style: italic;">[Evan] So it would be xxxxxxxxx instead of xxx-xx-xxxx.&nbsp; What percentage of people would recognize the first set of nine digits as a SSN?</span><br><br>This mailer was sent using third class, bulk mail delivery and may not have been delivered to you yet.<br><br>Currently, there is no evidence that anyone's Social Security number has been misused.<br><br>The University apologizes and deeply regrets this unfortunate mistake.<br><br>We are initiating immediate action to ensure that this error does not recur.<br><span style="font-style: italic;">[Evan] Like what?&nbsp; Maybe train people to review their query results and follow "normal process"?</span><br><br>The University of Maryland values the critical importance of your personal information.<br><br>We strongly recommend that you take appropriate precautions to mask, black out or destroy this document after use.<br><br>In unfortunate situations like this, it is possible that dishonest people may contact you asking for personal information in the guise of offering assistance from the University.<br><span style="font-style: italic;">[Evan] Equally unfortunate is the fact that there are a lot of dishonest people.</span><br><br>Please note that the University WILL NOT contact you by phone, e-mail or in any other way requesting personal information regarding this incident.<br><br>Please do not release any personal information in response to contacts claiming to be from the University.<br><br>In response to this incident, the University, and specifically the Department of Transportation Services, has moved to severely restrict access to sensitive student and faculty/staff information; we believe the fewer individuals who have access to this data will only increase our ability to protect sensitive information.<br><br>If individuals feel that they would like to take extra steps beyond the fraud alert, the University has arranged with Equifax to make available, at no cost to them, a 12-month service that includes credit monitoring, customer care, fraud expense reimbursement insurance and access to their credit report.<br><br>If you have not received this mailer and are unsure if you are included in the affected group, please call toll-free 1(877) 935-2428, Monday - Friday, 8:30 a.m. - 5 p.m. EST.<br><br><span style="font-weight: bold;">You may contact us in one of the following ways:</span><br>By telephone: Toll-free 1(877) 935-2428, Monday-Friday, 8:30 a.m. - 5 p.m. EST<br>Via e-mail: parkingmailer@umd.edu<br>Mailing address: Regents Drive Garage, Building #202, College Park, MD 20742<br><br><span style="font-weight: bold;">Commentary:</span><br>The lack of attention to detail coupled with lack of control leads to an increase of risk of confidential information disclosure.&nbsp; Not all that uncommon. <br><br><b>Past Breaches:</b><br>Unknown<br></font><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/07/18/umd.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Fri, 18 Jul 2008 05:18:07 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/university">university</category>
      <category domain="http://securityratty.com/tag/maryland">maryland</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/university identification">university identification</category>
      <category domain="http://securityratty.com/tag/university community">university community</category>
      <category domain="http://securityratty.com/tag/social security">social security</category>
      <category domain="http://securityratty.com/tag/addressees social security">addressees social security</category>
      <category domain="http://securityratty.com/tag/recipient social security">recipient social security</category>
      <source url="http://breachblog.com/2008/07/18/umd.aspx">Mailing error at the University of Maryland exposes student information</source>
    </item>
    <item>
      <title><![CDATA[The most insecure banking/sales terminal]]></title>
      <link>http://securityratty.com/article/35f1d465db02d6745fa91cf03800c59f</link>
      <guid>http://securityratty.com/article/35f1d465db02d6745fa91cf03800c59f</guid>
      <description><![CDATA[Can you imagine an ATM running Windows XP Home Edition and being connected to the Internet or a Point of Sale terminal running Tetris ? Unlikely! Why then is allowing a customer to use any computer on...]]></description>
      <content:encoded><![CDATA[<p>Can you imagine an <a href="http://www.youtube.com/watch?v=FAnmuRHYamc">ATM running Windows</a> XP Home Edition and being connected to the Internet or a Point of Sale <a href="http://www.youtube.com/watch?v=wWTzkD9M0sU">terminal running Tetris</a>? &ndash; Unlikely! Why then is allowing a customer to use any computer on the Internet to connect to the banking system, and transfer much more money than you can take out of a cash machine, a good idea? Why did arguably the most conservative organisations in the world &ndash; the banks &ndash; agree to lower their defenses so low that they practically invited the criminals in?</p>

<p>The answer is simple &ndash; the same reasons why even risk-averse investors were chasing after every Internet company in the late 90s  &ndash; the attractiveness of the global scale and reduced costs of e-channels. </p>

<p>Over the years, payments and savings have always been a subject of the most advanced protection:</p>

<ul>
  <li>Banknotes have watermarks and other security features to resist counterfeiting</li>


  <li>Cheques require the account holder's signature</li>


  <li>ATMs require both your card and your PIN, run secure software, and are physically tamper-resistant</li>


  <li>Point of Sale terminals in your favourite supermarket are protected from tampering and use dedicated secure connections to the payment processing network</li>


</ul>


<p>These are all very sensible measures that work (to one degree or another) to protect customers' and banks' money.</p>

<p>Today, however, there is a huge imbalance between the value of electronically accessible funds and their security. This is being very effectively exploited by criminals and the banks are looking for a solution. Personal computers are not tamper proof sales terminals, therefore it is unfeasible to rely on the customer to keep them 100% secure. No one can take away online banking but banks can deploy new security measures, and  solving this problem requires a new innovative approach that can equally address security, ease of use, and cost.</p>

<p>At Cronto, we identified this imbalance years ago. We also correctly predicted that the only <a href="http://blog.cronto.com/index.php?title=transaction_verification_can_protect_aga">solution to address this problem is transaction authentication</a> (where the customer confirms each banking instruction). We then developed an innovative visual transaction signing solution. Based on our unique <a href="http://www.cronto.com/visual_cryptogram.htm">Visual Cryptogram</a>, the Cronto solution supports multiple end user options allowing the bank to choose what is right for their customers whilst maintaining consistency in their backend systems.</p>]]></content:encoded>
      <pubDate>Mon, 14 Jul 2008 09:27:20 +0000</pubDate>
      <category domain="http://securityratty.com/tag/address">address</category>
      <category domain="http://securityratty.com/tag/address security">address security</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/secure">secure</category>
      <category domain="http://securityratty.com/tag/security features">security features</category>
      <category domain="http://securityratty.com/tag/banks">banks</category>
      <category domain="http://securityratty.com/tag/banks agree">banks agree</category>
      <category domain="http://securityratty.com/tag/secure software">secure software</category>
      <category domain="http://securityratty.com/tag/internet company">internet company</category>
      <source url="http://blog.cronto.com/index.php?title=most_insecure_banking_sales_terminal&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1">The most insecure banking/sales terminal</source>
    </item>
    <item>
      <title><![CDATA[Ironkey High Security Flash Drive: Use and Review]]></title>
      <link>http://securityratty.com/article/e0322cef5058990607beceacaf2e8df7</link>
      <guid>http://securityratty.com/article/e0322cef5058990607beceacaf2e8df7</guid>
      <description><![CDATA[New Video: Ironkey High Security Flash Drive: Use and Review
The Ironkey is a high security thumb drive designed to provide strong AES encryption, tamper resistance and other security services. Id...]]></description>
      <content:encoded><![CDATA[<b>New Video:</b><a href="http://www.irongeek.com/i.php?page=videos/ironkey-high-security-flash-drive-use-and-review">Ironkey High Security Flash Drive: Use and Review</a><br>
The Ironkey is a high security thumb drive designed to provide strong AES 
encryption, tamper resistance and other security services. I’d seen the Ironkey 
advertised quite a bit, and even read about its crypto systems and ruggedness, 
but was left wondering about how it works in operation. Since the hardcore tech 
side has been covered elsewhere, I’ll concentrate on the Ironkey’s usability and 
features. Some of the topics covered will include: How is the drive mounted 
without admin privileges in Windows? How is it mounted in Linux? How does the 
“Self Destruct” feature work? What is Secure Sessions? How is the Ironkey better 
than just using Truecrypt? I made this video to answer those sorts of questions 
for myself and others. If you want more details on the crypto involved, see the 
links section at the end of this video. The model I will be working with is the 
1GB Ironkey Personal. I’ll show its use and give my opinions on the device.<p>By 
the way, you may notice that I'm making fewer posts over the next month or so. 
I'll be busy studying for the GRE, wish me luck.
<p><a href="http://feeds.feedburner.com/~a/IrongeeksSecuritySite?a=LgLqIf"><img src="http://feeds.feedburner.com/~a/IrongeeksSecuritySite?i=LgLqIf" border="0"></img></a></p><img src="http://feeds.feedburner.com/~r/IrongeeksSecuritySite/~4/328510758" height="1" width="1"/>]]></content:encoded>
      <pubDate>Sun, 06 Jul 2008 20:48:42 +0000</pubDate>
      <category domain="http://securityratty.com/tag/ironkey">ironkey</category>
      <category domain="http://securityratty.com/tag/drive">drive</category>
      <category domain="http://securityratty.com/tag/security flash drive">security flash drive</category>
      <category domain="http://securityratty.com/tag/security thumb drive">security thumb drive</category>
      <category domain="http://securityratty.com/tag/1gb ironkey personal">1gb ironkey personal</category>
      <category domain="http://securityratty.com/tag/video">video</category>
      <category domain="http://securityratty.com/tag/crypto">crypto</category>
      <category domain="http://securityratty.com/tag/crypto systems">crypto systems</category>
      <category domain="http://securityratty.com/tag/secure sessions">secure sessions</category>
      <source url="http://feeds.feedburner.com/~r/IrongeeksSecuritySite/~3/328510758/i.php">Ironkey High Security Flash Drive: Use and Review</source>
    </item>
    <item>
      <title><![CDATA[.. and now - PIN stealing..]]></title>
      <link>http://securityratty.com/article/2e699cb88411c7ece62621d294d7f5fb</link>
      <guid>http://securityratty.com/article/2e699cb88411c7ece62621d294d7f5fb</guid>
      <description><![CDATA[Once the bad guys figured out how easy it was to sniff unencrypted ATM and card authorization traffic to steal track data, and after making a killing with stolen card numbers, they began setting their...]]></description>
      <content:encoded><![CDATA[Once the bad guys figured out how easy it was to sniff unencrypted ATM and card authorization traffic to steal track data, and after making a killing with stolen card numbers, they began setting their sights on bank PINs.  PIN numbers - thanks to ANSI's TG3 - are encrypted with a half decent algorithm (and they are looking to strengthen that even more now). Which means that sniffing the traffic will only give you an encrypted number - something which would require a decryption key. A number of security controls like requiring dual control and split knowledge for key components, strict physical security requirements and Tamper Resistant Security Modules help in securing the keys. Assuming one cannot gain access to the encryption keys, this leaves only two scenarios for an attacker to gain access to the unencrypted PINs:<br />1. Before the PIN is encrypted by the Tamper Resistant Security Module (an ATM in the case of bank customers). Most criminals have been using fake PIN PADs and a number of techniques like jamming cards etc steal PINs blissfully unaware that they are on camera most of the time. Nice video ?<a href="http://www.youtube.com/watch?v=9mi4kB15wMY"> here.</a><br /><br />2. After the PIN reaches the issuer and is decrypted. This is the scarier situation -as the attacker would have access to a database of unencrypted PIN numbers / PIN offsets coming in from all around the globe. PCI supposedly <a href="http://pcianswers.com/2007/08/31/issuer-pci-requirements/">requires </a> that issuers be compliant and not store unencrypted PANs or PINs - but no validation is required (unless they are a VisaNet processor). <br /><br />Well - Kevin Poulsen at Wired <a href="http://blog.wired.com/27bstroke6/2008/06/citibank-atm-se.html">wrote today</a> about how an alleged ATM crime spree has been blamed on a Citibank hack. Though Citibank has denied the hack as the cause of the fraudulent withdrawals - all signs seem to point towards it so far.<br />(This definitely is not new - While testing an issuer's security I'd stumbled upon ATM log entry files - complete with PAN, PIN, full name, address, zip code and atm location - back in the day when RFP just released<a href="http://www.wiretrip.net/rfp/"> whisker.</a> )<br /><br />This is probably just the beginning of a new wave. Issuers really need to pull up their socks and begin to treat cardmember data with the same respect that PCI Co is requiring merchants and processors to do. - and while I'm wishing horses - can ANSI or someone start working on some standards for requiring all track data to be encrypted in transit?]]></content:encoded>
      <pubDate>Thu, 19 Jun 2008 06:38:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/pin">pin</category>
      <category domain="http://securityratty.com/tag/pin reaches">pin reaches</category>
      <category domain="http://securityratty.com/tag/pin offsets">pin offsets</category>
      <category domain="http://securityratty.com/tag/fake pin pads">fake pin pads</category>
      <category domain="http://securityratty.com/tag/atm location">atm location</category>
      <category domain="http://securityratty.com/tag/atm">atm</category>
      <category domain="http://securityratty.com/tag/bank pins">bank pins</category>
      <category domain="http://securityratty.com/tag/atm crime spree">atm crime spree</category>
      <category domain="http://securityratty.com/tag/access">access</category>
      <source url="http://securitycoin.blogspot.com/2008/06/and-now-pin-stealing.html">.. and now - PIN stealing..</source>
    </item>
    <item>
      <title><![CDATA[I Am IronKey, and I Can Encrypt Anything]]></title>
      <link>http://securityratty.com/article/8601b15c2cb85c06b3dc5000ad9fab1c</link>
      <guid>http://securityratty.com/article/8601b15c2cb85c06b3dc5000ad9fab1c</guid>
      <description><![CDATA[The IronKey USB flash drive is one of the most secure devices I've ever worked with, but simultaneously tries to be--and achieves being--among the simplest to interact with in achieving that security....]]></description>
      <content:encoded><![CDATA[The IronKey USB flash drive is one of the most secure devices I've ever worked with, but simultaneously tries to be--and achieves being--among the simplest to interact with in achieving that security. The product, from the eponymous company IronKey, comes in capacities from 1 GB to 8 GB that encrypts data five ways to Sunday while achieving government certification as tamper evident. A secured, anonymized version of Firefox is also onboard. Prices start at $79 including a one-year subscription for anonymous browsing; an 8 GB drive is $299.]]></content:encoded>
      <pubDate>Wed, 21 May 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/eponymous company ironkey">eponymous company ironkey</category>
      <category domain="http://securityratty.com/tag/tamper evident">tamper evident</category>
      <category domain="http://securityratty.com/tag/government certification">government certification</category>
      <category domain="http://securityratty.com/tag/secure devices">secure devices</category>
      <category domain="http://securityratty.com/tag/one-year subscription">one-year subscription</category>
      <category domain="http://securityratty.com/tag/encrypts data">encrypts data</category>
      <category domain="http://securityratty.com/tag/prices start">prices start</category>
      <category domain="http://securityratty.com/tag/sunday">sunday</category>
      <category domain="http://securityratty.com/tag/onboard">onboard</category>
      <source url="http://www.networkworld.com/news/2008/052208-i-am-ironkey-and-i.html?fsrc=rss-security">I Am IronKey, and I Can Encrypt Anything</source>
    </item>
    <item>
      <title><![CDATA[What do the Cold Boot Crypto Attack, DVD Players, and MiFare tell us about the Future of Biometrics?]]></title>
      <link>http://securityratty.com/article/c9945cfe64ffaf97ac8736318bf1f990</link>
      <guid>http://securityratty.com/article/c9945cfe64ffaf97ac8736318bf1f990</guid>
      <description><![CDATA[Last week Slashdot pointed me to an interesting article in The Standard
Understanding anonymity and the need for biometrics
In fact, I found the article to be rather upsetting. Not because of the...]]></description>
      <content:encoded><![CDATA[<p>Last week Slashdot pointed me to an &#8220;interesting&#8221; article in The Standard:<br />
<a href="http://www.thestandard.com/news/2008/03/19/understanding-anonymity-and-need-biometrics" onclick="javascript:pageTracker._trackPageview('/outbound/article/http://www.thestandard.com/news/2008/03/19/understanding-anonymity-and-need-biometrics');">Understanding anonymity and the need for biometrics</a>.</p>
<p>In fact, I found the article to be rather upsetting.  Not because of the article&#8217;s thesis that strong authentication through a national ID program would not necessarily pose a threat to privacy; but rather, because of their naive (and irresponsible) handling of the realities of the biometric authentication challenge. They gloss over the real security challenges with creating a national biometric infrastructure.  Here are the two quotes that are most misleading:</p>
<ul>
<li><strong>&#8220;<span class="Apple-style-span" style="color: #171717; line-height: 17px">Confusing privacy with anonymity has delayed implementation of robust, virtually tamper-proof biometric authentication to replace paper-based forms of ID that neither assure privacy nor reliably prove identity.&#8221;</span></strong></li>
<li><strong><span class="Apple-style-span" style="color: #171717; line-height: 17px"></span><span class="Apple-style-span" style="color: #171717; line-height: 17px"><span class="Apple-style-span" style="color: #232323; line-height: 20px">&#8220;This emerging technology makes it virtually impossible to assume someone else&#8217;s unique identity.&#8221;</span></span></strong></li>
</ul>
<p>The problem that the authors are glossing over is that no such technology exists today, and it is unlikely to ever exist. Now, to be fair, I am assuming that  a  critical success factor for any national biometric program, as described, would be that the authentication devices have to be available, and usable, anyplace paper-based IDs can be used today. This of course implies that the authenticator must be an inexpensive, commodity device, easy to purchase, maintain, and operate. Such a device would have to be even more ubiquitous than the electronic credit card machine.</p>
<p>The problem is that the authenticator itself may be in the possession of the attacker (Perhaps after you authenticate your legitimate purchase the clerk desires to use your identity herself&#8230;). In the history of security controls, when the attacker has unsupervised at-will physical access, the attacker wins. Here are a few examples:</p>
<ul>
<li>Defeated copy protection on DVDs ( <a href="http://en.wikipedia.org/wiki/Jon_Lech_Johansen" onclick="javascript:pageTracker._trackPageview('/outbound/article/http://en.wikipedia.org/wiki/Jon_Lech_Johansen');">more</a> &amp; <a href="http://it.slashdot.org/it/08/03/21/1241234.shtml" onclick="javascript:pageTracker._trackPageview('/outbound/article/http://it.slashdot.org/it/08/03/21/1241234.shtml');">more info</a>)</li>
<li>Cold Boot Crypto Attack on hard disk encryption (<a href="http://www.engadget.com/2008/02/21/cold-boot-disk-encryption-attack-is-shockingly-effective/" onclick="javascript:pageTracker._trackPageview('/outbound/article/http://www.engadget.com/2008/02/21/cold-boot-disk-encryption-attack-is-shockingly-effective/');">more info</a>)</li>
<li>MiFare RFID Cards (<a href="http://www.pcworld.com/article/id,143371-pg,1/article.html" onclick="javascript:pageTracker._trackPageview('/outbound/article/http://www.pcworld.com/article/id,143371-pg,1/article.html');">more info</a>)</li>
<li>Skimming devices attached to ATM machines to steal card and PIN data (<a href="http://en.wikipedia.org/wiki/Credit_card_fraud#Skimming" onclick="javascript:pageTracker._trackPageview('/outbound/article/http://en.wikipedia.org/wiki/Credit_card_fraud#Skimming');">more info</a>)</li>
</ul>
<p>Of course, all of these systems worked in the lab. But when a security system is widely deployed, it has to  withstand an enormous amount of scrutiny, and minor flaws will be exploited. And of course, the greater the financial gain, the greater the time and energy attackers invest in trying to defeat the system. The authors of the article ignore  these issues, idealistically assuming biometrics will just work.</p>
<p>Now, of course there are lots of examples where biometrics work very effectively. But I would propose that biometric authentication is most useful when the authentication device is physically secure and the authentication itself is supervised. The MiFare example above also demonstrates two other issues:</p>
<ul>
<li>The system chose not to implement a reviewed and standard cryptographic algorithm - always a bad idea</li>
<li>MiFare was able to sell 1 billion cards and authenticators before the system failed</li>
</ul>
<p><strong>The cost of investing in a national biometric authentication program, and then having the security fail, is enormous.</strong> Can you imagine deploying a biometric authentication infrastructure to every bank, police car, restaurant, shop, etc. and then having video on YouTube of it being defeated ?</p>
<p>- Erik</p>
<p>BTW, Maybe the attacker doesn&#8217;t even need to  tamper with the device -&gt; ftp://ftp.ccc.de/pub/video/Fingerabdruck_Hack/fingerabdruck.mpg</p>
<p><a href="http://artofinfosec.com" >Art of Information Security</a> would <a href="http://artofinfosec.com/feedback/" >love your feedback</a> !</p>
<p><a href="http://artofinfosec.com/48/what-do-the-cold-boot-crypto-attack-dvd-players-and-mifare-tell-us-about-the-future-of-biometrics/" >What do the Cold Boot Crypto Attack, DVD Players, and MiFare tell us about the Future of Biometrics?</a></p>
<img src="http://feeds.feedburner.com/~r/artofinfosec/~4/257983662" height="1" width="1"/>]]></content:encoded>
      <pubDate>Tue, 25 Mar 2008 21:16:43 +0000</pubDate>
      <category domain="http://securityratty.com/tag/biometric authentication">biometric authentication</category>
      <category domain="http://securityratty.com/tag/biometric authentication infrastructure">biometric authentication infrastructure</category>
      <category domain="http://securityratty.com/tag/biometric authentication challenge">biometric authentication challenge</category>
      <category domain="http://securityratty.com/tag/tamper-proof biometric authentication">tamper-proof biometric authentication</category>
      <category domain="http://securityratty.com/tag/authentication">authentication</category>
      <category domain="http://securityratty.com/tag/authentication device">authentication device</category>
      <category domain="http://securityratty.com/tag/mifare">mifare</category>
      <category domain="http://securityratty.com/tag/tamper">tamper</category>
      <category domain="http://securityratty.com/tag/biometrics">biometrics</category>
      <source url="http://feeds.feedburner.com/~r/artofinfosec/~3/257983662/">What do the Cold Boot Crypto Attack, DVD Players, and MiFare tell us about the Future of Biometrics?</source>
    </item>
    <item>
      <title><![CDATA[ATM Communication - How Secure ?]]></title>
      <link>http://securityratty.com/article/c6c474141a396a1cf9568c75ac2e3e65</link>
      <guid>http://securityratty.com/article/c6c474141a396a1cf9568c75ac2e3e65</guid>
      <description><![CDATA[A while ago, I attended a class on PIN and Key Management for Payment Networks. ANSI has laid out strict guidelines (in their ANSI X9 TG-3 standards checklist, ANSI documents X9.8 and X9.24) for how a...]]></description>
      <content:encoded><![CDATA[<a href="http://bp3.blogger.com/_XTqu2iQGpYM/R-f5EstklxI/AAAAAAAAAcI/UFGeOMNLK38/s1600-h/atmcommunication.JPG"></a><br /><br /><br /><div><a href="http://bp2.blogger.com/_XTqu2iQGpYM/R-f45ctklwI/AAAAAAAAAcA/fPZDPKAUmzI/s1600-h/atmcommunication.JPG"></a><br /><br /><br /><br /><div><a href="http://bp0.blogger.com/_XTqu2iQGpYM/R-P6W8tklpI/AAAAAAAAAa4/xVpctmHSzUs/s1600-h/diebold-atm.jpg"><img id="BLOGGER_PHOTO_ID_5180259268567537298" style="DISPLAY: block; MARGIN: 0px auto 10px; CURSOR: hand; TEXT-ALIGN: center" alt="" src="http://bp0.blogger.com/_XTqu2iQGpYM/R-P6W8tklpI/AAAAAAAAAa4/xVpctmHSzUs/s200/diebold-atm.jpg" border="0" /></a> <div><br /><span style="font-family:sans-serif;font-size:85%;">A while ago, I attended a class on PIN and Key Management for Payment Networks. ANSI has laid out strict guidelines (in their ANSI X9 TG-3 standards checklist, ANSI documents X9.8 and X9.24) for how a customer's PIN should be kept secure: how they should be stored on the card (store only the difference/offset of the encrypted PIN value and the natural PIN), what the minimum encryption requirements are (Triple DES), what the specifications of the devices that encrypt/decrypt the PIN are (Tamper Resistant Security Modules), how PINs should be exchanged between various Financial Institutions (exchange keys between two FIs out-of-band AND under the principles of dual control and then encrypt the keys, how should compromised - no - even "suspect" compromised PINs and Keys that encrypt the PINs be treated (securely delete the key, recreate a new key under the principles of dual control and split knowledge and re-encrypt *every* key or PIN that has been encrypted under it! and re-issue cards containing PIN offsets for PINs encrypted under the new encryption key, if applicable) etc.</span></div><div><span style="font-family:sans-serif;font-size:85%;"></span></div><div><span style="font-family:sans-serif;font-size:85%;">It was simply awesome. To know that the Financial Institutions do their due diligence is a huge confidence booster. The fact that these guidelines are just that - guidelines, and haven't been strictly enforced by governing bodies is not my biggest concern. Neither is the fact that there are a number of papers out there that talk about the insecurities <a href="http://www.cl.cam.ac.uk/~jc407/pin.ppt">in PIN translation</a>. </span><br /></div><span style="font-family:sans-serif;font-size:85%;"></span><div><span style="font-family:sans-serif;font-size:85%;">The following, however, is:</span></div><div><span style="font-family:Arial;font-size:85%;"></span></div><div><span style="font-family:sans-serif;font-size:85%;"></span></div><div><span style="font-family:sans-serif;font-size:85%;">The folks at redspin (Brian Hayes, Matt Marshall) analysed ATM traffic and wrote a <a href="http://www.redspin.com/docs/ATM_Vulnerabilities_04_10_06.pdf">paper </a>on insecurities in ATM communications. </span></div><br /><div><br /></div></div><div></div><img id="BLOGGER_PHOTO_ID_5181383918638896930" style="DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 426px; CURSOR: hand; HEIGHT: 498px; TEXT-ALIGN: center" height="175" alt="" src="http://bp1.blogger.com/_XTqu2iQGpYM/R-f5OMtklyI/AAAAAAAAAcQ/eM765xZYtfI/s400/atmcommunication.JPG" width="113" border="0" /><br /><div></div><div></div><div></div><div></div><div></div><div></div><div></div><div></div><div></div><div></div><div><div><span style="font-family:sans-serif;font-size:85%;">What you see above is the raw data message format that leaves the atm connected to a network. Cleartext communication. Notice the account number and expiration date. Totally vulnerable to man-in-the-middle attacks. The response message that is supposed to come from the FI, looks something like this:</span> </div><br /><div></div><br /><div></div><br /><div></div><img id="BLOGGER_PHOTO_ID_5181384279416149810" style="DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 417px; CURSOR: hand; HEIGHT: 448px; TEXT-ALIGN: center" height="195" alt="" src="http://bp1.blogger.com/_XTqu2iQGpYM/R-f5jMtklzI/AAAAAAAAAcY/bVabJx2-k38/s400/response.JPG" width="165" border="0" /> <div></div><div><span style="font-family:sans-serif;font-size:85%;">I'm not going to say what one needs to do at this point. Read up m</span><span style="font-family:sans-serif;font-size:85%;">essage format ISO 8583. It is scary.</span><br /><span style="font-family:sans-serif;font-size:85%;"></span><br /><span style="font-family:sans-serif;font-size:85%;"><br /></div></span></div></div>]]></content:encoded>
      <pubDate>Fri, 21 Mar 2008 09:34:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/pin">pin</category>
      <category domain="http://securityratty.com/tag/pin offsets">pin offsets</category>
      <category domain="http://securityratty.com/tag/atm">atm</category>
      <category domain="http://securityratty.com/tag/pin translation">pin translation</category>
      <category domain="http://securityratty.com/tag/natural pin">natural pin</category>
      <category domain="http://securityratty.com/tag/key">key</category>
      <category domain="http://securityratty.com/tag/key management">key management</category>
      <category domain="http://securityratty.com/tag/atm communications">atm communications</category>
      <category domain="http://securityratty.com/tag/encryption key">encryption key</category>
      <source url="http://securitycoin.blogspot.com/2008/03/atm-communication.html">ATM Communication - How Secure ?</source>
    </item>
    <item>
      <title><![CDATA[Attack and Defense: Securing ASP.NET 2.0 Apps]]></title>
      <link>http://securityratty.com/article/64d0cb6b50e3ab56187a319511944401</link>
      <guid>http://securityratty.com/article/64d0cb6b50e3ab56187a319511944401</guid>
      <description><![CDATA[Thanks to all who attended this DevWeek talk today. Here's a link to the demos I did, along with the tamper-detection code I showed you. Enjoy
Updated (20 Mar 2008) with new...]]></description>
      <content:encoded><![CDATA[<P>Thanks to all who attended this <A href="http://www.devweek.com/sessions/conference3.asp">DevWeek talk</A> today. Here's a <A href="http://www.pluralsight.com/keith/presentations/attackDefenseDemos.zip">link</A> to the demos I did, along with the tamper-detection code I showed you. Enjoy!</P>
<P>Updated (20 Mar 2008) with new link.</P><div style="clear:both;"></div><img src="http://pluralsight.com/community/aggbug.aspx?PostID=50463" width="1" height="1">]]></content:encoded>
      <pubDate>Thu, 13 Mar 2008 06:44:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/link">link</category>
      <category domain="http://securityratty.com/tag/devweek talk">devweek talk</category>
      <category domain="http://securityratty.com/tag/mar">mar</category>
      <category domain="http://securityratty.com/tag/enjoy">enjoy</category>
      <category domain="http://securityratty.com/tag/demos">demos</category>
      <category domain="http://securityratty.com/tag/code">code</category>
      <source url="http://pluralsight.com/community/blogs/keith/archive/2008/03/13/50463.aspx">Attack and Defense: Securing ASP.NET 2.0 Apps</source>
    </item>
    <item>
      <title><![CDATA[Attack and Defense: Securing ASP.NET 2.0 Apps]]></title>
      <link>http://securityratty.com/article/c35b167cc60d1804decc892b90ce1a74</link>
      <guid>http://securityratty.com/article/c35b167cc60d1804decc892b90ce1a74</guid>
      <description><![CDATA[Thanks to all who attended this DevWeek talk today. Here's a link to the demos I did, along with the tamper-detection code I showed you. Enjoy
Updated (20 Mar 2008) with new...]]></description>
      <content:encoded><![CDATA[<P>Thanks to all who attended this <A href="http://www.devweek.com/sessions/conference3.asp">DevWeek talk</A> today. Here's a <A href="http://www.pluralsight.com/keith/presentations/attackDefenseDemos.zip">link</A> to the demos I did, along with the tamper-detection code I showed you. Enjoy!</P>
<P>Updated (20 Mar 2008) with new link.</P><div style="clear:both;"></div><img src="http://www.pluralsight.com/community/aggbug.aspx?PostID=50463" width="1" height="1">]]></content:encoded>
      <pubDate>Thu, 13 Mar 2008 06:44:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/link">link</category>
      <category domain="http://securityratty.com/tag/devweek talk">devweek talk</category>
      <category domain="http://securityratty.com/tag/mar">mar</category>
      <category domain="http://securityratty.com/tag/enjoy">enjoy</category>
      <category domain="http://securityratty.com/tag/demos">demos</category>
      <category domain="http://securityratty.com/tag/code">code</category>
      <source url="http://www.pluralsight.com/community/blogs/keith/archive/2008/03/13/50463.aspx">Attack and Defense: Securing ASP.NET 2.0 Apps</source>
    </item>
  </channel>
</rss>
