<?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: perpetrators]]></title>
    <link>http://securityratty.com/tag/perpetrators</link>
    <description></description>
    <pubDate>Mon, 03 Dec 2007 12:51:00 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Update on Cybercrime law by Congress]]></title>
      <link>http://securityratty.com/article/ca3f6d70b153df19737cbb787979943a</link>
      <guid>http://securityratty.com/article/ca3f6d70b153df19737cbb787979943a</guid>
      <description><![CDATA[Adding Keyloggers to punishable offenses makes it a whole new playing field for all


clipped from www.informationweek.com

Congress Extends Cybercrime Laws



The amendment criminalizes the use of...]]></description>
      <content:encoded><![CDATA[<div > Adding Keyloggers to punishable offenses makes it a whole new playing field for all. </div>
<table cellpadding="0" cellspacing="0" width="100%" style="margin: 12px 0px; font-family: arial; color: #333333; background: #ffffff; border: solid 4px #e5e5e5; width: 100%; clear: left;">
<tr>
<td valign="top">
<table cellpadding="0" cellspacing="0" width="100%" class="CM_CTB_Content_Wrap" style="margin: 0px; padding: 0px;background-color: #ffffff;">
<tr>
<td valign="top">
<table cellpadding="0" cellspacing="0" width="100%" style="border-bottom: solid 1px #dcdcdc; white-space: nowrap; margin-bottom: 8px; background-color: #eeeeee ;background-image: url(http://clipmarks.com/images/source-bg.gif); background-repeat: repeat-x; height: 24px; line-height: 24px; vertical-align: middle; padding-bottom: 4px; color: #666666; font-size: 10px;">
<tr>
<td valign="top"><a href="http://clipmarks.com/clipmark/A292722A-C96A-4D67-A2DA-9BD42FB6EA88/" title="go to this clipmark"><img src="http://content.clipmarks.com/blog_icon/0cc2f612-d596-4310-a7c7-bdc926c90945/A292722A-C96A-4D67-A2DA-9BD42FB6EA88/" alt="" width="19" height="19" border="0" style="vertical-align: middle; margin: 0px 4px; display: inline; border: none; float:none;" /></a>clipped from <a title="http://www.informationweek.com/news/security/cybercrime/showArticle.jhtml?articleID=210602182" href="http://www.informationweek.com/news/security/cybercrime/showArticle.jhtml?articleID=210602182" style="font-size: 11px;">www.informationweek.com</a></td>
</tr>
</table>
<table cellpadding="0" cellspacing="0" width="100%" style="text-align: left; padding: 0px 8px; margin: 4px 0px 8px 0px; background: transparent; border: none;">
<tr>
<td valign="top"><!-- CLIPPED FROM: http://www.informationweek.com/news/security/cybercrime/showArticle.jhtml?articleID=210602182 -->
<div style="margin: 4px 0px; color: #000000; font-size: 20px;">
Congress Extends Cybercrime Laws
</div>
</td>
</tr>
</table>
<div style="height: 2px; font-size: 2px; background: #dcdcdc; border-bottom: solid 1px #f5f5f5; margin: 2px 4px;"></div>
<table cellpadding="0" cellspacing="0" width="100%" style="text-align: left; padding: 0px 8px; margin: 4px 0px 8px 0px; background: transparent; border: none;">
<tr>
<td valign="top"><!-- CLIPPED FROM: http://www.informationweek.com/news/security/cybercrime/showArticle.jhtml?articleID=210602182 --><P><br />
The amendment criminalizes the use of malicious spyware and keystroke loggers to damage a computer, by eliminating a requirement that the loss exceed $5,000 and making it a misdemeanor to send <A href="http://www.techweb.com/encyclopedia/defineterm.jhtml?term=spyware&#038;x=&#038;y=">spyware</A> that causes any loss. Perpetrators would face fines and up to one year in prison.<br />
</P></td>
</tr>
</table>
</td>
</tr>
</table>
<div style="margin: 0px 6px 6px 4px;">
<table style="font-size: 11px;border-spacing: 0px;padding: 0px;" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td style="background:transparent;border-width:0px;padding:0px;">&nbsp;</td>
<td align="right" style="background:transparent;border-width:0px;padding:0px;width:107px" width="107"><a href="http://clipmarks.com/share/A292722A-C96A-4D67-A2DA-9BD42FB6EA88/blog/" title="blog or email this clip"><img src="http://content9.clipmarks.com/images/c2b-foot.png" border="0" alt="blog it" width="107" height="17" style="border-width:0px;padding:0px;margin:0px;" /></a></td>
</tr>
</table>
</div>
</td>
</tr>
</table>
<BR/><MAP name="bdv_RSS_Ad_170908113115"><AREA alt="Feed Ads By BidVertiser.com" shape="poly" coords="0,0,467,0,467,45,315,45,315,59,0,59" href="http://secure.bidvertiser.com/performance/bdv_rss_rd.dbm?pid=165886&amp;bid=400950&amp;PHS=170908113115&amp;click=1" target="_blank" /><AREA alt="Feed Ads By BidVertiser.com" shape="rect" coords="315,45,467,59" href="http://www.bidvertiser.com/bdv/bidvertiser/bdv_ref.dbm?Ref_PID=165886&amp;Ref_Option=main&amp;source=90614506" target="_blank" /></MAP><P><a href="http://secure.bidvertiser.com/performance/bdv_rss_rd.dbm?pid=165886&amp;bid=400950&amp;PHS=170908113115&amp;click=1" target="_blank"><IMG src="http://bdv.bidvertiser.com/BidVertiser.dbm?pid=165886&amp;bid=400950&amp;PHS=170908113115&amp;rssimage=1&amp;rSRC=2" border="0" usemap="#bdv_RSS_Ad_170908113115" /></a></P>]]></content:encoded>
      <pubDate>Wed, 17 Sep 2008 19:31:15 +0000</pubDate>
      <category domain="http://securityratty.com/tag/spyware">spyware</category>
      <category domain="http://securityratty.com/tag/malicious spyware">malicious spyware</category>
      <category domain="http://securityratty.com/tag/keystroke loggers">keystroke loggers</category>
      <category domain="http://securityratty.com/tag/loss">loss</category>
      <category domain="http://securityratty.com/tag/punishable offenses">punishable offenses</category>
      <category domain="http://securityratty.com/tag/damage">damage</category>
      <category domain="http://securityratty.com/tag/amendment">amendment</category>
      <category domain="http://securityratty.com/tag/keyloggers">keyloggers</category>
      <category domain="http://securityratty.com/tag/perpetrators">perpetrators</category>
      <source url="http://spywarebiz.com/spywarebizblog/?p=617">Update on Cybercrime law by Congress</source>
    </item>
    <item>
      <title><![CDATA[Corporate Identity Theft]]></title>
      <link>http://securityratty.com/article/57c21b4d57a8ae63a7ec8f43043877e8</link>
      <guid>http://securityratty.com/article/57c21b4d57a8ae63a7ec8f43043877e8</guid>
      <description><![CDATA[I remember a talk by the value investor Mason Hawkins (Longleaf Funds) where someone asked him about investing overseas. He answered that he does, but mainly in places where the British flag flew at...]]></description>
      <content:encoded><![CDATA[<p>I remember a <a href="http://www.bengrahaminvesting.ca/Resources/videos.htm#hawkins">talk</a>&#160;by the value investor&#160;<a href="http://en.wikipedia.org/wiki/Mason_Hawkins">Mason Hawkins</a>&#160;(Longleaf Funds) where someone asked him about investing overseas. He answered that he does, but mainly in places where the British flag flew at some point, where there is a rule of law. Here is one example of what he is worried about and why investing in places where your assets have no legal protection does not give the investor a margin of safety.</p><div>Hermitage Fund was until recently the largest fund in Russia. From the Business Week story<a href="http://hermitagefund.com/index.pl/news/article.html?id=895"> &quot;Hijacking the Hermitage Fund&quot;</a></div><br /><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><p>Corruption, intimidation, robbery, violent assault, forgery, large-scale fraud. No, not the subject of the latest John Grisham novel, but sensational allegations, made public Apr. 4 by Hermitage Capital Management -- until recently the largest foreign portfolio investor in Russia. In a detailed and damning report, titled Criminal Justice -- Russian-Style, Hermitage alleges the fund&#39;s Russian subsidiaries have fallen victim to an elaborate con designed to defraud the fund of hundreds of millions of dollars.&#160;<br />&#160;&#160;<br />The most sensational part of Hermitage&#39;s allegations is that the attempted larceny was carried out with the direct connivance of officials in the Russian police. Hermitage alleges the police seized documents and equipment that were instrumental to the attempted fraud, which involved bogus court cases based on forged documents, the aim of which was to sue Hermitage subsidiaries for hundreds of millions of dollars. &quot;The most shocking thing is not that there are corporate raiders in Russia who attempt to steal your shares,&quot; says Jamison Firestone, managing partner of Firestone Duncan, Hermitage&#39;s law firm. &quot;The shocking thing is that the police worked hand-in-hand with them, and actually performed the theft of the documents so that the corporate raiders could then do their work.&quot;</p></blockquote><div><br /><div>From the most recent Hermitage Fund letter, here is the current state:</div><br /><br /></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><p>So the two-pronged scam worked in one area and failed in another. The perpetrators weren’t able to steal the assets from us based on the fake court claims, but they were able to steal $230 million from the Russian government by filing amended tax returns on behalf of our stolen companies. What makes this story even more shocking is that we filed six 255-page criminal complaints with the Russian authorities in December last year, one month before the tax fraud took place, and they did nothing to stop it. Two complaints were sent to the Russian General Prosecutor, two to the Russian State Investigative Committee and two to the Internal Affairs Department of the Interior Ministry. There was enough information to prevent the fraud and indict a number of people behind it if the government had acted.&#160;</p><p>Instead of doing anything to save the Russian state from this highly sophisticated and organized looting, two of our complaints were thrown out immediately; two were returned to the same Interior Ministry official we were complaining about (essentially, he was being asked to “investigate himself”); and one was thrown out for “lack of any crime committed.” Only one complaint was taken seriously. It was taken up by the Russian State Investigative Committee in early February, but before it could get any traction, the case was lowered to the South region of the Moscow district of the State Investigative Committee (the lowest level of the Committee) and by June, another senior Interior Ministry official whom we had named in our complaint had joined the “investigation” team (again, to “investigate himself”). To this day there has been no serious response by the Russian authorities to this massive fraud against the Russian state.&#160;</p><p>As we described in our April letter, the problem of corporate “raiding” is now so endemic in Russia that President Medvedev speaks about it as one of the biggest problems faced by Russian businesses. In this case, raiders have taken this problem to a new and absurd extreme by “raiding” the Russian state itself and so far getting away with it. Together with HSBC, we will shortly be filing new criminal complaints with the Russian General Prosecutor and Russian State Investigative Committee as well as with many law enforcement authorities outside of Russia. It is hard to predict what will happen next in this unfolding and unbelievable saga, but as always we will keep you updated on any further developments as they arise.</p></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><br /></blockquote><p>Of course we see individual identity theft on a regular basis (actually as Ross Anderson points out its not really identity theft but poor controls on the bank&#39;s parts using SSNs as secrets and so on), but you dont see a major corporation stolen every day.</p>]]></content:encoded>
      <pubDate>Sat, 16 Aug 2008 05:58:30 +0000</pubDate>
      <category domain="http://securityratty.com/tag/russian police">russian police</category>
      <category domain="http://securityratty.com/tag/police">police</category>
      <category domain="http://securityratty.com/tag/russian">russian</category>
      <category domain="http://securityratty.com/tag/russian government">russian government</category>
      <category domain="http://securityratty.com/tag/government">government</category>
      <category domain="http://securityratty.com/tag/identity theft">identity theft</category>
      <category domain="http://securityratty.com/tag/russian-style">russian-style</category>
      <category domain="http://securityratty.com/tag/hermitage">hermitage</category>
      <category domain="http://securityratty.com/tag/fund">fund</category>
      <source url="http://1raindrop.typepad.com/1_raindrop/2008/08/corporate-identity-theft.html">Corporate Identity Theft</source>
    </item>
    <item>
      <title><![CDATA[Bust-out schemes are a fraud to make you go bust]]></title>
      <link>http://securityratty.com/article/275b74d12454e0fb2722e7b6bd27479a</link>
      <guid>http://securityratty.com/article/275b74d12454e0fb2722e7b6bd27479a</guid>
      <description><![CDATA[Increasing globalization is proving to be a boon for perpetrators of a type of fraud known as a &quot;bust-out scheme.&quot; This kind of fraud, commonplace in the computer and electronics industry, victimizes...]]></description>
      <content:encoded><![CDATA[Increasing globalization is proving to be a boon for perpetrators of a type of fraud known as a "bust-out scheme." This kind of fraud, commonplace in the computer and electronics industry, victimizes legitimate manufacturers and retailers. People in the industry should be aware of the particulars of such schemes so they can guard against them.]]></content:encoded>
      <pubDate>Sun, 08 Jun 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/fraud">fraud</category>
      <category domain="http://securityratty.com/tag/industry">industry</category>
      <category domain="http://securityratty.com/tag/electronics industry">electronics industry</category>
      <category domain="http://securityratty.com/tag/schemes">schemes</category>
      <category domain="http://securityratty.com/tag/bust-out scheme">bust-out scheme</category>
      <category domain="http://securityratty.com/tag/retailers">retailers</category>
      <category domain="http://securityratty.com/tag/manufacturers">manufacturers</category>
      <category domain="http://securityratty.com/tag/perpetrators">perpetrators</category>
      <category domain="http://securityratty.com/tag/commonplace">commonplace</category>
      <source url="http://www.networkworld.com/news/2008/060608-bust-out-schemes-are-a-fraud.html?fsrc=rss-security">Bust-out schemes are a fraud to make you go bust</source>
    </item>
    <item>
      <title><![CDATA[UltimateBet cheating goes undetected for almost 21 months]]></title>
      <link>http://securityratty.com/article/ab86750c9ca2ca89b4459be51f0a8dee</link>
      <guid>http://securityratty.com/article/ab86750c9ca2ca89b4459be51f0a8dee</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
5/29/08

Organization
Tokwiro Enterprises ENRG

Tokwiro Enterprises Enrg&quot; is a recognized Mohawk owned and controlled, gaming sole proprietorship,...]]></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/ultimatebet.jpg" align="right" height="102" width="120"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>5/29/08 <br><br><span style="font-weight: bold;">Organization: </span><br>Tokwiro Enterprises ENRG*<br><br><font size="1">*"Tokwiro Enterprises Enrg" is a recognized Mohawk owned and controlled, gaming sole proprietorship, presently undergoing a licencing process with the "Kahnawake Gaming Commission" ("KGC"), which was itself established on the 10th day of June, 1996. (Source: <a href="http://www.ultimatebet.com/about-us)</font><br><br><span">www.ultimatebet.com/about-us)</font><br><br><span</a> style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.ultimatebet.com/">UltimateBet</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>"hole card information during live play" resulting is financial loss<br><br><span style="font-weight: bold;">Breach Description:</span><br>"MONTREAL, CANADA (MAY 29, 2008) --- Tokwiro Enterprises ENRG ("Tokwiro"), proprietors of UltimateBet.com ("UltimateBet"), one of the world's largest online card rooms, today announced the results of its lengthy investigation into allegations of unfair play, which was triggered by concerns about an account named 'NioNio'."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.ultimatebet.com/poker-news/2008/may/NioNio-Findings">UltimateBet Statement</a> (full statement text below)<br><a href="http://www.cjad.com/news/565/729153">CJAD NewsTalk Radio</a> <br><a href="http://www.cardplayer.com/poker-news/article/4279/owner-of-ultimatebet-confirms-security-breach">Card Player</a> <br><a href="http://www.pokerlistings.com/ultimatebet-wraps-investigation-of-unfair-play-27499">PokerListings</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Tokwiro Enterprises ENRG and Bob Pajich at Card Player<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>Tokwiro Enterprises, the company that owns both Absolute Poker and UltimateBet, today released a statement confirming that cheating had gone on at UltimateBet by people who, according to the release, "worked for the previous ownership of UltimateBet prior to the sale of the business to Tokwiro in October 2006."<br><span style="font-style: italic;">[Evan] Shouldn't an information security and risk assessment be conducted as part of the acquisition and integration?&nbsp; If so, then wouldn't a code review of the proprietary software that came with the acquisition be included?&nbsp; This is the proprietary software that really drives the purpose of the site.</span><br><br>The player or players behind the 18 screen names that were identified as being corrupted have not been named.<br><br>Tokwiro will refund players their losses once the investigation is complete.<br><span style="font-style: italic;">[Evan] I wonder how expensive this will be.</span><br><br>The usernames that were used to cheat are: NioNio, Sleepless, NoPaddles, nvtease, flatbroke33, ilike2win, UtakeIt2, FlipFlop2, erick456, WhackMe44, RockStarLA, stoned2nite, monizzle, FireNTexas, HeadKase01, LetsPatttty, NYMobser, and WhoWhereWhen.<br><br>The cheating was able to take place because the perpetrators had access to what Tokwiro is calling an "unauthorized software code" that allowed the cheaters to see their opponents’ holecards.<br><span style="font-style: italic;">[Evan] This "unauthorized software code" use went undetected for almost 21 months!</span><br><br>The cheating took place from March 7, 2006 to Dec. 3, 2007, and it’s not known how much money the cheater(s) illicitly won.<br><br>The company refused to disclose the amount of fraudulent winnings, but poker observers have said it runs into the millions.<br><br>As soon as the cheating was suspected, Tokwiro said it contacted the Kahnawake Gaming Commission (KGC), the most used online poker regulatory commission, to start the investigation.<br><br>Tokwiro is mandated to contact KGC if any suspicious activety might be taking place.<br><br>This is the second cheating incident to hit the company since it purchased Absolute Poker and UltimateBet.<br><br>The first occurred when it was discovered that several players at Absolute Poker also had access to software that allowed them to see opponents’ holecards.<br><span style="font-style: italic;">[Evan] A link is included below</span><br><br><center>ULTIMATEBET ISSUES STATEMENT REGARDING UNFAIR PLAY</center><br><br><span style="font-weight: bold;">MONTREAL, CANADA (MAY 29, 2008)</span> --- Tokwiro Enterprises ENRG ("Tokwiro"), proprietors of UltimateBet.com ("UltimateBet"), one of the world's largest online card rooms, today announced the results of its lengthy investigation into allegations of unfair play, which was triggered by concerns about an account named 'NioNio'. Tokwiro has worked diligently in cooperation with its regulatory body, the Kahnawake Gaming Commission ("KGC"), and with independent third-party experts to conduct a thorough investigation that included a comprehensive review of hand histories and game data, thorough analyses of software and network security, and audits of its security practices and procedures.<br>&nbsp;<br>The investigation has concluded that certain player accounts did in fact have an unfair advantage, and that these accounts targeted the highest limit games on the site. The individuals responsible were found to have worked for the previous ownership of UltimateBet prior to the sale of the business to Tokwiro in October 2006. Tokwiro is taking full responsibility for this situation and will immediately begin refunding UltimateBet customers for any losses that were incurred as a result of unfair play. <br><br>The fraudulent activity was enabled by unauthorized software code that allowed the perpetrators to obtain hole card information during live play. The existence of this vulnerability was unknown to Tokwiro until February 2008 and existed prior to UltimateBet's acquisition by Tokwiro in October 2006. Our investigation has confirmed that the code was part of a legacy auditing system that was manipulated by the perpetrators. Gaming Associates, independent auditors hired by the KGC, have confirmed that the software code that provided the unfair advantage has been permanently removed.<br>&nbsp;<br>Throughout the investigation of this incident, Tokwiro's consistent priorities have been: <br></font><ol><li><font size="2">To permanently remove the ability to engage in unfair play;</font></li><li>To complete its investigation and come to a full understanding of what occurred;</li><li>To refund the affected customers; and</li><li>To implement measures that prevents future incidents. <br></li></ol><font size="2">The Company said, "We would like to thank our customers for their patience, loyalty and support, as well as for their understanding that we are doing everything we can to correct this situation. The staff and management of UltimateBet are fully committed to providing a safe and secure environment for our players, and we want to assure customers of our unwavering resolve to monitor site security with every resource at our disposal." <br><br><span style="font-weight: bold;">Investigation Timeline </span><br>These are the key events in the course of the incident. <br></font><ul><li><font size="2">January 2008: UltimateBet is alerted to suspicions of unfair play on the part of the account "NioNio". Within 24 hours, UltimateBet contacts the KGC to provide formal notice that UltimateBet has initiated an investigation of the incident. UltimateBet subsequently forwarded a copy of all related data to the KGC.</font></li><li>January 2008: The "NioNio" account and related accounts are suspended pending further investigation.</li><li>February 2008: Preliminary findings indicate abnormally high winning statistics for the suspect accounts. After discussions with the KGC, UltimateBet engages third-party gaming experts to assist with the analysis.</li><li>February 2008: Investigators confirm that the suspect accounts are associated with individuals who had worked for UltimateBet under the previous ownership.</li><li>February 2008: UltimateBet discovers the unauthorized code that allowed the perpetrators to obtain hole card information during live play. The code was part of a legacy auditing system that was manipulated by the perpetrators of the fraud.</li><li>February 2008: UltimateBet immediately removes the unauthorized code and works with the KGC and with third-party auditors to verify that the security hole has been eliminated.</li><li>March 2008: Six player accounts are confirmed to have participated in this scheme. No accounts were deleted at any point, although some account names were changed multiple times. The following account names are known to have been used in the fraudulent activity: NioNio, Sleepless, NoPaddles, nvtease, flatbroke33, ilike2win, UtakeIt2, FlipFlop2, erick456, WhackMe44, RockStarLA, stoned2nite, monizzle, FireNTexas, HeadKase01, LetsPatttty, NYMobser, and WhoWhereWhen.</li><li>May 2008: The investigation confirms that the fraudulent activity took place from March 7, 2006 to December 3, 2007.</li><li>May 2008: Gaming Associates certifies that the software code that enabled unfair play was removed from UltimateBet servers in February of 2008.</li><li>May 2008: Customers affected by this incident are identified, and plans for corrective action are reviewed with the KGC. <br></li></ul><font size="2"><span style="font-weight: bold;">Corrective Actions Taken </span><br>The following actions have been taken or are currently underway as a direct result of this investigation. <br></font><ul><li><font size="2">The security hole identified in UltimateBet's investigation has been permanently eliminated.</font></li><li>UltimateBet is establishing a state-of-the-art software Security Center that consolidates and greatly enhances existing security capabilities. The first release of the new Security Center focuses solely on the immediate detection of abnormal winnings. Gaming mathematicians, poker professionals, and security software developers have all contributed to the specifications for the new Security Center.</li><li>UltimateBet customers are no longer permitted to change account names unless they have suffered abuse in chat rooms. Requests for changes must be supported by proof of abuse and must be approved by the Chief Compliance Officer.</li><li>In addition to its existing security department, UltimateBet has established a new specialized Poker Security team of professionals dedicated to fraud prevention.</li><li>The refund process will begin immediately. The accounts associated with fraudulent activity did not use an unfair advantage in all play sessions. Regardless, UltimateBet is refunding all losses to these accounts.</li><li>Accounts related to the fraudulent activity have been disabled, and the individuals associated with those accounts permanently banned from the site.</li><li>UltimateBet has worked closely and transparently with its governing body, the KGC and its designated expert auditors, to determine exactly what happened, how it happened, and who was involved, and has taken action to prevent any possibility of this situation recurring.</li><li>Tokwiro is pursuing its legal options in regard to this incident. <br></li></ul><font size="2">For further inquiries please contract press@ultimatebet.com <br><br><span style="font-weight: bold;">Commentary:</span><br>This is potentially a multi-million dollar loss for Tokwiro Enterprises ENRG and its very troubling that this breach went undetected for so long. The software used by the site is proprietary and should really be subject to a significant amount of information security scrutiny.<br><br>If I were a player, I think I would be beyond angry.&nbsp; Not just angry about the loss of money, but angry about the loss of confidence and being cheated in general.&nbsp; I personally know people that refuse to play online poker because of the risk posed by poorly secured sites.<br><br>Information security of online gaming sites must be a #1 priority for the companies that run them.&nbsp; Seems obvious, but many statements in the information security business seem obvious.&nbsp; Personally, I like the response from Tokwiro.&nbsp; If they follow through (which I assume they would), Tokwiro's actions should go a long ways towards reducing risk and restoring customer confidence.<br><br>Check out the comments at <a href="http://www.cardplayer.com/poker-news/article/4279/owner-of-ultimatebet-confirms-security-breach">Card Player</a> to get some insight into what some players are thinking. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Tokwiro Enterprises ENRG/Absolute Poker:<br>October, 2007 - <a href="http://www.msnbc.msn.com/id/21381022/">Online poker cheating blamed on employee</a></font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/04/ultimatebet.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Wed, 04 Jun 2008 06:55:17 +0000</pubDate>
      <category domain="http://securityratty.com/tag/ultimatebet">ultimatebet</category>
      <category domain="http://securityratty.com/tag/tokwiro enterprises enrg">tokwiro enterprises enrg</category>
      <category domain="http://securityratty.com/tag/tokwiro enterprises">tokwiro enterprises</category>
      <category domain="http://securityratty.com/tag/ultimatebet issues statement">ultimatebet issues statement</category>
      <category domain="http://securityratty.com/tag/ultimatebet prior">ultimatebet prior</category>
      <category domain="http://securityratty.com/tag/ultimatebet subsequently">ultimatebet subsequently</category>
      <category domain="http://securityratty.com/tag/ultimatebet immediately removes">ultimatebet immediately removes</category>
      <category domain="http://securityratty.com/tag/ultimatebet servers">ultimatebet servers</category>
      <category domain="http://securityratty.com/tag/ultimatebet statement">ultimatebet statement</category>
      <source url="http://breachblog.com/2008/06/04/ultimatebet.aspx">UltimateBet cheating goes undetected for almost 21 months</source>
    </item>
    <item>
      <title><![CDATA[The Cybercrime Arms Race]]></title>
      <link>http://securityratty.com/article/ec6ba32b6856b213a9441213fb5860fd</link>
      <guid>http://securityratty.com/article/ec6ba32b6856b213a9441213fb5860fd</guid>
      <description><![CDATA[Source: Kaspersky Labs) Sophisticated groups are leading underworld efforts into cybercrime, creating viruses, spyware, Trojans, worms and other malware. These groups now even provide complementary...]]></description>
      <content:encoded><![CDATA[<b>(Source: Kaspersky Labs)</b>  Sophisticated groups are leading underworld efforts into cybercrime, creating viruses, spyware, Trojans, worms and other malware. These groups now even provide complementary criminal services to their clients helping them to outsmart Internet security providers and users. With little or no investment, there's plenty of payback for cybercrime perpetrators at every level of this ecosystem.  Download this whitepaper to learn more.
<p><a href="http://feeds.computerworld.com/~a/Computerworld/Security/News?a=1XdOg4"><img src="http://feeds.computerworld.com/~a/Computerworld/Security/News?i=1XdOg4" border="0"></img></a></p><img src="http://feeds.computerworld.com/~r/Computerworld/Security/News/~4/237638994" height="1" width="1"/>]]></content:encoded>
      <pubDate>Tue, 19 Feb 2008 11:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/cybercrime">cybercrime</category>
      <category domain="http://securityratty.com/tag/cybercrime perpetrators">cybercrime perpetrators</category>
      <category domain="http://securityratty.com/tag/underworld efforts">underworld efforts</category>
      <category domain="http://securityratty.com/tag/kaspersky labs">kaspersky labs</category>
      <category domain="http://securityratty.com/tag/plenty">plenty</category>
      <category domain="http://securityratty.com/tag/source">source</category>
      <category domain="http://securityratty.com/tag/spyware">spyware</category>
      <category domain="http://securityratty.com/tag/users">users</category>
      <category domain="http://securityratty.com/tag/whitepaper">whitepaper</category>
      <source url="http://feeds.computerworld.com/~r/Computerworld/Security/News/~3/237638994/whitepapers.do">The Cybercrime Arms Race</source>
    </item>
    <item>
      <title><![CDATA[Thieves steal four Diocese of Providence computers]]></title>
      <link>http://securityratty.com/article/8ad9d757579cc857b045427c5732a698</link>
      <guid>http://securityratty.com/article/8ad9d757579cc857b045427c5732a698</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
2/1/08

Organization
Roman Catholic Diocese of Providence

Contractor/Consultant/Branch
None

Victims
Current and former Catholic school employees
...]]></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/dop.jpg" align="right" height="69" width="198"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>2/1/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.dioceseofprovidence.org/index.php" target="_blank"> Roman Catholic Diocese of Providence</a><br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>Current and former Catholic school employees<br><br><span style="font-weight: bold;">Number Affected:</span><br>about 5,000<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>Sometime during the weekend of January 27th, 2008 thieves broke into the Chancery of the Roman Catholic Diocese of Providence and stolen four desktop computers, one of which contained sensitive personal information belonging to current and former Catholic school employees.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.dioceseofprovidence.org/?id=212" target="_blank"> The Diocese of Providence online announcement</a> <br><a href="http://www.projo.com/news/content/catholic_identity_theft_02-02-08_BK8S2PA_v13.363690c.html" target="_blank"> The Providence Journal online story</a><br><br><span style="font-weight: bold;">Report Credit:</span><br>The Diocese of Providence<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>An individual or individuals broke into the Diocesan Office Building (also known as the Chancery) located at One Cathedral Square in Providence.&nbsp; The perpetrator(s) gained access by breaking through an office window in the Catholic School Office suite.<br><br>Once in the building, the perpetrators forcibly entered through two locked office doors where they stole desktop computers and other equipment.<br><br>The office suite that was burglarized did not have an alarm system<br><span style="font-style: italic;">[Evan] It was reported that the Diocese does employ a security guard, but it is not known where he/she was at the time of the break-in.&nbsp; The fact that the timeframe in question is 8 hours (10 PM Friday - 6 AM Saturday) is interesting.&nbsp; Typically security guards are expected to make regular rounds (~ once every hour or two) throughout the area being guarded.&nbsp; Eight hours is a long time for a break-in to go undetected, so an alarm system would have been very beneficial as an alert if not a deterrent.</span><br><br>One of the stolen computers (a desktop computer, not a laptop) contained a substantial amount of data that included personnel information on present and former Catholic school employees throughout the Diocese of Providence. <br><br>The Rhode Island State Police have been notified of this incident.&nbsp; Additionally, the Providence Police Department has assumed responsibility for the investigation.<br><br>Thus far, the stolen equipment has not been recovered however, the Catholic Schools Office is fully cooperating with law enforcement who are investigating the situation.<br><br>Present and former employees of Rhode Island Catholic schools may be affected.<br><br>A number of safeguards are in place such as: locked offices, password protected computers, local administrator account password protected, guest accounts disabled.<br><span style="font-style: italic;">[Evan] These are all good security practices.</span><br><br>Employees have unique passwords that they are required to change every few weeks<br><span style="font-style: italic;">[Evan] Another good security practice, but every few weeks might be a little too often.&nbsp; If we make people change their passwords too often we increase the chances that they will write them down.</span><br><br>Additionally, personal information of students, teachers, parents and others associated with the Catholic Schools Office are prohibited from storage on lap top computers.<br><span style="font-style: italic;">[Evan] Yet another good security practice.</span><br><br>Personal information of students and their parents and or guardians was not stored on the stolen equipment.<br><br>In addition to notifying current and former employees by letters sent to last known addresses, the Catholic Schools Office has created this page on&nbsp; the web site and established a special phone number, 401/278-4678 to answer inquiries from those who feel they may have been affected<br><br>Another diocese office was broken into about a year ago and a computer stolen<br><br>“The Catholic schools office sincerely apologizes for any inconvenience this incident may cause its current and former employees,”<br><br><span style="font-weight: bold;">Commentary:</span><br>Judging from what the Diocese has told us about their security practices it is easy to see that they have made a conscience effort to secure confidential information.&nbsp; They put some sound information security practices to use, but now we understand that it wasn't enough.&nbsp; At least two vital information security controls were missed; data at rest encryption and adequate physical security (alarm system missing).&nbsp; There is no mention as to whether or not the Diocese or Chancery are surveilled. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br>
<br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/02/04/dop.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Mon, 04 Feb 2008 05:48:02 +0000</pubDate>
      <category domain="http://securityratty.com/tag/diocese">diocese</category>
      <category domain="http://securityratty.com/tag/providence">providence</category>
      <category domain="http://securityratty.com/tag/computers">computers</category>
      <category domain="http://securityratty.com/tag/roman catholic diocese">roman catholic diocese</category>
      <category domain="http://securityratty.com/tag/catholic school employees">catholic school employees</category>
      <category domain="http://securityratty.com/tag/employees">employees</category>
      <category domain="http://securityratty.com/tag/providence police department">providence police department</category>
      <category domain="http://securityratty.com/tag/police">police</category>
      <category domain="http://securityratty.com/tag/catholic schools office">catholic schools office</category>
      <source url="http://breachblog.com/2008/02/04/dop.aspx">Thieves steal four Diocese of Providence computers</source>
    </item>
    <item>
      <title><![CDATA[Stolen Wendy's laptop affects 1,092 employees]]></title>
      <link>http://securityratty.com/article/4842a985c79853d999c877db69363506</link>
      <guid>http://securityratty.com/article/4842a985c79853d999c877db69363506</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
12/21/07

Organization
Wendy's International, Inc

Contractor/Consultant/Branch
None

Victims
Wendy's employees

Number Affected
1,092

Types of Data...]]></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/wendys.jpg" align="right" height="129" width="110"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>12/21/07<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.wendys.com/" target="_blank"> Wendy's International, Inc.</a><br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>Wendy's employees<br><br><span style="font-weight: bold;">Number Affected:</span><br>1,092<br><br><span style="font-weight: bold;">Types of Data:</span><br>Name, email address, Social Security number, employee identification number, and salary information.<br><br><span style="font-weight: bold;">Breach Description:</span><br>A Wendy's laptop was stolen during a car burglary at a company employee's home on December 1, 2007.&nbsp; The laptop contained sensitive personal information belonging to 1,092 Wendy's employees including Social Security numbers and salary information.&nbsp; The employee reported the theft to Wendy's on December 3rd, and Wendy's reported the breach on December 21st.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://doj.nh.gov/consumer/pdf/wendys.pdf" target="_blank"> New Hampshire Attorney General breach notification</a><br><br><span style="font-weight: bold;">Report Credit:</span><br>New Hampshire State Attorney General<br><br><span style="font-weight: bold;">Response:</span><br>From the official New Hampshire breach notification:<br><br>We are writing to advise you of a recent incident involving the theft of a company-issued laptop containing certain personal information belonging to Wendy's employees.<br><br>On December 3, 2007, we were notified by any employee of a car burglary at an employee's residence on December 1, 2007, which resulted in the theft of a company-issued laptop.<br><br>Several cars in the neighborhood were the subject of break-ins that evening.&nbsp; Accordingly, it may well be that the computer data was not the target of the burglary, that the perpetrators are not aware that personal information in on the laptop, or that they are not sophisticated enough to access the data (the employee's log-in and password are required for traditional access methods, and the information was in a subfolder with an uninformative title).<br><span style="font-style: italic;">[Evan] I can see the logic in this statement, but it doesn't excuse the fact that the information was not well protected.&nbsp; Little (or no) sophistication is required for someone to gain access to the data on the laptop (circumvent the employee log-in) if someone wanted to, and there is little (or no) security in the fact that the information wasn't labeled "identitythiefopenme.xls".</span><br><br>The information included the name, email address, social security number, employee identification number, and salary information<br><br>The total number of affected individuals was around 1092 (U.S.)<br><br>In order to ensure that affected individuals could take immediate steps to protect themselves from possible identity theft or other monetary damage, Wendy's will be sending a communication by first class mail on December 21, 2007<br><span style="font-style: italic;">[Evan] Not really so "immediate", unless 20+ days is immediate.</span><br><br>at this time Wendy's has no specific knowledge that any information contained on the laptop has been accessed or misused<br><br>We are also determining internally whether having that data on the laptop was consistent with Wendy's data security policies and exceptions.<br><span style="font-style: italic;">[Evan] This is the one statement that is the most troubling to me.&nbsp; The letter was written by the Wendy's Chief Information Officer (CIO) and you would think that a person in this position would know without too much investigation.&nbsp; Information security policies must be clear and concise so that all people completely understand them.&nbsp; Avoid gray areas whenever possible and create a policy waiver request and approval process for exceptional circumstances.&nbsp; Policy waivers that are approved (granted) are logged and archived.</span><br><br>If you have questions, please contact your local HR staff member or contact Wendy's International, Inc. Corporate Office at 1-800-443-7266 and when prompted by the automated attendant, dial ext. 8052.<br><br>Please also accept my personal apology for any concern that this situation might create for you.<br><br><span style="font-weight: bold;">Commentary:</span><br>What can you say other than what was already written above.&nbsp; This is another instance of confidential data that was not adequately secured.&nbsp; It baffles me that there is a question as to whether or not the actions that led to this breach are against company policy.&nbsp; If the storage of confidential information on mobile media (thumb drives, CDs, DVDs, laptops, etc.) without encryption (and other controls) is not in policy, it certainly should be!&nbsp; Information security training and awareness also appear to be lacking. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/01/03/wendys.aspx" type="text/javascript" charset="utf-8"></script>
<br>
<br>
<script type="text/javascript"><!--
google_ad_client = "pub-4721162729073131";
google_ad_width = 468;
google_ad_height = 60;
google_ad_format = "468x60_as";
google_ad_type = "text_image";
google_ad_channel = "";
//-->
</script>
<script type="text/javascript">
</script>]]></content:encoded>
      <pubDate>Thu, 03 Jan 2008 11:08:27 +0000</pubDate>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/confidential information">confidential information</category>
      <category domain="http://securityratty.com/tag/information security policies">information security policies</category>
      <category domain="http://securityratty.com/tag/wendy">wendy</category>
      <category domain="http://securityratty.com/tag/breach description">breach description</category>
      <category domain="http://securityratty.com/tag/breach">breach</category>
      <source url="http://breachblog.com/2008/01/03/wendys.aspx">Stolen Wendy's laptop affects 1,092 employees</source>
    </item>
    <item>
      <title><![CDATA[A downside to being a Billionaire]]></title>
      <link>http://securityratty.com/article/d4b02ee119f372cc4722b1e0f50eb642</link>
      <guid>http://securityratty.com/article/d4b02ee119f372cc4722b1e0f50eb642</guid>
      <description><![CDATA[I guess the grass isn't always greener on the other side. Even if the other side is you having a couple billion dollars. I dug into the archives for this post by Ed Dickson, which described how NYC...]]></description>
      <content:encoded><![CDATA[<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://bp2.blogger.com/_jCJICLQ1WVs/RuMWgzaiV9I/AAAAAAAAARM/s1WbfS3cqEA/s320/michael_bloomberg.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 200px;" src="http://bp2.blogger.com/_jCJICLQ1WVs/RuMWgzaiV9I/AAAAAAAAARM/s1WbfS3cqEA/s320/michael_bloomberg.jpg" alt="" border="0" /></a><br />I guess the grass isn't always greener on the other side. Even if the other side is you having a couple billion dollars. I dug into the archives for this post by Ed Dickson, which described how <a href="http://fraudwar.blogspot.com/2007/10/how-was-mayor-bloombergs-bofa-account.html">NYC Mayor Bloomberg was victimized twice</a>, almost simultaneously, by thieves trying to get at his multi-billion dollar wallet.<br /><br />Check out Ed's post for the details, but let's take a quick look at what we can learn from these attacks. The first was a pretty standard check counterfeiting attack. Not much you can do about that. If someone gets a copy of your check, with the routing number and account number, then they can produce a likeness that could be accepted by any number of merchants out there.<br /><br />The banks invest a lot in anti-counterfeiting marks on the checks, but in the end it's up to the merchant and your bank as to whether they will accept the fake. Most of the time they won't, but other times they may. That's why it's so important for you to keep on top of your finances and check your balances daily. Then you'll know if unauthorized charges are showing up. This is discussed in detail in Step 6 of <a href="http://www.securitymike.com/">Security Mike's Guide to Internet Security</a>.<br /><br />The second attack involved the criminal logging into Mr. Mayor's bank account and transferring money to a 3rd party financial institution. How did someone get his login and password? Who knows? It could have been anything. This is another example where staying on top of your account balances would have shown a weird transfer and you could have investigated it.<br /><br />I'm sure Bloomberg has people to look into this. That's how they found the issues and with a high profile victim like the Mayor, the banks and law enforcement will work hard to bring the perpetrators to justice.  It makes for good PR. I'm sure the bank also returned the money right where they found it, and no one but the criminals are any worse for wear.<br /><br />So I guess the grass is greener after all for the Billionaires out there. If it's not, you certainly can afford a lot of spray paint, sod or whatever else you want to use to make your grass seem greener.<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/SecurityMike?a=xLYP6pC"><img src="http://feeds.feedburner.com/~f/SecurityMike?i=xLYP6pC" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/SecurityMike?a=3caoD7c"><img src="http://feeds.feedburner.com/~f/SecurityMike?i=3caoD7c" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/SecurityMike?a=JnZvmdc"><img src="http://feeds.feedburner.com/~f/SecurityMike?i=JnZvmdc" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/SecurityMike/~4/194579717" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 03 Dec 2007 12:51:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/account">account</category>
      <category domain="http://securityratty.com/tag/bank account">bank account</category>
      <category domain="http://securityratty.com/tag/pretty standard check">pretty standard check</category>
      <category domain="http://securityratty.com/tag/check">check</category>
      <category domain="http://securityratty.com/tag/nyc mayor bloomberg">nyc mayor bloomberg</category>
      <category domain="http://securityratty.com/tag/bloomberg">bloomberg</category>
      <category domain="http://securityratty.com/tag/mayor">mayor</category>
      <category domain="http://securityratty.com/tag/bank">bank</category>
      <category domain="http://securityratty.com/tag/greener">greener</category>
      <source url="http://feeds.feedburner.com/~r/SecurityMike/~3/194579717/downside-to-being-billionaire.html">A downside to being a Billionaire</source>
    </item>
  </channel>
</rss>
