A Guide to per State Data Breach Response

save
Share and earn Cybytes
Facebook Twitter LinkedIn Email

Part 1: Preparing for a US Data Breach

In the data management and IT space there have been significant consideration and hand wringing about how the European Union’s General Data Protection Regulation (GDPR) will eventually impact US based businesses or how a future US Federal data breach disclosure law might affect IT operations. What often is the missed in the discussion is that there are significant per state data disclosure notification regulations currently in effect in the USA..

What’s even worse, as laws vary so much state to state, you might not realize that they’re applicable to you until you’re already broken them.

What is a Data Breach?

Data integrity centers around control. Who can access a particular piece of data? Who has rights to modify a file? What accounts can write to a database?

If at any point, for any reason, an organization loses control of a piece of data it’s considered to be a data breach.

From a technical perspective there is a massive difference in the severity of the threat posed by something like the OPM Data breach – which exposed the background investigation files, fingerprints, medical history and Social Security Numbers of 4.2 million people and the forum software on a relatively small website being compromised.

While vastly different in scope and in the type of data that was exposed, it’s important to realize that the analysis, response and notifications that need to be taken are exactly the same.

We are right now living in a world where it’s very likely that what were previously routine attacks or incidents should be reported as a data breach.

Depending on what state you’re in and exactly what was exposed any of the following scenarios would trigger the need for you to execute on a data breach notification plan:

  1. A phishing attack that revealed employment data on a half dozen employees.
  2. A spreadsheet with a list of student emails and if they had peanut allergies
  3. A forum breach where emails and passwords were taken.
  4. A cloud based service that you use experiencing a security incident.

A ransomware attack that encrypts files containing PII data is considered a data breach in legal terms as while the data hasn’t left the confines of your network, it’s no longer in your control. For more information, read: Is a ransomware attack a data breach?

What to do to Prepare for a Data Breach Notification?

Understanding what data is in your possession, who it’s associated with and who is using it are all keys to making breach notification decisions.

Data Breach Preparation Checklist

  1. Properly associate your data with a user
  2. Maintain up to date contact information
  3. Keep up to date records of which US State a person resides in:
    • Self reported (shipping or billing address) and when it was last updated
    • IP Address
  4. Classify your data by type
    • First or Last Name
    • Social Security Number
    • State ID numbers (Driver License, Passport)
    • Any financial account information
    • Any biometric information (fingerprints, retina scans, etc.)
    • DNA (genetic) identifiers
    • Electronic Signatures
    • Employer ID numbers or access codes
    • Any Financial information (ex: retirement account numbers, investment information)
    • Health Insurance Info (a health insurance ID is sufficient)
    • Any medical information

A product like the Data Classification Framework can be very helpful in identifying PII within files on a network.

What to do when you Discover you have a Data Breach?

First you should take whatever steps are necessary to prevent further data loss (patch, modify permissions, other remediation).

Next:

  1. Formally note the date you first became aware of the data breach as the clock is ticking.
  2. Determine the number of people affected.
  3. Find out exactly what user identifying data attributes were disclosed.
  4. Investigate to find out exactly what types of application data were affected.
  5. If you prepared and have per state user information, determine what communication options.you have to contact each person (email, sms, mailing address)

How to Avoid Having to do Data Breach Notifications?

We’re going to presume that you’re already taking steps to secure your network and applications properly. You may or may not have taken additional steps to structure and monitor your data internally. Doing so both better protects data you’ve been entrusted with and limits the potential that you’ll need to be in a meeting with the CEO, Chief Legal Counsel and the Attorney General of your state.

Have a Data Retention and Purge Plan

Purge unused data (quantities of data matter as different rules are triggered at higher numbers of affected users). Products like Data Transport Engine and others allow you to do do things like remove data based on rules like “File hasn’t been accessed in 6 months”. Other applications like DatAdvantage let you conduct entitlement reviews continuously to limit who has access to what data.

Separate Authentication and Application Data

While this isn’t always possible, having separate higher security user authentication systems that contain users’ email, password (or other auth system) allows for another layer of security.

A great recent example of this is the Unity Forum data-breach. Unity is a framework for developing 3D content like games and virtual reality experiences. They have tens of thousands of developers who ask questions of each other and have discussions around such exciting topics as: “Dynamically Translating/Rotating a NavMeshSurface/NavMesh Agent”.

Users log into the forums via a central UnityID service that also controls access to their asset store, question and answer site, etc. So while their forums were defaced they were able to write:

“On April 30, our public forum website was attacked and successfully compromised due to poorly implemented password routines; our investigations show no theft of passwords in this attack, nor impact to any other Unity service.”

What’s unsaid is that they also sidestepped most data breach disclosure requirements as in most cases losing control of user passwords is a trigger. This separation helps keep a bad situation from turning into a legal quagmire.

Who Needs Notified when a Data Breach Occurs?

Affected users should be notified that a data breach has occurred. It’s important that they are informed of what has occurred and what steps they should take “without undue delay”.

Do I Need to Notify each State’s Attorney General?

Depending upon the per state breakdown of affected users, each state attorney generals’ office may need to be notified. For example, Hawaii requires that the attorney general be notified if over a 1000 state residents are included in breach, whereas North Data requires notification for more than 250 and New York State if any state residents are affected.

Do I need to Notify a Nationwide Consumer Credit Reporting Agency (Credit Bureau)?

Similar to the Attorney General notifications, per state requirements govern whether you will need to contact Consumer Credit Reporting Agencies (CCRA). Depending on the type of data that has been compromised you may need to coordinate requesting fraud alerts and freezing credit cards.

How Should People be Notified of a Data Breach?

For most small scale breaches (defined per state) notifications can be done via email, mail or telephone. It’s recommended to contact people in the most expeditious way possible, which for most organizations likely means you’ll be conducting notifications via email.

In cases where the the cost of notification exceeds a certain limit (most often $200,000), the number of people affected exceeds a threshold (most often 500,000) or in cases where you don’t have sufficient contact information to send individual notifications, mass notification procedures can be used instead.

Typically this comes down to placing a “prominent” notification on your public facing website for a period of time sufficient to inform affected users.

Alternatively, statewide media may be contacted and informed of the data breach. Typically this is considered to mean that you send your breach disclosure information to the newspapers and TV stations operating in the state. This quickly becomes something complex enough that you should not tackle on your own, instead use a Press Release service to distribute your notification. Such as:

How can I Figure Out What States My Users Reside In?

By far the easiest method is to ask them and then periodically reconfirm that their information is up to date. If you have ever registered a domain, you’ve likely received an email asking you confirm that your contact information is up to date. If circumstances allow you, you could build something similar into your own application or processes.

Unfortunately, that’s not always an option. A solid fallback is to record the most recently IP address of each user when they reconnect with your service. You may already be recording this for other reasons (rate limiting, load balancing, it’s a default feature of your authorization service, etc).

If needed you can then run the user recorded IP addresses through an IP to location service such as MaxMind, or FreeGeoIP which will return general location information including which US State the IP is located within.

It’s important to keep in mind that all of these services become increasingly inaccurate as the geographic specificity increases. In almost all cases they’ll identify what country a person is connecting from correctly, and in the vast majority of cases (barring VPN use or other network oddities) the state. If you’re relying upon IP state identification, it is probably a good idea to err on the side of caution and presume that you have mis-identified a few user locations if you’re on the cusp of a state notification limit.

What Should be in a Data Breach Notification?

California has the most detailed breach notification requirements in the United States, up to and including specifying the font-size that notifications should be displayed with.

Their requirements (and an excellent guideline for all communication)

  • Should be written in plain english
  • Title and Headings should be conspicuously displayed.
  • Should be titled: “Notice of Data Breach” with paragraphs covering:
    • What Happened
    • The Date of the Breach, Estimated Date or Date Range
    • What Information Was Involved
    • What We Are Doing
    • What You (the user) Can Do
    • For More Information
    • No smaller than 10pt type

In the case of California (and other states) there are further mandates based around the type of data exposed. For instance, if a social security number or a driver’s license or California identification card number is exposed then the toll free numbers and addresses of the major credit reporting agencies (listed above) need to be included in the communication.

We’ve included a copy of their form for your use below:

Download: California Model Data Breach Disclosure Form

Data Breach Notification Deadlines

It’s important to note that the timing requirements for disclosure are based around when your organization first learned of the data breach. The majority of states require that data breach notifications are sent: “Without undue delay”, most aggressively this is defined as within 30 days of discovery.

The distinction is important as there is often a significant lag between when a breach happens and when it’s discovered (many times by an outside party).

Given the tight timelines, it’s not practical to manually review all the different US State data breach notification laws.

So, please come back for Part 2 of this series where we’ll be covering each state’s laws in depth.

The post A Guide to per State Data Breach Response appeared first on Varonis Blog.

Share this post and earn Cybytes
Facebook Twitter LinkedIn Email
Follow
2690 Followers
About Varonis
Varonis is a pioneer in data security and analytics, fighting a different battle than conventional cybersecurity companies. Varonis focuses on protecting enterprise data on premises and in the cloud: sensitive files and emails; confidential customer, patient and employee data; financial records; strategic and product plans; and other intellectual property. The Varonis Data Security Platform detects insider threats and cyberattacks by analyzing data, account activity and user behavior; prevents and limits disaster by locking down sensitive and stale data; and efficiently sustains a secure state with automation. With a focus on data security, Varonis serves a variety of use cases including governance, compliance, classification, and threat analytics. Varonis started operations in 2005 and, as of December 31, 2017, had approximately 6,250 customers worldwide — comprised of industry leaders in many sectors including technology, consumer, retail, financial services, healthcare, manufacturing, energy, media, and education.
Promoted Content
The Road to HIPAA Compliance Wednesday, March 14 - 2pm EDT
Join us to hear first-hand how Rick Thompson, Network Administrator at Hugh Chatham Memorial Hospital, leverages Varonis to help meet HIPAA compliance. We'll also show you how to create an airtight HIPAA compliance program – from determining the scope of your PHI data all the way to setting alerts on non-compliant activity. You’ll learn: - How real customers use Varonis to help meet HIPAA compliance - How to identify and protect PHI - The anatomy of HIPAA (including the final omnibus rule) - A step-by-step plan for HIPAA compliance and ransomware defense

Our Revolution

We believe Cyber Security training should be free, for everyone, FOREVER. Everyone, everywhere, deserves the OPPORTUNITY to learn, begin and grow a career in this fascinating field. Therefore, Cybrary is a free community where people, companies and training come together to give everyone the ability to collaborate in an open source way that is revolutionizing the cyber security educational experience.

Cybrary On The Go

Get the Cybrary app for Android for online and offline viewing of our lessons.

Get it on Google Play
 

Support Cybrary

Donate Here to Get This Month's Donor Badge

 
Skip to toolbar

We recommend always using caution when following any link

Are you sure you want to continue?

Continue
Cancel