Welcome Guest. | Log In | Register | Membership Benefits


Topics:   Security Views : Compliance Tech Center

Breach Notification: Know The Rules

State and federal laws require notification when a breach of protected information occurs. You need to know which laws apply and how to comply

Jan 20, 2012 | 06:23 PM | 

By Richard E. Mackey, Jr.
Dark Reading

The vast majority of states and territories in the United States have rules requiring organizations managing personal information to notify affected parties if their private information has been breached.

However, the laws differ from state to state in the way they define personal information, the requirements for who needs to be notified, and how notification must take place. Add to this the fact that federal laws also require breach notification, and we see that organizations caring for personal identifying data have their work cut out for them in understanding which rules apply and how they can ensure they’ll comply in the event of a breach.

Which Rules Apply?
The key point to remember when determining which laws apply to your organization is that state laws are written to protect the residents of a state. This means you need to comply with the state laws applying to the people whose data you manage. In other words, if you have customers or employees from Massachusetts, then even though your business is located in New Hampshire, you need to comply with the Massachusetts data protection and breach notification laws.

If it seems like it a difficult task to understand and comply with upward of 50 different state and territorial laws, you get the message. It should also be clear why every year the U.S. Congress attempts to define federal data protection laws that would supersede these state laws. For better or worse, efforts at the national level have not succeeded, and we are left with the laws of the various states (in addition to the federal laws applying to financial and health information).

State breach notification laws have more in common than not. For example, these laws define personal information as a person’s first and last name, or first initial and last name, together with one or more other pieces of sensitive information. The obvious ones are Social Security number, driver’s license number, and credit card numbers. One area where differences tend to occur is banking information. For example, Massachusetts considers a bank account number (again, with a name) a piece of personal identifying information, even if there is no PIN or password that would allow a perpetrator to use the account. California, on the other hand, requires the presence of a PIN or password to make the account number a piece of protected data.

The first step in ensuring compliance with breach notification laws is knowing whose data you have. That means keeping accurate records of whose data you store, where they live, and where the data resides. Once you understand that, you can identify the laws that apply. Next, you can identify the particular pieces of information that you need to protect and understand the kind of breaches that would require you to notify the victims as well as state authorities.

In the next posting, I’ll talk about what constitutes a breach (and what doesn’t) and the mechanics of notification.

Richard Mackey is vice president of consulting at SystemExperts Corp.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Compliance Reports

report How To Boost Security Via FFIEC Compliance
With just a smartphone, users can conduct nearly all their banking business at any time of the day or night. However, all this flexibility and convenience opens up new avenues for fraud and cybercrime. Guidelines laid out by the FFIEC several years ago predate many of the capabilities-and vulnerabilities-that are in place today. In this report, we examine the latest guidelines and provide advice on how you can extend the work done to comply with FFIEC guidelines to strengthen your organization's overall security posture and keep customers and their data safe.

report Keeping Compliance In Check
Configuration mistakes, access control gaffes, poor documentation--it doesn?t take much for a compliance audit to go all wrong. In this special retrospective of recent news coverage, Dark Reading takes a look at the costs, common missteps and best practices for compliance, as well as the day the Internet nearly went dark due to the threat of new regulations.

report FISMA Lifts All Compliance Boats
FISMA may not be on your radar now, but it likely will be at some point. Geared specifically toward the federal government and its affiliate agencies and third parties, FISMA is a very specific set of requirements aimed at establishing and maintaining at least a baseline level of computer and network security. FISMA requires unique categorization and classification of information assets, not to mention a boatload of documentation to prove compliance. But once your organization achieves FISMA compliance, it will likely be compliant with just about every security mandate out there.

Other reports from the Compliance Tech Center:

Related Content

Log Management in 2012 and Beyond
2012 brings interesting changes to the log management world. Now, more than ever, it is critical to understand the impact to your log infrastructure and the solutions that will better prepare you to manage your security posture.

SANS Log Management Survey Report
Organizations are increasingly dependent on log management to support core business functions, including cost management, service level and line-of-business application monitoring, as well as traditional IT- and security-focused activities.

Cut the Time and Effort of Troubleshooting and Reporting
Organizations generate millions of logs a day and struggle with centralized collection, storage and analysis of those logs. ArcSight Logger is a universal log management solution that unifies searching, reporting, alerting and analysis across any type of IT data. It consolidates silos of logs into a single indexed repository for fast detection and mitigation of operational issues.

Get Turnkey and Automated PCI Compliance
PCI compliance monitoring is seamless with the self-contained ArcSight PCI Logger solution for log collection, storage and analysis. No database administration expertise is required and a web-based interface simplifies deployment and ongoing management.

Swiss Bank Meets Compliance Requirements and Protects Customer Data
Due to long-term data retention requirements, Swiss bank EFG needed a cost-effective way to collect, secure and store audit-quality log data in an easily accessible log repository. ArcSight Logger helps EFG meet key requirements of Switzerland?s banking laws fast and cost-effectively.




Featured Webcasts
Featured Whitepapers
Featured Reports