<?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: equifax]]></title>
    <link>http://securityratty.com/tag/equifax</link>
    <description></description>
    <pubDate>Tue, 15 Jan 2008 10:32:24 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Equifax bolsters border security ]]></title>
      <link>http://securityratty.com/article/02762ed90939b5fec285c30e70bf385a</link>
      <guid>http://securityratty.com/article/02762ed90939b5fec285c30e70bf385a</guid>
      <description><![CDATA[Equifax, the company that compiles credit reports, has chosen network-access-control technology to make sure contractors and employees access its network with machines that meet the firm's security...]]></description>
      <content:encoded><![CDATA[Equifax, the company that compiles credit reports, has chosen network-access-control technology to make sure contractors and employees access its network with machines that meet the firm's security requirements.]]></content:encoded>
      <pubDate>Wed, 02 Jul 2008 20:00:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/compiles credit reports">compiles credit reports</category>
      <category domain="http://securityratty.com/tag/employees access">employees access</category>
      <category domain="http://securityratty.com/tag/security requirements">security requirements</category>
      <category domain="http://securityratty.com/tag/equifax">equifax</category>
      <category domain="http://securityratty.com/tag/network">network</category>
      <category domain="http://securityratty.com/tag/contractors">contractors</category>
      <category domain="http://securityratty.com/tag/firm">firm</category>
      <category domain="http://securityratty.com/tag/machines">machines</category>
      <category domain="http://securityratty.com/tag/technology">technology</category>
      <source url="http://www.networkworld.com/news/2008/070308-equifax-border-security.html?fsrc=rss-security">Equifax bolsters border security </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[Oklahoma State University Parking Services server is compromised]]></title>
      <link>http://securityratty.com/article/f74dd3d54ef8465c68b7797c38075517</link>
      <guid>http://securityratty.com/article/f74dd3d54ef8465c68b7797c38075517</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
5/14/08

Organization
Oklahoma State University (&quot;OSU

Contractor/Consultant/Branch
OSU Parking &amp; Transit Services

Victims
OSU faculty, staff and...]]></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/okstate.jpg" align="right" height="127" width="198"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>5/14/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://osu.okstate.edu/">Oklahoma State University ("OSU")</a>&nbsp; <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.parking.okstate.edu/">OSU Parking &amp; Transit Services</a> <br><br><span style="font-weight: bold;">Victims:</span><br>OSU faculty, staff and students who had purchased a parking permit between July 2002 and March 2008<br><br><span style="font-weight: bold;">Number Affected:</span><br>as many as 70,000<br><br><span style="font-weight: bold;">Types of Data:</span><br>"names, addresses and Social Security numbers"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"Oklahoma State University has discovered that a server under the control of OSU Parking and Transit Services had been accessed from another country without authorization. The database contained confidential information, specifically the names, addresses and Social Security numbers of OSU faculty, staff and students who had purchased a parking permit between July 2002 and March 2008."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://idalert.okstate.edu/incident_00003.html">Oklahoma State University Alert</a> <br><a href="http://www.koco.com/news/16267153/detail.html">KOCO Channel 5 News</a> <br><a href="http://ocolly.com/2008/05/15/student-faculty-and-staff-info-exposed-in-osu-parking-server-breach/">The Daily O'Collegian</a> <br><a href="http://newsok.com/osu-admits-computer-security-breach/article/3243594/?tm=1210801442">The Oklahoman</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Oklahoma State University<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>STILLWATER, Okla. -- Personal information belonging to anybody who got a parking pass at Oklahoma State University over the last five years has been compromised, university officials said Wednesday.<br><br>Oklahoma State University has discovered that a server under the control of OSU Parking and Transit Services had been accessed from another country without authorization. The database contained confidential information, specifically the names, addresses and Social Security numbers of OSU faculty, staff and students who had purchased a parking permit between July 2002 and March 2008.<br><span style="font-style: italic;">[Evan] What does the OSU Parking and Transit Services department need Social Security numbers for?&nbsp; Do you suppose information security personnel knew that sensitive personal information was stored on the server prior to this incident?</span><br><br>Upon discovering this intrusion, the IT Information Security Office immediately removed the server from the network to evaluate server activity to ascertain if personal information had been accessed.<br><br>The confidential information has been removed from the database.<br><br>The illegal access was limited to the parking and transit server.<br><br>As a result of its investigation, OSU believes the intruder's purpose and only action was to use the OSU server for storage capacity and bandwidth to upload and distribute illegal and inappropriate content.<br><span style="font-style: italic;">[Evan] I wonder if I am getting this right.&nbsp; Was there a direct network path from the public Internet through a firewall to the compromised database server running http, ftp, or some other file transfer protocol?&nbsp; That's not cool.&nbsp; A database server storing confidential information should not be accessible from the internet directly through a firewall. It is generally a good practice to separate the database function from the file transfer function into different servers and different firewall DMZs.&nbsp; All this for parking?&nbsp; Ugh.</span><br><br>OSU contacted and worked with federal law enforcement authorities.<br><br>After evaluation of all available data related to this incident, OSU found no evidence which would indicate that the database was copied or viewed by the hacker; however, OSU cannot say with 100 percent certainty that the hacker did not access personally identifiable information.<br><span style="font-style: italic;">[Evan] I wonder what evidence they looked for and how they went about gathering it.</span><br><br>We are not aware of any instances of misuse of this information or of any identify theft as a result of the temporary availability of this information.<br><br>OSU recommends you carefully review any bills or financial transactions you receive in the near future to ensure that the charges associated with your accounts are accurate.<br><span style="font-style: italic;">[Evan] Yeah!&nbsp; Review your bills (pay them occasionally) and financial transactions carefully.&nbsp; But wait, you do this already?&nbsp; Disappointing statement coming from an organization that did not carefully review their controls in securing your personal information.</span><br style="font-style: italic;"><br>OSU President Burns Hargis said, "This breakdown in security is totally unacceptable. We are conducting a full review and will take whatever steps are necessary to protect our network from unauthorized access. This is a serious matter and we will deal with it aggressively. We regret the circumstances and concern this situation has caused."<br><span style="font-style: italic;">[Evan] This is my favorite statement from this story!&nbsp; What do you suppose his stance was prior to being notified of the breach?&nbsp; </span><br><br><span style="font-style: italic;">In my experience, there are primarily ("primarily" because there are always exceptions) four types of senior information security management.&nbsp; You have the organizations that just don't get it and don't really care or know that they don't get it.&nbsp; These organizations lose information over and over and dangerously continue to operate in a business as usual manner. </span><br style="font-style: italic;"><br style="font-style: italic;"><span style="font-style: italic;">Secondly, you have the organizations that didn't get it, suffer some adverse event, then HOLY &amp;$#^!&nbsp; They respond with all guns blazing and overspend on controls they don't need and run a very cost ineffective security program (I guess they really never got it either).&nbsp; </span><br style="font-style: italic;"><br style="font-style: italic;"><span style="font-style: italic;">Thirdly, there is the company that didn't get it, suffered an adverse event and admitted they have a problem.&nbsp; These companies may seek guidance and consultation in the effort to build a comprehensive information security program.&nbsp; These programs should be built around business objectives and sound risk management.&nbsp; </span><br style="font-style: italic;"><br style="font-style: italic;"><span style="font-style: italic;">Lastly, there are the companies that were proactive and built a sound information security program because it was good business.&nbsp; These organizations didn't need an adverse event or breach before taking action.&nbsp; These organizations don't panic when an adverse event occurs.&nbsp; They know that eventually an adverse event will occur and they will be prepared when it does.</span><br style="font-style: italic;"><br>The server is believed to have been compromised on November 23, 2007. OSU learned of the breech [sic] on March 20, 2008 and blocked access to the server immediately.<br><span style="font-style: italic;">[Evan] Wow.&nbsp; The server was 0wn3d (like my 1337 5p34k?) for almost 4 months before anyone noticed?!&nbsp; That is way, way, way too long for a compromised server to go unnoticed.&nbsp; We can now assume that there was no effective IDS/IPS (host or network) and no effective logging and monitoring of the server.</span><br><br>The OSU Parking Department has altered their procedures for the collection of private information. Additionally, the server which was located at the OSU Parking Service's office will be relocated to the IT Data Center for enhanced security. OSU is conducting a full review and will be taking additional steps to protect our network from unauthorized access.<br><span style="font-style: italic;">[Evan] It's a very good idea to not collect private information if it is not required.&nbsp; It's too bad that it took a breach for this to happen.&nbsp; Moving the server from the Parking Service's office to the IT Data Center will help protect against physical security attacks, but this was a logical attack.&nbsp; Maybe the IT Data Center has better firewalls or something <img src="http://breachblog.com/emoticons/smile.png" border="0" />.&nbsp; I like the "full review".&nbsp; This should be done no less than annually.</span><br><br>The IT Information Security Office has made security recommendations to the OSU Parking Office which include physical relocation of their server and database to a more secure location, additional training for server administrators, and added vulnerability assessments.<br><br>Q. How will I know if any of my personal information was used by someone else? <br>A. The best way to find out is to obtain your credit reports from the three major credit bureaus: Equifax, Experian and Trans Union. If you notice accounts on your credit report that you did not open or applications for credit ("inquiries") that you did not make, these could be indications that someone else is using your personal information, without your permission.<br><span style="font-style: italic;">[Evan] "If you notice accounts on your credit report that you did not open or applications for credit ("inquiries") that you did not make", then chances are you have <span style="font-weight: bold;">already</span> become an identity-theft victim.&nbsp; I'm not saying whether this is likely, or not.</span><br><br>Q. Why did you have my personal information? <br>A. You provided this information to us when you applied to Oklahoma State University, or during your tenure as a student or employee here. Oklahoma State, like other institutions, maintains records of all employees and students who have attended the University.<br><span style="font-style: italic;">[Evan] Great question!&nbsp; Why did you have my personal information (on a publicly accessible server used in a department that doesn't really need it without proper protections and without proper monitoring)?</span><br><br><span style="font-weight: bold;">Commentary:</span><br>This breach torques me a little, in case you didn't pick up on that from the comments above.&nbsp; I made plenty.<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/05/15/okstate.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Thu, 15 May 2008 11:08:54 +0000</pubDate>
      <category domain="http://securityratty.com/tag/server">server</category>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/server administrators">server administrators</category>
      <category domain="http://securityratty.com/tag/server immediately">server immediately</category>
      <category domain="http://securityratty.com/tag/server prior">server prior</category>
      <category domain="http://securityratty.com/tag/database server">database server</category>
      <category domain="http://securityratty.com/tag/confidential information">confidential information</category>
      <source url="http://breachblog.com/2008/05/15/okstate.aspx">Oklahoma State University Parking Services server is compromised</source>
    </item>
    <item>
      <title><![CDATA[File containing Interbank FX customer information exposed for almost a year]]></title>
      <link>http://securityratty.com/article/184d08544bae8b30426de5caac87fb7a</link>
      <guid>http://securityratty.com/article/184d08544bae8b30426de5caac87fb7a</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
4/9/08

Organization
Interbank FX, LLC (&quot;IBFX

Contractor/Consultant/Branch
None

Victims
Customers and prospective customers prior to April 2, 2007
...]]></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/interbank.jpg" align="right" height="62" width="169"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>4/9/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="https://secure.ibfx.com/Default.aspx">Interbank FX, LLC ("IBFX")</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>Customers and prospective customers prior to April 2, 2007<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>"social security number, driver's license, and passport information, and may also include your Interbank FX account information"<br><br><span style="font-weight: bold;">Breach Description:</span><br>In April, 2007 an employee posted a file to an insecure server that was accessible via the Internet.&nbsp; The file contained personal information belonging to certain persons who applied for an Interbank FX account prior to April, 2007.&nbsp; Interbank FX became aware of the exposure on March 28th, 2008.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://doj.nh.gov/consumer/pdf/interbank.pdf">The 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>The letter to victims is signed by Todd B. Crosland, CEO and President of Interbank FX<br><span style="font-style: italic;">[Evan] This fact is important to note.&nbsp; I admire corporate leaders who step up and respond to an incident.&nbsp; Mr. Crosland seems to understand his role very well as it pertains to information security.&nbsp; Business leaders are the people that are ultimately responsible for the security of the organizations they run.</span><br><br>We are writing to inform you of a matter that may affect you. The security of some personal information you provided as you considered our service was inadvertently compromised. <br><br>Interbank FX has thoroughly investigated the matter, has taken immediate steps to protect your information, and is taking the additional precautions outlined in this letter to assist you in monitoring and guarding the security of your personal information.<br><br>The incident involved an electronic file dated April 2, 2007, which contained personal information provided by certain individuals who had applied for an Interbank FX account prior to that date. <br><br>Around that time, an employee uploaded the file to a computer server accessible via the internet. <br><span style="font-style: italic;">[Evan] So, sometime around April, 2007 is the date of the actual exposure.</span><br><br>The employee's action - placing the file outside of the Company's development lab, firewalls and secure computing environment - was contrary to Interbank FX policies and procedures and compromised the security of the information in the file.<br><span style="font-style: italic;">[Evan] I understand what the meaning of this statement is, but I also want to make it clear that a "development lab, firewalls, and secure computing environment" do not ensure security.&nbsp; There is a lot of room for interpretation. </span><br><br>The file contained the information you provided to us when you opened or considered opening an account with us. This may include your social security number, driver's license, and passport information, and may also include your Interbank FX account information.<br><br>Upon learning on March 28, 2008 that this information was available outside our secured computing envirornnent, the Company took immediate steps to secure the information. <br><span style="font-style: italic;">[Evan] The breach was discovered (by Interbank FX) almost a year later.&nbsp; The window of exposure was pretty long.</span><br><br>Within hours of that discovery, all files containing sensitive personal information were removed from the server and brought within the Company's firewalls and electronic security controls. <br><br>We also terminated the employee's access to all personal information in Interbank FX 's files.<br><br>You are receiving this letter because your application information was provided prior to April 2, 2007. <br><br>The incident does not affect anyone who applied for an Interbank FX account after April 2, 2007.<br><br>Interbank FX is committed to protecting your personal information. Thus, we are offering you the opportunity to enroll, at no cost to you, in Equifax Credit Watch(TM) Gold with 3-in-l Monitoring for a one-year period.<br><span style="font-style: italic;">[Evan] Although one-year has become a sort of de-facto standard in breach responses, it is not long enough.&nbsp; A Social Security number is valuable for a much longer period of time.</span> <br><br>We also will reimburse you for the direct cost of any freeze you choose to put on your credit file as a result of this issue. <br><span style="font-style: italic;">[Evan] I though that this statement was interesting.&nbsp; Maybe I don't read breach notifications thoroughly enough, but I don't think I have seen this offer before.</span><br><br>As an additional precaution, we also encourage you to change any password you created for your Interbank FX account prior to April 2, 2007. <br><br>We have established a toll-free hotline (800-550-1571) to answer your questions and assist you in signing up for the Equifax Credit WatchTM program. We ask you to notify us immediately if you notice (or have noticed) any unusual activity in any of your accounts.<br><br>We regret this incident and apologize for any inconvenience.<br><br><span style="font-weight: bold;">Commentary:</span><br>One year of exposure is a very long time for confidential information.&nbsp; I wonder how the company finally learned about the presence of the file(s).&nbsp; What do you suppose are the chances that the employee who uploaded the file:<br><br>1. Was not aware of the "Interbank FX policies and procedures" that pertained to his/her actions?<br>2. Was not aware that the file contained sensitive personal information?<br>3. Was not aware that the server was insecure and accessible publicly?<br>4. All of the above?<br><br>Personnel that handle sensitive information must be trained and re-trained.&nbsp; These personnel must also be reminded regularly through an ongoing awareness program. <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/15/interbank.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 15 Apr 2008 19:57:04 +0000</pubDate>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/application information">application information</category>
      <category domain="http://securityratty.com/tag/handle sensitive information">handle sensitive information</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/interbank">interbank</category>
      <category domain="http://securityratty.com/tag/file">file</category>
      <category domain="http://securityratty.com/tag/confidential information">confidential information</category>
      <source url="http://breachblog.com/2008/04/15/interbank.aspx">File containing Interbank FX customer information exposed for almost a year</source>
    </item>
    <item>
      <title><![CDATA[Personal information stolen from Georgia DHR]]></title>
      <link>http://securityratty.com/article/bf493a8ef2c8aae077b6aa21c463f815</link>
      <guid>http://securityratty.com/article/bf493a8ef2c8aae077b6aa21c463f815</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
3/21/08

Organization
State of Georgia

Contractor/Consultant/Branch
Department of Human Resources

Victims
Current and former employees

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/gdhr.jpg" align="right" height="39" width="202"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>3/21/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.georgia.gov/00/home/0,2061,4802,00.html">State of Georgia</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.dhr.georgia.gov/portal/site/DHR/menuitem.c2a7c634015c941b50c8798dd03036a0/?vgnextoid=b49807b35414ff00VgnVCM100000bf01010aRCRD">Department of Human Resources</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Current and former employees<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, birth dates, home contact and federal tax information"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"The Georgia Department of Human Resources is taking extensive measures to alert current and former employees of a breach of confidential records that may expose personal employee information."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.dhr.georgia.gov/portal/site/DHR/menuitem.3d43c0fad7b3111b50c8798dd03036a0/?vgnextoid=365aba497eec8110VgnVCM100000bf01010aRCRD&amp;vgnextchannel=1c29e1d09cb4ff00VgnVCM100000bf01010aRCRD">Georgia Department of Human Resources</a> <br><a href="http://www.lincolnjournalonline.com/news/2008/0327/News/014.html">The Lincoln Journal</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Georgia Department of Human Resources<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>The Georgia Department of Human Resources is taking extensive measures to alert current and former employees of a breach of confidential records that may expose personal employee information.<br><br>An external hard drive that stored a database containing identifying information such as names, social security numbers, birth dates, home contact and federal tax information was removed by an unauthorized person.<br><br>The agency warns that the breach took place on or around March 19th.<br><span style="font-style: italic;">[Evan] This is a very quick public response by Georgia DHR.</span><br><br>Since discovering the breach, DHR has been working diligently to inform employees of the breach while also conducting an internal investigation led by the Office of Investigative Services.<br><br>The agency has also proactively alerted the three credit bureaus about the situation.<br><span style="font-style: italic;">[Evan] Using "proactively" is interesting.&nbsp; This seems more reactive to me!</span><br><br>DHR has instituted a new directive which requires password protection on jump and flash drives and portable computer media that contains personnel information.<br><span style="font-style: italic;">[Evan] So what?&nbsp; What about encryption?&nbsp; I am interested to see how this works out for DHR.</span><br><br>Additionally, the agency is directing employees to secure these items when away from their desks and offices.<br><br>While DHR has no evidence that the information is being used fraudulently, the agency is taking every immediate measure to limit the possibility of potential fraud and identity theft.<br><br>Georgia law indicates that all residents are to receive two credit reports free of charge each year. The agency urges employees to retrieve a copy of their credit report and request a fraud alert be placed on their records. Employees should contact each credit bureau at the following: Experian, P. O. Box 9595, Allen, TX 75013-9595&nbsp;&nbsp; Tel:&nbsp; 888-397-3742; Equifax, P. O. Box 740241, Atlanta, GA 30374-0241 Tel:&nbsp; 800-685-1111; and Trans Union, P. O. Box 1000, Chester, PA 19022 Tel:&nbsp; 800-888-4213.<br><br><span style="font-weight: bold;">Commentary:</span><br>I have more questions than answers about this breach.&nbsp; DHR is mandating password protection with no mention of encryption.&nbsp; I wonder if encryption is meant to be implied and how DHR will enforce the new directive. <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/03/27/gdhr.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Thu, 27 Mar 2008 12:51:45 +0000</pubDate>
      <category domain="http://securityratty.com/tag/georgia dhr">georgia dhr</category>
      <category domain="http://securityratty.com/tag/dhr">dhr</category>
      <category domain="http://securityratty.com/tag/georgia">georgia</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/agency">agency</category>
      <category domain="http://securityratty.com/tag/agency urges employees">agency urges employees</category>
      <category domain="http://securityratty.com/tag/georgia law">georgia law</category>
      <category domain="http://securityratty.com/tag/georgia department">georgia department</category>
      <category domain="http://securityratty.com/tag/employees">employees</category>
      <source url="http://breachblog.com/2008/03/27/gdhr.aspx">Personal information stolen from Georgia DHR</source>
    </item>
    <item>
      <title><![CDATA[51,000 Current and former Agilent Technologies employees at risk]]></title>
      <link>http://securityratty.com/article/7f98d0a3b5ecf0829f46d93469acf677</link>
      <guid>http://securityratty.com/article/7f98d0a3b5ecf0829f46d93469acf677</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
3/22/08

Organization
Agilent Technologies

Contractor/Consultant/Branch
Stock &amp; Options Solutions

Victims
Current and former Agilent employees

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/agilent.jpg" align="right" height="51" width="200"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>3/22/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.home.agilent.com/agilent/home.jspx?cc=US&amp;lc=eng&amp;cmpid=4533">Agilent Technologies</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.sos-team.com/">Stock &amp; Options Solutions</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Current and former Agilent employees<br><br><span style="font-weight: bold;">Number Affected:</span><br>51,000<br><br><span style="font-weight: bold;">Types of Data:</span><br>"names, Social Security numbers, home addresses and details of stock options and other stock-related awards"<br><br><span style="font-weight: bold;">Breach Description:</span><br>"A laptop containing sensitive and unencrypted personal data on 51,000 current and former employees of Agilent Technologies was stolen from the car of an Agilent vendor March 1 in San Francisco, the company said in a letter mailed to former employees this week."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.mercurynews.com/peninsula/ci_8660115?nclick_check=1&amp;forced=true">The Mercury News - Silicon Valley</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Vindu Goel, The Mercury News<br><br><span style="font-weight: bold;">Response:</span><br>From the online source cited above:<br><br>A laptop containing sensitive and unencrypted personal data on 51,000 current and former employees of Agilent Technologies was stolen from the car of an Agilent vendor March 1 in San Francisco, the company said in a letter mailed to former employees this week.<br><span style="font-style: italic;">[Evan] A person in the comments of Vindu's View From The Valley "</span><a style="font-style: italic;" href="http://www.mercextra.com/blogs/vindu/2008/03/21/agilent-alert-thief-steals-laptop-with-personal-info-on-51000-employees/">Agilent alert: Thief steals laptop with personal info on 51,000 employees</a><span style="font-style: italic;">" story claims "Estimates show that 700,000 laptops are stolen every year. A little more than 1900 a day!"&nbsp; This number seems high to me, but I guess I wouldn't be too surprised if it were true.&nbsp; Storing confidential information on laptops (especially without additional controls) is risky.</span><br><br>The data includes employee names, Social Security numbers, home addresses and details of stock options and other stock-related awards.<br><br>In the letter, Agilent blamed the San Jose vendor, Stock &amp; Option Solutions, for failing to scramble or otherwise safeguard the data - "in violation of the contracted agreement."<br><span style="font-style: italic;">[Evan] We don't often read about a company coming right out and blatantly pointing the finger at their vendor.&nbsp; I like the "call it like you see it" approach.</span><br><br>"It wasn't encrypted, which was a surprise to us," said Agilent spokeswoman Amy Flores. She said the vendor told Agilent that an East Coast employee had brought the data-laden laptop to California for encryption, but someone broke into her car and stole the computer and her other belongings while the vehicle was parked near Fisherman's Wharf.<br><span style="font-style: italic;">[Evan] #1, we (meaning information security personnel) should not be surprised by what our vendors are doing with the information we are charged with protecting.&nbsp; Not only should we mandate specific controls in policies and contracts, but we also need to audit for compliance.&nbsp; #2, The vendor employee was bringing the laptop to California for encryption?&nbsp; I don't think there are any requirements that you have to go to California to encrypt laptops.&nbsp; Encryption should have taken place prior to allowing the information on it in the first place, and better yet should be part of a "standard" laptop build.</span><br><br>Flores said Agilent, a Santa Clara maker of test and measurement equipment, has no evidence that the lost data has been used to steal anyone's identity. However, Agilent is offering affected employees one free year of credit monitoring from Equifax.<br><span style="font-style: italic;">[Evan] I haven't said this for a while, but credit "monitoring" is an after the fact solution that only alerts a person after they are an identity theft victim.&nbsp; One year of monitoring is good for monitoring information that is no longer useful after one year.&nbsp; Obviously a Social Security number will still be valid after the monitoring has ended.</span><br><br>Ironically, Stock &amp; Option Solutions was hired to make sure that money management firm Smith Barney had properly transferred employee stock data to a new management firm, Fidelity Investments, which had been hired to administer Agilent's stock programs.<br><br>Matt O'Brien of Milpitas, a former research manager at Agilent who left in 2001, said he was "disgusted" when he received notice of the theft in his Friday mail.<br><br>said O'Brien. "Agilent should have put all of the data into an encrypted format to begin with."<br><span style="font-style: italic;">[Evan] Bingo.&nbsp; A victim with more information security common sense than the offender.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>At what point do we no longer accept lost or stolen laptops with confidential personal information at risk?&nbsp; Are the myriad of laws, regulations, negative news reports, etc. having a positive impact in reducing the frequency and number of victims?&nbsp; Maybe it's too early to tell.<br><br>I am also curious what Agilent and/or Stock &amp; Options Solutions are planning in order to prevent similar circumstances in the future. <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/03/25/agilent.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 25 Mar 2008 06:13:20 +0000</pubDate>
      <category domain="http://securityratty.com/tag/agilent">agilent</category>
      <category domain="http://securityratty.com/tag/agilent technologies">agilent technologies</category>
      <category domain="http://securityratty.com/tag/agilent vendor march">agilent vendor march</category>
      <category domain="http://securityratty.com/tag/vendor">vendor</category>
      <category domain="http://securityratty.com/tag/administer agilent">administer agilent</category>
      <category domain="http://securityratty.com/tag/agilent alert">agilent alert</category>
      <category domain="http://securityratty.com/tag/agilent employees">agilent employees</category>
      <category domain="http://securityratty.com/tag/stock">stock</category>
      <category domain="http://securityratty.com/tag/stock options">stock options</category>
      <source url="http://breachblog.com/2008/03/25/agilent.aspx">51,000 Current and former Agilent Technologies employees at risk</source>
    </item>
    <item>
      <title><![CDATA[Intrusion at Stedmans.com exposes credit card information]]></title>
      <link>http://securityratty.com/article/b843fad19d119230af985462a5bfdc22</link>
      <guid>http://securityratty.com/article/b843fad19d119230af985462a5bfdc22</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
3/10/08

Organization
Wolters Kluwer

Contractor/Consultant/Branch
Lippincott Williams &amp; Wilkins
Stedman's
Bixler Incorporated

Victims
Customers who...]]></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/wolters.jpg" align="right" height="45" width="201"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>3/10/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.wolterskluwer.com/WK/">Wolters Kluwer</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.lww.com/index.html">Lippincott Williams &amp; Wilkins</a> <br><a href="http://www.stedmans.com/">Stedman's</a> <br><a href="http://bixler.com/">Bixler Incorporated</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Customers who made online purchases from Stedman's between August 30th, 2007 and February 27th, 2008<br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown*<br><br><font size="1">*There were 25 New Hampshire residents affected.&nbsp; The total number affected is expected to be much larger.<br></font><br><span style="font-weight: bold;">Types of Data:</span><br>Names, addresses, telephone numbers, email addresses, credit card numbers, expiration dates, and card verification numbers.<br><br><span style="font-weight: bold;">Breach Description:</span><br>"On February 27, 2008, Lippincott Williams &amp; Wilkins, a Wolters Kluwer business was informed by the company that hosts one of our websites, <a href="http://www.stedmans.com,">www.stedmans.com,</a> that personal information collected from consumers through the website may have been compromised through an unauthorized intrusion into the server that stores information from individuals who purchased products at our website."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://doj.nh.gov/consumer/pdf/wolters.pdf">The New Hampshire State Attorney General breach notification</a> <a href="http://doj.nh.gov/consumer/pdf/wolters.pdf%3Cbr%3E%3Cbr%3E%3Cspan"><br><br><span></span></a><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>On February 27, 2008, Lippincott Williams &amp; Wilkins, a Wolters Kluwer business was informed by the company that hosts one of our websites, <a href="http://www.stedmans.com,">www.stedmans.com,</a> that personal information collected from consumers through the website may have been compromised through an unauthorized intrusion into the server that stores information from individuals who purchased products at our website.<br><span style="font-style: italic;">[Evan] The company that hosts stedmans.com is </span><a style="font-style: italic;" href="http://bixler.com/portfolio.cfm/Life%20Sciences/6">Bixler Incorporated</a><span style="font-style: italic;">.</span><br><br>The personal information that may have been comprised may include names, addresses, telephone numbers, email addresses, credit card numbers, expiration dates, and card verification numbers of individuals who made purchases at the site from approximately August 30, 2007 to February 27, 2008.<br><span style="font-style: italic;">[Evan] Storing card verification numbers is a violation of the Payment Card Industry (PCI) Data Security Standard.&nbsp; According to Requirement 3: Protect stored cardholder data, Section 3.2.1 "NEVER store the card verification code or value or PIN verification value data elements." and 3.2.2 "Do not store the card-validation code or value (three-digit or four-digit number printed on the front or back of a payment card) used to verify card-not-present transactions"&nbsp; Stedmans.com was not compliant with the standard.&nbsp; Why wasn't the site compliant, and what vulnerability was exploited?</span><br style="font-style: italic;"><br>The company has contacted the three major national credit reporting agencies, and the company mailed a notice to consumers who may have been affected by this incident on March 10, 2008<br><span style="font-style: italic;">[Evan] It would be a better idea to contact Visa and Mastercard than it would be to contact the credit reporting agencies.&nbsp; If the information was limited to what was reported, then there is not a high risk of immediate identity theft (no Social Security numbers in particular).&nbsp; There is a medium to high risk of credit card fraud, which is much different.</span><br style="font-style: italic;"><br>We are working with our website hosting company on additional security measures for the Stedmans.com website<br><span style="font-style: italic;">[Evan] It would be a good idea to work with information security professionals (third-party review).</span><br><br>we have arranged with Equifax Personal Solutions to provide potentially affected consumers with an opportunity to enroll in the Equifax Credit Watch Gold identity theft protection product at no cost to them for one year<br><span style="font-style: italic;">[Evan] Again, this is not really an identity theft issue.&nbsp; It is a credit card fraud issue.&nbsp; Two related but different issues.</span><br><br>Lippincott Williams &amp; Wilkins is committed to maintaining and protecting the confidentiality of our customers' personal, private, and sensitive information. We regret that this situation has occurred, and we will be working to reduce the risks of a similar situation happening in the future.<br><br><span style="font-weight: bold;">Commentary:</span><br>This breach certainly affects much more than the 25 New Hampshire residents mentioned in the breach notification to the New Hampshire State Attorney General.&nbsp; I am disappointed by appearance that stedmans.com was not VISA/PCI DSS compliant and the response that shows a misunderstanding of risks.&nbsp; Stedmans.com customers are mostly people in the medical field, so I am guessing that many of these credit cards have limits that exceed mine. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/03/23/wolters.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Sat, 22 Mar 2008 21:37:57 +0000</pubDate>
      <category domain="http://securityratty.com/tag/credit">credit</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/credit card">credit card</category>
      <category domain="http://securityratty.com/tag/credit cards">credit cards</category>
      <category domain="http://securityratty.com/tag/equifax credit">equifax credit</category>
      <category domain="http://securityratty.com/tag/report credit">report credit</category>
      <category domain="http://securityratty.com/tag/stedmans">stedmans</category>
      <category domain="http://securityratty.com/tag/information security professionals">information security professionals</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <source url="http://breachblog.com/2008/03/23/wolters.aspx">Intrusion at Stedmans.com exposes credit card information</source>
    </item>
    <item>
      <title><![CDATA[40,000 BlueCross BlueShield members notified of lost laptop]]></title>
      <link>http://securityratty.com/article/4d3b40d70e709c609969c6cfd0bb93f0</link>
      <guid>http://securityratty.com/article/4d3b40d70e709c609969c6cfd0bb93f0</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
3/10/08

Organization
HealthNow New York Inc

Contractor/Consultant/Branch
BlueCross BlueShield of Western New York

Victims
Healthcare members

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/bcbswny.jpg" align="right" height="78" width="128"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>3/10/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.healthnowny.com/">HealthNow New York Inc.</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.bcbswny.com/">BlueCross BlueShield of Western New York</a><br><br><span style="font-weight: bold;">Victims:</span><br>Healthcare members<br><br><span style="font-weight: bold;">Number Affected:</span><br>40,000<br><br><span style="font-weight: bold;">Types of Data:</span><br>Names, dates of birth, Social Security numbers, addresses, employer group names, and health insurance identifier numbers<br><br><span style="font-weight: bold;">Breach Description:</span><br>"Blue-Cross Blue-Shield of Western New York says it is notifying tens of thousands of its members about identity theft concerns after one of it's company laptops went missing."<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.buffalonews.com/145/story/296415.html">The Buffalo News</a> <br><a href="http://http://www.wivb.com/Global/story.asp?S=7992428">WIVB Channel 4 News</a> <br><a href="http://www.wgrz.com/sports/sports_article.aspx?storyid=56110&amp;provider=gnews">WGRZ Channel 2 News</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>WGRZ Channel 2 News<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>HealthNow New York has alerted 40,000 members in Western and Northeastern New York that they may be at risk for identity theft, after a former employee’s laptop computer went missing with confidential information several months ago.<br><br>The Buffalo-based parent of Blue- Cross BlueShield of Western New York sent letters late last week to the affected customers, even though officials are still not certain what, if anything, was on the computer.<br><span style="font-style: italic;">[Evan] Not sure where confidential information is?&nbsp; Sad, common and true.</span><br><br>Based on the company’s investigation, the potential information includes names, dates of birth, Social Security numbers, addresses, employer group names, and health insurance identifier numbers.<br><br>there was no health or medical claims information involved<br><span style="font-style: italic;">[Evan] I think a name, date of birth, Social Security number, address, and employer should be enough to do some damage.</span><br><br>HealthNow has arranged for any affected member to receive a one-year free membership in Equifax Credit Watch, to monitor for identity theft.<br><br>The laptop was not encrypted, but does have security features, including the requirement to enter the user’s identification number and passcode after 15 minutes of inactivity.<br><span style="font-style: italic;">[Evan] OK, seriously?&nbsp; Does anyone expect a username and password to stop someone with even novice computer skills?&nbsp; I am assuming that this is a Windows laptop, all the more simple.</span><br><br>the company shut down the laptop’s access to the corporate network, and has not detected any activity from the laptop since the disappearance.<br><span style="font-style: italic;">[Evan] Shutdown the laptop's access or access from the user id of the person that had been using the laptop?&nbsp; Semantics, I know.&nbsp; The information that may be on the laptop is the real concern.</span><br><br>The employee is no longer with HealthNow, having accepted a position at another company out of state, but the insurer is still in contact.<br><br>the company is reconfiguring its claims software system, and the employee had downloaded some member information to his laptop while working on the project so he could work either in building or at home<br><span style="font-style: italic;">[Evan] Too many "no-nos".&nbsp; "No-no" #1 is not knowing where confidential resides within the organization.&nbsp; "No-no" #2 is allowing confidential information onto mobile devices without additional controls such as encryption.&nbsp; "No-no" #3 is working with sensitive confidential information for software development and testing purposes.&nbsp; Only sanitized information should be used for development and test work.</span><br><br>The laptop was reported missing in late fall, but the company did not notify customers until now because officials wanted to make sure whether such action would be necessary.<br><span style="font-style: italic;">[Evan] This is way too long!&nbsp; An excerpt from New York Bill A02261 "Notice of Information Breach" can be found in the commentary below.</span><br><br>officials first "spent an exhorbitant amount of time" to try and locate the laptop, which they still believe is in the company’s building<br><br>Using the company’s shared drive and with the cooperation of the employee, officials retraced his path to determine what information he was working with. The company then set up the credit-monitoring, and began contacting members last Thursday and Friday.<br><br>"We didn’t want to have to reach out to our members and cause them unnecessary worry until we knew the potential of what we were dealing with," she said. "With all of the factors and orchestrating credit monitoring, we do believe our response time has been reasonable."<br><span style="font-style: italic;">[Evan] "We didn't want to have to reach out to our members and cause them unnecessary worry until we know the potential of what we were dealing with" is a terrible reason to delay notification.&nbsp; BlueCross BlueShield needs to understand that they are NOT the information owners.</span><br><br>The company has also tightened its policies and procedures about use of laptops and other mobile devices "to ensure that the policies are more strict," she said. She added that officials are also encrypting all information on laptops "to prevent this situation from recurring."<br><span style="font-style: italic;">[Evan] Of the "No-nos" I mentioned above, this takes care of one.</span><br><br><span style="font-weight: bold;">Commentary:</span><br>Another laptop that may or may not have contained sensitive personal information that goes missing without encryption.&nbsp; Do you think John Doe from XYZ company thought twice about filling out his health insurance forms on his first day of work?&nbsp; He probably just expected better protection from a company that handles thousands of personal records. <br><br>I am certainly not a lawyer, nor am I qualified to give legal advise of any kinds, but this is a simple copy and paste...<br><br>Excerpt from <a href="http://assembly.state.ny.us/leg/?bn=A02261&amp;sh=t">New York Bill A02261</a>:<br>"ANY&nbsp; PERSON,&nbsp; FIRM,&nbsp; PARTNERSHIP,&nbsp; ASSOCIATION OR CORPORATION THAT COLLECTS, OWNS, MAINTAINS OR USES PERSONAL INFORMATION SHALL DISCLOSE&nbsp; A BREACH&nbsp; OF&nbsp; SECURITY&nbsp; RELATED&nbsp; TO&nbsp; UNENCRYPTED&nbsp; OR NON-REDACTED PERSONAL INFORMATION CONCERNING TWENTY-FIVE OR MORE RESIDENTS OF NEW YORK.&nbsp;&nbsp;&nbsp; THE DISCLOSURE&nbsp; SHALL BE MADE WITHIN TWO BUSINESS DAYS AFTER LEARNING OF THE BREACH OF SECURITY, BUT MAY BE&nbsp; DELAYED&nbsp; IF&nbsp; A&nbsp; LAW&nbsp; ENFORCEMENT&nbsp; AGENCY DETERMINES&nbsp; THAT&nbsp; THE NOTIFICATION WILL IMPEDE A CRIMINAL INVESTIGATION. THE NOTIFICATION REQUIRED BY THIS SECTION SHALL BE MADE&nbsp; AFTER&nbsp; THE&nbsp; LAW ENFORCEMENT&nbsp; AGENCY&nbsp; DETERMINES THAT IT WILL NOT COMPROMISE THE INVESTIGATION."<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/03/11/bcbswny.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 11 Mar 2008 12:31:27 +0000</pubDate>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/confidential information">confidential information</category>
      <category domain="http://securityratty.com/tag/laptop">laptop</category>
      <category domain="http://securityratty.com/tag/information owners">information owners</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/security breach">security breach</category>
      <source url="http://breachblog.com/2008/03/11/bcbswny.aspx">40,000 BlueCross BlueShield members notified of lost laptop</source>
    </item>
    <item>
      <title><![CDATA[Nestle Waters North America employee affected by Systematic Automation breach]]></title>
      <link>http://securityratty.com/article/2037234f20d359e95edd4fe9f57e2ede</link>
      <guid>http://securityratty.com/article/2037234f20d359e95edd4fe9f57e2ede</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
2/26/08

Organization
Nestle Waters North America Inc. (&quot;NWNA

Contractor/Consultant/Branch
Systematic Automation

This breach is related to
Theft from...]]></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/nestlewaters.jpg" align="right" height="86" width="116">
<font size="2"><span style="font-weight: bold;">Date Reported: </span><br>2/26/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.nestle-watersna.com/">Nestle Waters North America Inc. ("NWNA")</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://maps.google.com/maps?hl=en&amp;client=opera&amp;rls=en&amp;hs=cvf&amp;um=1&amp;ie=UTF-8&amp;q=Systematic+Automation+Inc.&amp;near=Fullerton,+CA&amp;fb=1&amp;view=text&amp;latlng=33917450,-117929410,15433360472739007456">Systematic Automation</a>*<br><br><font size="1">*This breach is related to:<br>"<a href="http://breachblog.com/2008/02/12/modschools.aspx">Theft from vendor affects Modesto City Schools employees</a>" dated 2/12/08, <br>"<a href="http://breachblog.com/2008/02/19/dwp.aspx">L.A. Dept. of Water of Power employees exposed</a>" dated 2/19/08, and<br>"<a href="http://breachblog.com/2008/02/21/clovis.aspx">Clovis Unified School District employees receive notice</a>" dated 2/21/08<br></font></font><font size="1">"<a href="http://breachblog.com/2008/02/25/torrance.aspx">Systematic Automation breach continued...</a>" dated 2/22/08</font><br><font size="2"><br><span style="font-weight: bold;">Victims:</span><br>Employees of NWNA in 2006<br><br><span style="font-weight: bold;">Number Affected:</span><br>8,245<br><br><span style="font-weight: bold;">Types of Data:</span><br>Names, dates of birth, addresses and Social Security numbers.<br><br><span style="font-weight: bold;">Breach Description:</span><br>Computer equipment was stolen from a Nestle Waters North America ("NWNA") vendor, Systematic Automation that contained sensitive personal information belonging to persons employed with NWNA in 2006.&nbsp; Systematic Automation was employed by NWNA to create and distribute employee benefits statements.&nbsp; So far, this single breach has affected persons affiliated with five separate organizations.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://doj.nh.gov/consumer/pdf/nestle_waters.pdf">The 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>An Important Notification To Our NWNA Employees:<br>Systematic Automation Inc. ("SAI"), one of our vendors, recently experienced a breakin at their facility in Fullerton, California. Among other things, a desktop computer was stolen that contained a database of sensitive personal informatiion about NWNA employees, including a list of NWNA employees' names, addresses, dates of birth, and social security numbers.<br><br>This database only contained information about employees that were on the payroll as of February 1, 2006. <br><br>The information was password protected, but was not in an encrypted format.<br><span style="font-style: italic;">[Evan] A username and password (most likely Windows operating system) is not adequate protection for confidential information.&nbsp; A Windows XP/2000 password can be bypassed in a matter of minutes.&nbsp; IF the desktop computer were stolen for the information it contained, then we should consider it disclosed.&nbsp; Although encryption is not a perfect solution, it reduces the risk of exposure to an acceptable level in most circumstances.</span><br><br>We use SAI to create and distribute your employee benefits statements. In order for SAI to properly complete the work, we must provide SAI with certain personal information.<br><span style="font-style: italic;">[Evan] Understood, but then SAI needs to be regularly monitored for compliance with policy around the protection of such information.</span><br><br>We deeply regret that this incident occurred and we are talking immediate steps to make sure that something like this does not happen again.<br><br>At this time, we do not know if the thieves stole the computer with the intent to use the personal information for credit fraud purposes or whether this was merely a random criminal act. <br><br>The Fullerton Police Department is investigating the incident and SAI is cooperating fully with the Police Department investigation. <br><br>If this stolen personal information got in the wrong hands, however, you are at risk for identity theft or fraud.<br><br>NWNA will also provide, at no cost to you, one year of premium credit monitoring from Equifax, a leading credit monitoring company. <br><span style="font-style: italic;">[Evan] Equifax is a leading credit monitoring company, but also one of the three credit reporting agencies.&nbsp; It amazes me how Experian has capitalized on the information they collect, manage and sell.&nbsp; They are responsible for keeping accurate records, but at the same time will charge people a fee to make sure that they are doing what they are supposed to be doing.&nbsp; Something should give.</span><br><br>In the near future, instructions on enrollment will be mailed directly to your homes.<br><br>In addition, NWNA is in the process of establishing a hotline to provide you with the resources you need to get your questions answered. <br><br>NWNA sincerely regrets any inconvenience this incident may cause you. <br><br><span style="font-weight: bold;">Commentary:</span><br>As mentioned earlier, NWNA is the fifth known organization to be affected by the single breakin at Systematic Automation.&nbsp; It is becoming more and more clear that Systematic Automation did not follow some information security "best practices" by segmenting confidential customer data and encrypting it at rest.<br><br>I have not yet seen a statement from Systematic Automation. <br><br><span style="font-weight: bold;">Past Breaches:</span><br><span style="font-weight: bold;">Nestle Waters North America:</span><br>Unknown<br><span style="font-weight: bold;">Systematic Automation:</span><br>February, 2008 - <a href="http://breachblog.com/2008/02/25/torrance.aspx">Systematic Automation breach continued...</a> <br>February, 2008 - <a href="http://breachblog.com/2008/02/21/clovis.aspx">Clovis Unified School District employees receive notice</a> <br>February, 2008 - <a href="http://breachblog.com/2008/02/19/dwp.aspx">L.A. Dept. of Water of Power employees exposed</a> <br>February, 2008 - <a href="http://breachblog.com/2008/02/12/modschools.aspx">Theft from vendor affects Modesto City Schools employees</a></font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/03/04/nestlewaters.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 04 Mar 2008 07:08:42 +0000</pubDate>
      <category domain="http://securityratty.com/tag/systematic automation breach">systematic automation breach</category>
      <category domain="http://securityratty.com/tag/systematic automation">systematic automation</category>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/breach">breach</category>
      <category domain="http://securityratty.com/tag/employees">employees</category>
      <category domain="http://securityratty.com/tag/power employees">power employees</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/nwna">nwna</category>
      <source url="http://breachblog.com/2008/03/04/nestlewaters.aspx">Nestle Waters North America employee affected by Systematic Automation breach</source>
    </item>
    <item>
      <title><![CDATA[Another Wisconsin mailing exposes Social Security numbers]]></title>
      <link>http://securityratty.com/article/9a6d54372e14b872a4ab99130a9853eb</link>
      <guid>http://securityratty.com/article/9a6d54372e14b872a4ab99130a9853eb</guid>
      <description><![CDATA[Technorati Tag: Security Breach

Date Reported
1/9/08

Organization
State of Wisconsin

Contractor/Consultant/Branch
Department of Revenue
Department of Administration

Victims
Wisconsin residents who...]]></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/wdor.jpg" align="right" height="70" width="200"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>1/9/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="http://www.wisconsin.gov" target="_blank"> State of Wisconsin</a> <br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br><a href="http://www.revenue.wi.gov/" target="_blank"> Department of Revenue</a> <br><a href="http://www.doa.state.wi.us/" target="_blank"> Department of Administration</a> <br><br><span style="font-weight: bold;">Victims:</span><br>Wisconsin residents who itemized deductions, received a 2006 Wisconsin income tax refund, AND live in Freedom, Kaukauna, Keshena, Kimberly, Krakow, Lakewood, Lena, Little Chute, Little Suamico, or Marinette community.<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>Name, address and Social Security number.<br><br><span style="font-weight: bold;">Breach Description:</span><br>The Wisconsin Department of Revenue announced that as many as 5,000 mailings were sent to residents in which Social Security numbers were exposed through the envelope window.&nbsp; The error is being blamed on a "misfold" on Form 1099-G.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://www.revenue.wi.gov/news/1099-g.pdf" target="_blank"> Wisconsin Department of Revenue News Release</a> <br><a href="http://www.greenbaypressgazette.com/apps/pbcs.dll/article?AID=/20080115/GPG0101/80115078/1207/GPGnews" target="_blank"> The Associated Press Story at greenbaygazette.com</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Wisconsin Department of Revenue<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>The Department of Administration (DOA) and Department of Revenue (DOR) learned on January 9, 2008, that during a mailing, a printing misfold led to some social security numbers on Form 1099-G being partially visible through the window envelope.<br><span style="font-style: italic;">[Evan] Oh boy!&nbsp; Not again.</span><br><br>The State of Wisconsin apologizes for this error and is taking steps to assist any taxpayer that may be affected. <br><br>You may be affected if all the following apply: <br>You itemized your deductions AND received a 2006 Wisconsin income tax refund. The forms at risk were sent to the following communities with a postmark of January 2, 2008: Freedom, Kaukauna, Keshena, Kimberly, Krakow, Lakewood, Lena, Little Chute, Little Suamico, and Marinette. <br><br>Only the social security number of the “primary” taxpayer were printed on the Form 1099-G. <br><br>DOA, the agency responsible for printing, folding and mailing the Form 1099-G, corrected the problem with the folding machine.<br><span style="font-style: italic;">[Evan] "DOA" is the Department of Administration. </span><br><br>DOA and DOR identified which machine malfunctioned, what zip codes were impacted, and which taxpayers’ social security numbers were potentially viewable through the window envelope. <br><br>DOR contacted the taxpayers potentially affected and offered instructions on how to apply for one year of free credit monitoring.<br><span style="font-style: italic;">[Evan] One year of free credit monitoring is better than nothing, but hardly adequate.&nbsp; Credit monitoring only alerts a victim after the attacker has committed fraud.&nbsp; When confidential information is disclosed, the information is disclosed forever, not for only a year. </span><br><br>A letter to affected taxpayers was mailed the week of January 14, 2007. If your social security number is identified as one of the 5,000 potentially affected by the misfolding, you will receive a letter. <br><br>The social security number is required by the Internal Revenue Service to be placed on all 1099 forms. The social security number is necessary to ensure that income reported on the form belongs to the taxpayer. <br><br>Taxpayers who receive a letter with a Equifax PIN should follow the instructions to apply for free credit monitoring. There are other steps that can be taken to protect personal information. Ask credit bureaus to place a “fraud alert” in your credit files for free. Fraud alerts notify potential credit grantors to verify your indetification before extending credit in your name. You can also place a “security freeze” on your credit report, which prohibits a credit bureau from releasing information in your credit report without your express authorization. You must request a freeze in writing by certified mail with each of the three credit bureaus, and there is a $10 fee per credit bureau.<br><br><span style="font-weight: bold;">Commentary:</span><br>This is the second similar (mailing) breach involving the State of Wisconsin in the last week!<br><br>Maybe the State of Wisconsin should QA their folding machines and other mailing processes before sending.&nbsp; I have not worked in a mailing shop before, but don't they do test runs before production runs?<br><br>At least the Packers are in the NFC Championship game.&nbsp; Go Pack! <br><br><span style="font-weight: bold;">Past Breaches:</span><br>January, 2008 - <a href="http://breachblog.com/2008/01/08/dhfs.aspx" target="_blank"> Wisconsin Dept. of Health and Family Services mails Social Security numbers</a> <br>December, 2006 - <a href="http://privacy.wi.gov/alerts/jan0107.jsp" target="_blank"> Wisconsin mails tax forms with Social Security numbers printed on them</a></font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/01/15/wdor.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Tue, 15 Jan 2008 10:32:24 +0000</pubDate>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/taxpayers">taxpayers</category>
      <category domain="http://securityratty.com/tag/taxpayers social security">taxpayers social security</category>
      <category domain="http://securityratty.com/tag/social security">social security</category>
      <category domain="http://securityratty.com/tag/wisconsin">wisconsin</category>
      <category domain="http://securityratty.com/tag/credit bureau">credit bureau</category>
      <category domain="http://securityratty.com/tag/credit">credit</category>
      <category domain="http://securityratty.com/tag/breach description">breach description</category>
      <category domain="http://securityratty.com/tag/breach">breach</category>
      <source url="http://breachblog.com/2008/01/15/wdor.aspx">Another Wisconsin mailing exposes Social Security numbers</source>
    </item>
  </channel>
</rss>
