<?xml version="1.0" encoding="UTF-8"?>
<incident>
  <arrest type="boolean">false</arrest>
  <breach-type-id type="integer">1</breach-type-id>
  <comments-count type="integer">1</comments-count>
  <data-family-id type="integer">1</data-family-id>
  <data-recovered type="boolean">false</data-recovered>
  <disputed type="boolean">false</disputed>
  <fringe type="boolean">false</fringe>
  <fringe-description nil="true"></fringe-description>
  <id type="integer">15</id>
  <lawsuit type="boolean">false</lawsuit>
  <records type="integer">0</records>
  <submission-id type="integer" nil="true"></submission-id>
  <updated-at type="datetime">2011-06-16T22:47:27Z</updated-at>
  <user-id type="integer" nil="true"></user-id>
  <breach-types type="array">
    <breach_type>
      <name>Hack</name>
    </breach_type>
  </breach-types>
  <data-types type="array">
    <data_type>
      <short_name>CCN</short_name>
    </data_type>
  </data-types>
  <timeline-items type="array">
    <timeline_item>
      <first_date>2000-12-23 00:00:00 UTC</first_date>
      <second_date>2009-10-02 22:31:00 UTC</second_date>
      <type>Organization reports incident</type>
    </timeline_item>
  </timeline-items>
  <vector>
    <name>Outside</name>
  </vector>
  <primary-organization>
    <business-type-id type="integer">1</business-type-id>
    <freebase-cached-data type="yaml" nil="true"></freebase-cached-data>
    <freebase-description nil="true"></freebase-description>
    <freebase-pref-name nil="true"></freebase-pref-name>
    <id type="integer">11</id>
    <is-private type="boolean" nil="true"></is-private>
    <name>Egghead.com</name>
    <stock-symbol nil="true"></stock-symbol>
    <updated-at type="datetime">2008-07-14T22:16:59Z</updated-at>
  </primary-organization>
  <secondary-organizations type="array"/>
  <summary>
    <summary>Large number of credit card numbers accessed by a hacker</summary>
  </summary>
  <comments type="array">
    <comment>
      <content>The problem I see is Heartland is being anything but transparent.  Releasing the story on inaugural day, and stating &quot;people aren't really at risk.&quot;   What that statement seems to ignore is data pirates can and do combine artifacts assembled from disparate origin, and it would be a trove to have millions of CC to cross-match against existing partial CC stolen from elsewhere, or existing names, etc.   Heartland must be compelled to release the merchant names involved, so the issue can be fully addressed by all involved, not least of which is the public who may be impacted.  Finally, any data incident found by 'anomalous billing patterns' is pretty much assured to have been missed by existing method of detection, and heartland has nothing to be proud of in that area either.  Visa told them, not the other way around.   I want to see heartland held to a higher standard than they are attempting to hold themselves to.</content>
      <created_at>2009-01-23 15:02:45 UTC</created_at>
    </comment>
  </comments>
  <location>
    <address>USA</address>
    <thoroughfare_name></thoroughfare_name>
    <dependent_locality_name></dependent_locality_name>
    <locality_name></locality_name>
    <sub_administrative_area_name></sub_administrative_area_name>
    <administrative_area_name></administrative_area_name>
    <postal_code_number></postal_code_number>
    <country_name_code>US</country_name_code>
    <longitude>37.0902</longitude>
    <latitude>-95.7129</latitude>
    <accuracy>1</accuracy>
  </location>
</incident>

