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

Date Reported
6/13/08

Organization
CNET Networks, Inc. (&quot;CNET

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

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

Date Reported
2/8/08

Organization
Administrative Systems, Inc. (ASI

ASI is a licensed third party administrator that provides certain administrative services on...]]></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/asi.jpg" align="right" height="74" width="161"><font size="2"><span style="font-weight: bold;">Date Reported: </span><br>2/8/08<br><br><span style="font-weight: bold;">Organization: </span><br><a href="https://www.asibpi.com/" target="_blank"> Administrative Systems, Inc. (ASI)</a>*<br><br><font size="1">*ASI is a licensed third party administrator that provides certain administrative services on behalf of its clients, which include insurance companies and other financial services companies. These services often include processing employee applications for insurance coverage, issuing of insurance plans and employee certificates, managing premium billing and collection for insurance plans, responding to customer service requests and other record-keeping functions.</font><br><br><span style="font-weight: bold;">Contractor/Consultant/Branch:</span><br>None<br><br><span style="font-weight: bold;">Victims:</span><br>Customers of various ASI partner companies**<br><br><font size="1">** Lists of companies in "<a href="https://www.asibpi.com/partners.htm" target="_blank"> Strategic Partnerships</a>"&nbsp; and <a href="https://www.asibpi.com/forms2.asp" target="_blank"> forms</a>.</font><br><br><span style="font-weight: bold;">Number Affected:</span><br>Unknown<br><br><span style="font-weight: bold;">Types of Data:</span><br>Name, dates of birth, mailing addresses, and Social Security numbers<br><br><span style="font-weight: bold;">Breach Description:</span><br>On December 29th, 2008, a desktop computer was stolen from the Seattle offices of Administrative Systems, Inc. ("ASI") that contained a database of sensitive personal information belonging to customers of the company's clients.<br><br><span style="font-weight: bold;">Reference URL:</span><br><a href="http://incident.asibpi.com/notice.html" target="_blank"> Administrative Systems, Inc. official notice to victims</a> <br><a href="http://www.pogowasright.org/article.php?story=20080210130455236" target="_blank"> PogoWasRight.org Story</a> <br><br><span style="font-weight: bold;">Report Credit:</span><br>Administrative Systems, Inc., with a special thanks to PogoWasRight.org<br><br><span style="font-weight: bold;">Response:</span><br>From the online sources cited above:<br><br>A desktop computer stolen from an Administrative Systems, Inc. (ASI) office in Seattle on December 29th contained names and sensitive information about customers or employees of several of the firm's clients: Continental American Medical, EyeMed Vision/Kelly Services Vision, and Jefferson Pilot Financial Dental.<br><br>ASI is a licensed third party administrator that provides certain administrative services on behalf of its clients, which include insurance companies and other financial services companies. These services often include processing employee applications for insurance coverage, issuing of insurance plans and employee certificates, managing premium billing and collection for insurance plans, responding to customer service requests and other record-keeping functions.<br><span style="font-style: italic;">[Evan] Sheesh, this is some very sensitive information.&nbsp; There is no mention in the notification or the Administrative Systems, Inc. web site about what is done to protect this information.</span><br><br>personal information about customers including name, date of birth, mailing address, social security number (“sensitive information”). The information did not include credit card information or driver’s license numbers.<br><br>We are writing to notify you of this incident and to assure you that we take this matter seriously and are taking steps designed to minimize the likelihood of such an event occurring in the future.<br><span style="font-style: italic;">[Evan] What specifically is being done?</span><br><br>We have tightened our security measures to provide greater protection for the information we maintain and are working closely with local authorities to minimize future risks.<br><span style="font-style: italic;">[Evan] Again, no specifics.</span><br><br>The Seattle Police Department is investigating this incident and ASI is cooperating fully with this investigation.<br><br>We suggest that you remain vigilant over the next twelve to twenty-four months by reviewing your financial account statements and monitoring your credit reports to minimize your potential risk of identity theft or fraud.<br><span style="font-style: italic;">[Evan] The onus is on the data custodian to protect the information according to what is expected by the data owner.&nbsp; The victims can remain vigilant, but what if data custodians are not?&nbsp; Take your business elsewhere?</span><br><br>ASI sincerely regrets any inconvenience this incident may cause you. We know our clients value your trust and confidence and we remain committed to ensuring the security of your personal information. If you have questions for ASI regarding this incident, please call toll free 1-866-614-9454. We will be available Monday through Friday from 8 am to 8 pm Eastern time.<br><br>In its notification letter, ASI did not indicate whether the data were encrypted nor why it took over a month for individuals to be notified of the theft<br><br><br><span style="font-weight: bold;">Commentary:</span><br>This is a very unfortunate breach.&nbsp; I assume that many of the victims do not even know who ASI is or how they came into the possession of their information.&nbsp; If I received one of the notifications from ASI, I would have more questions than answers and I would be frustrated.&nbsp; As customers of companies, we provide certain personal information.&nbsp; We trust that the companies we do business with will see to it that our information is adequately protected.&nbsp; In this instance, information was passed on to a third-party and that third-party did not do what they should have done to protect personal information.<br><br>There is no mention of any existing controls or what controls ASI plans to evaluate to further strengthen their information security and reduce risk.&nbsp; Victims and customers are left in the dark.&nbsp; One can only assume what type of physical controls were in place to protect against the physical theft or what technological controls were in place to protect against compromised confidentiality.&nbsp; Your guess is as good as mine. <br><br><span style="font-weight: bold;">Past Breaches:</span><br>Unknown</font><br><br>
<script src="http://feeds.feedburner.com/%7Es/breachblog?i=http://breachblog.com/2008/02/11/asi.aspx" type="text/javascript" charset="utf-8"></script>]]></content:encoded>
      <pubDate>Mon, 11 Feb 2008 11:53:04 +0000</pubDate>
      <category domain="http://securityratty.com/tag/protect personal information">protect personal information</category>
      <category domain="http://securityratty.com/tag/personal information">personal information</category>
      <category domain="http://securityratty.com/tag/sensitive personal information">sensitive personal information</category>
      <category domain="http://securityratty.com/tag/companies">companies</category>
      <category domain="http://securityratty.com/tag/include insurance companies">include insurance companies</category>
      <category domain="http://securityratty.com/tag/financial services companies">financial services companies</category>
      <category domain="http://securityratty.com/tag/information">information</category>
      <category domain="http://securityratty.com/tag/information security">information security</category>
      <category domain="http://securityratty.com/tag/asi partner companies">asi partner companies</category>
      <source url="http://breachblog.com/2008/02/11/asi.aspx">Desktop computer stolen from Administrative Systems, Inc.</source>
    </item>
  </channel>
</rss>
