<?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: memorial]]></title>
    <link>http://securityratty.com/tag/memorial</link>
    <description></description>
    <pubDate>Thu, 14 Feb 2008 07:17:22 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA["many of Colt's clients" affected by breach, CNET included]]></title>
      <link>http://securityratty.com/article/3313abd868212bd3a9ed98811169e851</link>
      <guid>http://securityratty.com/article/3313abd868212bd3a9ed98811169e851</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/13/08

Organization
CNET Networks, Inc. (&quot;CNET

Contractor/Consultant/Branch
Colt Express Outsourcing Services, Inc. (&quot;Colt

Victims
current and former...]]></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/colt.jpg" width="78" align="right" height="69"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/13/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.cnetnetworks.com/">CNET Networks, Inc. ("CNET")</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.colthr.com/">Colt Express Outsourcing Services, Inc. ("Colt")</a><br><br><span style="font-weight: bold;">Victims:</span><br>"current and former employees and their dependants"<br><br><span style="font-weight: bold;">Number Affected:</span><br>"around 6,500"<br><br><span style="font-weight: bold;">Types of Data:</span><br>"first names, last names, date of birth, Social Security numbers, address, employer, hire date, benefits group numbers, and relationship to the policy holder"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"Colt informed our client by this letter that on Memorial Day, Monday, May 26, 2008, Colt's offices in Walnut Creek, California were burglarized.&nbsp; Certain computer equipment was taken which contains the human resources data of several of their clients, including CNET.&nbsp; The theft of this equipment may have compromised the personal information of our client's current and former employees and their dependants, and our client is working to understand the extent of any exposure for its employees."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.oag.state.md.us/idtheft/Breach%20Notices/ITU-153493.pdf">Maryland State Attorney General breach notification</a><br><a href="http://www.pcworld.com/businesscenter/article/147460/cnet_employees_notified_after_data_breach.html">PCWorld</a> <br><a href="http://www.webpronews.com/topnews/2008/06/24/cnet-affected-by-security-breach">WebProNews</a> <br><a href="http://www.pogowasright.org/article.php?story=20080619103835325">PogoWasRight</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The Maryland State Attorney General<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>On June 6, 2008, CNET received the attached letter from Colt Express Outsourcing Services, Inc., ("Colt") who has provided our client with employee benefit plan administrative services for the past 8 years.<br><br>Colt informed our client by this letter that on Memorial Day, Monday, May 26, 2008, Colt's offices in Walnut Creek, California were burglarized.<br><span style="font-style: italic;">[Evan] Uh Oh!, this is starting to read like and smell like the </span><a style="font-style: italic;" href="http://breachblog.com/2008/02/11/asi.aspx">ASI breach</a><span style="font-style: italic;"> reported in February.</span><br><br>The breach occurred on Memorial Day, Monday, May 26, 2008, between approximately 4:30 p.m. and 5:00 p.m. PST, when someone broke into Colt Express's office at 2125 Oak Grove Road, Suite 210, Walnut Creek, California, 94598<br><br>Certain computer equipment was taken which contains the human resources data of several of their clients, including CNET. <br><span style="font-style: italic;">[Evan] According to a CNET spokesperson, via PogoWasRight.org, the "computer equipment" did not employ encryption to protect the information.&nbsp; Encryption could have been a prudent control in a defense-in-depth approach, a mitigating control to protect information against a physical break-in and theft.</span><br><br>The theft of this equipment may have compromised the personal information of our client's current and former employees and their dependants, and our client is working to understand the extent of any exposure for its employees.<br><span style="font-style: italic;">[Evan] Not "may have", but did.&nbsp; Information security and control can no longer be reasonably assured, which in my book constitutes a compromise.</span><br><br>Colt has also informed us that they reported the break-in to Walnut Creek police and to REACT High Tech Crimes Task Force in Silicon Valley when they discovered the burglary and that there is an ongoing criminal investigation.<br><br>report number 08-12367<br><br>In speaking directly with the Walnut Creek Police on June 12, 2008, Officer Greg Leonard, the primary investigator for the incident informed us that they are not aware of any misuse of personal information as a result of this theft at this time.<br><br>The information included first names, last names, Social Security numbers, address, employer, hire date, benefits group numbers, and relationship to the policy holder for around 6,500 of our client's current and former employees, and their dependants.<br><br><img src="http://images.quickblogcast.com/95781-88451/cnetnumbers.jpg" width="435" border="0"><br><br>some of your current and former employees and their dependants during the time period of 01-Aug-00 to present.<br><span style="font-style: italic;">[Evan] August 1st, 2000 through May 26th, 2008 is almost eight years of information!&nbsp; I wonder what the data retention policy states at Colt, supposing one exists.</span><br><br>We do not have any understanding that the computers stored personal health information.<br><br>Our client is providing written notification to all affected individuals at the last home address we have on record<br><br>Although there is no evidence of misuse of the data to date, our client's notification will also inform affected individuals that it has contracted with Equifax to provide Equifax Credit Watch Gold with 3 in 1 Monitoring service, including identity theft insurance, for one full year at no cost.<br><span style="font-style: italic;">[Evan] I have said it before, and I will say it again.&nbsp; One year of semi-effective protection should not be considered adequate for information that has a usable life that far exceeds this time frame.&nbsp; It should be pointed out howevere that it is better than nothing and the company is not required to offer it.</span><br><br>Although we are not aware of the exact number of individuals affected by the Colt breach, we do know that we were among many of Colt's clients whose data were stored on the stolen computers.<br><span style="font-style: italic;">[Evan] The word that catches my attention almost immediately is "many".&nbsp; How many clients will be affected in the end?&nbsp; PogoWasRight is already following up on another company that may be affected.</span><br><br>Colt Express takes the protection of its customer and personal information very seriously.<br><span style="font-style: italic;">[Evan] Making a statement like this and the demonstration by action are two entirely different matters.&nbsp; An organization such as Colt Express creates, collects, stores and transfers very sensitive information as an integral part of their business.&nbsp; This being said, I wonder why this information was not protected better.</span><br><br>Colt Express is taking steps to ensure that a potential data security breach does not occur in the future.<br><br>We installed an alarm system on Friday, May 30th.<br><span style="font-style: italic;">[Evan] Are we to assume that there was none prior to May 30th?&nbsp; I hope not!</span><br><br>Colt Express is looking into what additional steps may be taken to provide enhanced security.<br><br>By this letter and enclosures, we are providing you with all the information we believe you need, and that we are able to give you.&nbsp; We do not have the resources, financial and otherwise, to assist you further.<br><span style="font-style: italic;">[Evan] Say huh?</span><br><br>Towards the end of last year, our customer base was reduced to an unsustainable level.<br><br>Colt has been in the process of going out of business, while at the same time providing time for remaining customers to find alternative solutions.<br><span style="font-style: italic;">[Evan] This is a twist.&nbsp; How long has the company been in the process of going out of business and was CNET (and the "many" other clients) aware of it?&nbsp; If so, this could have been a sign that could have spurred some action.&nbsp; Then again, maybe not.</span><br><br><img src="http://images.quickblogcast.com/95781-88451/cnetcolthomepage.jpg" width="241" border="0"><br><font size="1">http://www.colthr.com/</font><br><br><br><br>Those decisions are now final.<br><br>We are firmly committed to protecting all of the information that is entrusted to us both before and after we close down.<br><br>We sincerely apologize for the inconvenience and concern this incident will cause.<br><br><span style="font-weight: bold;">Commentary:</span><br>As I stated earlier in the post, I am a little fearful that this breach could end up as significant or more significant (in terms of number of people and organizations affected) than the <a href="http://breachblog.com/2008/02/11/asi.aspx">ASI breach</a> reported in February.&nbsp; The ASI breach was the 2nd most popular posting in The Breach Blog's history at the time, based on number of online page reads and comments posted.<br><br>This breach has got me thinking.&nbsp; Some of the key risks that we address with the organizations we work with are those involving the management of vendor and third-party relationships.&nbsp; Ideally, information security personnel are involved throughout the relationship, including the initial vendor feasibility assessment.&nbsp; Vendors and "trusted" third-parties need to be held to the same high security standards that we set for the organization.&nbsp; The methods in which this can be accomplished vary from organization to organization, but typically include risk assessments (initial and ongoing), information security requirements built into contractual language, and enforcement actions if necessary.&nbsp; If a vendor is not encrypting confidential information or employing burglar alarms, it is known (and hopefully addressed). <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/25/colt.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Wed, 25 Jun 2008 07:25:20 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/confidential information">confidential information</category>
      <category domain="http://securityratty.com/tag/protect information">protect information</category>
      <category domain="http://securityratty.com/tag/breach">breach</category>
      <category domain="http://securityratty.com/tag/sensitive information">sensitive information</category>
      <category domain="http://securityratty.com/tag/information security requirements">information security requirements</category>
      <category domain="http://securityratty.com/tag/colt">colt</category>
      <source url="http://breachblog.com/2008/06/25/colt.aspx">"many of Colt's clients" affected by breach, CNET included</source>
    </item>
    <item>
      <title><![CDATA[Online theft and fraud involves OSU Bookstore customers]]></title>
      <link>http://securityratty.com/article/8476417975cb621bc420aa71c01e43ab</link>
      <guid>http://securityratty.com/article/8476417975cb621bc420aa71c01e43ab</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/3/08

Organization
Oregon State University

Contractor/Consultant/Branch
OSU Bookstore, Inc

OSU Bookstore is a nonprofit corporation that has been...]]></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/osubooks.jpg" align="right" height="51" width="200"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/3/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://oregonstate.edu/">Oregon State University</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.osubookstore.com/">OSU Bookstore, Inc.</a>* <br><br><font size="1">*OSU Bookstore is a nonprofit corporation that has been serving Oregon State University and the town of Corvallis since 1914. Our main store is located in the Memorial Union on the Oregon State University campus.&nbsp; Today, as in 1914, the bookstore is governed by a Board of Directors composed of faculty, staff, and students of Oregon State University.</font><br><br><span style="font-weight: bold;">Victims:</span><br>Online customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>"as many as 4,700"<br><br><span style="font-weight: bold;">Types of Data:</span><br>Personal information including credit card numbers<br><br><span style="font-weight: bold;">Breach Description:</span><br>"The Oregon State Police is investigating the theft of personal information from as many as 4,700 online customers of the OSU Bookstore who used credit cards to purchase items."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.dhonline.com/articles/2008/06/03/news/local/5loc10_osu.txt">Albany Democrat Herald</a> <br><a href="http://www.kval.com/news/local/19535104.html">Associated Press via KVAL Channel 13 News</a> <br><a href="http://www.kval.com/news/local/19549224.html">KVAL Channel 13 News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Albany Democrat Herald<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>CORVALLIS, Ore. (AP) - Oregon State officials say credit card scammers may have defrauded 4,700 online customers of the school's bookstore.<br><br>In March, OSP began investigation into a report that approximately 30 OSU Bookstore customers’ personal information may have been compromised following online orders.<br><span style="font-style: italic;">[Evan] Unfortunately, the bookstore did not appear to be monitoring web traffic to and from the server to detect unusual (and potentially attack) traffic. The fact that this detective control was missing from the security architecture meant that the bookstore had to rely on customers to tell them something was wrong.&nbsp; An incident response should have probably been initiated at this point (March not May).</span><br><br>Then last week, telephone calls and e-mails began coming into the bookstore from customers who had noticed fraudulent charges on their credit cards almost immediately after placing online orders<br><br>Bookstore General Manager Steve Eckrich says servers were shut down when the security breach was discovered.<br><span style="font-style: italic;">[Evan] 2+ months after the bookstore was originally notified that something was wrong.&nbsp; At the time of this post, the site is still down.</span><br><br><img src="http://images.quickblogcast.com/95781-88451/osubooksdown.jpg" border="0" width="576"><br><br>"They tried different attacks and our Web site evidently had one vulnerability in it," said General Manager Steve Eckrich.<br><span style="font-style: italic;">[Evan] I would bet my cup of coffee that the Web site had more than on vulnerability!&nbsp; I love my coffee.&nbsp; Where is the IDS/IPS?</span><br><br>The Bookstore has alerted its online customers who had made a purchase<br><br>State Police Lieutenant Jeff Lanz says the security breach appears to have originated outside the university, but where is unknown.<br><br>The OSU Bookstore has hired an outside agency to help with its own investigation and to provide guidance on strengthened security safeguards for its computing network.<br><span style="font-style: italic;">[Evan] Good call it just stinks that the bookstore was reactive and not proactive.</span><br><br>"We'll be using their recommendations not only to solve that particular problem that was exploited but to add additional layers of security on top of that so that information is not exposed or cannot be exposed in the way that it was,"<br><span style="font-style: italic;">[Evan] Another good call.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>Obviously the OSU Bookstore did not employ the proper security controls to #1 secure the site, #2 detect a breach, and #3 respond to a breach.&nbsp; Three strikes.&nbsp; Poor planning and poor implementation.&nbsp; I hope that OSU Bookstore, Inc. takes the proper steps to formalize their information security program and reduce risk.&nbsp; We'll see. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/04/osubooks.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Thu, 05 Jun 2008 05:42:32 +0000</pubDate>
      <category domain="http://securityratty.com/tag/bookstore">bookstore</category>
      <category domain="http://securityratty.com/tag/osu bookstore">osu bookstore</category>
      <category domain="http://securityratty.com/tag/breach description">breach description</category>
      <category domain="http://securityratty.com/tag/breach">breach</category>
      <category domain="http://securityratty.com/tag/online">online</category>
      <category domain="http://securityratty.com/tag/security breach">security breach</category>
      <category domain="http://securityratty.com/tag/customers">customers</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <source url="http://breachblog.com/2008/06/05/osubooks.aspx">Online theft and fraud involves OSU Bookstore customers</source>
    </item>
    <item>
      <title><![CDATA[Inside the Attack that Crippled Revision3]]></title>
      <link>http://securityratty.com/article/e262ba5902ab38edc05567c775f45403</link>
      <guid>http://securityratty.com/article/e262ba5902ab38edc05567c775f45403</guid>
      <description><![CDATA[As many of you know, Revision3s servers were brought down over the Memorial Day weekend by a denial of service attack. Its an all too common occurrence these days. But this one wasnt your normal...]]></description>
      <content:encoded><![CDATA[As many of you know, Revision3’s servers were brought down over the Memorial Day weekend by a denial of service attack. It’s an all too common occurrence these days. But this one wasn’t your normal cybercrime – there’s a chilling twist at the end. Here’s what happened, and why we’re even more concerned today, after it’s over, than we were on Saturd]]></content:encoded>
      <pubDate>Thu, 29 May 2008 12:00:11 +0000</pubDate>
      <category domain="http://securityratty.com/tag/memorial day weekend">memorial day weekend</category>
      <category domain="http://securityratty.com/tag/normal cybercrime">normal cybercrime</category>
      <category domain="http://securityratty.com/tag/service attack">service attack</category>
      <category domain="http://securityratty.com/tag/revision3s servers">revision3s servers</category>
      <category domain="http://securityratty.com/tag/common occurrence">common occurrence</category>
      <category domain="http://securityratty.com/tag/denial">denial</category>
      <category domain="http://securityratty.com/tag/twist">twist</category>
      <category domain="http://securityratty.com/tag/saturd">saturd</category>
      <category domain="http://securityratty.com/tag/days">days</category>
      <source url="http://digg.com/security/Inside_the_Attack_that_Crippled_Revision3_3">Inside the Attack that Crippled Revision3</source>
    </item>
    <item>
      <title><![CDATA[If you love your freedom, Thank a Vet.]]></title>
      <link>http://securityratty.com/article/81b09cf4a46775a70eb03a9c7ff5ee99</link>
      <guid>http://securityratty.com/article/81b09cf4a46775a70eb03a9c7ff5ee99</guid>
      <description><![CDATA[Please join me in remembering those who gave the supreme sacrafice to protect the freedoms we have


clipped from www.usmemorialday.org





Memorial Day, originally called Decoration Day, is a day of...]]></description>
      <content:encoded><![CDATA[<div > Please join me in remembering those who gave the supreme sacrafice to protect the freedoms we have. </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/505D8201-1496-4F86-A003-F643790863DD/" title="go to this clipmark"><img src="http://content.clipmarks.com/blog_icon/a0ccb0e7-6355-49b2-a736-5a9ff4a18524/505D8201-1496-4F86-A003-F643790863DD/" 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.usmemorialday.org/backgrnd.html" href="http://www.usmemorialday.org/backgrnd.html" style="font-size: 11px;">www.usmemorialday.org</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.usmemorialday.org/backgrnd.html --><DIV align="center"><TABLE cellspacing="0" cellpadding="0" border="1" align="left"><TBODY><TR><TH><A href="http://www.usmemorialday.org/index.htm"><IMG width="54" height="93" border="0" alt="Memorial Day Home Page" src="http://www.usmemorialday.org/unkwn2sm.jpg" /></A></TH></TR></TBODY></TABLE><TABLE cellspacing="0" cellpadding="0" border="0" align="right"><TBODY><TR><TD colspan="3">?</TD></TR><TR><TH valign="top"><A href="http://www.usmemorialday.org/backgrndspa.html"><IMG width="29" height="21" border="0" alt="Spanish Translation (by Bablefish)" src="http://www.usmemorialday.org/spanflag.gif" /></A> ? <A href="http://www.usmemorialday.org/backgrndfra.html"><IMG width="29" height="21" border="0" alt="French Translation (by Bablefish)" src="http://www.usmemorialday.org/franflag.gif" /></A> ? <A href="http://www.usmemorialday.org/backgrndhun.html"><IMG width="30" height="20" border="0" alt="Hungarian Translation (by Veronika Nagy)" src="http://www.usmemorialday.org/images/hunflag.gif" /></A></TH><TD>???</TD><TH valign="top"></TH></TR></TBODY></TABLE><IMG width="248" height="49" alt="Memorial Day" src="http://www.usmemorialday.org/memorialday.gif" /><IMG width="128" height="49" alt="History" src="http://www.usmemorialday.org/history.gif" /></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.usmemorialday.org/backgrnd.html --><B>Memorial Day, originally called Decoration Day, is a day of remembrance for those who have died in our nation&#8217;s service.</B></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/505D8201-1496-4F86-A003-F643790863DD/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>
]]></content:encoded>
      <pubDate>Mon, 26 May 2008 12:56:17 +0000</pubDate>
      <category domain="http://securityratty.com/tag/day">day</category>
      <category domain="http://securityratty.com/tag/decoration day">decoration day</category>
      <category domain="http://securityratty.com/tag/memorial day">memorial day</category>
      <category domain="http://securityratty.com/tag/nations service">nations service</category>
      <category domain="http://securityratty.com/tag/supreme sacrafice">supreme sacrafice</category>
      <category domain="http://securityratty.com/tag/usmemorialday">usmemorialday</category>
      <category domain="http://securityratty.com/tag/org">org</category>
      <category domain="http://securityratty.com/tag/freedoms">freedoms</category>
      <category domain="http://securityratty.com/tag/protect">protect</category>
      <source url="http://spywarebiz.com/spywarebizblog/?p=462">If you love your freedom, Thank a Vet.</source>
    </item>
    <item>
      <title><![CDATA[Dual-Use Technologies and the Equities Issue]]></title>
      <link>http://securityratty.com/article/c066e281bbaa6113f0af7b18dbf10846</link>
      <guid>http://securityratty.com/article/c066e281bbaa6113f0af7b18dbf10846</guid>
      <description><![CDATA[On April 27, 2007, Estonia was attacked in cyberspace. Following a diplomatic incident with Russia about the relocation of a Soviet World War II memorial, the networks of many Estonian organizations,...]]></description>
      <content:encoded><![CDATA[<p>On April 27, 2007, Estonia was attacked in cyberspace.  Following a diplomatic incident with Russia about the relocation of a Soviet World War II memorial, the networks of many Estonian organizations, including the Estonian parliament, banks, ministries, newspapers and broadcasters, were attacked and -- in many cases -- shut down.  Estonia was quick to blame Russia, which was equally quick to deny any involvement.  </p>

<p>It was <a href="http://www.wired.com/politics/security/magazine/15-09/ff_estonia">hyped</a> as the <a href="http://www.wired.com/politics/security/magazine/15-09/ff_estonia">first cyberwar</a>: Russia attacking Estonia in cyberspace.  But nearly a year later, evidence that the Russian government was involved in the denial-of-service attacks still hasn't emerged. Though Russian hackers were indisputably the major instigators of the attack, the only individuals <a href="http://blog.wired.com/27bstroke6/2008/01/we-traced-the-c.html">positively identified</a> have been young ethnic Russians living inside Estonia, who were  pissed off over the statue incident.</p>

<p>You know you've got a problem when you can't tell a hostile attack by another nation from bored kids with an axe to grind. </p>

<p>Separating cyberwar, cyberterrorism and cybercrime isn't easy; these days you need a <a href="http://www.schneier.com/blog/archives/2007/06/cyberwar.html">scorecard to tell the difference</a>.  It's not just that it’s hard to trace people in cyberspace, it's that military and civilian attacks -- and defenses -- look the same.  </p>

<p>The traditional term for technology the military shares with civilians is "dual use."  Unlike hand grenades and tanks and missile targeting systems, dual-use technologies have both military and civilian applications.  Dual-use technologies used to be exceptions; even things you'd expect to be dual use, like radar systems and toilets, were designed differently for the military.  But today, almost all information technology is dual use.  We both use the same operating systems, the same networking protocols, the same applications, and even the same security software.</p>

<p>And attack technologies are the same.  The recent spurt of targeted hacks against U.S. military networks, commonly attributed to China, exploit the same vulnerabilities and use the same techniques as criminal attacks against corporate networks.  Internet worms make the jump to physically-separate classified military networks in less than 24 hours, even if those networks are physically separate.  The <a href="https://www.ncdoc.navy.mil/">Navy Cyber Defense Operations Command</a> uses the same tools against the same threats as any large corporation.</p>

<p>Because attackers and defenders use the same IT technology, there is a fundamental tension between cyberattack and cyberdefense. The National Security Agency has referred to this as the "equities issue," and it can be summarized as follows: When a military discovers a vulnerability in a dual-use technology, they can do one of two things.  They can alert the manufacturer and fix the vulnerability, thereby protecting both the good guys and the bad guys.  Or they can keep quiet about the vulnerability and not tell anyone, thereby leaving the good guys insecure but also leaving the bad guys insecure.</p>

<p>The equities issue has long been hotly debated inside the NSA.  Basically, the NSA has two roles: eavesdrop on their stuff, and protect our stuff.  When both sides use the same stuff, the agency has to decide whether to exploit vulnerabilities to eavesdrop on their stuff or close the same vulnerabilities to protect our stuff.</p>

<p>In the 1980s and before, the tendency of the NSA was to keep vulnerabilities to themselves.  In the 1990s, the tide shifted, and the NSA was starting to open up and help us all improve our security defense.  But after the attacks of 9/11, the NSA shifted back to the attack: vulnerabilities were to be hoarded in secret.  Slowly, things in the U.S. are shifting back again.</p>

<p>So now we're seeing the NSA <a href="http://www.schneier.com/blog/archives/2007/01/nsa_helps_micro_1.html">help secure Windows Vista</a> and releasing their <a href="http://www.nsa.gov/selinux/">own version of Linux</a>. The DHS, meanwhile, is funding a project to <a href="http://www.eweek.com/c/a/Security/DHS-Funds-OpenSource-Security-Project/">secure popular open source software packages</a>, and across the Atlantic the UK’s GCHQ is finding bugs in PGPDisk and reporting them back to the company.  (NSA is rumored to be doing the same thing with BitLocker.)</p>

<p>I'm in favor of this trend, because my security improves for free.  Whenever the NSA finds a security problem and gets the vendor to fix it, our security gets better.  It's a side-benefit of dual-use technologies.</p>

<p>But I want governments to do more.  I want them to use their buying power to improve my security.  I want them to offer countrywide contracts for software, both security and non-security, that have explicit security requirements.  If these contracts are big enough, companies will work to modify their products to meet those requirements.  And again, we all benefit from the security improvements.</p>

<p>The only example of this model I know about is a U.S. government-wide procurement competition for <a href="http://www.schneier.com/blog/archives/2007/01/us_government_t.html">full-disk encryption</a>, but this can certainly be done with firewalls, intrusion detection systems, databases, networking hardware, even operating systems.</p>

<p>When it comes to IT technologies, the equities issue should be a no-brainer.  The good uses of our common hardware, software, operating systems, network protocols, and everything else vastly outweigh the bad uses.  It's time that the government used its immense knowledge and experience, as well as its buying power, to improve cybersecurity for all of us.</p>

<p>This essay <a href="http://www.wired.com/politics/security/commentary/securitymatters/2008/05/blog_securitymatters_0501">originally appeared</a> on Wired.com.</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=s6bk9H"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=s6bk9H" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=dIFfqH"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=dIFfqH" border="0"></img></a>
</div>]]></content:encoded>
      <pubDate>Tue, 06 May 2008 01:17:24 +0000</pubDate>
      <category domain="http://securityratty.com/tag/technologies">technologies</category>
      <category domain="http://securityratty.com/tag/dual-use technologies">dual-use technologies</category>
      <category domain="http://securityratty.com/tag/bad guys insecure">bad guys insecure</category>
      <category domain="http://securityratty.com/tag/guys">guys</category>
      <category domain="http://securityratty.com/tag/dual">dual</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/non-security">non-security</category>
      <category domain="http://securityratty.com/tag/security improves">security improves</category>
      <category domain="http://securityratty.com/tag/security improvements">security improvements</category>
      <source url="http://www.schneier.com/blog/archives/2008/05/dualuse_technol.html">Dual-Use Technologies and the Equities Issue</source>
    </item>
    <item>
      <title><![CDATA[Dual-Use Technologies and the Equities Issue]]></title>
      <link>http://securityratty.com/article/1d05ea6ca2a32ede477cd62e958e31c8</link>
      <guid>http://securityratty.com/article/1d05ea6ca2a32ede477cd62e958e31c8</guid>
      <description><![CDATA[On April 27, 2007, Estonia was attacked in cyberspace. Following a diplomatic incident with Russia about the relocation of a Soviet World War II memorial, the networks of many Estonian organizations,...]]></description>
      <content:encoded><![CDATA[<p>On April 27, 2007, Estonia was attacked in cyberspace.  Following a diplomatic incident with Russia about the relocation of a Soviet World War II memorial, the networks of many Estonian organizations, including the Estonian parliament, banks, ministries, newspapers and broadcasters, were attacked and -- in many cases -- shut down.  Estonia was quick to blame Russia, which was equally quick to deny any involvement.  </p>

<p>It was <a href="http://www.wired.com/politics/security/magazine/15-09/ff_estonia">hyped</a> as the first cyberwar: Russia attacking Estonia in cyberspace.  But nearly a year later, evidence that the Russian government was involved in the denial-of-service attacks still hasn't emerged. Though Russian hackers were indisputably the major instigators of the attack, the only individuals <a href="http://blog.wired.com/27bstroke6/2008/01/we-traced-the-c.html">positively identified</a> have been young ethnic Russians living inside Estonia, who were  pissed off over the statue incident.</p>

<p>You know you've got a problem when you can't tell a hostile attack by another nation from bored kids with an axe to grind. </p>

<p>Separating cyberwar, cyberterrorism and cybercrime isn't easy; these days you need a <a href="http://www.schneier.com/blog/archives/2007/06/cyberwar.html">scorecard to tell the difference</a>.  It's not just that it’s hard to trace people in cyberspace, it's that military and civilian attacks -- and defenses -- look the same.  </p>

<p>The traditional term for technology the military shares with civilians is "dual use."  Unlike hand grenades and tanks and missile targeting systems, dual-use technologies have both military and civilian applications.  Dual-use technologies used to be exceptions; even things you'd expect to be dual use, like radar systems and toilets, were designed differently for the military.  But today, almost all information technology is dual use.  We both use the same operating systems, the same networking protocols, the same applications, and even the same security software.</p>

<p>And attack technologies are the same.  The recent spurt of targeted hacks against U.S. military networks, commonly attributed to China, exploit the same vulnerabilities and use the same techniques as criminal attacks against corporate networks.  Internet worms make the jump to classified military networks in less than 24 hours, even if those networks are physically separate.  The <a href="https://www.ncdoc.navy.mil/">Navy Cyber Defense Operations Command</a> uses the same tools against the same threats as any large corporation.</p>

<p>Because attackers and defenders use the same IT technology, there is a fundamental tension between cyberattack and cyberdefense. The National Security Agency has referred to this as the "equities issue," and it can be summarized as follows: When a military discovers a vulnerability in a dual-use technology, they can do one of two things.  They can alert the manufacturer and fix the vulnerability, thereby protecting both the good guys and the bad guys.  Or they can keep quiet about the vulnerability and not tell anyone, thereby leaving the good guys insecure but also leaving the bad guys insecure.</p>

<p>The equities issue has long been hotly debated inside the NSA.  Basically, the NSA has two roles: eavesdrop on their stuff, and protect our stuff.  When both sides use the same stuff, the agency has to decide whether to exploit vulnerabilities to eavesdrop on their stuff or close the same vulnerabilities to protect our stuff.</p>

<p>In the 1980s and before, the tendency of the NSA was to keep vulnerabilities to themselves.  In the 1990s, the tide shifted, and the NSA was starting to open up and help us all improve our security defense.  But after the attacks of 9/11, the NSA shifted back to the attack: vulnerabilities were to be hoarded in secret.  Slowly, things in the U.S. are shifting back again.</p>

<p>So now we're seeing the NSA <a href="http://www.schneier.com/blog/archives/2007/01/nsa_helps_micro_1.html">help secure Windows Vista</a> and releasing their <a href="http://www.nsa.gov/selinux/">own version of Linux</a>. The DHS, meanwhile, is funding a project to <a href="http://www.eweek.com/c/a/Security/DHS-Funds-OpenSource-Security-Project/">secure popular open source software packages</a>, and across the Atlantic the UK’s GCHQ is finding bugs in PGPDisk and reporting them back to the company.  (NSA is rumored to be doing the same thing with BitLocker.)</p>

<p>I'm in favor of this trend, because my security improves for free.  Whenever the NSA finds a security problem and gets the vendor to fix it, our security gets better.  It's a side-benefit of dual-use technologies.</p>

<p>But I want governments to do more.  I want them to use their buying power to improve my security.  I want them to offer countrywide contracts for software, both security and non-security, that have explicit security requirements.  If these contracts are big enough, companies will work to modify their products to meet those requirements.  And again, we all benefit from the security improvements.</p>

<p>The only example of this model I know about is a U.S. government-wide procurement competition for <a href="http://www.schneier.com/blog/archives/2007/01/us_government_t.html">full-disk encryption</a>, but this can certainly be done with firewalls, intrusion detection systems, databases, networking hardware, even operating systems.</p>

<p>When it comes to IT technologies, the equities issue should be a no-brainer.  The good uses of our common hardware, software, operating systems, network protocols, and everything else vastly outweigh the bad uses.  It's time that the government used its immense knowledge and experience, as well as its buying power, to improve cybersecurity for all of us.</p>

<p>This essay <a href="http://www.wired.com/politics/security/commentary/securitymatters/2008/05/blog_securitymatters_0501">originally appeared</a> on Wired.com.</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=EwyO1H"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=EwyO1H" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/schneier/fulltext?a=TsVOVH"><img src="http://feeds.feedburner.com/~f/schneier/fulltext?i=TsVOVH" border="0"></img></a>
</div>]]></content:encoded>
      <pubDate>Tue, 06 May 2008 01:17:24 +0000</pubDate>
      <category domain="http://securityratty.com/tag/technologies">technologies</category>
      <category domain="http://securityratty.com/tag/dual-use technologies">dual-use technologies</category>
      <category domain="http://securityratty.com/tag/bad guys insecure">bad guys insecure</category>
      <category domain="http://securityratty.com/tag/guys">guys</category>
      <category domain="http://securityratty.com/tag/dual">dual</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/non-security">non-security</category>
      <category domain="http://securityratty.com/tag/security improves">security improves</category>
      <category domain="http://securityratty.com/tag/security improvements">security improvements</category>
      <source url="http://www.schneier.com/blog/archives/2008/05/dualuse_technol_1.html">Dual-Use Technologies and the Equities Issue</source>
    </item>
    <item>
      <title><![CDATA[America's Dilemma: Close Security Holes, or Exploit Them Ourselves]]></title>
      <link>http://securityratty.com/article/6c5a6bba27a7c8a251a63217810ea9a6</link>
      <guid>http://securityratty.com/article/6c5a6bba27a7c8a251a63217810ea9a6</guid>
      <description><![CDATA[On April 27, 2007, Estonia was attacked in cyberspace. Following a diplomatic incident with Russia about the relocation of a Soviet World War II memorial, the networks of many Estonian organizations,...]]></description>
      <content:encoded><![CDATA[<p>On April 27, 2007, Estonia was attacked in cyberspace.  Following a diplomatic incident with Russia about the relocation of a Soviet World War II memorial, the networks of many Estonian organizations, including the Estonian parliament, banks, ministries, newspapers and broadcasters, were attacked and -- in many cases -- shut down.  Estonia was quick to blame Russia, which was equally quick to deny any involvement.  
</p><p>
It was <a href="http://www.wired.com/politics/security/magazine/15-09/ff_estonia">hyped</a> as the <a href="http://www.wired.com/politics/security/magazine/15-09/ff_estonia">first cyberwar</a>: Russia attacking Estonia in cyberspace.  But nearly a year later, evidence that the Russian government was involved in the denial-of-service attacks still hasn't emerged. Though Russian hackers were indisputably the major instigators of the attack, the only individuals <a href="http://blog.wired.com/27bstroke6/2008/01/we-traced-the-c.html">positively identified</a> have been young ethnic Russians living inside Estonia, who were  pissed off over the statue incident.
</p><p>
You know you've got a problem when you can't tell a hostile attack by another nation from bored kids with an axe to grind. 
</p><p>
Separating cyberwar, cyberterrorism and cybercrime isn't easy; these days you need a <a href="http://www.schneier.com/blog/archives/2007/06/cyberwar.html">scorecard to tell the difference</a>.  It's not just that it’s hard to trace people in cyberspace, it's that military and civilian attacks -- and defenses -- look the same.  
</p><p>
The traditional term for technology the military shares with civilians is "dual use."  Unlike hand grenades and tanks and missile targeting systems, dual-use technologies have both military and civilian applications.  Dual-use technologies used to be exceptions; even things you'd expect to be dual use, like radar systems and toilets, were designed differently for the military.  But today, almost all information technology is dual use.  We both use the same operating systems, the same networking protocols, the same applications, and even the same security software.
</p><p>
And attack technologies are the same.  The recent spurt of targeted hacks against U.S. military networks, commonly attributed to China, exploit the same vulnerabilities and use the same techniques as criminal attacks against corporate networks.  Internet worms make the jump to physically-separate classified military networks in less than 24 hours, even if those networks are physically separate.  The <a href="https://www.ncdoc.navy.mil/">Navy Cyber Defense Operations Command</a> uses the same tools against the same threats as any large corporation.
</p><p>
Because attackers and defenders use the same IT technology, there is a fundamental tension between cyberattack and cyberdefense. The National Security Agency has referred to this as the "equities issue," and it can be summarized as follows: When a military discovers a vulnerability in a dual-use technology, they can do one of two things.  They can alert the manufacturer and fix the vulnerability, thereby protecting both the good guys and the bad guys.  Or they can keep quiet about the vulnerability and not tell anyone, thereby leaving the good guys insecure but also leaving the bad guys insecure.
</p><p>
The equities issue has long been hotly debated inside the NSA.  Basically, the NSA has two roles: eavesdrop on their stuff, and protect our stuff.  When both sides use the same stuff, the agency has to decide whether to exploit vulnerabilities to eavesdrop on their stuff or close the same vulnerabilities to protect our stuff.
</p><p>
In the 1980s and before, the tendency of the NSA was to keep vulnerabilities to themselves.  In the 1990s, the tide shifted, and the NSA was starting to open up and help us all improve our security defense.  But after the attacks of 9/11, the NSA shifted back to the attack: vulnerabilities were to be hoarded in secret.  Slowly, things in the U.S. are shifting back again.
</p><p>
So now we're seeing the NSA <a href="http://www.schneier.com/blog/archives/2007/01/nsa_helps_micro_1.html">help secure Windows Vista</a> and releasing their <a href="http://www.nsa.gov/selinux/">own version of Linux</a>. The DHS, meanwhile, is funding a project to <a href="http://www.eweek.com/c/a/Security/DHS-Funds-OpenSource-Security-Project/">secure popular open source software packages</a>, and across the Atlantic the UK’s GCHQ is finding bugs in PGPDisk and reporting them back to the company.  (NSA is rumored to be doing the same thing with BitLocker.)
</p><p>
I'm in favor of this trend, because my security improves for free.  Whenever the NSA finds a security problem and gets the vendor to fix it, our security gets better.  It's a side-benefit of dual-use technologies.
</p><p>
But I want governments to do more.  I want them to use their buying power to improve my security.  I want them to offer countrywide contracts for software, both security and non-security, that have explicit security requirements.  If these contracts are big enough, companies will work to modify their products to meet those requirements.  And again, we all benefit from the security improvements.
</p><p>
The only example of this model I know about is a U.S. government-wide procurement competition for <a href="http://www.schneier.com/blog/archives/2007/01/us_government_t.html">full-disk encryption</a>, but this can certainly be done with firewalls, intrusion detection systems, databases, networking hardware, even operating systems.
</p><p>
When it comes to IT technologies, the equities issue should be a no-brainer.  The good uses of our common hardware, software, operating systems, network protocols, and everything else vastly outweigh the bad uses.  It's time that the government used its immense knowledge and experience, as well as its buying power, to improve cybersecurity for all of us.
</p><p>

---

<p>
<em>Bruce Schneier is CTO of BT Counterpane and author of </em><a href="http://www.schneier.com/bf.html">Beyond Fear: Thinking Sensibly About Security in an Uncertain World</a><em>. You can read more of his writings on his <a href="http://www.schneier.com/">website</a>.</em>
</p><br style="clear: both;"/>
  <img alt="" style="border: 0; height:1px; width:1px;" border="0" src="http://www.pheedo.com/img.phdo?i=41dd69cbe69db123540011715fc85efe" height="1" width="1"/>
<img src="http://www.pheedo.com/feeds/tracker.php?i=41dd69cbe69db123540011715fc85efe" style="display: none;" border="0" height="1" width="1" alt=""/><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=19SaqG"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=19SaqG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=Nxxvdg"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=Nxxvdg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=n2OLyg"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=n2OLyg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/wired/politics/privacy?a=bXDtBG"><img src="http://feeds.feedburner.com/~f/wired/politics/privacy?i=bXDtBG" border="0"></img></a>
 <a href="http://feeds.wired.com/~f/wired/politics/security?a=0cARiG"><img src="http://feeds.wired.com/~f/wired/politics/security?i=0cARiG" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=Zquz9g"><img src="http://feeds.wired.com/~f/wired/politics/security?i=Zquz9g" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=KDtrqg"><img src="http://feeds.wired.com/~f/wired/politics/security?i=KDtrqg" border="0"></img></a> <a href="http://feeds.wired.com/~f/wired/politics/security?a=G2B3DG"><img src="http://feeds.wired.com/~f/wired/politics/security?i=G2B3DG" border="0"></img></a> </div><img src="http://feeds.feedburner.com/~r/wired/politics/privacy/~4/281236763" height="1" width="1"/><img src="http://feeds.wired.com/~r/wired/politics/security/~4/281236764" height="1" width="1"/>]]></content:encoded>
      <pubDate>Thu, 01 May 2008 00:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/bad guys insecure">bad guys insecure</category>
      <category domain="http://securityratty.com/tag/guys">guys</category>
      <category domain="http://securityratty.com/tag/non-security">non-security</category>
      <category domain="http://securityratty.com/tag/security improves">security improves</category>
      <category domain="http://securityratty.com/tag/technologies">technologies</category>
      <category domain="http://securityratty.com/tag/dual-use technologies">dual-use technologies</category>
      <category domain="http://securityratty.com/tag/security improvements">security improvements</category>
      <category domain="http://securityratty.com/tag/agency">agency</category>
      <source url="http://feeds.wired.com/~r/wired/politics/security/~3/281236764/blog_securitymatters_0501">America's Dilemma: Close Security Holes, or Exploit Them Ourselves</source>
    </item>
    <item>
      <title><![CDATA[700,000 records on stolen CCB server]]></title>
      <link>http://securityratty.com/article/31a0c887e162bd0eecb24965eb90aaeb</link>
      <guid>http://securityratty.com/article/31a0c887e162bd0eecb24965eb90aaeb</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
4/18/08

Organization
Numerous

See Commentary section for list of businesses

Contractor/Consultant/Branch
Central Collection Bureau (&quot;CCB

Victims...]]></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/cbb.jpg" align="right" height="150" width="150"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>4/18/08<br><br><span style="font-weight: bold;">Organization: </span><br>Numerous*<br><br><font size="1">*See Commentary section for list of businesses</font><br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.ccbinc.net/index.htm">Central Collection Bureau ("CCB")</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Individuals who were referred to CCB for debt collection purposes by Indiana businesses, on or before March 20, 2008 <br><br><span style="font-weight: bold;">Number Affected:</span><br>~700,000<br><br><span style="font-weight: bold;">Types of Data:</span><br>"personal information, including names, contact information, Social Security numbers, dates of birth, dates of service, and medical procedure codes"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"Indiana residents are hereby alerted to a security breach at Central Collection Bureau (CCB, located at 7510 South Madison Avenue, Indianapolis, Indiana.&nbsp; This breach potentially exposed the personal information, including names, contact information, Social Security numbers, dates of birth, dates of service, and medical procedure codes."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.ccbinc.net/press_release_04182008.htm">Central Collection Bureau</a> <br><a href="http://www.suntimes.com/news/nation/906211,identity042108.article">Chicago Sun-Times (Associated Press)</a> <br><a href="http://www.wthr.com/Global/story.asp?S=8195357&amp;nav=menu188_2">NBC Channel 13 Eyewitness News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Central Collection Bureau<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>SECURITY BREACH NOTIFICATION ALERT:<br>CENTRAL COLLECTION BUREAU<br>Dated April 18, 2008<br><br>Indiana residents are hereby alerted to a security breach at Central Collection Bureau (CCB, located at 7510 South Madison Avenue, Indianapolis, Indiana. <br><br>This breach potentially exposed the personal information, including names, contact information, Social Security numbers, dates of birth, dates of service, and medical procedure codes.<br><br>These individuals were referred to CCB for debt collection purposes by Indiana businesses, on or before March 20, 2008 <br><br>Approximately 700,000 files may have been breached.<br><br>The businesses that engaged CCB for debt collection during that period of time are listed below.<br><br>Please note that only a very small percentage of the individuals who were patients or customers of the businesses below—i.e., those who ultimately were referred for debt collection—would have their personal information included in the CCB database.<br><br>Some of the information might be outdated. St. Vincent Health System said it had not given any billing business to Central Collection in more than three years, so all of the missing billing information is several years old.<br><span style="font-style: italic;">[Evan] This was a question that my colleagues and I were debating about this breach.&nbsp; 700,000 records seems like an awful lot of "active" collection accounts.&nbsp; CCB would need quite a few collection agents to service this many accounts, if in fact they were all active.&nbsp; I think we can assume that only a fraction of the 700,000 records were actually "active" and CCB did not effectively destroy information that they no longer needed to keep.</span><br><br>Other patients and customers of those companies are not affected by this breach.<br><br>The theft occurred on Friday, March 21, 2008, at CCB's location in Indianapolis.<br><br>On that date,&nbsp; thieves broke into the company's offices and stole 8 computers, as well as one of its servers (databases).<br><br>The server was password protected and protected by three locked doors.&nbsp; The 8 computers did not contain personal information.<br><br>The information was protected by two passwords but was not encrypted, Klene said.<br><br>"Our server was password protected. We have obviously spoken to some IT people who feel that a good computer hacker could get through those passwords," he said.<br><span style="font-style: italic;">[Evan] It doesn't even take a "good computer hacker" to get through the passwords.</span><br><br>CCB promptly contacted the police and is working with the Indiana Attorney General's office. <br><br>The company also promptly installed additional locks, a security system, and a motion detection system to help minimize the risk of any further unauthorized access to its information.<br><span style="font-style: italic;">[Evan] These will help with physical security.&nbsp; Full-disk encryption and a effective data retention policy wouldn't hurt for logical security, eh?&nbsp; Us information security guys would refer to multiple defensive layers as "defense in depth".&nbsp; Brilliant!</span><br><br>CCB apologizes to its clients and all Indiana residents affected by this incident.<br><br>"We're obviously heartsick about this," said Chet Klene, Central Collection Bureau president. "We've been in business since 1972, and nothing like this has ever happened before."<br><span style="font-style: italic;">[Evan] I don't doubt that CCB is "heartsick" by this incident.&nbsp; I feel bad for them and the fact that they probably did not know any better.&nbsp; Maybe this is partly a failure on the part of the information security profession as a whole.</span><br><br>While the company has no information suggesting that the breach occurred for purposes of identity theft, it nevertheless has contacted the three national credit bureaus to place a fraud alert.<br><br>Please go to the CCB website at <a href="http://www.ccbinc.net,">www.ccbinc.net,</a> call CCB at 317-887-5165 or 1-800-878-5165 or email CCB at theft@ccbinc.net for more information<br><br><span style="font-weight: bold;">Commentary:</span><br>Clients of CCB with information on the stolen server include:&nbsp; <br><br>Academy Animal Hospital, Advanced Interventional Pain, Advanced Physical Therapy, Alternative Care Experience, Anderson General Surgery, Andrew Dick MD, Anesthesia, Aqua Systems, Associated Billing, "Barbara Sturm, MD", Brad Sammons DDS, Brien Grow DO, Buchanan Counseling Services, Campion Barrow &amp; Assoc., Cardiothoracis Surgeons, Cardiovascular Diagnostic Services, Carl Foster MD, Caryn Guba DDS, Center For Orthopaedic Surgery, Central Indiana Phys Medicine &amp; Rehab, Charles Howe Professional Medical Corp, Charles Kelley III DPM, Charles Kerkhove Jr DDS, Charles Tomich DDS, Chiropractic Thereputics, Citizens Gas &amp; Coke, City of Franklin Ambulance, Clarian Radiology, Clinical Laboratory Physicians, Comdent, Comprecare, Culligan Water Conditioning, Cummins Behavioral Health System, D.E. Kelley DDS, Daniel Feeny MD, David Pennington III MD, David Shaw MD, David Szentes MD, Denture By Design, Dermatopathology Lab, Diagnostic Medicine, Dunlap Urgent Care, Edward J Diekhoff MD, Emily Cline MD, Emergency Medical Group Physicians, Forest Creek Family Dental, Friendly Village of Indy, Gary Hunt DDS, Gary Taylor DDS, Generations In Dentistry, George Small Jr MD, Gial Anesthesiology Service, Grandmas House Child Care, Greg Hardin MD, Hamilton Anesthesia Group, Hearing Center, Henderson Drugs &amp; Home Health, House of Kids, Howard Alig MD, Howard Regional Health System, Indiana Radiology Partners, Indiana Spine Group, Indiana General Surgery, Indiana Medical Network, Indpls Neurosurgical Group, Internal Medicine Plus, JCB Anesthesia &amp; Pain Mgt, Jeffrey Stevens DPM, Jennifer Siegel DDS, JMH Health Affiliates, John Jackson DC, John Norris MD, Johnson Co Anesthesia, Johnson County REMC, Johnson Memorial Hospital, Joseph Meek DDS, Julie Chao MD, Kenny Stall MD, Kerry Mays MD, Kevin Macadaeg MD, Khalil Wakim MD, Kidd Pediatrics, Knowledge Learning Corp, Koehring &amp; Sons, Kokomo Sports Center, Larry Buckel MD, Laura Steiner MD, Laura Stitle MD, Laurette Robey MD, Laverne Tubergen MD, Lawrence Falender DDS, Library Park Immediate Care, Lora Overton DO, Madison Anesthesia Group, Madison Avenue Flower Shop, Mark Ellis DDS, Mark Kahn DDS, Mark Ogle MD, Mark Yamanaka MD, Martinsville Dental Center, Memory Maker Studios, Mere Image Sportswear, Meridian Veterinary Clinic, Methodist Arthritis Physicians, Methodist Medical Group, Michael Arnold DDS, Michael Cozzi MD, Michael Harper, Midamerica Surgery Center, Milto Cleaners, Mitchell Foster MD, Muncie Cataract &amp; Laser Center, Nancy Zinni MD, Northside Surgical Specialists, Northside Anesthesia Services, Northwest Medical Pain Control, Nufinity, Orthopaedic Supplies Inc., Panchapakesan Harlan MD, Paul Batties MD, Paul Johnson DDS, Paul Johnson DDS, Paul Strange MD, Philip Borders MD, Pioneer Anesthesia Consultanta, PT Buntin MD, R.D. McQuiston MD, Rebecca De La Rosa DDS, Richard Herd Jr DDS, Rick Stephens Builder, Riley Bennett &amp; Egloff LLP, Robert Smith MD, Robert's Salon &amp; Day Spa, Ronald Wines DDS, RW Armstrong, Sandhya Nanda MD, Sarah Akard DDS, Scot Hagadorn MD, South Emerson Anesthesia Assoc., South Emerson Pain Management, South Emerson Surgery Center, Southeast Family Physicians, Southside Animal Hospital, Southside Family Medical Group, Southside Pediatrics, St. Vincent Health and related entities, Stephen Stitle MD, Stephen Szynal DO, Stonehedge Apartments, Stop 11 Animal Hospital, Sun Medical, Surgical Associates of Madison Co, Susan Wagner DDS, Thomas Eads MD, Thomas Ferrara MD, Tim Schafer DDS, University Family Physicians, University Pediatric Associates, University Surgeons, USF Inc, Valle Vista Guidance Center, Valle Vista Hospital, Walker Family Dentistry, Wells &amp; Marvel PC <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/04/22/cbb.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 22 Apr 2008 10:57:38 +0000</pubDate>
      <category domain="http://securityratty.com/tag/dds">dds</category>
      <category domain="http://securityratty.com/tag/gary taylor dds">gary taylor dds</category>
      <category domain="http://securityratty.com/tag/gary hunt dds">gary hunt dds</category>
      <category domain="http://securityratty.com/tag/lawrence falender dds">lawrence falender dds</category>
      <category domain="http://securityratty.com/tag/joseph meek dds">joseph meek dds</category>
      <category domain="http://securityratty.com/tag/caryn guba dds">caryn guba dds</category>
      <category domain="http://securityratty.com/tag/mark ellis dds">mark ellis dds</category>
      <category domain="http://securityratty.com/tag/sarah akard dds">sarah akard dds</category>
      <category domain="http://securityratty.com/tag/ccb">ccb</category>
      <source url="http://breachblog.com/2008/04/22/cbb.aspx">700,000 records on stolen CCB server</source>
    </item>
    <item>
      <title><![CDATA[You never know whose tomorrow it will be]]></title>
      <link>http://securityratty.com/article/47215e75beabf108c4cfbdd7216d3f03</link>
      <guid>http://securityratty.com/article/47215e75beabf108c4cfbdd7216d3f03</guid>
      <description><![CDATA[Beware -Another non-security story . Last week I wrote a story about my son Landon and how proud I was about his experience in baseball. I used a Yiddish word that I learned from my Grandmother -...]]></description>
      <content:encoded><![CDATA[
<div xmlns="http://www.w3.org/1999/xhtml"><p><em>Beware -Another non-security story</em>. Last week I wrote <a href="http://www.stillsecureafteralltheseyears.com/ashimmy/2008/03/this-weeks-yidd.html" target="_blank">a story</a> about my son Landon and how proud I was about his experience in baseball.&nbsp; I used a Yiddish word that I learned from my Grandmother - <em>naches</em>.&nbsp; As I have gotten older I have developed a deeper admiration and respect for the inherent wisdom that my Grandmother brought to life and the many things I learned from her.&nbsp; I remember being younger and thinking she was a little bit <em>meshuguna</em> as she would say. But as I now realize she was crazy as a fox and I hope I can be only half as intuitively smart as she was.&nbsp; She had an intuitive grasp of people and life that cannot be learned in books.&nbsp; People who think I am outgoing and loud would think me quiet and shy in comparison to her. But enough about my grandma, let me get on with the story.&nbsp; </p>

<p>One of the phrases she used to use that I would laugh at was, &quot;my grandson, you never know whose tomorrow it will be&quot;.&nbsp; I was never quite sure what that meant, but had enough of the general gist that I didn't question her.&nbsp; Today again I heard my Grandmother talking to me and saying that very phrase.&nbsp; I had contacted an old business partner of mine who I had not spoken to in 3 or 4 years. I knew he had season tickets to the Yankees and wanted to buy a couple of tickets to take my sons to the Stadium in this its last year.&nbsp; My old partner &quot;Bob&quot; called me back this morning, very early not realizing I was out in California.&nbsp; Of course I asked how he was and he replied that he had been diagnosed with pancreatic cancer a while ago. He has undergone surgery and is receiving chemo at Sloan-Kettering Memorial, but the prognosis is not good.&nbsp; Bob is just a few years older than me and his youngest child is just 10 years old.&nbsp; I have known Bob for 20 years.&nbsp; He was always the kind of guy who did the right thing.&nbsp; A good family guy, he grew up like I did on the Long Island-Queens border in NY from working class parents. He worked hard and bought a house in Westchester County for&nbsp; his wife, children and he.&nbsp; He lived the American dream, working hard and passing on to his children the best of what he knew. What are you supposed to say to someone who tells you this?&nbsp; Are there any words that provide comfort?&nbsp; Is going to a frigging Yankee game relevant here?&nbsp; Of course you try to be brave for their sake.&nbsp; You say things like &quot;they are doing so much with that disease now.&nbsp; Keep your head up, attitude is important.&quot;&nbsp; Maybe most of all, I will pray for you. How cruel is fate that this good, decent human being has been chosen to suffer from this death sentence of a disease at such a young age?&nbsp; Of course Bob is not alone. Unfortunately I know too many good people who have been stricken with terminal illnesses well before their time here should be done.</p>

<p>I was speaking to a friend/family member the other day about the breakup of his marriage and I told him life is rarely what we think it is going to be.&nbsp; Making lemonade out of lemons seems to be the ultimate and eternal human condition. It also drives home my grandmother's inherent intelligence.&nbsp; You never know whose tomorrow it will be.&nbsp; I get it now, you never know for whom the bell tolls.&nbsp; All we can do is enjoy the good moments that God, fate or whatever grants us, because in an instant that can all be taken away and our lives changed forever.&nbsp; Bob is in my prayers and I hope for a miracle for him and others who have to face similar challenges. Lesson to you all enjoy the moment, cause you never do know whose tomorrow it will be.</p></div>

<p><a href="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?a=lvlizk"><img src="http://feeds.feedburner.com/~a/StillsecureAfterAllTheseYears?i=lvlizk" border="0"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=HzylGlG"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=HzylGlG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=baFTfNG"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=baFTfNG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=nA2hoKG"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=nA2hoKG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=eWQciqG"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=eWQciqG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=XdEDKLg"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=XdEDKLg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?a=A25qoEg"><img src="http://feeds.feedburner.com/~f/StillsecureAfterAllTheseYears?i=A25qoEg" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~4/265961560" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 07 Apr 2008 14:52:27 +0000</pubDate>
      <category domain="http://securityratty.com/tag/tomorrow">tomorrow</category>
      <category domain="http://securityratty.com/tag/bob">bob</category>
      <category domain="http://securityratty.com/tag/grandmother">grandmother</category>
      <category domain="http://securityratty.com/tag/guy">guy</category>
      <category domain="http://securityratty.com/tag/life">life</category>
      <category domain="http://securityratty.com/tag/yankee game relevant">yankee game relevant</category>
      <category domain="http://securityratty.com/tag/season tickets">season tickets</category>
      <category domain="http://securityratty.com/tag/people">people</category>
      <category domain="http://securityratty.com/tag/partner">partner</category>
      <source url="http://feeds.feedburner.com/~r/StillsecureAfterAllTheseYears/~3/265961560/you-never-know.html">You never know whose tomorrow it will be</source>
    </item>
    <item>
      <title><![CDATA[Donor personal information was on Lifeblood stolen laptop]]></title>
      <link>http://securityratty.com/article/942b00ba051c5682ac533eb6b8c57745</link>
      <guid>http://securityratty.com/article/942b00ba051c5682ac533eb6b8c57745</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
2/13/08

Organization
Lifeblood

Contractor/Consultant/Branch
None

Victims
Blood donors

Number Affected
320,000

Types of Data
names, contact...]]></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/lifeblood.jpg" align="right" height="69" width="199"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>2/13/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.lifeblood.org" target="_blank"> Lifeblood</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>Blood donors<br><br><span style="font-weight: bold;">Number Affected:</span><br>320,000<br><br><span style="font-weight: bold;">Types of Data:</span><br>"names, contact information, blood type, gender, ethnicity, and, in some cases, Social Security numbers"<br><br><span style="font-weight: bold;">Breach Description:</span><br>Two laptop computers are lost and presumed stolen from a storage room at the Lifeblood office building.&nbsp; The laptops contained sensitive and personal information belonging to blood donors.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.lifeblood.org/index.php?option=com_content&amp;task=view&amp;id=108&amp;Itemid=35" target="_blank"> Lifeblood Press Release</a> <br><a href="http://www.commercialappeal.com/news/2008/feb/13/missing-lifeblood-laptops-personal-information-tho/" target="_blank"> Commercialappeal.com story</a> <br><a href="http://www.wreg.com/Global/story.asp?S=7869589" target="_blank"> WREG Memphis Channel 3 News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Lifeblood<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>Two laptop computers are missing from Lifeblood’s possession and presumed to be stolen.<br><br>Someone got inside a storage room at the Lifeblood building on Madison and took the computers.<br><br>The dual-password protected laptops were used on mobile blood collection drives, and each included information about Lifeblood’s blood donors, including names, contact information, blood type, gender, ethnicity, and, in some cases, Social Security numbers.<br><span style="font-style: italic;">[Evan] I have to say, "dual-password protected" sounds very impressive and very secure, but the I should follow-up and say <span style="font-weight: bold;">IT'S NOT</span>.&nbsp; I am guessing that one password is for the operating system, which takes less than five minutes to bypass/change and I am also guessing that there is (was) a password to access the database or the program that opens the database.&nbsp; The second password probably isn't that hard to crack/bypass either.</span><br><br>The organization is notifying all of the approximately 320,000 affected individuals about the situation and encouraging them to place fraud alerts on their credit reports in the unlikely event that an unauthorized person gained access to the data on the computers.<br><span style="font-style: italic;">[Evan] What a hassle for 320,000 people.</span><br><br>Lifeblood started sending out letters to donors this week, notifying them about what happened.<br><br>Based on the level of password security and the intricacies of the database structure, Lifeblood believes that is extremely unlikely that an individual who is not specifically trained to use the laptop and who does not have a valid Lifeblood ID and password could access the information contained on it.<br><span style="font-style: italic;">[Evan] If this statement weren't so sad, it would be funny.&nbsp; I could stretch and maybe agree with "unlikely", but I would certainly not go as far as to say "extremely unlikely".&nbsp; It really is easier than most people think.</span><br><br>"Our hope was we'd be able to locate the devices and with that we'd be able to find whether the database had been accessed or not," said Dr. Edward Scott of Lifeblood.<br><br>Since the discovery Lifeblood has implemented additional security measures to protect against future theft of property or donor information. These measures include more restrictive access to and continuous closed circuit monitoring of the areas housing the laptops, installation of software to allow remote tracking and erasure of the hard drives on laptops used on mobile drives, and additional programming to prevent full Social Security numbers from being downloaded to mobile laptops.<br><span style="font-style: italic;">[Evan] WHERE IS ENCRYPTION?&nbsp; Remote tracking and erasure provides some protection, but it isn't very hard to disable/bypass either to anyone with skill.&nbsp; <span style="font-weight: bold;">Nobody </span>breaks strong encryption with sound key management, no matter how skilled they may be.&nbsp; Why does a donor have to supply a Social Security number to donate blood in the first place?&nbsp; What does my blood have to do with my Social Security benefits?</span><br><br>He says a private investigator's been working this case. But with no solid leads, they've now teamed up with Memphis Police.<br><br>"We're concerned it may be a former employee. Or someone else who had access to building at the time," said Dr. Scott.<br><span style="font-style: italic;">[Evan] Someone did have access or the laptops wouldn't be stolen.</span><br><br>The worry now though is that this breach will discourage people from donating.<br><br>"Blood is always going to be needed in the community, there's no substitute for that," said Dr. Scott.<br><span style="font-style: italic;">[Evan] This is by far the most intelligent remark of any I have read about this breach.&nbsp; <span style="font-weight: bold;">PEOPLE NEED BLOOD AND BLOOD SAVES LIVES</span>.&nbsp; At the end of the day, I would trade my Social Security number to save someone's life.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>We have now reported two blood centers that each stored confidential personal information on laptops (without encryption) and had them stolen.&nbsp; The other was <a href="http://breachblog.com/2007/12/06/mbc.aspx" target="_blank"> Memorial Blood Centers in Minnesota</a>.&nbsp; I don't understand why blood centers need my Social Security number in order for them to take my blood.&nbsp; I assume they use it as a personal identifier.&nbsp; I would much prefer that they create an identifier for me that cannot be used against me later.<br><br>I <span style="font-weight: bold;">really</span> appreciate all the work that blood centers do for the communities they serve, but they really don't serve the victims well when they don't take the time to properly secure the information they collect.<br><br>I cannot think of a good alternative to laptop encryption.&nbsp; Why won't Lifeblood encrypt confidential data at rest? <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/14/lifeblood.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Thu, 14 Feb 2008 07:17:22 +0000</pubDate>
      <category domain="http://securityratty.com/tag/mobile blood collection">mobile blood collection</category>
      <category domain="http://securityratty.com/tag/blood">blood</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/memorial blood centers">memorial blood centers</category>
      <category domain="http://securityratty.com/tag/blood saves lives">blood saves lives</category>
      <category domain="http://securityratty.com/tag/blood type">blood type</category>
      <category domain="http://securityratty.com/tag/lifebloods blood donors">lifebloods blood donors</category>
      <category domain="http://securityratty.com/tag/lifeblood">lifeblood</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <source url="http://breachblog.com/2008/02/14/lifeblood.aspx">Donor personal information was on Lifeblood stolen laptop</source>
    </item>
  </channel>
</rss>
