Posts Tagged ‘Data breach’

Another Korean data breach – GOMTV.NET spills user account data, including passwords

Published by pratyushkp on August 16th, 2011 - in Social, Technology

Image via Wikipedia

Another South Korean service provider has reported a large-scale data breach, leaking usernames and passwords for subscribers worldwide.

Late last month, cybercrooks made off with the personal information of up to 35,000,000 users of popular Korean sites Nate and Cyworld.

This time, it’s the turn of Seoul-based streaming media service GOMTV to suffer a data-spilling intrusion.

(That’s ‘GOM TV’, where GOM means Gretech Online Movies, not ‘GO MTV’, where MTV means Music Television. Gretech Corporation is the Korean legal entity which sets the terms and conditions and the privacy policy to which you agree when you sign up for GOM TV.)

Tags: breach, , , , data leakage, gom, GOM Player, gomtv, gretech, hash, korea, , OpenBSD, , , pii, , , , Vulnerability

President Obama’s cybersecurity plan – Part 2 Data Breach Notification Act

Published by pratyushkp on May 19th, 2011 - in Social

Image via Wikipedia

Following up on yesterday’s post outlining the proposed changes to RICO and the Computer Fraud and Abuse Act, today I will dissect the White House’s proposal for the National Data Breach Notification Act.

Currently 47 states have data breach notification laws with varying rules and requirements. This makes it very difficult for national and multinational organizations to understand when they must report lost or stolen data and how they must report it. The idea of a national law in the US has been debated for a couple of years now, and this proposal seems to strike a nice balance.

First, the definition of Personally Identifiable Information, or PII:

  1. Full name plus any two of the following
    1. Address and phone number
    2. Mother’s maiden name
    3. Month, day, and year of birth
  2. Social Security Number (SSN), driver’s license number, passport number, alien registration number, or other government issued identification number
  3. Biometric data such as fingerprints, retinal scans, etc.
  4. Unique account numbers, financial account numbers, credit card numbers, debit card numbers, electronic IDs, user names or routing codes
  5. Any combination of the following
    1. First and last name or first initial and last name
    2. See item four above
    3. Security codes, access codes, passwords or source codes used to derive the aforementioned

The new rules would apply to any business possessing the PII of 10,000 or more individuals in a 12-month period. They would supersede any existing state laws, creating one unified national standard.

Organizations discovering lost or stolen PII would have 60 days to notify affected customers unless law enforcement or national security concerns intervene. If there are extenuating circumstances, organizations can provide proof to the Federal Trade Commission (FTC) that they require up to an additional 30 days.

The proposal includes a “safe harbor” provision when measures are in place to protect data (encryption). Organizations must still report the data loss to the FTC within 45 days, including a professional risk assessment, logs of access to the data and a complete list of users who had access to the protected data.

If data is determined to be properly protected and evidence is submitted on time, individual notifications would be unnecessary. Financial institutions who only lose account numbers are also exempt if other protective measures are in place to prevent fraud.

After a data loss incident, organizations would be required to notify individuals by letter, phone or email.

Notices would include what information was compromised and a toll-free number to contact the company responsible to obtain more information. If a third party lost the data, the notice must include the name of the original collector (direct business relationship) of the PII.

States may pass laws requiring notifications to include information about identity theft/fraud prevention.

When more than 5,000 victims are involved, organizations would be required to do the following:

  • Place advertisements in mass media ensuring potential victims are aware of the risk they are being exposed to.
  • Notify all consumer credit reporting agencies of the victims within 60 days of discovery.

Businesses would be required to notify the Department of Homeland Security for law enforcement purposes when any of the following are true:

  • The breach contains, or is believed to contain, PII on 5,000 or more individuals.
  • The breach involves a database or network of databases that contain PII on 500,000 or more individuals.
  • The breach involves a database owned by the United States government.
  • The breach involves PII of employees or contractors of the United States government involved in law enforcement or national security.

Notice to DHS must occur 72 hours before individual notices are served, or 10 days after discovery of the incident, whichever comes first.

The proposed rules would be enforced by the FTC after consultation with the US Attorney General to ensure there is no interference with ongoing criminal investigations. State Attorneys General would also be able to enforce the rules within their jurisdiction after notifying the FTC.

Penalties for non-compliance would be $1000 per person affected per day, for a maximum of $1 million. There would not be a maximum penalty if it is determined the non-compliance was willful or intentional.

Organizations that are required to comply with HIPAA or HITECH data protection laws are exempt from this legislation.

It appears the Obama Administration and Howard Schmidt, the President’s Cyber-Security Coordinator, have taken careful notes from the different laws passed by individual states. This proposal is a great start to making data security a priority and contains provisions to make adjustments after implementation.

Why not download the “The State of Data Security” report we published today? It covers the most prominent data loss incidents and details the actions you can take to prevent you from being the next company to have to notify your customers.

Source :- http://nakedsecurity.sophos.com

  • White House Seeks National Data-Breach Notification Law (informationweek.com)
  • The U.S. Cyber Policy Blitz (technologyreview.in)
  • White House Wants Mandatory 3-Year Sentence for Critical Infrastructure Hackers (wired.com)
  • Does Obama Really Have an Internet Kill Switch? (pcworld.com)
  • How security chief’s bank details leaked (theage.com.au)
  • How big was the Epsilon data breach? (superconductor.voltage.com)
  • Five things companies must do to protect customer data (news.consumerreports.org)
  • U.S. Cybersecurity Proposal – A Plan about Plans: We Need More Action and Talent If We’re Serious about Securing Our Nation’s Data (lumension.com)
  • White House Releases Cybersecurity Plans (informationweek.com)
  • Is Sony Getting a Bad Rap on Its Data Breach? (pcworld.com)
© Social Media Blog