Compliance

201 CMR 17.00: What the Massachusetts Data Security Regulation Requires

201 CMR 17.00 explained in plain English: who it covers, what a WISP must include, the encryption and access rules, vendor oversight and how the AG enforces it.

By Boston IT Services Group · Published November 14, 2026 · Updated November 14, 2026 · 9 min read

In short

201 CMR 17.00 is the Massachusetts regulation that requires any business or person that owns or licenses personal information about a Massachusetts resident to keep a written information security program (WISP) and specific technical safeguards. It applies regardless of where the business is located. This guide explains who is covered, what counts as personal information, what the WISP and computer security sections require, and how the Attorney General enforces the rules. It is general information, not legal advice.

201 CMR 17.00 is the Massachusetts data security regulation. It requires any business that owns or licenses personal information about a Massachusetts resident to maintain a written information security program (WISP) plus a defined set of computer security controls, such as encryption on laptops and unique user IDs. It applies to a five-person bookkeeping office the same way it applies to a large employer, with the safeguards scaled to the size of the business.

This post walks through what the regulation says, section by section, and then turns it into a practical checklist. It is general information, not legal advice; confirm your specific obligations with your attorney or compliance advisor.

What 201 CMR 17.00 is and where it comes from

The regulation is issued by the Office of Consumer Affairs and Business Regulation (OCABR) under Chapter 93H, section 2 of the Massachusetts General Laws. That statute told OCABR to write rules that take into account a business's size, scope and type, its resources, how much data it stores, and the need to protect both consumer and employee information. The full text is posted on Mass.gov; the state notes that version is unofficial and the official version is published by the Massachusetts Register.

Section 17.05 set the compliance date of March 1, 2010. So this is not new. What has changed is how firms store data. In 2010 the risk was a laptop left in a cab. Today it is a phished Microsoft 365 account with ten years of client tax returns in OneDrive.

Who is covered

Section 17.01 says the regulation applies to "all persons that own or license personal information about a resident of the Commonwealth."

Two definitions make that wider than it sounds:

  • Person means a natural person, corporation, association, partnership or other legal entity. Massachusetts state agencies are excluded; private businesses and nonprofits are not.
  • Owns or licenses means receiving, storing, maintaining, processing or otherwise having access to personal information in connection with providing goods or services or in connection with employment.

That employment clause is the one owners overlook. If you have even one Massachusetts employee, you hold their Social Security number and direct deposit details. You are covered. Location does not matter either: the test is whose information you hold, not where your office is.

What counts as personal information

The definition in section 17.02 is narrower than most people expect. Personal information means a Massachusetts resident's first name and last name, or first initial and last name, combined with any one of:

Data element Examples you probably hold
Social Security number W-4s, I-9 files, tax returns, benefits enrollment
Driver's license or state-issued ID number Copies of IDs for new hires, client onboarding, notarizations
Financial account number, or credit or debit card number, that would permit access to the account Direct deposit forms, ACH authorizations, stored card numbers

Information lawfully obtained from publicly available sources, or from government records lawfully made available to the public, is excluded.

A name alone is not personal information. A name plus a bank account number on a payroll form is. Firms that do tax work, payroll, lending, medical billing or HR usually hold large volumes of it, often in email attachments and scanned PDFs nobody has looked at in years. That is why we treat 201 CMR 17.00 as a core part of IT support for accounting firms.

Massachusetts WISP requirements under section 17.03

Section 17.03 requires every covered person to develop, implement and maintain a written security program with administrative, technical and physical safeguards. It can be written "in one or more readily accessible parts," so a binder of linked policies works as well as a single document. The safeguards must also be consistent with any state or federal rules that already apply to you, such as HIPAA or the FTC Safeguards Rule.

The regulation lists the minimum Massachusetts WISP requirements. Your written information security program in Massachusetts must include:

  1. Designating one or more employees to maintain the program.
  2. Identifying and assessing reasonably foreseeable internal and external risks to paper, electronic and other records with personal information, and evaluating and improving current safeguards. This includes ongoing training for employees (including temporary and contract staff), employee compliance with policies, and ways to detect and prevent security system failures.
  3. Security policies for whether and how employees store, access and transport records with personal information outside the office.
  4. Disciplinary measures for violations.
  5. Preventing terminated employees from accessing records with personal information.
  6. Overseeing service providers, covered in its own section below.
  7. Reasonable restrictions on physical access to records, and storing records and data in locked facilities, storage areas or containers.
  8. Regular monitoring to make sure the program is working and upgrading safeguards as needed.
  9. Reviewing the scope of the security measures at least annually, or whenever there is a material change in business practices that may affect the security or integrity of the records.
  10. Documenting responsive actions taken after any incident involving a breach of security, and a mandatory post-incident review of events and actions taken, so you can change business practices that protect personal information.

Notice how much of that is people and process rather than technology. A firm can buy every security tool on the market and still fail section 17.03 because nobody is named as owner, nobody reviews the program each year, and departing employees keep access to the shared drive for a month.

Computer system security requirements under section 17.04

If you store or transmit personal information electronically, section 17.04 adds technical requirements, to the extent technically feasible. Here is each one, with what it usually means in a modern small office.

Requirement What it usually looks like in practice
Secure user authentication: control of user IDs, reasonably secure passwords or token/biometric methods, protecting stored passwords, access limited to active accounts, blocking after repeated failed logins Unique accounts, a password manager, MFA on email and remote access, account lockout policies, prompt disabling of departed users
Secure access controls limiting personal information to people who need it for their jobs, and unique IDs with passwords that are not vendor defaults Role-based folder permissions, no shared logins, changing default passwords on firewalls, printers and WiFi gear
Encryption of records with personal information sent across public networks, and of all personal information sent wirelessly Encrypted email or a secure client portal for tax returns and pay stubs, WPA2 or WPA3 on office WiFi, VPN or encrypted connections for remote access
Reasonable monitoring for unauthorized use of or access to personal information Sign-in alerts, audit logging in Microsoft 365, EDR alerts reviewed by a person
Encryption of all personal information stored on laptops or other portable devices BitLocker or FileVault on every laptop, encrypted USB drives or a ban on them, managed phones
Reasonably up-to-date firewall protection and operating system security patches for internet-connected systems holding personal information A supported firewall with current firmware, a patching schedule with reports
Reasonably up-to-date security agent software with malware protection, current patches and virus definitions, set to receive updates regularly Managed antivirus or EDR on every endpoint, with someone checking that it is actually running
Education and training on proper use of the computer security system and the importance of protecting personal information Onboarding training plus periodic phishing and security awareness sessions, with attendance recorded

On encryption, it helps to know the statutory definition. Chapter 93H, section 1 defines encrypted data as data transformed through "a 128-bit or higher algorithmic process" so there is a low probability of assigning meaning without the key. Ask your IT provider to confirm which algorithm and key length your laptop encryption uses, that it is actually turned on, and where the recovery keys are stored.

"To the extent technically feasible" is not a loophole for skipping laptop encryption in 2026. It is there for genuinely constrained systems, and if you rely on it you should write down why.

Vendor oversight: your IT provider, payroll company and cloud apps

Section 17.03 requires overseeing service providers in two ways: taking reasonable steps to select and retain providers capable of maintaining appropriate security, and requiring them by contract to implement and maintain those security measures.

A service provider is anyone who receives, stores, maintains, processes or otherwise is permitted access to personal information while providing services to you. That includes your payroll processor, your tax software vendor, your document management platform, your shredding company and your MSP. If an outside IT firm has admin access to your file server, it is a service provider under this definition.

Practically, that means:

  • Keep a list of every vendor that touches personal information.
  • Ask how each one secures it (MFA, encryption, background checks, incident notification).
  • Make sure the contract includes a security obligation. The regulation's grandfather clause for older contracts expired March 1, 2012.
  • Review the list when you add or drop a vendor.

When you evaluate an IT provider, ask how they protect their own remote access tools and admin accounts. We cover that in how to choose a managed service provider.

How the Attorney General enforces it

The Attorney General enforces Chapter 93H and the regulation. Section 6 of Chapter 93H lets the Attorney General bring an action under section 4 of Chapter 93A, the state consumer protection law. Section 4 of Chapter 93A allows a court to issue injunctions, order restitution, and impose a civil penalty of up to $5,000 for each violation when the person knew or should have known the conduct was unlawful. The court can also require the defendant to pay reasonable costs of investigation and litigation, including attorneys' fees.

The WISP also comes up at the worst possible time. Under the breach notification law, the notice you file with the Attorney General and OCABR must state whether you maintain a written information security program and whether you have updated it. The OCABR breach guidance says organizations that experience a breach must report whether they have a WISP. Answering "no" on that form is not a position anyone wants to be in.

A practical 201 CMR 17 compliance checklist

OCABR publishes its own 201 CMR 17.00 compliance checklist in question form, and it is worth reading in full. It also asks whether you limit how much personal information you collect, how long you keep it, and who can see it. Here is the order we would tackle things in for a small firm:

  1. Name the person responsible for the program. Put it in writing.
  2. Find the data. List every place personal information lives: file shares, email, OneDrive and SharePoint, practice management software, paper files, scanners, backups, former employees' mailboxes.
  3. Delete what you do not need. The less you hold, the less you protect and the less you report.
  4. Encrypt every laptop and portable device, and confirm it with a report rather than an assumption.
  5. Turn on MFA for email, remote access and admin accounts.
  6. Lock down permissions so only the people who need personal information can open it.
  7. Set up patching and endpoint protection with monitoring, and keep the reports.
  8. Write the offboarding checklist and use it every time someone leaves.
  9. List your vendors and check their contracts for security language.
  10. Train staff, and record who attended.
  11. Write the WISP itself, tying each section to what you actually do.
  12. Put the annual review on the calendar, and document each one.

Most of steps 4 through 8 are routine work for a managed provider. Our cybersecurity services for Boston businesses cover the technical controls, and firms outside the city can start from our managed IT services Massachusetts page. If you already have a WISP template from a few years ago, the most useful next step is comparing it line by line against what your systems actually do today, then fixing whichever side is wrong.

Frequently asked questions

Who has to comply with 201 CMR 17.00?

The regulation applies to every person that owns or licenses personal information about a Massachusetts resident. Person includes corporations, partnerships and other legal entities, but not state agencies. Owns or licenses is defined broadly: receiving, storing, maintaining, processing or otherwise having access to personal information in connection with goods, services or employment. A business outside Massachusetts with Massachusetts employees or customers can be covered.

What counts as personal information under 201 CMR 17.00?

Personal information is a Massachusetts resident's first and last name, or first initial and last name, combined with a Social Security number, a driver's license or state ID number, or a financial account or credit or debit card number that would permit access to the account. Information lawfully obtained from public sources or public government records is excluded.

Does 201 CMR 17.00 require encryption?

Yes, to the extent technically feasible. Section 17.04 requires encrypting records and files containing personal information that travel across public networks, all personal information transmitted wirelessly, and all personal information stored on laptops or other portable devices. In practice that means full-disk encryption on laptops, encrypted email or secure file transfer for sensitive documents, and encrypted WiFi.

How often does a WISP need to be reviewed?

Section 17.03 requires reviewing the scope of your security measures at least annually, and also whenever there is a material change in business practices that could affect the security or integrity of records containing personal information. Examples include moving to a new cloud system, opening a new office, or changing payroll providers. Keep a dated record of each review.

What are the penalties for violating 201 CMR 17.00?

Chapter 93H, section 6 lets the Attorney General bring an action under section 4 of Chapter 93A, the consumer protection law. Section 4 allows a court to order a civil penalty of up to $5,000 for each violation when the person knew or should have known it was unlawful, plus reasonable costs of investigation and litigation, including attorneys' fees, as well as injunctions and restitution.

Sources and references

  1. Mass.gov (OCABR): 201 CMR 17.00, Standards for the Protection of Personal Information of MA Residents
  2. Mass.gov (OCABR): 201 CMR 17.00 Compliance Checklist
  3. Mass.gov (OCABR): Requirements for Data Breach Notifications
  4. Mass.gov (Attorney General): Obligations under the Data Security Regulations and Breach Notification Law
  5. Massachusetts General Laws c. 93H, section 2 (regulations to safeguard personal information)
  6. Massachusetts General Laws c. 93H, section 1 (definitions, including encrypted)
  7. Massachusetts General Laws c. 93H, section 6 (enforcement)
  8. Massachusetts General Laws c. 93A, section 4 (actions by the Attorney General)
  9. Massachusetts General Laws c. 93H, section 3 (duty to report breaches)

Talk to a Boston IT engineer

Tell us what is slowing your team down. We will review your current setup and send back a plain-English plan with priorities, at no cost.