Showing posts with label Massachusetts data security regulations. Show all posts
Showing posts with label Massachusetts data security regulations. Show all posts

Friday, June 25, 2010

July 13 Data Security Workshop - FREE

On July 13, Mintz Levin will be joined by Sophos, Six Weight Consulting, and MFA Cornerstone Consulting to hold a free compliance workshop focused on both the gaps and overlap of Massachusetts’ data protection regulation 201 CMR 17.oo and the recent updates to federal health and medical data privacy found in the HITECH Act. We'll have an interactive hands-on workshop that will help you to address some critical questions within your organization:
  • What are my organization and business partner’s obligations?
  • What kind of information do I need to protect and how do identify it?
  • Is data encryption necessary?
  • What is a WISP?
  • What is a data breach and what is my responsibility and liability if I have one?

    For information or to register to attend the event, which will be hosted by Mintz Levin in our downtown Boston office, please click this link: http://tinyurl.com/35pk3yr

Tuesday, March 23, 2010

Massachusetts Data Security Compliance Workshop

In case your data security compliance plan is stuck in neutral, you have questions, or you haven't started yet...there will be a free (!) breakfast hands-on workshop on Thursday in Tewksbury, MA.

"Massachusetts Data Protection Law: Demystifying the Details" is being sponsored by the Merrimack Valley Venture Forum. The Merrimack Valley Venture Forum has assembled a panel of legal, technology, and process experts to break down the law and give you a clear path to compliance through a hands-on workshop. Panelists include: Cynthia Larose, Mintz Levin, Matt Pettine, MFA Cornerstone Consulting, Nagraj Seshadri, Sophos, and Mike Spinney, SixWeight. Registration through Wednesday afternoon at 5:00 pm at sferrara@mvvf.org.

Bring your questions!

Monday, March 1, 2010

Today is the day......

After implementation delays and rule changes, new data protection regulations that are widely considered the most stringent in the nation take effect today. The Massachusetts data security regulations require institutions that hold personal data on Massachusetts citizens to encrypt that information and implement written data protection policies, reports the Boston Globe.

Discussion continues and questions abound. Will this set the bar nationwide as the articulation of what constitutes "reasonable security" for personal information? How should companies handle the varying risk of harm standards when dealing with state laws and federal law, such as the HITECH Act?

Friday, February 26, 2010

Top 3 questions relating to compliance with 201 CMR 17.00

At the beginning of the "countdown" to the March 1st effective date of 201 CMR 17.00, we offered some posts with "misapprehensions" and compliance suggestions (see
16 Days to March 1..... and Countdown to compliance with 201 CMR 17.00.....11 days). Here are some questions that have been reoccurring over the last few weeks:

1) What should I be doing about the requirement relating to third party service providers and how does my company get "assurances" that those service providers (like payroll and benefits) are in compliance?

The answer to this will depend upon the kind of access and extent of information that the vendors have. Some companies have created extensive 3rd party/ vendor PI due diligence forms and processes. In the end, all your vendors should provide their own attestation that they are capable of meeting the requirements of 201 CMR 17.00 as part of the vendor review process, and it should be part of the contract. Depending on the situation, targeted risk assessments of vendors may be appropriate, as well as detailed security exhibits attached to contractual agreements. With existing service providers, if the contract is in place by Monday, you will have two years to amend it....but you should be addressing the security safeguard issues now.

2) What about faxes? How can I encrypt those, and is that required under 201 CMR 17,04?

A rather complex answer, but if the fax machine is using the Plain Old Telephone System (POTS to telecom engineers) this is not a "Public Transport" as used in 17.04(3). POTS is a private, switched, 2 party connection. The fax transmission in this case is simply not traveling over a public connection....and does not need to be encrypted nor would the fax machine require an encryption key technology. There are many other concerns with the "process" of sending and receiving faxes, most of these fall under logical or physical access controls, that are required elsewhere in 201 CMR 17.00. One thought of caution, is that there are many FAX systems that are NOT, 100% based on POTS or based on private switched network technology. If your business uses eFax or some other Internet-based form of transmission, that may be going to a traditional fax machine -- it’s POTS to me, but an email to you that is traveling over the public network. If you have a concern about the security of PI in a process, then you most likely have something which needs to be locked down and controlled.

3) We have a good handle on the computer system security requirements and the technical issues, including the whole portable device issue, but what about all that paper?

Start with the basics - do you really need to have the PI in paper format, and do you need as much as you have? If you don't have it, you can't lose it. Keep track of what is in the file, so missing items will be noticed, and to enable you to comply with data breach notification obligations if the worst happens. Simple things like: use color-coding and labels to indicate the sensitivity of the file; consider whether the original or a copy can be taken, if a copy, track the number of copies and stamp them; physically attaching documents to a folder makes copying/losing items more difficult. Use log-in/out records for the files. Remind employees to keep the records in sight or in a safe location when out of sight - use a briefcase lock if there is one, keep files in the trunk of the car and not on the car seat. The most important step is to make sure the plan is followed and to TRAIN EMPLOYEES. Companies can craft great policies and procedures to handle PI and comply with 201 CMR 17.00. But if employees and third parties are not educated and trained in these policies then compliance with the law is highly unlikely! Training, training, training. Security awareness is a big key to avoiding the unfortunate data breach.


And, it's Friday, February 26th......

And that means today is the last business day before the new Massachusetts data security regulations go live-- as Jim Cramer would say, "That's 201 CMR 17.00 for all you home gamers."

Monday, February 22, 2010

T Minus 10,080 Minutes and Counting.....

We have just one week to go before all entities that own, store, license -- or basically do anything with -- personal information of Massachusetts residents must comply with the Commonwealth's new data security regulations. Things to consider:
  • Have you done your risk assessment? Looked at what you collect and how you collect and how it is transmitted through and outside your organization?
  • Have you reached out to service providers that may have access to PI of your employees/customers?
  • Is your written information security plan in place, or at least have you started pulling together the various policies and processes ("P&P") that would make up a "written information security plan"? Is the plan tailored to your actual P&P and, thus an accurate representation of what your business really does (and not a template with [insert company name here])?
  • Have you thought about employee security awareness training?

Wednesday, February 17, 2010

Countdown to compliance with 201 CMR 17.00.....11 days

As we approach the 10 day mark to the March 1 effective date of the Massachusetts data security regulations, 201 CMR 17.00, we thought that we would share another misapprehension in the ever-growing list.

"I ordered one of those $99 "Compliance Kits" from the Internet, and they say that they will "certify" that I am compliant. I should be all set."

You might be -- but then again, we are not sure that we would bet the company on it. First, if any packaged template provider or consultant promises to issue a "certification" of your company's compliance with 201 CMR 17.00, run the other way. There are no standards that would form the basis for any such "certification" and neither the Attorney General nor the Office of Consumer Affairs and Business Regulation have authorized any such "certifications."

The Attorney General's office has been clear in various outreach programs across the state -- any company that chooses anything less than "strict compliance" with the very specific requirements of the written information security and control requirements in the Standards will need to be able to legally support their decision based on the risk elements in the Standards. In other words, did you do something more than insert your company's name in the pre-fab "policy" that you purchased?

The Massachusetts Standards take a hybrid approach to privacy/security requirements and require specific controls mandated through a general risk-based framework. Without a legal analysis to interpret and apply the risk-based factors to your particular business and business processes, companies run a serious risk with "one size fits all" templates.

The main question on March 1 should be: "If the worst happens, how comfortable are we defending our legal position to the Attorney General's office concerning our information security program and security controls under the law?" And where will the provider of that $99 template or "certification" be by that time?

Thursday, February 11, 2010

16 Days to March 1.....

Just in case you missed it, March 1 is the deadline for compliance with 201 CMR 17.00, the new Massachusetts data security regulations, and we published a client alert last week as a "reminder"... Privacy and Security Alert.

In addition to the top five "misapprehensions" about the applicability of the new regulations that we included in the Privacy and Security Alert, here are a couple of others:

"We are a [law][dental][medical] practice and have [patient][client] confidentiality obligations. The regulations do not apply to our activities."

Patient/client confidentiality obligations are separate and apart from the requirements of 201 CMR 17.00. The Data Security Regulations apply to any entity "in commerce" that owns, stores, licenses or maintains the personal information of Massachusetts residents. It is highly likely in the course of a medical practice that the practice would have at least patient name, address and social security number. Also, because a health insurance number entitles one to obtain benefits and could impose a financial burden on the individual in the wrong hands, such account number could also be "PI". Lawyers with trusts and estates practices, immigration practices and employment practices will certainly have some amount of PI in their files. Lawyers may have PI that is obtained in the course of conducting transactions (real estate closings, private placements, etc.), on certain tax forms to make payments, or on other types of transactional documents. All of these would come under the Data Security Regulations and a Plan must be developed for administrative, physical and technical safeguarding of the PI.

"We only have 5 employees. Isn't there an exemption for small companies?"
There is no "small company exemption" under the Data Security Regulations. If you are "in commerce," the requirements of 201 CMR 17.00 to safeguard PI apply to you. However, the Data Security Regulations also state that your Plan for safeguarding such PI may be commensurate with the size and resources of your business and the scope of the PI. If you do not have any PI other than that of your employees, and all of that is under lock and key in a single file cabinet, then your Plan can state exactly that. But, you must have a Plan.

Monday, February 1, 2010

27 days and counting...

March 1st is the deadline for compliance with the Massachusetts data security regulations, 201 CMR 17.00. We have blogged incessantly for months about the need to get compliance programs into gear and develop information security plans as required by the regulations. The time is here.

If you are one of the procrastinators (and, you are not alone), the basic information and the regulations can be found at the Office of Consumer and Business Affairs Regulation website. If you are larger than a mom-and-pop shop, however, you rely on the template information security plan at some considerable risk.

Over the next week or so, we will be blogging with preparedness tips, so come back often.

Thursday, January 28, 2010

Data Privacy Day -- Tip #4 -- Transactional Best Practices for Lawyers

Written by Michael Arnold and Jennifer Rubin

Even though lawyers working on both sides of an M&A transaction during the due diligence phase might immerse themselves in a “confidentiality bubble”, they still must be careful not to disclose or access confidential employee information in the course of that transaction. Attorneys evaluating potential transactions might be tempted to access information regarding target employees, such as personnel files, compensation information, and information concerning performance evaluation and other historical employment information. Transactional attorneys are often surprised to learn that dissemination of some of this information, even among those subject to a confidentiality agreement, may violate an employee’s privacy rights and even violate the law.

Some states preclude employers from disclosing employee personnel information or from revealing information regarding employee compensation altogether while other states require a waiver from the employee as a condition to dissemination to any third parties. Federal and many states laws make it illegal for companies to disclose employee medical records without authorization, and this is particularly a concern where those records include personal health information and may implicate newly-expanded HIPAA regulations. Personnel files of employees that are Massachusetts residents will contain "personal information" that can only be transmitted in compliance with the Massachusetts regulations. In the cross-border M&A context, "personal data" of employees can only be transferred to the U.S. (or to U.S. persons) in compliance with applicable data protection laws in their country of residence/employment -- and in most cases can only be with the employee's consent. Even documents in a digital "data room" that can be accessed from the U.S. may fall afoul of data protection laws in other countries.

Companies must ensure that they have the proper mechanisms in place to minimize the exposure of personnel information during a contemplated transaction, including having a good understanding as to what legally may and may not be provided to potential acquirers, and securing any necessary waivers from employees prior to turning that information over in the due diligence process.

And finally, storage and disposal of due diligence files containing personal information or protected health information must be handled in accordance with applicable state and federal laws. If you don't keep it, you can't lose it!

Happy Data Privacy Day! Tip #1

Today is worldwide Data Privacy Day. What is your company doing to promote data privacy and security in your enterprise? I'll be participating in a KnowledgeNet in Boston, sponsored by the International Association of Privacy Professionals. The discussion topic is Privacy Awareness and Training.

And don’t forget, the March 1 deadline for compliance with the sweeping Massachusetts data security regulations is fast approaching. Click here for complete information and FAQs. We'll be posting additional tips through the day in honor of Data Privacy Day 2010.

Thursday, November 12, 2009

Massachusetts Attorney General proposes privacy regulations to apply to her office

Written by Cynthia and Elissa

An oft-cited criticism of the Massachusetts data security regulations (201 CMR 17.00), effective March 1, 2010, is that the regulations specifically do not apply to government entities -- the only reason being that the Office of Consumer Affairs and Business Regulation does not have the authority or jurisdiction to enact regulations over governmental entities in Massachusetts.

One agency is seeking to correct that. The Massachusetts Office of the Attorney General has released draft privacy regulations to apply to the AG’s office, effective December 31, 2009. The regulations mirror the obligations imposed upon private business by 201 CMR 17.00.

This post would not be complete if we did not also take note of the fact that Attorney General Martha Coakley is a candidate for the U.S. Senate seat left vacant by the death of Senator Edward Kennedy.

Thursday, September 17, 2009

From Privacy Academy - The Seven Step Program

Sounds like common sense, but it is food for thought -- and will be required under new Massachusetts data security regulations:

The seven easy ways to protect PC based information from theft

The proliferation of Personal Storage Devices (thumb drives, iPods, USB external hard disks, etc.) and simple remote access has created unprecedented levels of convenience and at the same time a substantially increased risk of data loss. Pocket sized external USB storage devices can put hundreds of Gigabytes of data storage at your fingertips which is easily enough space to house an industrial-strength database or thousands of documents, spreadsheets, photos and other sensitive information. With the right software installed, these devices can be configured to automatically transfer data off any machine into which they’re plugged. This can be a convenience for the owner of the data, or for the Bad Guy an easy way to potentially access and steal your data. Exploiting this type of threat is very inexpensive and does not take expertise.

Securing your environment is very easy and involves a multi-tiered Best Practices approach including:
  • Creating and enforcing sound policies and procedures that lock down the system BIOS on all computers processing, storing or transmitting data.
  • Creating a logon requirement that uses password and / or biometric authentication every time the PC is turned on.
  • Requiring the use of strong passwords that contain a minimum 7 character combination of both alpha and numeric symbols.
  • Never sharing or writing down your passwords.
  • Automated forced changing of passwords every 60 days.
  • Locking the PC after 10 minutes of inactivity to prevent unauthorized access to the machine and its data when the user steps away.
  • Turning off the PC when it is unattended for long periods of time. This one is an often overlooked critical step. If it’s on it can be accessed remotely.

Friday, August 21, 2009

Changes to the Massachusetts Data Security Regulations: What do they really mean?

Now that the dust has settled after this week’s “Breaking News” regarding the proposed changes to the Massachusetts data security regulations, here is an analysis of what the changes actually mean to the business community.

Some other interesting commentary is linked below:

Evan Schuman - Storefront Backtalk

Monday, August 17, 2009

BREAKING NEWS - Changes to 201 CMR 17.00

Just released - proposed amendments to the Massachusetts data security regulations -- and a three-month extension of time to comply. Stay tuned for a full analysis.

Friday, August 14, 2009

To Encrypt or Not To Encrypt…….An Incentive Rather than a Mandate From Michigan

Add Michigan to the list of states that are proposing that adoption of comprehensive data security safeguards will provide a safe harbor for data breaches.

The Information Security Program Standards Act introduced last week differs a bit from Massachusetts and Nevada (and other pending legislation) in that it would not require the implementation of detailed security measures --- the Michigan act provides a carrot to those who do: Breach liability immunity.

Friday, August 7, 2009

Massachusetts Data Security Standards vs. New HIPAA Guidelines

Here's a link to an article (by the author of this blog...) comparing the Massachusetts data security standards (effective January 1, 2010) to the Department of Health & Human Services Guidelines promulgated under the new HITECH Act (effective in mid-September).   Compliance challenges are coming on all fronts -- and it's best not to duplicate efforts.