<?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: evan]]></title>
    <link>http://securityratty.com/tag/evan</link>
    <description></description>
    <pubDate>Tue, 24 Jun 2008 13:51:19 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Employee fraud at Wells Fargo Home Mortgage affects some customers]]></title>
      <link>http://securityratty.com/article/769d77ddea6a7ce4dd58d70e453e805b</link>
      <guid>http://securityratty.com/article/769d77ddea6a7ce4dd58d70e453e805b</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
5/16/08

Organization
Wells Fargo &amp; Company

Contractor/Consultant/Branch
Wells Fargo Home Mortgage

Victims
Customers

Number Affected
Unknown

Types of...]]></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/wellsfargo.jpg" width="62" align="right" height="62"><font size="2"><b>Date Reported: </b><br>5/16/08<br><br><b>Organization: </b><br><a href="https://www.wellsfargo.com">Wells Fargo &amp; Company</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="https://www.wellsfargo.com/mortgage">Wells Fargo Home Mortgage</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>"names, addresses, dates of birth, loan numbers, Personal Identification Numbers (PIN), current bank account numbers and last five digits of their Social Security numbers"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"We have learned that a former Wells Fargo employee working in our reverse mortgage servicing department inappropriately used another customer's account information. We have taken appropriate action against this individual."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://doj.nh.gov/consumer/pdf/WellsFargoBank.pdf%20">New Hampshire State Attorney General breach notification</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The New Hampshire State Attorney General<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above:<br><br>Pursuant to the information compromise notification requirements of the State of New Hampshire, Wells Fargo hereby notifies you that we have give notice to approximately 24 residents of the state of New Hampshire of a potential compromise of their Social Security numbers and mortgage loan account numbers.<br><br>We have learned that a former Wells Fargo employee working in our reverse mortgage servicing department inappropriately used another customer's account information.<br><span style="font-style: italic;">[Evan] Employee fraud is one of the most difficult breaches to prevent (and sometimes to detect).&nbsp; Most controls are largely administrative in nature such as background checks, segregation of duties, job rotation, policy and procedure, etc.&nbsp; Sometimes even the best controls won't do much to prevent an attack from the enemy within.</span><br style="font-style: italic;"><br>We have taken appropriate action against this individual.<br><span style="font-style: italic;">[Evan] I wonder what this means.</span><br><br>We have no information indicating your information was compromised.<br><br>However, the former employee, in the course of their employment, had access to information that may have included your name, address, date of birth, loan number, Personal Identification Number (PIN), current bank account number and last five digits of your Social Security number.<br><span style="font-style: italic;">[Evan] The fact that only the last five digits of the Social Security numbers were accessible is a good indication that Wells Fargo identified the risk involved with a person in the former employee's position accessing confidential information.&nbsp; Limiting Social Security number exposure also limits the extent and impact of the breach.</span><br style="font-style: italic;"><br>We started mailing consumer notices on May 13, 2008.<br><br>Wells Fargo Home Mortgage takes information security very seriously and wants to assure you that we are taking precautionary measures to reduce the potential risk associated with this incident.<br><br>Wells Fargo Home Mortgage, to ensure everything is done to protect you, will be providing you with a new PIN to access the line of credit on your reverse mortgage loan.<br><span style="font-style: italic;">[Evan] Not just "to protect you".&nbsp; Remember that Wells Fargo is in business to make money and I am pretty sure that the things they do are to that end.</span><br><br>As a precaution, Wells Fargo has partnered with a company called Intersections, Inc. to provide you with a free one-year subscription to IDENTITY GUARD CREDITPROTECTX3.<br><span style="font-style: italic;">[Evan] Cool!&nbsp; "CREDITPROTECTX3" sounds super strong and effective!</span><br><br>Wells Fargo Home Mortgage values and appreciates the trust you have placed in us by allowing us to serve you.<br><br>We sincerely apologize for this situation.<br><br>If we can be of further assistance, please do not hesitate to call us at (800) 472-3209 between the hours of 8:00 am and 8:00 pm eastern time, Monday through Friday.<br><br><span style="font-weight: bold;">Commentary:</span><br>I think that breaches like this are more common than some people would like to admit.&nbsp; Banks have the one thing that everyone wants! <br><br><b>Past Breaches:</b><br>Unknown<br></font><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/07/08/wellsfargo.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 08 Jul 2008 08:58:12 +0000</pubDate>
      <category domain="http://securityratty.com/tag/fargo">fargo</category>
      <category domain="http://securityratty.com/tag/fargo home mortgage">fargo home mortgage</category>
      <category domain="http://securityratty.com/tag/employee">employee</category>
      <category domain="http://securityratty.com/tag/fargo employee">fargo employee</category>
      <category domain="http://securityratty.com/tag/reverse mortgage loan">reverse mortgage loan</category>
      <category domain="http://securityratty.com/tag/reverse mortgage">reverse mortgage</category>
      <category domain="http://securityratty.com/tag/social security">social security</category>
      <category domain="http://securityratty.com/tag/evan cool">evan cool</category>
      <category domain="http://securityratty.com/tag/evan">evan</category>
      <source url="http://breachblog.com/2008/07/08/wellsfargo.aspx">Employee fraud at Wells Fargo Home Mortgage affects some customers</source>
    </item>
    <item>
      <title><![CDATA[Houghton Mifflin Harcourt server breach leads to notification]]></title>
      <link>http://securityratty.com/article/a32c42499f84224830293f2af83d152f</link>
      <guid>http://securityratty.com/article/a32c42499f84224830293f2af83d152f</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
7/1/08

Organization
Houghton Mifflin Harcourt (&quot;HMH

Contractor/Consultant/Branch
None

Victims
individuals affiliated with Harcourt Trade

Number...]]></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/hmh.jpg" width="200" align="right" height="44"><font size="2"><b>Date Reported: </b><br>7/1/08<br><br><b>Organization: </b><br><a href="http://www.hmco.com/indexf.html">Houghton Mifflin Harcourt ("HMH")</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>"individuals affiliated with Harcourt Trade"<br><br><span style="font-weight: bold;">Number Affected:</span><br>194<br><br><span style="font-weight: bold;">Types of Data:</span><br>Social Security numbers<br><br><span style="font-weight: bold;">Breach Description:</span><br>"Houghton Mifflin Harcourt (HMH), a publishing company based in Boston, will begin notifying individuals whose information may have been compromised by a worldwide Internet-based attack that affected one of its websites."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://doj.nh.gov/consumer/pdf/wilmerhale.pdf">New Hampshire State Attorney General breach notification</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The New Hampshire State Attorney General<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above:<br><br>Houghton Mifflin Harcourt (HMH), a publishing company based in Boston, will begin notifying individuals whose information may have been compromised by a worldwide Internet-based attack that affected one of its websites.<br><span style="font-style: italic;">[Evan] A "worldwide Internet-based attack" sounds impressive.&nbsp; In order for an attack to be successful, a vulnerability must be exploited.&nbsp; I wonder what the vulnerability was.</span><br><br>On April 25, 2008, HMH's Information Security group learned of a worldwide Internet-based attack that affected one of its non-e-commerce websites.<br><br>Within minutes, HMH took steps to secure the affected databases.<br><br>HMH has reported this matter to the U.S. Secret Service and state law enforcement, who are actively investigating the incident.<br><span style="font-style: italic;">[Evan] I question how "actively" the U.S. Secret Service is investigating this incident.&nbsp; The incident doesn't seem to be significant enough.&nbsp; Sad but usually true.&nbsp; The Secret Service has to prioritize just like everyone else.</span><br><br>As part of its internal investigation, which is still ongoing, HMH retained digital forensics experts to collect and analyze data from the relevant computer systems.<br><span style="font-style: italic;">[Evan] The attack was detected on April 25th (not necessarily originated on this date), and the notification went out to the New Hampshire State Attorney General on June 1st.&nbsp; This is a long forensic investigation!&nbsp; I also noticed that this statement mentions "computer systems".&nbsp; Does this mean that more than one server was compromised?</span><br><br>They have determined that social security numbers of approximately 194 individuals affiliated with Harcourt Trade, 2 of whom are New Hampshire residents, were in a company database on the affected computer server, and may have been compromised as a result.<br><span style="font-style: italic;">[Evan] I don't like the "may have been" portion of this statement.&nbsp; My definition of compromise probably differs though.</span><br><br>HMH has no evidence to date to suggest that the data has been misused.<br><br>Although we do not know whether any of your information has been misused, we are committed to doing what we can to make sure support is available to you<br><br>Since learning of the incident, HHM [sic] has:<br></font><ol><li><font size="2">Reported this matter to the U.S. Secret Service and state law enforcement;</font></li><li>Cooperated with law enforcement, which is actively investigating the incident;</li><li>Conducted a thorough investigation of the incident, including an assessment of whether or not the theft created any prospective data security risk;</li><li>Identified the sensitive personal information about individuals stored on the affected server; and</li><li>Made arrangements to notify affected individuals about the incident in accordance with state laws, offer premium credit monitoring, ID theft insurance, and ID theft resolution services, and provide additional information about prevention and detection of ID theft including information about credit alerts and credit freezes.<br></li></ol><font size="2"><br>HMH is continuing to work with information security professionals to review current policies and procedures to identify steps that can be taken to better protect against incidents of this kind.<br><br>We apologize and deeply regret that this happened.<br><br>I have asked our editors to reach out directly to everyone affected by this matter and I hope they will be or already have been able to answer your questions.<br><span style="font-style: italic;">[Evan] This is a nice touch.&nbsp; The letter to the affected persons was signed by Gary Gentel, President or Houghton Mifflin Harcourt Publishing Company, Trade and Reference Division.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>There aren't many publicly available details available other than those outlined in the breach notification, so we are left to speculate.&nbsp; Why was a server that contained a database of Social Security numbers available to this "worldwide Internet-based attack"? <br><br><b>Past Breaches:</b><br>Unknown<br></font><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/07/08/hmh.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 08 Jul 2008 08:22:09 +0000</pubDate>
      <category domain="http://securityratty.com/tag/houghton mifflin harcourt">houghton mifflin harcourt</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/information security professionals">information security professionals</category>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/server">server</category>
      <category domain="http://securityratty.com/tag/notification">notification</category>
      <category domain="http://securityratty.com/tag/hmh">hmh</category>
      <category domain="http://securityratty.com/tag/company based">company based</category>
      <source url="http://breachblog.com/2008/07/08/hmh.aspx">Houghton Mifflin Harcourt server breach leads to notification</source>
    </item>
    <item>
      <title><![CDATA[Laptop containing personal information is stolen from U.S. Foodservice]]></title>
      <link>http://securityratty.com/article/75e76f13934090aa771da66fbd1be73c</link>
      <guid>http://securityratty.com/article/75e76f13934090aa771da66fbd1be73c</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/13/08

Organization
U.S. Foodservice, Inc

Contractor/Consultant/Branch
None

Victims
Present and former employees, &quot;and in a few instances, their...]]></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/usfoodservice.jpg" width="146" align="right" height="71"><font size="2"><b>Date Reported: </b><br>6/13/08<br><br><b>Organization: </b><br><a href="http://www.usfoodservice.com/usf/html/index1.html">U.S. Foodservice, 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>Present and former employees, "and in a few instances, their dependents and applicants for jobs at USF"<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>"names, social security numbers, home addresses, and/or dates of birth"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"We were informed recently of the theft of a U.S. Foodservice, Inc. ("USF") laptop computer, which contained sensitive personnel information."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://doj.nh.gov/consumer/pdf/us_foodservice.pdf">New Hampshire State Attorney General breach notification</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The New Hampshire State Attorney General<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above:<br><br>We were informed recently of the theft of a U.S. Foodservice, Inc. ("USF") laptop computer, which contained sensitive personnel information.<br><span style="font-style: italic;">[Evan] We now add U.S. Foodservice to the ever-growing list of organizations that refuse to encrypt laptops, yet allow confidential information to be stored on them.</span><br><br>Local authorities were immediately notified and we conducted an internal investigation.<br><br>the laptop contained certain old data files<br><span style="font-style: italic;">[Evan] I wonder how old these data files were.&nbsp; I also wonder if these files were supposed to have been removed and/or destroyed, but were missed.</span><br><br>In the course of our investigation, we determined that the laptop computer contained the names, social security numbers, home addresses, and/or dates of birth of some present and former USF employees, and in a few instances, their dependents and applicants for jobs at USF.<br><br>We are sending a notification letter to individuals impacted by this incident.<br><br>We expect to begin mailing the notification letters on June 13, 2008.<br><br>we have no indication that any of the information is being misused<br><span style="font-style: italic;">[Evan] A breach notification is almost not a real breach notification without this mention.</span><br><br>Please note that several years ago, the Company stopped using social security numbers to identify employees for internal reporting or other purposes.<br><span style="font-style: italic;">[Evan] A good move by the Company.&nbsp; USF is still required to collect Social Security numbers however.</span><br><br>Pursuant to USF policies, the laptop was protected by a unique user ID and password, but the individual files containing personal information were not encrypted or password protected.<br><span style="font-style: italic;">[Evan] I am interested in reading the USF policies.&nbsp; Do the policies only require a user ID and password to protect (or access) confidential information?&nbsp; Probably not sufficient.</span><br><br>U.S. Foodservice takes the security of your personal information seriously and apologizes for any inconvenience or worry this incident may cause you.<br><br>As a precautionary measure, we are making several services available at the Company's expense, free of charge to you, to assist you in protecting your identity.<br><span style="font-style: italic;">[Evan] A true "precautionary measure" might have been restricting confidential information storage on laptops (and other mobile media) or encryption.</span><br><br>Although at this point we have no indication that your information has been compromised<br><span style="font-style: italic;">[Evan] My definition of "compromised" obviously differs.&nbsp; In my opinion, if the confidentiality, integrity or availability of information cannot be reasonable assured, then the information IS compromised.&nbsp; If you believe that password-protection provides reasonable assurance, then you and I disagree.</span><br><br>Call the Toll Free Help Line at 1-866-584-9681 to get answer [sic] to your questions.<br></font><ul><li><font size="2">Staffed by a team of professionals</font></li><li>Monday through Friday from 6:00 a.m. to 6:00 p.m. (Pacific Daylight Time)</li><li>Saturday and Sunday from 8:00 a.m. to 5:00 p.m. (Pacific Daylight Time)<br></li></ul><font size="2"><br>Please know that while we have information security policies in place, we are reviewing those practices and procedures to see what changes need to be made.<br><span style="font-style: italic;">[Evan] Its good the USF has information security policies in place, but it doesn't mean that they are effective or that they are well enforced.&nbsp; A poorly enforced policy isn't worth the paper its written on.</span><br style="font-style: italic;"><br><span style="font-weight: bold;">Commentary:</span><br>U.S. Foodservice is also offering one year of free credit monitoring and identity theft insurance.&nbsp; This would be fine minus the fact that a Social Security number has an effective lifespan that far exceeds one year.<br><br>If only there were other controls available to protect information stored on a laptop.&nbsp; Wait, we do!<br>&nbsp;<br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown<br></font><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/07/05/usfoodservice.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Mon, 07 Jul 2008 19:35:13 +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/confidential information">confidential information</category>
      <category domain="http://securityratty.com/tag/protect information">protect information</category>
      <category domain="http://securityratty.com/tag/information security policies">information security policies</category>
      <category domain="http://securityratty.com/tag/usf">usf</category>
      <category domain="http://securityratty.com/tag/usf policies">usf policies</category>
      <category domain="http://securityratty.com/tag/policies">policies</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <source url="http://breachblog.com/2008/07/07/usfoodservice.aspx">Laptop containing personal information is stolen from U.S. Foodservice</source>
    </item>
    <item>
      <title><![CDATA[Social Security Administration lists live people in the Death Master File]]></title>
      <link>http://securityratty.com/article/83b43862a5d586f2e8d29257c1e832ef</link>
      <guid>http://securityratty.com/article/83b43862a5d586f2e8d29257c1e832ef</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/26/08

Organization
U.S. Government

Contractor/Consultant/Branch
Social Security Administration

Victims
United States citizens

Number Affected
more...]]></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/ssa.jpg" width="76" align="right" height="76"><font size="2"><b>Date Reported: </b><br>6/26/08<br><br><b>Organization: </b><br><a href="http://www.usa.gov/">U.S. Government</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.ssa.gov/">Social Security Administration</a> <br><br><span style="font-weight: bold;">Victims:</span><br>United States citizens<br><br><span style="font-weight: bold;">Number Affected:</span><br>"more than 20,000"<br><br><span style="font-weight: bold;">Types of Data:</span><br>Name, date of birth and Social Security number<br><br><span style="font-weight: bold;">Breach Description:</span><br>"The Social Security Administration inadvertently compromised the personal information of more than 20,000 people by listing them in the Death Master File (DMF) while they were still alive"<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.fcw.com/online/news/152975-1.html">FederalComputerWeek</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Michael Hardy, FederalComputerWeek<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above:<br><br>The Social Security Administration inadvertently compromised the personal information of more than 20,000 people by listing them in the Death Master File (DMF) while they were still alive, the agency's inspector general has determined.<br><span style="font-style: italic;">[Evan] "The DMF is a publicly available database maintained by SSA that contains detailed information on more than 82 million deceased numberholders. Each year, SSA receives death reports for more than 2.5 million individuals and adds the information to the DMF. " (Source: SSA Inspector General </span><a style="font-style: italic;" href="http://www.ssa.gov/oig/ADOBEPDF/audittxt/A-06-07-27156.htm">AUDIT REPORT A-06-07-27156</a><span style="font-style: italic;">).&nbsp; This breach was not the result of single occurrence, but instead is a result of errors in current process.</span><br><br>The IG's analysis dates to January 2004.<br><br>Since then, SSA has made the live people's Social Security number, full name, date of birth, and state and ZIP code of last known residence available to users of the database<br><span style="font-style: italic;">[Evan] The organization that distributes and manages the "system" cannot secure the information.&nbsp; Is this is just another case that proves that the "system" is busted?</span><br><br>After learning that those people were not deceased, SSA deleted the information<br><br>The IG's investigators found some instances where the personal information was available for free viewing on the Internet<br><br>SSA provides the data to the Commerce Department's National Technical Information Service (NTIS), which in turn sells it to customers.<br><span style="font-style: italic;">[Evan] Selling a dead man's (or woman's) information doesn't seem right to me.&nbsp; Do you see anything wrong with it?</span><br><br>Customers include the government, investigative businesses, financial and credit reporting firms, and geneaology researchers.<br><br>Some, including prominent geneaology Web sites, post some or all of the information online for their users. <br><br>To prevent a repeat of the situation, the IG's&nbsp; recommendations include: <br></font><ul><li><font size="2">Implementing a risk-based approach for distribution of DMF information. One suggestion: Have NTIS delay release of updates to public customers for one year to give SSA ample time to correct erroneous entires.</font></li><li>Limiting information included in the data sold to public customers.</li><li>Starting required breach notification evaluation procedures.</li><li>Providing appropriate notification to living individuals whose information was released in error.<br></li></ul><font size="2"><br>In response to the IG's report, SSA said limiting the personal information might be difficult, but it would consider doing so.<br><span style="font-style: italic;">[Evan] There are many practices to secure information that "might be difficult", but this is not a good excuse.&nbsp; Life "might be difficult", so what?</span><br><br>The agency agreed with the other recommendations. <br><br><span style="font-weight: bold;">Commentary:</span><br>The use of Social Security numbers as personal identifiers as well as authenticators seems to be a very significant contributing factor to the identity theft mess we face today.&nbsp; So how did Social Security numbers become so important in the first place?&nbsp; Read the "<a href="http://www.ssa.gov/history/ssn/ssnchron.html">Social Security Number Chronology</a>" on the Social Security Administration web site for some clues.<br><br>To my knowledge, the victims in this breach have not been (nor will they be) notified. <br><br><span style="font-weight: bold;">Past Breaches:</span><br><span style="font-weight: bold;">U.S. Government:</span><br>March, 2008 - <a href="http://breachblog.com/2008/03/22/usdos.aspx">A breach that hits home with 2008 presidential candidates</a>&nbsp; <br>March, 2008 - <a href="http://breachblog.com/2008/03/24/nhlbi.aspx%20">Laptop stolen from NHLBI contained personal health information</a> <br></font><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/07/07/ssa.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Mon, 07 Jul 2008 04:44:12 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/secure information">secure information</category>
      <category domain="http://securityratty.com/tag/social security">social security</category>
      <category domain="http://securityratty.com/tag/social security administration">social security administration</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/information online">information online</category>
      <category domain="http://securityratty.com/tag/dmf information">dmf information</category>
      <category domain="http://securityratty.com/tag/death master file">death master file</category>
      <category domain="http://securityratty.com/tag/ssa">ssa</category>
      <source url="http://breachblog.com/2008/07/07/ssa.aspx">Social Security Administration lists live people in the Death Master File</source>
    </item>
    <item>
      <title><![CDATA[Daily Mail publisher admits to stolen laptop]]></title>
      <link>http://securityratty.com/article/9af68c57ed3f10d814be79e5d395b72b</link>
      <guid>http://securityratty.com/article/9af68c57ed3f10d814be79e5d395b72b</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
7/4/08

Organization
Daily Mail and General Trust plc

Contractor/Consultant/Branch
Northcliffe Media
Associated Newspapers Ltd

Victims
Staff, suppliers...]]></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/dailymail.jpg" width="203" align="right" height="43"><font size="2"><b>Date Reported: </b><br>7/4/08<br><br><b>Organization: </b><br><a href="http://www.dmgt.co.uk/">Daily Mail and General Trust plc</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.thisisnorthcliffe.co.uk/">Northcliffe Media</a> <br><a href="http://www.associatednewspapers.com/">Associated Newspapers Ltd</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Staff, suppliers and contributors<br><br><span style="font-weight: bold;">Number Affected:</span><br>"thousands"<br><br><span style="font-weight: bold;">Types of Data:</span><br>"name, address, bank account number and bank sort code"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"Daily Mail publisher Associated Newspapers has admitted that a laptop containing financial and personal details of thousands of staff, suppliers and contributors has been stolen."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.computerworlduk.com/management/security/data-control/news/index.cfm?newsid=9904">ComputerWorldUK</a> <br><a href="http://www.guardian.co.uk/media/2008/jul/04/dailymail.dmgt1?gusrc=rss&amp;feed=media">Guardian News (UK)</a> <br><a href="http://www.guardian.co.uk/media/2008/jul/04/dailymail.dmgt?gusrc=rss&amp;feed=media">Guardian News (UK) additional info</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Guardian Newspaper<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>Daily Mail publisher Associated Newspapers has admitted that a laptop containing financial and personal details of thousands of staff, suppliers and contributors has been stolen.<br><br>A Daily Mail &amp; General Trust spokeswoman said: "DMGT confirms that a laptop company computer containing certain confidential information was stolen last week.<br><br>After months of criticising "criminally careless" government departments for losing confidential records, the company has been forced to send out an embarrassing letter telling journalists they may now be at risk of identity theft<br><span style="font-style: italic;">[Evan] This is the same Daily Mail managed by Associated Newspapers that according to The Guardian "has been at the forefront of coverage of the recent bank and government department missing data scandals".&nbsp; It would be very difficult for Associated Newspapers to claim that they didn't know any better than to store confidential information on a poorly protected laptop.</span><br><br>Details such as names, addresses, bank account numbers and sort codes were on the laptop<br><br>the laptop was "password protected" but tell recipients to contact their banks and also "consult the government website ... for advice on avoiding or dealing with identity theft"<br><span style="font-style: italic;">[Evan] The mention of password protection is nothing more than an effort to minimize the effect of the breach.&nbsp; It does very little (if anything) to protect the personal information.</span><br><br>In a letter to those who details were affected, Simon Dyson, finance director at Daily Mail publisher Associated Newspapers, and Martyn Hindley, his counterpart at sister company Northcliffe, said it was likely that the details had been erased by the thief.<br><span style="font-style: italic;">[Evan] How is the conclusion drawn?&nbsp; I don't see how there could be enough information to determine what the thief was likely to do.</span><br><br>From the letter to affected persons from the Associated Newspapers group finance director, Simon Dyson, and his Northcliffe counterpart, Martyn Hindley:<br><br>"Unfortunately one of the company's laptops has been stolen."<br><br>"The contents included personal data, some of which related to you."<br><br>"The laptop was password-protected. "<br><span style="font-style: italic;">[Evan] So what?&nbsp; This won't adequately protect the information on the laptop, so why mention it?</span><br><br>"We are writing to you as quickly as possible to alert you to the fact that the theft has happened and to inform you of the data types lost, so that you can take appropriate action."<br><span style="font-style: italic;">[Evan] I guess we should give some credit for the quick notification, if nothing else.</span><br><br>"In your case, your name, address, bank account number and bank sort code were the sensitive information lost."<br><br>"The likelihood is that this theft was carried out in an opportunistic manner by a thief who will not realise that there is any personal data on the laptop and who may just erase what is on the hard disk in order to disguise the fact that the laptop is stolen."<br><span style="font-style: italic;">[Evan] This is nothing more than speculation.&nbsp; I can't imagine that there are any specific facts for which this conclusion is based on.</span><br><br>"We have, of course, notified the police of the theft of the laptop and are talking to the Office of the Information Commissioner about what has happened."<br><br>"On behalf of the company, I would like to offer my sincere apologies for any annoyance and inconvenience to you that this breach of security may cause."<br><br>"I can assure you that we take security of personal data very seriously and have, since this incident, which was inadvertently caused by a technical issue, already further strengthened procedures."<br><span style="font-style: italic;">[Evan] This breach was caused by a "technical issue"?&nbsp; Like what?&nbsp; I presume that the technical aspects surrounding this breach were working exactly as they were designed to in the manner of which that they were implemented.&nbsp; Without further elaboration, "strengthened procedures" is subjective and means little.&nbsp; Organizations should offer details, instead of general statements in order to bolster some sense of confidence.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>This breach must be embarrassing for Associated Newspapers.&nbsp; A breach like this should be embarrassing for any organizations.&nbsp; Unencrypted lost of stolen laptops storing personal (or other confidential) information is a pretty well-known risk nowadays.&nbsp; An unacceptable risk for most. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown<br></font><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/07/05/dailymail.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Sat, 05 Jul 2008 08:55:49 +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/daily mail publisher">daily mail publisher</category>
      <category domain="http://securityratty.com/tag/daily mail">daily mail</category>
      <category domain="http://securityratty.com/tag/personal">personal</category>
      <category domain="http://securityratty.com/tag/store confidential information">store confidential information</category>
      <category domain="http://securityratty.com/tag/laptop">laptop</category>
      <category domain="http://securityratty.com/tag/personal data">personal data</category>
      <category domain="http://securityratty.com/tag/laptop company computer">laptop company computer</category>
      <source url="http://breachblog.com/2008/07/05/dailymail.aspx">Daily Mail publisher admits to stolen laptop</source>
    </item>
    <item>
      <title><![CDATA[Service Canada employee loses flash drive]]></title>
      <link>http://securityratty.com/article/0b1145db0ad92794aa6d34d54d9a00ca</link>
      <guid>http://securityratty.com/article/0b1145db0ad92794aa6d34d54d9a00ca</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/27/08

Organization
Government of Canada

Contractor/Consultant/Branch
Service Canada

Victims
Canadian Residents

Number Affected
More than 1,500
...]]></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/servicecanada.jpg" width="103" align="right" height="54"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/27/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://canada.gc.ca/home.html">Government of Canada</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.servicecanada.gc.ca/">Service Canada</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Canadian Residents<br><br><span style="font-weight: bold;">Number Affected:</span><br>More than 1,500<br><br><span style="font-weight: bold;">Types of Data:</span><br>Name and <a href="http://www.servicecanada.gc.ca/en/sc/sin/">Social Insurance Number</a><br><br><span style="font-weight: bold;">Breach Description:</span><br>"Service Canada recently sent a letter to 1500 individuals that where affected by a recent incident. It seems that a USB key, containing the names and social security number of 1500 canadians was lost."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.nowpublic.com/tech-biz/service-canada-loses-canadians-data">NowPublic</a> <br><a href="http://www.radio-canada.ca/nouvelles/National/2008/06/23/003-service-canada-donn%C3%A9es.shtml">Radio-Canada (French)</a> <br><a href="http://translate.google.com/translate?u=http%3A%2F%2Fwww.radio-canada.ca%2Fnouvelles%2FNational%2F2008%2F06%2F23%2F003-service-canada-donn%C3%A9es.shtml&amp;hl=en&amp;ie=UTF8&amp;sl=fr&amp;tl=en">Radio-Canada (Google English translation)</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Radio-Canada, via an email from an informed Breach Blog reader<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>An Employee Service Canada has lost in March, a USB stick containing personal information on more than 1,500 Canadians.<br><span style="font-style: italic;">[Evan] This statement was translated from french.&nbsp; An employee of Service Canada lost a flash drive with confidential personal information belonging to more than 1,500 Canadians stored on it.&nbsp; Service Canada is responsible for the security of some very sensitive personal information belonging to thousands (maybe millions) of Canadians.&nbsp; As such, the people that are permitted to access (assuming that role-based access control is enforced at Service Canada) confidential information must be properly trained and made constantly aware of the risks involved with creating, accessing, storing, destroying, and transferring this information.&nbsp; Was this employee aware of the risk of using a flash drive to store this information?&nbsp; If so, then there should be consequences for his/her actions.&nbsp; If not, then Service Canada really needs some help.&nbsp; Training and awareness is only a part of an effective information security program, but it is a very important one.&nbsp; Are flash drives permitted for use at Service Canada?&nbsp; They probably shouldn't be.</span><br><br>The agency sent a letter to the persons concerned to advise them of the situation and asking them to check their bank accounts, their credit file and expenditure on their card.<br><br>Among the information contained in the key, were found including the names of persons and their number of social insurance.<br><br>One of the victims wanted to know why Canada Service data contained on the key, a minidisk drive, were not protected.&nbsp; "They said they did not want to invest to secure customer data," said Queen Fraser.<br><span style="font-style: italic;">[Evan] Obviously, this is an unacceptable response and probably one that wasn't authorized.</span><br><br>There are a few problems with this statement of course... First and foremost, Service Canada employees need training in Security incident management and, in particular, in the important aspect of security incident communications.<br><span style="font-style: italic;">[Evan] Among many other things, I'm sure.</span><br><br>Second, this means that they are either not aware of Governement of Canada <a href="http://www.tbs-sct.gc.ca/pubs_pol/gospubs/tbm_12a/gsp-psg_e.asp">security policies</a> or <a href="http://www.tbs-sct.gc.ca/pubs_pol/gospubs/tbm_128/chap1_1-1_e.asp">Privacy policies</a> as published by Treasury Bord [sic] Secretariat, or they do not care.<br><br>The government agency has opened an investigation and added that no identity theft had been reported.<br><br>It did not specify whether measures have been taken to avoid another incident.<br><span style="font-style: italic;">[Evan] We can only imagine what the current state of information security is at Service Canada.&nbsp; It may be worse than some of us think, and it may be better than others of us think.&nbsp; In my opinion, Service Canada owes a thorough explanation to the victims of this breach and owes detailed assurances to Canadian citizens.</span><br style="font-style: italic;"><br>As anyone with some knowledge of IT security practices can tell you, USB keys should not be used to carry delicate, protected or private information.<br><span style="font-style: italic;">[Evan] In general, I agree.</span><br><br>If it must be done then, at a minimum, a threat and risk assessment must be done and proper encryption of the data must be used.<br><span style="font-style: italic;">[Evan] I absolutely agree.&nbsp; Risk management is critical.</span><br><br>However, mosts organisations that deal with data that is sensitive, protected under privacy laws, such as PIPEDA, commercial trade secrets or of national interest (such as National Defence secrets) AND are serious about IT security would disable floppy disk drives and USB ports on most computers. <br><span style="font-style: italic;">[Evan] Most "organisations" should, but unfortunately most do not.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>I would like to think that this is an isolated incident at Service Canada, but I don't think that it actually is.&nbsp; I would like to see the <a href="http://www.privcom.gc.ca/index_e.asp">Privacy Commissioner of Canada</a> investigate and audit the security program and practices at Service Canada.&nbsp; We'll see if this happens.&nbsp; I don't expect things to change until the people responsible are <span style="font-style: italic;">held</span> responsible.<br><br>How does the Canadian government expect the private sector to provide adequate security measures for the protection of personal information if it does not follow best practices and the law itself? <br><br><span style="font-weight: bold;">Past Breaches:</span><br><span style="font-weight: bold;">Government of Canada:</span><br>November, 2007 - <a href="http://breachblog.com/2007/11/26/servicecanada.aspx">Service Canada stolen laptop affects more than 1,600</a>&nbsp; <br>December, 2007 - <a href="http://breachblog.com/2007/12/05/passport.aspx">Passport Canada web site suffers serious breach</a>&nbsp; <br>June, 2008 - <a href="http://breachblog.com/2008/06/08/ccga.aspx">Canadian farmer personal information on stolen CCGA laptop</a>&nbsp; <br><span style="font-weight: bold;">Service Canada:</span><br>November, 2007 - <a href="http://breachblog.com/2007/11/26/servicecanada.aspx">Service Canada stolen laptop affects more than 1,600</a> </font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/28/servicecanada.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Sat, 28 Jun 2008 19:18:19 +0000</pubDate>
      <category domain="http://securityratty.com/tag/service canada">service canada</category>
      <category domain="http://securityratty.com/tag/employee">employee</category>
      <category domain="http://securityratty.com/tag/service canada recently">service canada recently</category>
      <category domain="http://securityratty.com/tag/canada">canada</category>
      <category domain="http://securityratty.com/tag/service canada employees">service canada employees</category>
      <category domain="http://securityratty.com/tag/employee aware">employee aware</category>
      <category domain="http://securityratty.com/tag/practices">practices</category>
      <category domain="http://securityratty.com/tag/security practices">security practices</category>
      <category domain="http://securityratty.com/tag/employee service canada">employee service canada</category>
      <source url="http://breachblog.com/2008/06/28/servicecanada.aspx">Service Canada employee loses flash drive</source>
    </item>
    <item>
      <title><![CDATA[Australian medical information found in abandoned amusement park]]></title>
      <link>http://securityratty.com/article/5603502d0088acde782f2669d07e2fb6</link>
      <guid>http://securityratty.com/article/5603502d0088acde782f2669d07e2fb6</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/27/08

Organization
New South Wales Government (AU

Contractor/Consultant/Branch
Sydney West Area Health Service
Unnamed &quot;bankrupt contractor

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/swahs.jpg" width="165" align="right" height="58"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/27/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://nsw.gov.au/">New South Wales Government (AU)</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.wsahs.nsw.gov.au/">Sydney West Area Health Service</a> <br>Unnamed "bankrupt contractor"<br><br><span style="font-weight: bold;">Victims:</span><br>Patients<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>"confidential medical records"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"The Sydney West Area Health Service has been embarrassed by the discovery of medical records in an abandoned amusement park."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.abc.net.au/news/stories/2008/06/27/2288377.htm">ABC News</a> <br><a href="http://www.livenews.com.au/Articles/2008/06/27/Shipping_container_full_of_medical_waste_dumped_at_derelict_fun_park">Macquarie National News</a> <br><a href="%20http://livenews.com.au/Articles/2008/06/28/Dumped_medical_container_blamed_on_bankrupt_contractor">Macquarie National News (2)</a><br><br><span style="font-weight: bold;">Report Credit:</span><br>ABC NEws<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>The Sydney West Area Health Service has been embarrassed by the discovery of medical records in an abandoned amusement park.<br><span style="font-style: italic;">[Evan] This is a first.&nbsp; An abandoned amusement park?&nbsp; I would be embarrassed too!</span><br><br>Pathology results and slides were found when a container dumped in the former Magic Kingdom park at Lansvale was set alight this week.<br><br>The container was discovered after it caught on fire yesterday, attracting the attention of the local fire department.<br><br>A bankrupt contractor is being blamed for dumping confidential medical records and contaminated waste in the grounds of an abandoned fun park.<br><span style="font-style: italic;">[Evan] Confidential medical records AND contaminated waste?&nbsp; Ugh.</span><br><br>Police said it was likely the container had been there for a decade.<br><span style="font-style: italic;">[Evan] A decade?&nbsp; This story keeps getting more bizarre.</span><br><br>The Health Department is reviewing waste disposal procedures following the discovery at Lansvale in Sydney's south west.<br><span style="font-style: italic;">[Evan] I presume that the waste disposal procedures have probably changed over the past ten years.&nbsp; The Health Department should be reviewing procedures on a regular basis anyway.</span><br style="font-style: italic;"><br>The health service's chief executive, Professor Steven Boyages, says it is a serious breach and the health service is reviewing its waste disposal procedures.<br><br>"There are clear policy and procedures in place to manage records and disposal of records and clear policies in place to manage and dispose of any clinical waste," he said.<br><br>"It appears at first glance that the policy and procedures weren't followed by the contractors who were engaged to do this."<br><br>“It is a huge concern, I’ve called for an immediate review to ensure our existing contractors are following standard policy and procedures so this doesn't happen again," he said <br><br>Shadow health minister Jillian Skinner said the state government also has some explaining to do.<br><br>"Why if it was know this company had gone bankrupt and wasn't carrying out its duties they didn't check to make sure this material was disposed of properly?" Ms Skinner said. <br><br><span style="font-weight: bold;">Commentary:</span><br>The landscape of information security and personal information issues has changed markedly over the past ten years.&nbsp; SWAHS should still be held accountable, but how much can you comment on something that happened ten years ago and probably does not reflect upon current practice.<br><br>This is one of the most bizarre breaches I have read about in some time. <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/28/swahs.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Sat, 28 Jun 2008 09:10:55 +0000</pubDate>
      <category domain="http://securityratty.com/tag/confidential medical records">confidential medical records</category>
      <category domain="http://securityratty.com/tag/medical records">medical records</category>
      <category domain="http://securityratty.com/tag/clinical waste">clinical waste</category>
      <category domain="http://securityratty.com/tag/waste">waste</category>
      <category domain="http://securityratty.com/tag/waste disposal procedures">waste disposal procedures</category>
      <category domain="http://securityratty.com/tag/disposal">disposal</category>
      <category domain="http://securityratty.com/tag/records">records</category>
      <category domain="http://securityratty.com/tag/procedures">procedures</category>
      <category domain="http://securityratty.com/tag/amusement park">amusement park</category>
      <source url="http://breachblog.com/2008/06/28/swahs.aspx">Australian medical information found in abandoned amusement park</source>
    </item>
    <item>
      <title><![CDATA[Montgomery Ward breached, no notification obligation?]]></title>
      <link>http://securityratty.com/article/d0a7010fb8fd83b7750424b96154c42b</link>
      <guid>http://securityratty.com/article/d0a7010fb8fd83b7750424b96154c42b</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/27/08

Organization
Direct Marketing Services Inc

Contractor/Consultant/Branch
Montgomery Ward
HomeVisions.com
SearsHomeCenter.com
SearsShowPlace.com...]]></description>
      <content:encoded><![CDATA[Technorati Tag: <a href="http://technorati.com/tag/security+breach" rel="tag">Security Breach</a><br><br>
<img src="http://breachblog.com/images/95781-88451/wards.jpg" width="200" align="right" height="50"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/27/08<br><br><span style="font-weight: bold;">Organization: </span><br>Direct Marketing Services Inc.<br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.wards.com/wards/default.asp">Montgomery Ward</a> <br><a href="http://www.homevisions.com/hvprod/Default.asp">HomeVisions.com</a> <br><a href="http://www.searshomecenter.com/homecenter/default.asp">SearsHomeCenter.com</a> <br><a href="http://www.searsshowplace.com/showplace/default.asp">SearsShowPlace.com</a> <br><a href="http://www.searsroomforkids.com/roomforkids/default.asp?partner=0">SearsRoomForKids.com</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Customers<br><br><span style="font-weight: bold;">Number Affected:</span><br>"at least 51,000 records"<br><br><span style="font-weight: bold;">Types of Data:</span><br>Names, addresses, phone numbers, card numbers, "security codes", and expiration dates<br><br><span style="font-weight: bold;">Breach Description:</span><br>"NEW YORK (AP) -- The parent company of Montgomery Ward is admitting that it was hit with a credit card hack, but it didn't inform the customers affected."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://ap.google.com/article/ALeqM5hMgFbRpfc74PW0CvbF3kFbWFkHsAD91IJCHG2">The Associated Press</a> <br><a href="http://www.wztv.com/template/inews_wire/wires.national/2c50aedd-www.fox17.com.shtml">The Associated Press via WZTV Channel 17 News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>The Associated Press<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>At least 51,000 records were exposed in the breach at the parent company of Montgomery Ward.<br><br>The venerable Wards chain that began in 1872 went out of business in 2001, but in 2004 a catalog company, Direct Marketing Services Inc., bought the brand name out of bankruptcy.<br><br>Direct Marketing Services' CEO, David Milgrom, said the financial company Citigroup detected the computer invasion in December.<br><br>By going through HomeVisions.com, another Direct Marketing Services site, hackers had plundered the database that holds account information for all the company's retail properties.<br><span style="font-style: italic;">[Evan] The AP story names five of the six Direct Marketing Services retail properties (See Above).&nbsp; I don't know what the sixth is.</span><br style="font-style: italic;"><br>It now runs a Wards.com Web site along with six other sites, including three with Sears brands it has acquired: SearsHomeCenter.com, SearsShowplace.com and SearsRoomforKids.com<br><br>Milgrom said Direct Marketing Services immediately informed its payment processor and Visa and MasterCard.<br><br>Direct Marketing Services closely followed a set of guidelines, issued by Visa, on how to respond to a security breach.<br><span style="font-style: italic;">[Evan] This is sad.&nbsp; The Visa documentation regarding breach response is way too narrowly focused to be used as an organizational incident response.&nbsp; Every organization that creates, collects, uses, stores, and/or transfers confidential information should have an incident response policy and accompanying procedures.&nbsp; Take a look at the Visa "</span><a style="font-style: italic;" href="http://usa.visa.com/download/merchants/cisp_what_to_do_if_compromised.pdf?it=r%7C/merchants/risk_management/cisp_if_compromised.html%7CWhat%20to%20Do%20If%20Compromised">What To Do if Compromised</a><span style="font-style: italic;">" procedures, and judge for yourself.</span><br style="font-style: italic;"><br>That included a report to the U.S. Secret Service.<br><br>He said he believed by the end of December that Direct Marketing Services had met its obligations.<br><span style="font-style: italic;">[Evan] Mr. Milgrom is the president of the company.&nbsp; He really thought that his company had met all of its obligations with respect to this breach?&nbsp; It never occurred to him that he should notify customers, even if he weren't required to by law?&nbsp; Not only was the lack of notification illegal, but I think it is also unethical.</span><br style="font-style: italic;"><br>However, those guidelines from Visa are largely technical, and they do not cover a key additional step: that notification laws in nearly every state generally require organizations that have been hacked to come clean to the affected consumers, not just to the financial industry.<br><br>Companies that fail to comply can be hit with fines or be sued by affected customers, depending on the state<br><br>After being asked about those laws by The Associated Press, Milgrom said Direct Marketing Services now plans to contact consumers.<br><br>This hack might have stayed quiet except for online chatter detected in June by Affinion Group Inc.'s CardCops, a group of investigators who track payment-card theft for financial institutions.<br><br>In Internet chat rooms frequented by card thieves, CardCops spotted hackers touting the sale of 200,000 payment cards belonging to one merchant.<br><br>CardCops then intercepted several hundred of the records, along with the online handles belonging to hackers whose real names remain unknown.<br><br>Along with the card numbers, their three-digit "security codes" and expiration dates, the thieves had the cardholders' names, addresses and phone numbers.<br><br>The data had been organized in the same way, indicating the numbers likely came from the same database.<br><br>CardCops' president, Dan Clements, also noticed that the vast majority of the cardholders were women, a clue that the records came from a merchant catering to a certain demographic.<br><br>When he began calling them, the first eight said they had bought things online or through mail order from Montgomery Ward. At that point, Clements realized, "there's a high probability the entire database of Montgomery Ward was breached."<br><span style="font-style: italic;">[Evan] This is some good investigative work.</span><br><br>It is not clear to Clements, though, whether the hackers were inflating their claim when they offered 200,000 records or whether Milgrom's number of 51,000 is accurate.<br><span style="font-style: italic;">[Evan] According to the article, the "hackers" were able to compromise the information from all six Direct Marketing Services, Inc. properties.&nbsp; 51,000 may be Montgomery Wards customer accounts, and the remainder could be from the other five properties (just speculating).</span><br style="font-style: italic;"><br>A spokeswoman for Discover Financial Services LLC, Mai Lee Ua, said her company had addressed the problem by sending new cards to its cardholders who appeared in the compromised records.<br><br>Ua said they weren't told which merchant had been breached<br><br>Visa declined to comment.<br><span style="font-style: italic;">[Evan] Visa always declines to comment.&nbsp; No sense in even seeking one.</span><br><br>MasterCard issued a statement Friday acknowledging it was aware of the breach at Direct Marketing Services, and had notified the banks that issue MasterCards, telling them to monitor the accounts for suspicious charges.<br><span style="font-style: italic;">[Evan] Three different card companies, three entirely different responses.&nbsp; Of the three, I think I like the Discover one the best.</span><br style="font-style: italic;"><br>Such silence was the norm in the industry for years. But in response to fears of identity theft, 44 states have passed laws that generally require organizations holding consumer data to tell people when their information has leaked<br><br>Clements and other security analysts say that despite those laws, many breaches still are kept quiet, judging by the data being hawked in online black markets.<br><br>Avivah Litan, an analyst at Gartner Inc., believes unreported data breaches might still outnumber the ones that do get publicized.<br><span style="font-style: italic;">[Evan] I absolutely agree.&nbsp; You would be naïve to think that victim notifications go out in all breaches.&nbsp; Too many corporate leaders would rather not notify and hope that nobody notices.</span><br style="font-style: italic;"><br>Litan says it especially is the case with online merchants. She believes it happens because of a lack of pressure from credit card companies, which are not responsible for fraudulent charges in "card not present" transactions over the Web and mail order.<br><br>Until fraud actually appears on the card, they'd rather avoid the cost of voiding compromised cards and giving consumers new ones, she said.<br><br>"What it reveals is the convoluted banking system," she said. "If this had taken place at a grocery store, we all would have heard about it."<br><br>In fact, because of the silence that still sometimes follows data breaches, even people who have never been informed one of their records has leaked should assume their information is floating online, Litan said.<br><br>"Probably every one of our cards is up there somewhere now," she said.<br><span style="font-style: italic;">[Evan] I agree with all of the statements made by Avivah Litan except this one.&nbsp; This is a stretch.</span><br><br><span style="font-weight: bold;">On the Net:</span><br>Links to the <a href="http://www.ncsl.org/programs/lis/cip/priv/breachlaws.htm">44 state notification laws</a> <br><br><span style="font-weight: bold;">Commentary:</span><br>Is this a case of a company that was caught trying to cover up a breach, or was this a company that didn't know any better?&nbsp; </font><font size="2">I lean towards the former.&nbsp; </font><font size="2">Either way, is ignorance of the law any kind of valid excuse?&nbsp; <br><br>Let's assume for a second that company really didn't know that they were required to notify victims.&nbsp; If this were true, then this leads me to believe that the company doesn't govern information security well (due care?), probably has no formal information security program, lacks incident response policy and procedures, and doesn't manage risk well.<br><br>I could only guess how the "hack" took place.&nbsp; What vulnerability was exploited?&nbsp; Even in this, the company appears to have not detected the attack.&nbsp; </font><font size="2">Direct Marketing Services, Inc. had to be told of it by Citibank.&nbsp; </font><font size="2">Does this mean that the company did not use intrusion detection/prevention?&nbsp; <br><br>I could go on and on, but in the end I don't have much confidence here. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/27/wards.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Fri, 27 Jun 2008 19:45:03 +0000</pubDate>
      <category domain="http://securityratty.com/tag/card companies">card companies</category>
      <category domain="http://securityratty.com/tag/companies">companies</category>
      <category domain="http://securityratty.com/tag/services">services</category>
      <category domain="http://securityratty.com/tag/services closely">services closely</category>
      <category domain="http://securityratty.com/tag/credit card companies">credit card companies</category>
      <category domain="http://securityratty.com/tag/services retail properties">services retail properties</category>
      <category domain="http://securityratty.com/tag/financial company citigroup">financial company citigroup</category>
      <category domain="http://securityratty.com/tag/company">company</category>
      <category domain="http://securityratty.com/tag/montgomery ward">montgomery ward</category>
      <source url="http://breachblog.com/2008/06/27/wards.aspx">Montgomery Ward breached, no notification obligation?</source>
    </item>
    <item>
      <title><![CDATA["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[Errant email exposed Department of Consumer Affairs personal information]]></title>
      <link>http://securityratty.com/article/ca6f5be22b8296dc3dbda7041339d863</link>
      <guid>http://securityratty.com/article/ca6f5be22b8296dc3dbda7041339d863</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
6/23/08

Organization
State of California

Contractor/Consultant/Branch
Department of Consumer Affairs

Victims
employees, contractors and board members...]]></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/caldca.jpg" width="169" align="right" height="65"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>6/23/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.ca.gov/">State of California</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.dca.ca.gov/">Department of Consumer Affairs</a><br><br><span style="font-weight: bold;">Victims:</span><br>"employees, contractors and board members"<br><br><span style="font-weight: bold;">Number Affected:</span><br>5,000<br><br><span style="font-weight: bold;">Types of Data:</span><br>Names, Social Security numbers, salaries and job titles<br><br><span style="font-weight: bold;">Breach Description:</span><br>"The state Department of Consumer Affairs (DCA) has sent letters to 5,000 employees, contractors and board members warning them of a security breach that has compromised their names and social security numbers. "<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.capitolweekly.net/article.php?_adctlid=v%7Cjq2q43wvsl855o%7Cx7o1tt8kp1c3g5&amp;issueId=x79xdv8us2oeyp&amp;xid=x7csom3a3og08k">Capitol Weekly</a> <br><a href="http://www.centralvalleybusinesstimes.com/stories/001/?ID=9111">Central Valley Business Times</a> <br><a href="http://www.pogowasright.org/article.php?story=20080624114400847">Props to PogoWasRight</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Malcolm Maclachlan, Capitol Weekly<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>The state Department of Consumer Affairs (DCA) has sent letters to 5,000 employees, contractors and board members warning them of a security breach that has compromised their names and social security numbers.<br><br>About 2,800 of the people on the list are current, full-time employees of the DCA.<br><br>The document also included some former employees and numerous contractors, such as people who proctor state job examinations.<br><br>The rest of the names were employees and board members of the 56 professional boards and bureaus administered by the DCA, such as the Bureau of Automotive Repair and the Medical Board.<br><br>The breach occurred on June 5 or 6 when a Microsoft Word document was improperly transmitted electronically outside of the department, said DCA spokesman Russ Heimerich.<br><br>The document also contained the salaries and titles of everyone on the list, but Heimerich noted that this was public information.<br><br>"The thing that is troubling to us is that information was coupled with their social security numbers," Heimerich said.<br><span style="font-style: italic;">[Evan] Troubling to you?&nbsp; It's probably hard for the victims to have much sympathy.</span><br><br>The main danger with giving away a social security number is that it can be used to set up new credit cards, loans or purchases in someone's name.<br><br>However, a thief would generally need other information that was not included and could be harder to get, such as addresses, phone numbers and driver's license numbers.<br><span style="font-style: italic;">[Evan] Addresses and phone numbers are usually pretty easy to obtain and I would think are much easier to get than Social Security numbers.&nbsp; Unless of course, somebody emails them to you.</span><br><br>The DCA is the main state agency charged with protecting consumers in California.<br><span style="font-style: italic;">[Evan] Ironic.</span><br><br>From 2003 to 2007, it also housed the office charged with educating consumers and businesses about identity theft and fraud.<br><span style="font-style: italic;">[Evan] More Ironic</span><br><br>One agency whose employees were not on the list is the California Office of Privacy Protection (OPP).<br><br>Heimerich said the incident is still being investigated, and that he could not disclose who had received the document.<br><br>He said that so far there is no evidence that any information has been used. It was not even clear the recipient had opened the document.<br><br>"We know that it left the building and that it wound up somewhere it shouldn't have wound up," Heimerich. "We're looking into how that happened."<br><br>“We kind of know where it was sent,” Mr. Heimerich says<br><span style="font-style: italic;">[Evan] Sounds obvious, but did anyone check "Sent Items"?&nbsp; Yeah, probably.&nbsp; Seriously though, does the California DCA not log email sends and receives?&nbsp; It's hard to believe that the sender does not recall to whom they sent the email and there is no evidence of where it was sent.</span><br><br>The breach was discovered on Monday, June 9<br><span style="font-style: italic;">[Evan] It took 3 or 4 days for the DCA to discover the breach.</span><br><br>People's whose names were on the list were sent an email the next day and an official letter a week later.<br><span style="font-style: italic;">[Evan] Excellent quick notification.&nbsp; The earlier that a breach is detected and communicated to the data owner, the better.</span><br><br>Heimerich said the DCA will pay for a year of free credit reports and provide fraud insurance of up to $25,000 for everyone on the list.<br><span style="font-style: italic;">[Evan] One year of protection does not adequately protect information that has a lifespan that far exceeds that one year.&nbsp; Most bad guys (or gals) know that the "standard" organization response to a breach includes one year of free credit monitoring/protection, so many of them wait a year to use the information.&nbsp; It is also important to point out that just because a person monitors their credit, does not mean that their identity isn't being used elsewhere.&nbsp; It's a scary thought, but it's a broken system.</span><br><br>He said the DCA had not yet determined how much these protections were going to cost. <br><span style="font-style: italic;">[Evan] You can estimate the cost yourself.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>I like how Microsoft Outlook helps me when I am typing an email address in the "To:" field of my email.&nbsp; It saves me some keystrokes and a few precious seconds.&nbsp; Sometimes I am in such a hurry that I don't even notice that Outlook put in the wrong email address.&nbsp; I type my email, click send and away I go onto another task.&nbsp; A couple of days later, I get a call from a customer asking where their information is.&nbsp; I state that I sent it to them a couple of days ago, but they claim to have never gotten my email.&nbsp; I look through my sent items, and HOLY #*@^!&nbsp; I just sent some confidential (sensitive and potentially damaging) information to a competitor instead of my customer.<br><br>Sound conceivable?&nbsp; Have you ever sent an embarrassing email to the wrong person?&nbsp; It is very easy to do if your not paying attention.<br><br>There are a number of controls us information security guys can put in place to reduce the risk of this happening.&nbsp; One of the best is information security training and awareness (kind of an administrative control). <br><br><span style="font-weight: bold;">Past Breaches:</span><br><span style="font-weight: bold;">State of California:</span><br>March, 2008 - <a href="http://breachblog.com/2008/03/31/caldoc.aspx">San Quentin visitor and volunteer information lost</a> </font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/06/24/caldca.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 24 Jun 2008 13:51:19 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/email">email</category>
      <category domain="http://securityratty.com/tag/volunteer information lost">volunteer information lost</category>
      <category domain="http://securityratty.com/tag/wrong email address">wrong email address</category>
      <category domain="http://securityratty.com/tag/email address">email address</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/adequately protect information">adequately protect information</category>
      <category domain="http://securityratty.com/tag/credit cards">credit cards</category>
      <category domain="http://securityratty.com/tag/credit">credit</category>
      <source url="http://breachblog.com/2008/06/24/caldca.aspx">Errant email exposed Department of Consumer Affairs personal information</source>
    </item>
  </channel>
</rss>
