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

When the Absence of Noise Becomes Signal: Defensive Considerations for Lazarus FudModule

In February 2023, X-Force posted a blog entitled “Direct Kernel Object Manipulation (DKOM) Attacks on ETW Providers” that details the capabilities of a sample attributed to the Lazarus group leveraged to impair visibility of the malware’s operations. This blog will not rehash analysis of the Lazarus malware sample or Event Tracing for Windows (ETW) as that has been previously covered in the X-Force blog post. This blog will focus on highlighting the opportunities for detection of the FudModule within the…

Breaking Down a Cyberattack, One Kill Chain Step at a Time

In today’s wildly unpredictable threat landscape, the modern enterprise should be familiar with the cyber kill chain concept. A cyber kill chain describes the various stages of a cyberattack pertaining to network security. Lockheed Martin developed the cyber kill chain framework to help organizations identify and prevent cyber intrusions. The steps in a kill chain trace the typical stages of an attack from early reconnaissance to completion. Analysts use the framework to detect and prevent advanced persistent threats (APT). Organizations…

Defining the Cobalt Strike Reflective Loader

The Challenge with Using Cobalt Strike for Advanced Red Team Exercises While next-generation AI and machine-learning components of security solutions continue to enhance behavioral-based detection capabilities, at their core many still rely on signature-based detections. Cobalt Strike being a popular red team Command and Control (C2) framework used by both threat actors and red teams since its debut, continues to be heavily signatured by security solutions. To continue Cobalt Strikes operational usage in the past, we on the IBM X-Force…

What is a Red Teamer? All You Need to Know

A red teamer is a cybersecurity professional that works to help companies improve IT security frameworks by attacking and undermining those same frameworks, often without notice. The term “red teaming” is often used interchangeably with penetration testing. While the terms are similar, however, there are key distinctions. First and foremost is the lack of notice from red teams. Pen testing may be scheduled in advance to assess the ability of specific security measures to handle a simulated attack; red team…