<?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: arguably]]></title>
    <link>http://www.securityratty.com/tag/arguably</link>
    <description></description>
    <pubDate>Tue, 29 Apr 2008 20:00:00 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[XSF & XSS: Double your pleasure, double your fun]]></title>
      <link>http://www.securityratty.com/article/1fae85d8335f0c9fbe56b8858c8692c2</link>
      <guid>http://www.securityratty.com/article/1fae85d8335f0c9fbe56b8858c8692c2</guid>
      <description><![CDATA[If you've read this blog, or those of my peers, you're likely quite familiar with cross-site scripting, and the problems associated with open redirect vulnerabilities. A vulnerability you may be less...]]></description>
      <content:encoded><![CDATA[If you've read this blog, or those of my peers, you're likely quite familiar with cross-site scripting, and the problems associated with open redirect vulnerabilities. A vulnerability you may be less familiar with is <a href="http://www.xssed.com/news/26/Cross-site_framed/" target="_blank">cross-site framing</a>, which largely couples the best of both above-mentioned vulnerabilities. <br />What then, if there's a cross-site framing vulnerability coupled with cross-site scripting in the content offered by the frame? All sorts of problems come to mind: phishing, malware, credential theft; all arguably twice removed from the attacker's source, tucked away in the context of two victim sites.<br />First, I'll discuss the original XSS issue that led to this finding.<br />Recently, I was investigating a flawed parameter in <a href="http://www.openhire.com/" target="_blank">Openhire</a>, a career posting vendor used by major companies like <a href="http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?company_id=15635&version=1" target="_blank">Crate&Barrel</a>, Eileen Fisher, Enterprise, Benjamin Moore, Scottrade, and Getty Images.<br />Most of these sites simply link to the Openhire offering that hosts job postings on their behalf which, in turn, has been crafted to look like the referring site.<br />As an example, here's Scottrade's employment page hosted by Openhire.<br /><br /><span style="font-style:italic;"><a href="http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?version=1&company_id=15624" target="_blank">http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?version=1&company_id=15624</a></span><br /><br />Standard stuff, looks nicely like the Scottrade site, so everything's cool, right?<br />Wrong? What if someone hosting a service on your behalf suffers a security gap?<br /><span style="font-weight:bold;">You're only as strong as your weakest link!</span><br />Here's the posting for an Application Security Engineer (funny, eh?) at Scottrade as hosted on their behalf by Openhire:<br /><br /><span style="font-style:italic;"><a href="http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspjob&id=23&jobid=130527&company_id=15624&version=1&source=ONLINE&JobOwner=976367&level=levelid3&levelid3=18247&parent=St.%20Louis%20Corporate%20Headquarters%3B%3B%3BInformation%20Technology%3B%3B%3BSecurity&startflag=3&CFID=66851845&CFTOKEN=29a95-d12594d4-47d9-49e8-9067-1091bdf68e80" target="_blank">http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspjob&id=23&jobid=130527&company_id=15624&version=1&source=ONLINE&JobOwner=976367&level=levelid3&levelid3=18247&parent=St.%20Louis%20Corporate%20Headquarters%3B%3B%3BInformation%20Technology%3B%3B%3BSecurity&startflag=3&CFID=66851845&CFTOKEN=29a95-d12594d4-47d9-49e8-9067-1091bdf68e80</a></span><br /><br />Now here the same job posting spewing massive cookie data:<br /><br /><span style="font-style:italic;"><a href="http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspjob&id=23&jobid=130527&company_id=15624&version=1&source=ONLINE&JobOwner=%22%3E%3CSCRIPT%3Ealert(document.cookie)%3C/SCRIPT%3E&level=levelid3&levelid3=18247&parent=St.%20Louis%20Corporate%20Headquarters;;;Information%20Technology;;;Security&startflag=3" target="_blank">http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspjob&id=23&jobid=130527&company_id=15624&version=1&source=ONLINE&JobOwner=%22%3E%3CSCRIPT%3Ealert(document.cookie)%3C/SCRIPT%3E&level=levelid3&levelid3=18247&parent=St.%20Louis%20Corporate%20Headquarters;;;Information%20Technology;;;Security&startflag=3</a></span><br /><br />Screen shot offered below, as the code above will likely be repaired very soon by Openhire. I notified them this past Thursday.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_kVOWaY1TAF0/SNcebDIT4JI/AAAAAAAAADA/2umzh0wbmmw/s1600-h/Scottrade_Openhire.png" target="_blank"><img style="cursor:pointer; cursor:hand;" src="http://1.bp.blogspot.com/_kVOWaY1TAF0/SNcebDIT4JI/AAAAAAAAADA/2umzh0wbmmw/s320/Scottrade_Openhire.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5248697340769067154" /></a><br /><br />It's bad enough when there's an application security hole in code someone else is hosting on your behalf, but what if your method of displaying said code is also at risk? Enter the Getty Images Jobs page.<br /><br /><span style="font-style:italic;"><a href="http://www.gettyimagesjobs.com/gettyImagesJobsDisplay.html?http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=careeropps&startflag=0&company_id=15531&version=2&CFID=12265212&CFTOKEN=60213778" target="_blank">http://www.gettyimagesjobs.com/gettyImagesJobsDisplay.html?http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=careeropps&startflag=0&company_id=15531&version=2&CFID=12265212&CFTOKEN=60213778</a></span><br /><br />Watch what happens when you pull the Openhire code. Can you say self-replicating frame loop from hell (in Firefox)? Trust me your browser will crash if you leave this running too long. This will likely be fixed soon, so if the URL doesn't work, the screen shot exemplifies the issue.<br /><br /><a href="http://www.gettyimagesjobs.com/gettyImagesJobsDisplay.html" target="_blank">http://www.gettyimagesjobs.com/gettyImagesJobsDisplay.html</a><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_kVOWaY1TAF0/SNcqO933d4I/AAAAAAAAADY/SSzLv3ZpiN0/s1600-h/GettyonGetty.png" target="_blank"><img style="cursor:pointer; cursor:hand;" src="http://4.bp.blogspot.com/_kVOWaY1TAF0/SNcqO933d4I/AAAAAAAAADY/SSzLv3ZpiN0/s320/GettyonGetty.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5248710327339022210" /></a><br /><br />What if, instead of Openhire's Getty Images page, or nothing at all (which obviously creates its own issue), we drop in an arbitrary URL?<br />Yep, you guessed it.<br /><span style="font-style:italic;"><br />http://www.gettyimagesjobs.com/gettyImagesJobsDisplay.html?http://www.xssed.com/news/26/Cross-site_framed/</span><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_kVOWaY1TAF0/SNcmqF3wQyI/AAAAAAAAADI/EhR6rYOmwlI/s1600-h/Getty_XSF.png" target="_blank"><img style="cursor:pointer; cursor:hand;" src="http://2.bp.blogspot.com/_kVOWaY1TAF0/SNcmqF3wQyI/AAAAAAAAADI/EhR6rYOmwlI/s320/Getty_XSF.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5248706395295990562" /></a><br /><br />Now, bringing it all home for double the pleasure, double the fun, what if we coupled the original Openhire cross-site scripting vuln with Getty Images cross-site frame vuln?<br /><br />It hurts twice as much, in my book.<br /><br /><span style="font-style:italic;">http://www.gettyimagesjobs.com/gettyImagesJobsDisplay.html?http://hostedjobs.openhire.com/epostings/jobs/submit.cfm?fuseaction=dspjob&id=23&jobid=130527&company_id=15624&version=1&source=ONLINE&JobOwner=%22%3E%3CSCRIPT%3Ealert(document.cookie)%3C/SCRIPT%3E&level=levelid3&levelid3=18247&parent=St.%20Louis%20Corporate%20Headquarters;;;Information%20Technology;;;Security&startflag=3</span><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_kVOWaY1TAF0/SNco1c6ensI/AAAAAAAAADQ/QaKByEFozTU/s1600-h/Getty%2BScottrade.png" target="_blank"><img style="cursor:pointer; cursor:hand;" src="http://1.bp.blogspot.com/_kVOWaY1TAF0/SNco1c6ensI/AAAAAAAAADQ/QaKByEFozTU/s320/Getty%2BScottrade.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5248708789483249346" /></a><br /><br />The lessons learned:<br />1) Ensure your partners are writing secure code on you behalf.<br />2) Ensure that the code you utilize to incorporate said partner's code is also well written. ;-)<br /><br />Double the headache, double the dumb.<br /><br /><a href="http://del.icio.us/post?url=http://holisticinfosec.blogspot.com/2008/09/xsf-xss-double-your-pleasure-double.html&title=XSF%20&%20XSS:%20Double%20your%20pleasure,%20double%20your%20fun " title="XSF & XSS: Double your pleasure, double your fun ">del.icio.us</a> | <a href="http://digg.com/submit?phase=2&amp;url=http://holisticinfosec.blogspot.com/2008/09/xsf-xss-double-your-pleasure-double.html" title="XSF & XSS: Double your pleasure, double your fun ">digg</a>]]></content:encoded>
      <pubDate>Sun, 21 Sep 2008 17:00:00 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/openhire code">openhire code</category>
      <category domain="http://www.securityratty.com/tag/openhire">openhire</category>
      <category domain="http://www.securityratty.com/tag/original openhire cross-site">original openhire cross-site</category>
      <category domain="http://www.securityratty.com/tag/scottrade site">scottrade site</category>
      <category domain="http://www.securityratty.com/tag/scottrade">scottrade</category>
      <category domain="http://www.securityratty.com/tag/cross-site">cross-site</category>
      <category domain="http://www.securityratty.com/tag/site">site</category>
      <category domain="http://www.securityratty.com/tag/secure code">secure code</category>
      <category domain="http://www.securityratty.com/tag/code">code</category>
      <source url="http://holisticinfosec.blogspot.com/2008/09/xsf-xss-double-your-pleasure-double.html">XSF &amp; XSS: Double your pleasure, double your fun</source>
    </item>
    <item>
      <title><![CDATA[The most insecure banking/sales terminal]]></title>
      <link>http://www.securityratty.com/article/35f1d465db02d6745fa91cf03800c59f</link>
      <guid>http://www.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://www.securityratty.com/tag/address">address</category>
      <category domain="http://www.securityratty.com/tag/address security">address security</category>
      <category domain="http://www.securityratty.com/tag/security">security</category>
      <category domain="http://www.securityratty.com/tag/secure">secure</category>
      <category domain="http://www.securityratty.com/tag/security features">security features</category>
      <category domain="http://www.securityratty.com/tag/banks">banks</category>
      <category domain="http://www.securityratty.com/tag/banks agree">banks agree</category>
      <category domain="http://www.securityratty.com/tag/secure software">secure software</category>
      <category domain="http://www.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[OWASP Talk Q&A Notes]]></title>
      <link>http://www.securityratty.com/article/81fb1dfdb408580202cb30b424d72c9c</link>
      <guid>http://www.securityratty.com/article/81fb1dfdb408580202cb30b424d72c9c</guid>
      <description><![CDATA[On Monday I did a talk on Web Services security at the MSP OWASP. The talk was ok, but not as good as at RSA because I Brian Chess did a better job with some of the stories than me. What was really...]]></description>
      <content:encoded><![CDATA[<p>On Monday I did a talk on Web Services security at the MSP OWASP. The talk was ok, but not as good as at RSA because I Brian Chess did a better job with some of the stories than me. What was really good though was a number of questions and answers afterwards.</p><div><br><div>One person asked the old chestnut - "do we need to care about web services security if we are inside the firewall?" Now, I have heard this question many, many times in different ways, and this time my brain just shorted out, I basically said that I am not sure what difference it really makes. You don't get security from a firewall, you may get the ability to fire someone if they do something bad, but in most companies there is no "wall" and there sure isn't any "fire", at most they are speed bumps. I am *not* saying to remove them, they are part and parcel of how you operate a network but they are not really providing any additional security. Network firewalls are thought of as a security tools because they began as a security innovation and they are paid for out of the security budget.</div><br>

<p><br>
<a href="http://1raindrop.typepad.com/photos/uncategorized/2008/05/19/innovatecompare_2.png"><img  alt="Innovatecompare_2" title="Innovatecompare_2" src="http://1raindrop.typepad.com/1_raindrop/images/2008/05/19/innovatecompare_2.png" width="300" height="167" border="0"></a></p>
<div><a href="http://1raindrop.typepad.com/1_raindrop/2007/02/thinking_about_.html">Robert Garigue</a> said several years ago that network firewalls are part of network hygiene like brushing your teeth. Information security should not have to help people brush their teeth, and instead should operate like a dentist helping groups work more complex and risky issues. I have advised CISOs at several companies to off load the network firewall jockeys out of infosec and into network groups. Sometimes they listen. If so, the infosec group can focus on other issues instead of managing a Visio-driven "security" device. </div><br><div>Why Visio? Well, the main security property from a firewall is the scary flames and brick wall on Visio. And how do you know whether or not to open up a port? You just open the org chart (in Visio) and find the level of the person who is requesting the port be opened. If VP Then Yes. Is this security? Hardly.</div><br><div>So one last time - Web Services are used to provide access to your main systems (which live on mainframes, big RDBMS, SAP, ERP, CRM, and so on) these are the keys to the kingdom, and lots of apps need them. The whole point of Web Services is to make it easier to talk to them. So "inside" or "outside" the firewall, do you need to care about authentication, authorization, and auditing on the systems that run your entire business???</div><br><div>Another interesting question from the Q &amp; A from <a href="http://hursk.com/">Jon Passki</a> was on XML Security Gateways. We talked a fair bit about their utility in solving the aforementioned authentication, authorization, and auditing problems. I pulled up <a href="http://www.vordel.com/products/vx_gateway/">Vordel's gateway</a> and showed how to build security workflows to deploy security as a service. Jon asked could I ever imagine a Web services security architecture without a gateway? I said I think that they are not always the starting point but mid to long term they are definitely in basically any effective security architecture I can think of. Having a place to deploy, manage, and enforce policy that is separate the code solves a lot of real world problems. People are hung up on thinking about Web services programming like it has to be Web app programming (this happens in REST a lot), but there is another school of successful web apps, arguably the most successful, and its called email. </div><br><div>Email app architecture looks nothing like web app design. You wouldn't read every email sent to your address would you? Of course not, it goes through spam filters, virus checkers and so on. Further its a message oriented paradigm, and you know that unless its signed/encrypted with PGP/GPG security is suspect at best. So yeah, I think gateways are an hugely important part of a Web Services security architecture.</div><br><div>Finally, I can also not imagine going live when you are supporting multiple protocols and token types without a good testing strategy. Mark O'Neill recently <a href="http://radio.weblogs.com/0111797/2008/07/07.html#a115">blogged</a> something I recommend to all my clients - namely make sure you have security specific test cases, test harnesses and testing tools, like for example <a href="http://www.vordel.com/products/soapbox/">Vordel's Soapbox</a>.</div><br></div>]]></content:encoded>
      <pubDate>Fri, 11 Jul 2008 11:36:26 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/security">security</category>
      <category domain="http://www.securityratty.com/tag/additional security">additional security</category>
      <category domain="http://www.securityratty.com/tag/security workflows">security workflows</category>
      <category domain="http://www.securityratty.com/tag/security innovation">security innovation</category>
      <category domain="http://www.securityratty.com/tag/effective security architecture">effective security architecture</category>
      <category domain="http://www.securityratty.com/tag/web services">web services</category>
      <category domain="http://www.securityratty.com/tag/gateways">gateways</category>
      <category domain="http://www.securityratty.com/tag/web services security">web services security</category>
      <category domain="http://www.securityratty.com/tag/xml security gateways">xml security gateways</category>
      <source url="http://1raindrop.typepad.com/1_raindrop/2008/07/owasp-talk-qa-notes.html">OWASP Talk Q&amp;A Notes</source>
    </item>
    <item>
      <title><![CDATA[Opera Browser Integrates Malware Protection]]></title>
      <link>http://www.securityratty.com/article/ee1c35e6ac591be9f90a77c56f737b50</link>
      <guid>http://www.securityratty.com/article/ee1c35e6ac591be9f90a77c56f737b50</guid>
      <description><![CDATA[Opera, arguably one of the fastest rendering browsers available, is stepping up on security. With their version 9.5 release they are adding in malware protection courtesy of a deal that was struck...]]></description>
      <content:encoded><![CDATA[<p>Opera, arguably one of the fastest rendering browsers available, is stepping up on security. With their version 9.5 release they are adding in malware protection courtesy of a deal that was struck with Haute Secure. </p>
<p>From Tech Crunch:</p>
<blockquote><p>Haute Secure makes software that aggressively monitors and alerts users to malware sites. Besides the version that is being integrated into Opera, Haute is also available as a free plugin for Internet Explorer and Firefox. It differentiates itself from other blocking software by analyzing sites on the link level instead of at the domain level. This means that on very large sites like MySpace that contain a combination of legitimate material along with more sinister profiles, pages will be blocked on a case by case basis instead of simply banning the entire MySpace site.</p>
<p>Opera, while not nearly as popular as Internet Explorer or Firefox, has managed to gain something of a cult following since its original launch in 1996.</p></blockquote>
<p>Nice upgrade for the little browser that <strike>could</strike> can. If you haven&#8217;t tried it give Opera a test drive. I use it as one of my 3 regular browsers. </p>
<p><a href="http://www.techcrunch.com/2008/06/06/opera-browser-integrates-haute-secure-to-block-malware/">Article Link</a></p>

<p><a href="http://feeds.feedburner.com/~a/Liquidmatrix?a=ccqVjI"><img src="http://feeds.feedburner.com/~a/Liquidmatrix?i=ccqVjI" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=umS4NI"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=umS4NI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=bFYYri"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=bFYYri" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=q56kqi"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=q56kqi" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=NK0hGi"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=NK0hGi" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Liquidmatrix?a=kjqY5i"><img src="http://feeds.feedburner.com/~f/Liquidmatrix?i=kjqY5i" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/Liquidmatrix/~4/307382453" height="1" width="1"/>]]></content:encoded>
      <pubDate>Sun, 08 Jun 2008 10:27:05 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/opera">opera</category>
      <category domain="http://www.securityratty.com/tag/haute secure">haute secure</category>
      <category domain="http://www.securityratty.com/tag/haute">haute</category>
      <category domain="http://www.securityratty.com/tag/malware sites">malware sites</category>
      <category domain="http://www.securityratty.com/tag/internet explorer">internet explorer</category>
      <category domain="http://www.securityratty.com/tag/sites">sites</category>
      <category domain="http://www.securityratty.com/tag/myspace">myspace</category>
      <category domain="http://www.securityratty.com/tag/entire myspace site">entire myspace site</category>
      <category domain="http://www.securityratty.com/tag/malware protection courtesy">malware protection courtesy</category>
      <source url="http://feeds.feedburner.com/~r/Liquidmatrix/~3/307382453/">Opera Browser Integrates Malware Protection</source>
    </item>
    <item>
      <title><![CDATA[Fax Signatures]]></title>
      <link>http://www.securityratty.com/article/02253ed921c243d2881b5f9b92f99712</link>
      <guid>http://www.securityratty.com/article/02253ed921c243d2881b5f9b92f99712</guid>
      <description><![CDATA[Aren't fax signatures the weirdest thing? It's trivial to cut and paste -- with real scissors and glue -- anyone's signature onto a document so that it'll look real when faxed. There is so little...]]></description>
      <content:encoded><![CDATA[<p>Aren't fax signatures the weirdest thing? It's trivial to cut and paste -- with real scissors and glue -- anyone's signature onto a document so that it'll look real when faxed.  There is so little security in fax signatures that it's mind-boggling that anyone accepts them.</p>

<p>Yet people do, all the time. I've signed book contracts, credit card authorizations, nondisclosure agreements and all sorts of financial documents -- all by fax. I even have a scanned file of my signature on my computer, so I can virtually cut and paste it into documents and fax them directly from my computer without ever having to print them out.  What in the world is going on here?</p>

<p>And, more importantly, why are fax signatures still being used after years of experience?  Why aren't there many stories of signatures forged through the use of fax machines?</p>

<p>The answer comes from looking at fax signatures not as an isolated security measure, but in the context of the larger system. Fax signatures work because signed faxes exist within a broader communications context.</p>

<p>In a 2003 paper, <a href="http://www.dtc.umn.edu/~odlyzko/doc/econ.psych.security.pdf">"Economics, Psychology, and Sociology of Security,"</a> Professor Andrew Odlyzko looks at fax signatures and concludes:</p>

<blockquote>Although fax signatures have become widespread, their usage is restricted. They are not used for final contracts of substantial value, such as home purchases. That means that the insecurity of fax communications is not easy to exploit for large gain. Additional protection against abuse of fax insecurity is provided by the context in which faxes are used. There are records of phone calls that carry the faxes, paper trails inside enterprises and so on.  Furthermore, unexpected large financial transfers trigger scrutiny. As a result, successful frauds are not easy to carry out by purely technical means.</blockquote>

<p>He's right. Thinking back, there really aren't ways in which a criminal could use a forged document sent by fax to defraud me. I suppose an unscrupulous consulting client could forge my signature on an non-disclosure agreement and then sue me, but that hardly seems worth the effort. And if my broker received a fax document from me authorizing a money transfer to a Nigerian bank account, he would certainly call me before completing it.</p>

<p>Credit card signatures aren't verified in person, either -- and I can already buy things over the phone with a credit card -- so there are no new risks there, and Visa knows how to monitor transactions for fraud. Lots of companies accept purchase orders via fax, even for large amounts of stuff, but there's a physical audit trail, and the goods are shipped to a physical address -- probably one the seller has shipped to before. Signatures are kind of a business lubricant: mostly, they help move things along smoothly.</p>

<p>Except when they don't.</p>

<p>On October 30, 2004, Tristian Wilson was <a href="http://www.theeveningtimes.com/articles/2004/11/04/news/news5.txt">released</a> from a Memphis jail on the authority of a forged fax message. It wasn't even a particularly good forgery. It wasn't on the standard letterhead of the West Memphis Police Department. The name of the policeman who signed the fax was misspelled. And the time stamp on the top of the fax clearly showed that it was sent from a local McDonald's.</p>

<p>The success of this hack has nothing to do with the fact that it was sent over by fax. It worked because the jail had lousy verification procedures. They didn't notice any discrepancies in the fax. They didn't notice the phone number from which the fax was sent. They didn't call and verify that it was official. The jail was accustomed to getting release orders via fax, and just acted on this one without thinking. Would it have been any different had the forged release form been sent by mail or courier?</p>

<p>Yes, fax signatures always exist in context, but sometimes they are the linchpin within that context. If you can mimic enough of the context, or if those on the receiving end become complacent, you can get away with mischief.</p>

<p>Arguably, this is part of the security process. Signatures themselves are poorly defined.  Sometimes a document is valid even if not signed: A person with both hands in a cast can still buy a house. Sometimes a document is invalid even if signed: The signer might be drunk, or have a gun pointed at his head. Or he might be a minor. Sometimes a valid signature isn't enough; in the United States there is an entire infrastructure of "notary publics" who officially witness signed documents. When I started filing my tax returns electronically, I had to sign a document stating that I wouldn't be signing my income tax documents. And banks don't even bother verifying signatures on checks less than $30,000; it's cheaper to deal with fraud after the fact than prevent it.</p>

<p>Over the course of centuries, business and legal systems have slowly sorted out what types of additional controls are required around signatures, and in which circumstances.</p>

<p>Those same systems will be able to sort out fax signatures, too, but it'll be slow. And that's where there will be potential problems. Already fax is a declining technology. In a few years it'll be largely obsolete, replaced by PDFs sent over e-mail and other forms of electronic documentation. In the past, we've had time to figure out how to deal with new technologies. Now, by the time we institutionalize these measures, the technologies are likely to be obsolete.</p>

<p>What that means is people are likely to treat fax signatures -- or whatever replaces them -- exactly the same way as paper signatures. And sometimes that assumption will get them into trouble.</p>

<p>But it won't cause social havoc. Wilson's story is remarkable mostly because it's so exceptional. And even he was rearrested at his home less than a week later. Fax signatures may be new, but fake signatures have always been a possibility.  Our legal and business systems need to deal with the underlying problem -- false authentication -- rather than focus on the technology of the moment. Systems need to defend themselves against the possibility of fake signatures, regardless of how they arrive.</p>

<p>This essay <a href="http://www.wired.com/politics/security/commentary/securitymatters/2008/05/securitymatters_0529">previously appeared</a> on Wired.com.</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=AcrMPI"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=AcrMPI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=cTPMJI"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=cTPMJI" border="0"></img></a>
</div>]]></content:encoded>
      <pubDate>Tue, 03 Jun 2008 03:01:20 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/fax">fax</category>
      <category domain="http://www.securityratty.com/tag/fax signatures">fax signatures</category>
      <category domain="http://www.securityratty.com/tag/fax communications">fax communications</category>
      <category domain="http://www.securityratty.com/tag/fax insecurity">fax insecurity</category>
      <category domain="http://www.securityratty.com/tag/insecurity">insecurity</category>
      <category domain="http://www.securityratty.com/tag/fax machines">fax machines</category>
      <category domain="http://www.securityratty.com/tag/fax message">fax message</category>
      <category domain="http://www.securityratty.com/tag/treat fax signatures">treat fax signatures</category>
      <category domain="http://www.securityratty.com/tag/fax document">fax document</category>
      <source url="http://www.schneier.com/blog/archives/2008/06/fax_signatures.html">Fax Signatures</source>
    </item>
    <item>
      <title><![CDATA[Fax Signatures]]></title>
      <link>http://www.securityratty.com/article/7f8f07462740c577743663da07c14ae3</link>
      <guid>http://www.securityratty.com/article/7f8f07462740c577743663da07c14ae3</guid>
      <description><![CDATA[Aren't fax signatures the weirdest thing? It's trivial to cut and paste -- with real scissors and glue -- anyone's signature onto a document so that it'll look real when faxed. There is so little...]]></description>
      <content:encoded><![CDATA[<p>Aren't fax signatures the weirdest thing? It's trivial to cut and paste -- with real scissors and glue -- anyone's signature onto a document so that it'll look real when faxed.  There is so little security in fax signatures that it's mind-boggling that anyone accepts them.</p>

<p>Yet people do, all the time. I've signed book contracts, credit card authorizations, nondisclosure agreements and all sorts of financial documents -- all by fax. I even have a scanned file of my signature on my computer, so I can virtually cut and paste it into documents and fax them directly from my computer without ever having to print them out.  What in the world is going on here?</p>

<p>And, more importantly, why are fax signatures still being used after years of experience?  Why aren't there many stories of signatures forged through the use of fax machines?</p>

<p>The answer comes from looking at fax signatures not as an isolated security measure, but in the context of the larger system. Fax signatures work because signed faxes exist within a broader communications context.</p>

<p>In a 2003 paper, <a href="http://www.dtc.umn.edu/~odlyzko/doc/econ.psych.security.pdf">"Economics, Psychology, and Sociology of Security,"</a> Professor Andrew Odlyzko looks at fax signatures and concludes:</p>

<blockquote>Although fax signatures have become widespread, their usage is restricted. They are not used for final contracts of substantial value, such as home purchases. That means that the insecurity of fax communications is not easy to exploit for large gain. Additional protection against abuse of fax insecurity is provided by the context in which faxes are used. There are records of phone calls that carry the faxes, paper trails inside enterprises and so on.  Furthermore, unexpected large financial transfers trigger scrutiny. As a result, successful frauds are not easy to carry out by purely technical means.</blockquote>

<p>He's right. Thinking back, there really aren't ways in which a criminal could use a forged document sent by fax to defraud me. I suppose an unscrupulous consulting client could forge my signature on an non-disclosure agreement and then sue me, but that hardly seems worth the effort. And if my broker received a fax document from me authorizing a money transfer to a Nigerian bank account, he would certainly call me before completing it.</p>

<p>Credit card signatures aren't verified in person, either -- and I can already buy things over the phone with a credit card -- so there are no new risks there, and Visa knows how to monitor transactions for fraud. Lots of companies accept purchase orders via fax, even for large amounts of stuff, but there's a physical audit trail, and the goods are shipped to a physical address -- probably one the seller has shipped to before. Signatures are kind of a business lubricant: mostly, they help move things along smoothly.</p>

<p>Except when they don't.</p>

<p>On October 30, 2004, Tristian Wilson was <a href="http://www.theeveningtimes.com/articles/2004/11/04/news/news5.txt">released</a> from a Memphis jail on the authority of a forged fax message. It wasn't even a particularly good forgery. It wasn't on the standard letterhead of the West Memphis Police Department. The name of the policeman who signed the fax was misspelled. And the time stamp on the top of the fax clearly showed that it was sent from a local McDonald's.</p>

<p>The success of this hack has nothing to do with the fact that it was sent over by fax. It worked because the jail had lousy verification procedures. They didn't notice any discrepancies in the fax. They didn't notice the phone number from which the fax was sent. They didn't call and verify that it was official. The jail was accustomed to getting release orders via fax, and just acted on this one without thinking. Would it have been any different had the forged release form been sent by mail or courier?</p>

<p>Yes, fax signatures always exist in context, but sometimes they are the linchpin within that context. If you can mimic enough of the context, or if those on the receiving end become complacent, you can get away with mischief.</p>

<p>Arguably, this is part of the security process. Signatures themselves are poorly defined.  Sometimes a document is valid even if not signed: A person with both hands in a cast can still buy a house. Sometimes a document is invalid even if signed: The signer might be drunk, or have a gun pointed at his head. Or he might be a minor. Sometimes a valid signature isn't enough; in the United States there is an entire infrastructure of "notary publics" who officially witness signed documents. When I started filing my tax returns electronically, I had to sign a document stating that I wouldn't be signing my income tax documents. And banks don't even bother verifying signatures on checks less than $30,000; it's cheaper to deal with fraud after the fact than prevent it.</p>

<p>Over the course of centuries, business and legal systems have slowly sorted out what types of additional controls are required around signatures, and in which circumstances.</p>

<p>Those same systems will be able to sort out fax signatures, too, but it'll be slow. And that's where there will be potential problems. Already fax is a declining technology. In a few years it'll be largely obsolete, replaced by PDFs sent over e-mail and other forms of electronic documentation. In the past, we've had time to figure out how to deal with new technologies. Now, by the time we institutionalize these measures, the technologies are likely to be obsolete.</p>

<p>What that means is people are likely to treat fax signatures -- or whatever replaces them -- exactly the same way as paper signatures. And sometimes that assumption will get them into trouble.</p>

<p>But it won't cause social havoc. Wilson's story is remarkable mostly because it's so exceptional. And even he was rearrested at his home less than a week later. Fax signatures may be new, but fake signatures have always been a possibility.  Our legal and business systems need to deal with the underlying problem -- false authentication -- rather than focus on the technology of the moment. Systems need to defend themselves against the possibility of fake signatures, regardless of how they arrive.</p>

<p>This essay <a href="http://www.wired.com/politics/security/commentary/securitymatters/2008/05/securitymatters_0529">previously appeared</a> on Wired.com.</p>

<p>EDITED TO ADD (6/3): 2005 story, "<a href="http://www.law.com/jsp/article.jsp?id=1124960718229">Federal Jury Convicts N.Y. Attorney of Faking Judge's Order</a>."</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=Cp1KKI"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=Cp1KKI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=vxhJ2I"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=vxhJ2I" border="0"></img></a>
</div>]]></content:encoded>
      <pubDate>Tue, 03 Jun 2008 03:01:20 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/fax">fax</category>
      <category domain="http://www.securityratty.com/tag/fax signatures">fax signatures</category>
      <category domain="http://www.securityratty.com/tag/fax communications">fax communications</category>
      <category domain="http://www.securityratty.com/tag/fax insecurity">fax insecurity</category>
      <category domain="http://www.securityratty.com/tag/insecurity">insecurity</category>
      <category domain="http://www.securityratty.com/tag/fax machines">fax machines</category>
      <category domain="http://www.securityratty.com/tag/fax message">fax message</category>
      <category domain="http://www.securityratty.com/tag/treat fax signatures">treat fax signatures</category>
      <category domain="http://www.securityratty.com/tag/fax document">fax document</category>
      <source url="http://www.schneier.com/blog/archives/2008/06/fax_signatures_1.html">Fax Signatures</source>
    </item>
    <item>
      <title><![CDATA[Why Do We Accept Signatures by Fax?]]></title>
      <link>http://www.securityratty.com/article/ec46457fe9307589ce91fe4fedfce2af</link>
      <guid>http://www.securityratty.com/article/ec46457fe9307589ce91fe4fedfce2af</guid>
      <description><![CDATA[Aren't fax signatures the weirdest thing? It's trivial to cut and paste -- with real scissors and glue -- anyone's signature onto a document so that it'll look real when faxed. There is so little...]]></description>
      <content:encoded><![CDATA[<p>Aren't fax signatures the weirdest thing? It's trivial to cut and paste -- with real scissors and glue -- anyone's signature onto a document so that it'll look real when faxed.  There is so little security in fax signatures that it's mind-boggling that anyone accepts them. 
</p>

<p>
Yet people do, all the time. I've signed book contracts, credit card authorizations, nondisclosure agreements and all sorts of financial documents -- all by fax. I even have a scanned file of my signature on my computer, so I can virtually cut and paste it into documents and fax them directly from my computer without ever having to print them out.  What in the world is going on here?
</p>

<p>
And, more importantly, why are fax signatures still being used after years of experience?  Why aren't there many stories of signatures forged through the use of fax machines?
</p>

<p>
The answer comes from looking at fax signatures not as an isolated security measure, but in the context of the larger system. Fax signatures work because signed faxes exist within a broader communications context.
</p>

<p>
In a 2003 paper, <cite><a href="http://www.dtc.umn.edu/~odlyzko/doc/econ.psych.security.pdf">Economics, Psychology, and Sociology of Security</a></cite>, professor Andrew Odlyzko looks at fax signatures and concludes:
</p>

<div class="blockquote">
Although fax signatures have become widespread, their usage is restricted. They are not used for final contracts of substantial value, such as home purchases. That means that the insecurity of fax communications is not easy to exploit for large gain. Additional protection against abuse of fax insecurity is provided by the context in which faxes are used. There are records of phone calls that carry the faxes, paper trails inside enterprises and so on.  Furthermore, unexpected large financial transfers trigger scrutiny. As a result, successful frauds are not easy to carry out by purely technical means.
</div> 
<p>
<p>
He's right. Thinking back, there really aren't ways in which a criminal could use a forged document sent by fax to defraud me. I suppose an unscrupulous consulting client could forge my signature on an non-disclosure agreement and then sue me, but that hardly seems worth the effort. And if my broker received a fax document from me authorizing a money transfer to a Nigerian bank account, he would certainly call me before completing it. 
</p>

<p>
Credit card signatures aren't verified in person, either -- and I can already buy things over the phone with a credit card -- so there are no new risks there, and Visa knows how to monitor transactions for fraud. Lots of companies accept purchase orders via fax, even for large amounts of stuff, but there's a physical audit trail, and the goods are shipped to a physical address -- probably one the seller has shipped to before. Signatures are kind of a business lubricant: mostly, they help move things along smoothly.
</p>
<p>
Except when they don't.
</p>
<p>
On October 30, 2004, Tristian Wilson was <a href="http://www.theeveningtimes.com/articles/2004/11/04/news/news5.txt">released</a> from a Memphis jail on the authority of a forged fax message. It wasn't even a particularly good forgery. It wasn't on the standard letterhead of the West Memphis Police Department. The name of the policeman who signed the fax was misspelled. And the time stamp on the top of the fax clearly showed that it was sent from a local McDonald's.
</p>

<p>
The success of this hack has nothing to do with the fact that it was sent over by fax. It worked because the jail had lousy verification procedures. They didn't notice any discrepancies in the fax. They didn't notice the phone number from which the fax was sent. They didn't call and verify that it was official. The jail was accustomed to getting release orders via fax, and just acted on this one without thinking. Would it have been any different had the forged release form been sent by mail or courier?
</p>
<!--pagebreak-->
<p>
Yes, fax signatures always exist in context, but sometimes they are the linchpin within that context. If you can mimic enough of the context, or if those on the receiving end become complacent, you can get away with mischief.
</p>
<p>
Arguably, this is part of the security process. Signatures themselves are poorly defined.  Sometimes a document is valid even if not signed: A person with both hands in a cast can still buy a house. Sometimes a document is invalid even if signed: The signer might be drunk, or have a gun pointed at his head. Or he might be a minor. Sometimes a valid signature isn't enough; in the United States there is an entire infrastructure of "notary publics" who officially witness signed documents. When I started filing my tax returns electronically, I had to sign a document stating that I wouldn't be signing my income tax documents. And banks don't even bother verifying signatures on checks less than $30,000; it's cheaper to deal with fraud after the fact than prevent it.
</p>

<p>
Over the course of centuries, business and legal systems have slowly sorted out what types of additional controls are required around signatures, and in which circumstances.
</p>

<p>
Those same systems will be able to sort out fax signatures, too, but it'll be slow. And that's where there will be potential problems. Already fax is a declining technology. In a few years it'll be largely obsolete, replaced by PDFs sent over e-mail and other forms of electronic documentation. In the past, we've had time to figure out how to deal with new technologies. Now, by the time we institutionalize these measures, the technologies are likely to be obsolete.
</p>
<p>
What that means is people are likely to treat fax signatures -- or whatever replaces them -- exactly the same way as paper signatures. And sometimes that assumption will get them into trouble.
</p>
<p>
But it won't cause social havoc. Wilson's story is remarkable mostly because it's so exceptional. And even he was rearrested at his home less than a week later. Fax signatures may be new, but fake signatures have always been a possibility.  Our legal and business systems need to deal with the underlying problem -- false authentication -- rather than focus on the technology of the moment. Systems need to defend themselves against the possibility of fake signatures, regardless of how they arrive.
</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;"/>
      <a href="http://www.pheedo.com/click.phdo?s=7ab87f90e62b86d6fc020a727bf5fac9"><img alt="" style="border: 0;" border="0" src="http://www.pheedo.com/img.phdo?s=7ab87f90e62b86d6fc020a727bf5fac9"/></a>
  <img src="http://www.pheedo.com/feeds/tracker.php?i=7ab87f90e62b86d6fc020a727bf5fac9" style="display: none;" border="0" height="1" width="1" alt=""/><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=RZ3SLH"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=RZ3SLH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=kVmJ6h"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=kVmJ6h" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=u6RKCh"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=u6RKCh" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=ZotVrH"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=ZotVrH" border="0"></img></a>
 <a href="http://feeds.wired.com/~f/wired/politics/security?a=eaNyrH"><img src="http://feeds.wired.com/~f/wired/politics/security?i=eaNyrH" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=tf8uVh"><img src="http://feeds.wired.com/~f/wired/politics/security?i=tf8uVh" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=QWxnGh"><img src="http://feeds.wired.com/~f/wired/politics/security?i=QWxnGh" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=MqAv8H"><img src="http://feeds.wired.com/~f/wired/politics/security?i=MqAv8H" border="0"></img></a> </div><img src="http://feeds.feedburner.com/~r/wired/politics/privacy/~4/300217736" height="1" width="1"/><img src="http://feeds.wired.com/~r/wired/politics/security/~4/300217738" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 28 May 2008 21:00:00 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/fax">fax</category>
      <category domain="http://www.securityratty.com/tag/fax communications">fax communications</category>
      <category domain="http://www.securityratty.com/tag/fax insecurity">fax insecurity</category>
      <category domain="http://www.securityratty.com/tag/insecurity">insecurity</category>
      <category domain="http://www.securityratty.com/tag/fax machines">fax machines</category>
      <category domain="http://www.securityratty.com/tag/fax message">fax message</category>
      <category domain="http://www.securityratty.com/tag/treat fax signatures">treat fax signatures</category>
      <category domain="http://www.securityratty.com/tag/fax document">fax document</category>
      <category domain="http://www.securityratty.com/tag/document">document</category>
      <source url="http://feeds.wired.com/~r/wired/politics/security/~3/300217738/securitymatters_0529">Why Do We Accept Signatures by Fax?</source>
    </item>
    <item>
      <title><![CDATA[Wiretapping is really, really easy]]></title>
      <link>http://www.securityratty.com/article/2a6ae9e8f0ccf2b07465fd919b086594</link>
      <guid>http://www.securityratty.com/article/2a6ae9e8f0ccf2b07465fd919b086594</guid>
      <description><![CDATA[Ask Pellicano, whose case went to the jury last week, and offered arguably more for people who enjoy talk of encryption software, code-wiping booby traps or the low-tech secrets of phone company...]]></description>
      <content:encoded><![CDATA[Ask Pellicano, whose case went to the jury last week, and offered arguably more for people who enjoy talk of encryption software, code-wiping booby traps or the low-tech secrets of phone company networks than anyone else.]]></content:encoded>
      <pubDate>Mon, 05 May 2008 10:44:04 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/phone company networks">phone company networks</category>
      <category domain="http://www.securityratty.com/tag/enjoy talk">enjoy talk</category>
      <category domain="http://www.securityratty.com/tag/encryption software">encryption software</category>
      <category domain="http://www.securityratty.com/tag/low-tech secrets">low-tech secrets</category>
      <category domain="http://www.securityratty.com/tag/booby traps">booby traps</category>
      <category domain="http://www.securityratty.com/tag/week">week</category>
      <category domain="http://www.securityratty.com/tag/arguably">arguably</category>
      <category domain="http://www.securityratty.com/tag/pellicano">pellicano</category>
      <category domain="http://www.securityratty.com/tag/people">people</category>
      <source url="http://digg.com/security/Wiretapping_is_really_really_easy">Wiretapping is really, really easy</source>
    </item>
    <item>
      <title><![CDATA[Opinion: Promise for protecting laptops]]></title>
      <link>http://www.securityratty.com/article/b884bed85451e5601df3e4981d982afc</link>
      <guid>http://www.securityratty.com/article/b884bed85451e5601df3e4981d982afc</guid>
      <description><![CDATA[Dealing with laptop protection is arguably the least favorite job for IT managers, and indications are that laptop sales will surpass desktop sales, so the situation is likely to only worsen. But...]]></description>
      <content:encoded><![CDATA[Dealing with laptop protection is arguably the least favorite job for IT managers, and indications are that laptop sales will surpass desktop sales, so the situation is likely to only worsen. But upcoming chip-level antitheft technology and remote outsourced backup services promise relief.
<p><a href="http://feeds.computerworld.com/~a/Computerworld/Security/News?a=Zhkwht"><img src="http://feeds.computerworld.com/~a/Computerworld/Security/News?i=Zhkwht" border="0"></img></a></p><img src="http://feeds.computerworld.com/~r/Computerworld/Security/News/~4/280999425" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 30 Apr 2008 09:00:00 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/surpass desktop sales">surpass desktop sales</category>
      <category domain="http://www.securityratty.com/tag/chip-level antitheft technology">chip-level antitheft technology</category>
      <category domain="http://www.securityratty.com/tag/favorite job">favorite job</category>
      <category domain="http://www.securityratty.com/tag/laptop protection">laptop protection</category>
      <category domain="http://www.securityratty.com/tag/laptop sales">laptop sales</category>
      <category domain="http://www.securityratty.com/tag/situation">situation</category>
      <category domain="http://www.securityratty.com/tag/arguably">arguably</category>
      <category domain="http://www.securityratty.com/tag/remote">remote</category>
      <category domain="http://www.securityratty.com/tag/indications">indications</category>
      <source url="http://feeds.computerworld.com/~r/Computerworld/Security/News/~3/280999425/article.do">Opinion: Promise for protecting laptops</source>
    </item>
    <item>
      <title><![CDATA[Promise for protecting laptops]]></title>
      <link>http://www.securityratty.com/article/a0fad6510198ccd40f910c22e2379618</link>
      <guid>http://www.securityratty.com/article/a0fad6510198ccd40f910c22e2379618</guid>
      <description><![CDATA[Among the multitude of data protection challenges facing IT organizations, arguably the least favorite for IT managers is dealing with laptop systems. Each week we read more horror stories about lost...]]></description>
      <content:encoded><![CDATA[Among the multitude of data protection challenges facing IT organizations, arguably the least favorite for IT managers is dealing with laptop systems. Each week we read more horror stories about lost notebook computers and potentially compromised data as organizations attempt to grapple with what is literally a moving target.<p><NOLAYER>
<IFRAME id="rss" src="http://ad.doubleclick.net/adi/idg.us.nwf.rss/security;sz=468x60;ord=16435?" width="468" height="60" frameborder="no" border="0" marginwidth="0" marginheight="0" scrolling="no">
<A href="http://ad.doubleclick.net/jump/idg.us.nwf.rss/security;sz=468x60;ord=16435?">
<IMG src="http://ad.doubleclick.net/ad/idg.us.nwf.rss/security;sz=468x60;ord=16435?" border="0" width="468" height="60"></A>
</IFRAME>
</NOLAYER></p>]]></content:encoded>
      <pubDate>Tue, 29 Apr 2008 20:00:00 +0000</pubDate>
      <category domain="http://www.securityratty.com/tag/data protection challenges">data protection challenges</category>
      <category domain="http://www.securityratty.com/tag/data">data</category>
      <category domain="http://www.securityratty.com/tag/organizations attempt">organizations attempt</category>
      <category domain="http://www.securityratty.com/tag/organizations">organizations</category>
      <category domain="http://www.securityratty.com/tag/lost notebook computers">lost notebook computers</category>
      <category domain="http://www.securityratty.com/tag/laptop systems">laptop systems</category>
      <category domain="http://www.securityratty.com/tag/horror stories">horror stories</category>
      <category domain="http://www.securityratty.com/tag/week">week</category>
      <category domain="http://www.securityratty.com/tag/arguably">arguably</category>
      <source url="http://www.networkworld.com/news/2008/043008-promise-for-protecting.html?fsrc=rss-security">Promise for protecting laptops</source>
    </item>
  </channel>
</rss>
