On Jan. 10, 2019, the governor of Massachusetts finalized the legislative changes to the state data breach law by placing his signature on HB 4806. The amended law, which includes several new requirements and raises the bar for businesses collecting data on Massachusetts residents, is driving organizations to review and update their data breach notification-related policies and procedures, as well as their incident response processes.

This update can be seen as part of a wider trend in data privacy regulations where guidelines on breach reporting and incident response documentation are becoming more specific. This can be seen in Europe with the General Data Protection Regulation (GDPR) and the Network Information Security (NIS) Directive, as well as in North America with Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA), among others.

What Are the Significant Changes to Massachusetts’ Data Breach Law?

The amendment changes the timeline for reporting a breach to affected individuals, adds additional requirements for any report to the Massachusetts Office of Attorney General (AG) or the Office of Consumer Affairs and Business Regulation (OCABR), and changes the content of any notice to affected individuals. Your legal counsel and privacy experts can provide you with specific information regarding how these changes will impact your organization and what you need to do to comply.

The Importance of an Incident Response Plan

The update to the Massachusetts law highlights the importance of having a documented process around all aspects of security and risk management, as was already required under the law with the need to maintain a comprehensive written information security program (WISP). This requirement has now been updated as part of the notification process.

Findings from a recent survey conducted by the Ponemon Institute and sponsored by IBM Security showed that 77 percent of organizations surveyed do not have an enterprisewide cybersecurity incident response plan, a key part of a wider information security program. As a growing number of global privacy regulations expect more documentation and rigor around the incident response process, organizations need to focus on ensuring that their plans are up to date and appropriate to the threats they face.

You can find more information on the changes to the Massachusetts breach law here, and more findings from the recent Ponemon study here.

Helpful links and references:

Link to 93H MA Breach Law

Link to regulation 201 CMR 17.03

More from Incident Response

Tequila OS 2.0: The first forensic Linux distribution in Latin America

3 min read - Incident response teams are stretched thin, and the threats are only intensifying. But new tools are helping bridge the gap for cybersecurity pros in Latin America. IBM Security X-Force Threat Intelligence Index 2023 found that 12% of the security incidents X-force responded to were in Latin America. In comparison, 31% were in the Asia-Pacific, followed by Europe with 28%, North America with 25% and the Middle East with 4%. In the Latin American region, Brazil had 67% of incidents that…

Alert fatigue: A 911 cyber call center that never sleeps

4 min read - Imagine running a 911 call center where the switchboard is constantly lit up with incoming calls. The initial question, “What’s your emergency, please?” aims to funnel the event to the right responder for triage and assessment. Over the course of your shift, requests could range from soft-spoken “I’m having a heart attack” pleas to “Where’s my pizza?” freak-outs eating up important resources. Now add into the mix a volume of calls that burnout kicks in and important threats are missed.…

SIEM and SOAR in 2023: Key trends and new changes

4 min read - Security information and event management (SIEM) systems remain a key component of security operations centers (SOCs). Security orchestration, automation, and response (SOAR) frameworks, meanwhile, have emerged to fill the gap in these capabilities left by many SIEM systems. But as many companies have begun reaching the limits of SIEM and SOAR systems over the last few years, they have started turning to other solutions such as extended detection and response (XDR). But does this shift spell the end of SIEM…

X-Force releases detection & response framework for managed file transfer software

5 min read - How AI can help defenders scale detection guidance for enterprise software tools If we look back at mass exploitation events that shook the security industry like Log4j, Atlassian, and Microsoft Exchange when these solutions were actively being exploited by attackers, the exploits may have been associated with a different CVE, but the detection and response guidance being released by the various security vendors had many similarities (e.g., Log4shell vs. Log4j2 vs. MOVEit vs. Spring4Shell vs. Microsoft Exchange vs. ProxyShell vs.…