201 CMR 17.00 is the Massachusetts regulation that made the written information security plan a legal requirement for almost every business in the United States that holds a Massachusetts resident’s data — years before the FTC Safeguards Rule required one of financial institutions.
Issued by the Office of Consumer Affairs and Business Regulation under M.G.L. c. 93H and in force since 1 March 2010, it applies to all persons that own or license personal information about a resident of the Commonwealth, wherever the business is located, and requires them to develop, implement and maintain a comprehensive information security program that is written, contains administrative, technical and physical safeguards, and includes ten specified elements in section 17.03 — from designating an employee to run it, through risk assessment, employee policies, discipline, terminated-employee access, service-provider contracts, physical access, monitoring and annual review, to documenting incident response.
For electronic records it adds the eight computer system security requirements of section 17.04, including encryption of personal information transmitted over public networks or wirelessly and stored on laptops and portable devices. This guide sets out who 201 CMR 17.00 binds and what “personal information” means, the ten WISP elements of 17.03, the eight technical requirements of 17.04, how the regulation lines up with the FTC Safeguards Rule so that one plan satisfies both, and how it is enforced.

Free gap assessment
Where do you actually stand against ISO 27001?
Score every management system clause and all 93 Annex A controls, free, and get a prioritised gap list back.
Run the free ISO 27001 gap assessment → or View premium report sample
201 CMR 17.00 in 2026: key dates and what has changed
The regulation itself has been stable for a long time. The version Mass.gov publishes is still the text dated 13 November 2009, and its compliance deadline passed in 2010. What has moved since is everything around it: the breach-notice statute it sits under, the size of the settlements the Attorney General negotiates, and a comprehensive privacy bill that is still in conference.
| Date | Event | What it means for your WISP |
|---|---|---|
| 1 March 2010 | Compliance deadline in 17.05: every person who owns or licenses personal information about a resident must be in full compliance on or before this date | There is no phase-in left. A business that starts holding Massachusetts data today is covered from day one |
| 1 March 2012 | End of the grandfather clause in 17.03(2)(f)2: vendor contracts signed no later than 1 March 2010 were deemed compliant until this date even without a security clause | Every service provider contract now needs a clause requiring the vendor to maintain appropriate security measures |
| 10 April 2019 | Chapter 444 of the Acts of 2018 amends the breach law, M.G.L. c. 93H, as the Office of Consumer Affairs and Business Regulation (OCABR) records it | The breach notice to the Attorney General and OCABR must say whether you maintain a WISP and whether you have updated it; SSN breaches trigger 18 months of free credit monitoring |
| 19 August 2025 | The Attorney General announces a $795,000 settlement, pending court approval, with Peabody Properties for 201 CMR 17.00 and c. 93H failures | The largest recent signal of what the AG expects: MFA, phishing protection, an asset inventory, vulnerability management and timely notice |
| September 2025 to 2026 | The Senate (S.2619, September 2025) and the House (4 June 2026) pass different versions of a Massachusetts Data Privacy Act; a conference committee has been reconciling them since June 2026 | Not law at our last check (8 November 2026). It would add consumer privacy rights; it does not repeal the 201 CMR 17.00 security duty |
Two things that are often assumed and are not true: there is no 201 CMR 17.00 certification, audit scheme or registration, and there is no small-business exemption. Compliance is self-assessed and tested by the Attorney General after something goes wrong, usually a breach notice.
Who 201 CMR 17.00 applies to
| Term (17.02) | Definition | Consequence |
|---|---|---|
| Person | A natural person, corporation, association, partnership or other legal entity, other than a Commonwealth agency or political subdivision | Every private business, non-profit and professional practice, in any state |
| Owns or licenses | Receives, stores, maintains, processes, or otherwise has access to personal information in connection with the provision of goods or services or in connection with employment | Employers with Massachusetts employees are covered; so are service providers |
| Personal information | A Massachusetts resident’s first name and last name, or first initial and last name, in combination with a Social Security number, a driver’s license or state-issued ID number, or a financial account number or credit or debit card number (with or without codes) that would permit access to the account — excluding information lawfully obtained from public records | Payroll, HR files, customer payment records and tax data all qualify |
| Service provider | Any person that receives, stores, maintains, processes or is otherwise permitted access to personal information through its provision of services directly to a covered person | Vendors are pulled in by contract under 17.03(2)(f) |
| Breach of security | Unauthorized acquisition or use of unencrypted data, or of encrypted data together with the key, that creates a substantial risk of identity theft or fraud; good-faith acquisition for a lawful purpose is excluded unless the information is misused | The definition the incident-response element of 17.03 is written for |
Section 17.03(1) scales the program to the size, scope and type of business, the resources available, the amount of stored data and the need for security of consumer and employee information — but it does not exempt anyone. A sole practitioner with one Massachusetts client is covered. Our guide to the written information security plan covers the federal ten elements the Massachusetts ten are so often confused with.
The ten WISP elements of 201 CMR 17.03
| Element | 17.03(2) requirement | What it looks like |
|---|---|---|
| (a) | Designating one or more employees to maintain the comprehensive information security program | A named data security coordinator — the Massachusetts counterpart of the federal Qualified Individual |
| (b) | Identifying and assessing reasonably foreseeable internal and external risks to the security, confidentiality and/or integrity of records containing personal information, and evaluating and improving safeguards, including ongoing employee training, employee compliance and means for detecting and preventing security system failures | A written risk assessment reviewed with training and compliance records |
| (c) | Security policies for employees on the storage, access and transportation of records containing personal information outside business premises | Remote work, laptop and paper-file rules |
| (d) | Disciplinary measures for violations of the program rules | A sanctions clause in the policy and the employee handbook |
| (e) | Preventing terminated employees from accessing records containing personal information | Same-day deprovisioning and physical access removal |
| (f) | Overseeing service providers: reasonable steps to select and retain providers capable of maintaining appropriate security measures, and requiring them by contract to implement and maintain such measures | Vendor due diligence and a contractual security clause |
| (g) | Reasonable restrictions on physical access to records, and storage in locked facilities, storage areas or containers | Locked cabinets, restricted rooms, clean desk |
| (h) | Regular monitoring to ensure the program operates as intended, and upgrading safeguards as necessary to limit risks | Log review, spot checks, a monitoring record |
| (i) | Reviewing the scope of the security measures at least annually or whenever there is a material change in business practices that may implicate the security or integrity of records | A dated annual review |
| (j) | Documenting responsive actions taken in connection with any incident involving a breach of security, and mandatory post-incident review of events and actions taken to make changes in business practices | An incident log and a lessons-learned record |
The eight computer system security requirements of 201 CMR 17.04
| Requirement | 17.04 text (condensed) | Practical control |
|---|---|---|
| (1) Secure user authentication | Control of user IDs; a reasonably secure method of assigning and selecting passwords or unique identifier technologies such as biometrics or tokens; secure storage of passwords; access restricted to active users and accounts; lockout after multiple failed attempts | Password policy, MFA, account lockout, no shared or dormant accounts |
| (2) Secure access control | Access to personal information restricted to those who need it for their job duties; unique IDs plus passwords that are not vendor-supplied defaults | Role-based access; default credentials changed |
| (3) Encryption in transit | Encryption of all transmitted records and files containing personal information that travel across public networks, and of all such data transmitted wirelessly | TLS, encrypted email or portals, WPA-secured wireless |
| (4) Monitoring | Reasonable monitoring of systems for unauthorized use of or access to personal information | Logging and review |
| (5) Encryption on portable devices | Encryption of all personal information stored on laptops or other portable devices | Full-disk encryption on laptops, phones, USB media |
| (6) Firewall and patches | Reasonably up-to-date firewall protection and operating system security patches for systems connected to the Internet | Managed firewall; patch cycle |
| (7) Malware protection | Reasonably up-to-date system security agent software with malware protection and current patches and virus definitions, set to receive updates regularly | Endpoint protection with automatic updates |
| (8) Training | Education and training of employees on the proper use of the computer security system and the importance of personal information security | Onboarding and annual training records |
All eight apply “to the extent technically feasible” — a qualification that excuses genuinely infeasible measures, not inconvenient ones, and that the Attorney General reads narrowly for encryption.
The 201 CMR 17.00 compliance checklist, mapped to evidence
OCABR publishes a 201 CMR 17.00 compliance checklist for small businesses, written as yes/no questions. OCABR is clear that the checklist is not a substitute for compliance; it is an aid to building the program. The table below groups its questions, names the section each one tests, and lists the record that answers it if the Attorney General ever asks.
| Checklist question (condensed) | Section | Evidence that answers it |
|---|---|---|
| Is there a written, comprehensive program covering all records with personal information, with administrative, technical and physical safeguards? | 17.03(1) | The WISP document itself, dated and approved |
| Is one or more employees designated to maintain and supervise it? | 17.03(2)(a) | A named coordinator in the WISP and a role description |
| Have you identified the paper, electronic and other records, systems and storage media, including laptops and portable devices, that hold personal information (or chosen to treat all records as if they do)? | Checklist item supporting 17.03(2)(b) | A data and asset inventory, or a written decision to treat everything as covered |
| Have you identified foreseeable internal and external risks and evaluated current safeguards? | 17.03(2)(b) | A dated risk assessment with owners and actions |
| Is there ongoing training and monitoring of employee compliance? | 17.03(2)(b)1-2 | Training records and spot-check notes |
| Are there disciplinary measures for violations? | 17.03(2)(d) | A sanctions clause in the policy and handbook |
| Are there rules for keeping, accessing and transporting records off premises? | 17.03(2)(c) | A remote-work and portable-media policy |
| Is a terminated employee’s physical and electronic access blocked immediately, including passwords and user names? | 17.03(2)(e) | A leaver checklist with dates and sign-off |
| Do you select capable service providers and require security by contract? | 17.03(2)(f) | Vendor due-diligence notes and the contract clause |
| Is collection limited to what the business reasonably needs, and storage time limited to what it needs? | Checklist only (good practice) | A retention schedule and a data-collection review |
| Is access limited to people with a need to know? | 17.04(2) | An access matrix and periodic access review |
| Is physical access restricted and are records kept in locked facilities or containers? | 17.03(2)(g) | Locked storage, visitor and key controls |
| Is the program monitored and upgraded as needed? | 17.03(2)(h) | A monitoring log and change record |
| Is the scope reviewed at least annually or on a material change? | 17.03(2)(i) | Signed annual review minutes |
| Are breach responses documented with a post-incident review? | 17.03(2)(j) | An incident log and lessons-learned record |
| For electronic records: secure authentication, access control, encryption in transit and on portable devices, monitoring, firewall and patches, malware protection, training | 17.04(1)-(8) | The technical controls checklist below, with screenshots or configuration exports |
The collection-limits and retention questions are worth noticing. They go beyond the lettered elements of 17.03(2), but OCABR asks them, and a short retention schedule is the cheapest way to shrink what a breach can expose.
201 CMR 17.00 and the FTC Safeguards Rule: one plan for both
| Topic | 201 CMR 17.00 | 16 CFR Part 314 (FTC Safeguards Rule) | One plan covers both by |
|---|---|---|---|
| Who | Anyone holding a Massachusetts resident’s personal information | Financial institutions under FTC jurisdiction, including tax preparers, mortgage brokers, dealers, collection agencies | A financial institution with Massachusetts clients or employees needs both; a non-financial business needs only the state rule |
| Coordinator | One or more designated employees (17.03(2)(a)) | A Qualified Individual, who may be a service provider (314.4(a)) | Naming the Qualified Individual as the 17.03 designee |
| Risk assessment | Required, with training and compliance evaluation (17.03(2)(b)) | Written risk assessment with specified criteria (314.4(b)); writing exempt below 5,000 consumers | One written assessment covering both |
| Technical safeguards | Eight specified in 17.04, including encryption in transit and on portable devices | Access controls, inventory, encryption at rest and in transit, MFA, secure development, disposal, change management, monitoring (314.4(c)) | The federal list is broader; the state list is more specific on portable-device encryption |
| Service providers | Select and retain capable providers; contract for safeguards (17.03(2)(f)) | Select, contract and periodically assess (314.4(f)) | One vendor procedure with periodic assessment |
| Testing | Regular monitoring (17.03(2)(h)) | Continuous monitoring or annual penetration testing and six-monthly vulnerability assessments (314.4(d)) | The federal testing regime satisfies the state monitoring requirement |
| Incident response | Document responsive actions and post-incident review (17.03(2)(j)); breach notice under c. 93H §3 | Written incident response plan (314.4(h)); FTC notice at 500 consumers within 30 days (314.4(j)) | One plan with both notice paths |
| Review | At least annually or on material change (17.03(2)(i)) | Evaluate and adjust in light of testing and changes (314.4(g)); annual report to the board (314.4(i)) | One annual review producing the federal report |
Our guides to the Qualified Individual and to FTC Safeguards Rule breach notification cover the two federal elements with the closest state counterparts.
How 201 CMR 17.00 is enforced
The regulation is issued under M.G.L. c. 93H, and the Attorney General enforces it under c. 93H §6 through the Massachusetts consumer protection statute, c. 93A, which allows civil penalties, injunctions and costs; the breach notification duty in c. 93H §3 — notice to the Attorney General, the Office of Consumer Affairs and Business Regulation and affected residents — is where most enforcement begins, because a breach notice invites the question whether the WISP existed. The Attorney General’s settlements have routinely required the written program, encryption, training and audits that the regulation already demanded. Our guide to FTC Safeguards Rule penalties covers the federal enforcement path that runs alongside for financial institutions.
Under c. 93A §4, a court that finds a person knew or should have known the conduct was unlawful may order a civil penalty of up to $5,000 for each violation, plus the costs of investigation and litigation and reasonable attorneys’ fees. In practice almost every matter ends in a negotiated consent judgment or assurance of discontinuance that combines a payment with a list of security measures the business must put in place and keep.
The Peabody Properties settlement (2025)
The clearest recent example is the $795,000 settlement the Attorney General announced on 19 August 2025 with Peabody Properties, a Braintree property manager running about 227 residential properties. Between November 2019 and September 2021 it suffered five breaches, all reached through phishing emails, exposing Social Security numbers, driver’s license numbers and bank account information and leading to nearly 14,000 consumer notices. The first two were not reported to the Attorney General or to residents until nearly seven months after they occurred.
| What the AG alleged | What the consent judgment requires | The 201 CMR 17.00 element it maps to |
|---|---|---|
| No adequate security program to prevent attacks | Phishing protection software on all company laptops and desktops | 17.03(2)(b) risk assessment; 17.04(7) malware protection |
| Weak access protection | Multi-factor authentication | 17.04(1) secure user authentication |
| Unknown attack surface | An asset inventory and a vulnerability management program | 17.03(2)(b) and the checklist’s records inventory; 17.04(6) patches |
| Attacks not detected promptly | An intrusion detection/prevention system and a security incident and event management platform | 17.03(2)(h) and 17.04(4) monitoring |
| Late notice for two incidents | Payment covers the notice delay as well as the security failures | c. 93H §3 notice as soon as practicable and without unreasonable delay |
| Program not tested | An annual security assessment for three years | 17.03(2)(i) annual review |
Read that list as the Attorney General’s current idea of a reasonable program for a mid-sized business in 2026. None of MFA, an asset inventory or SIEM appear by name in a regulation written in 2009, but each is now the practical way to show that 17.03 and 17.04 are met.
Breach notice: what the 2019 amendments added
Breach notification sits in the statute, not the regulation, but it is where a weak 201 CMR 17.00 WISP surfaces. Since 10 April 2019 the notice to the Attorney General and OCABR must go out as soon as practicable and without unreasonable delay, and OCABR’s guidance says not to wait for a final count of affected residents: report, then update.
| Requirement | Since 10 April 2019 |
|---|---|
| Notice to the AG and OCABR | Nature of the breach, number of Massachusetts residents affected at the time of notice, steps taken and planned, the type of personal information compromised, the person responsible if known, whether you maintain a WISP, and whether you have updated it |
| Sample consumer notice | A copy goes to the AG and OCABR with the filing; OCABR posts it on its website within one business day of receipt |
| Social Security numbers exposed | Free credit monitoring for at least 18 months through a third-party vendor (at least 42 months for a consumer reporting agency), plus a filing certifying the monitoring complies with c. 93H §3A |
| No waiver | A resident cannot be made to waive the right to sue in exchange for the credit monitoring |
| Consumer notice contents | Right to a police report, how to place a free security freeze, mitigation services offered, and the name of any parent or affiliated company; it must not state the nature of the breach or the number of residents affected |
The WISP question in the notice is the practical reason to keep the document current. Answering “no WISP” or “WISP last reviewed in 2019” in a regulator filing is an admission against the 17.03(2)(i) annual review duty.
How to build a 201 CMR 17.00 WISP in eight steps
For a small firm, a first version is typically a few days of work spread over two to four weeks; for a business with several systems and vendors, expect four to eight weeks. These are typical ranges from WISP projects, not regulatory figures. The order below follows the regulation, so each step produces the evidence for the next.
- Name the coordinator. One person owns the program under 17.03(2)(a). If you also fall under the FTC Safeguards Rule, make the same person your Qualified Individual.
- Inventory the data. List every place Massachusetts personal information lives: payroll, HR, client files, tax software, email, cloud storage, laptops, phones, paper. If that is impractical, decide in writing to treat all records as covered.
- Assess the risks. Write a short risk assessment for each store of data: what could go wrong, what controls exist, what you will add and by when.
- Write the policies. Access, passwords and MFA, remote work and off-premises records, portable media and encryption, acceptable use, sanctions, leavers.
- Close the 17.04 technical gaps. Encryption on every laptop and phone, TLS or an encrypted portal for anything sent, unique accounts with no vendor default passwords, lockout after failed logins, patching, endpoint protection, logging.
- Fix the vendor contracts. Due diligence on each provider that touches the data and a contract clause requiring appropriate security measures.
- Train and record it. Onboarding and annual training, with attendance kept.
- Set the review and incident cycle. An incident log with post-incident review, and a dated annual review of the whole program that also feeds the breach-notice answer on whether the WISP is current.
Our guide to the WISP for sole practitioners shows the same steps scaled down to a one-person practice.
Will the Massachusetts Data Privacy Act replace 201 CMR 17.00?
No, on the evidence so far. Massachusetts still has no comprehensive consumer privacy law in force: the Senate passed its Massachusetts Data Privacy Act (S.2619) in September 2025, the House passed a different version 146-0 on 4 June 2026, and the two chambers have been in a conference committee since June 2026. At our last check, on 8 November 2026, we found no report of an enacted compromise.
Whatever emerges would add consumer rights such as access and deletion and limits on selling sensitive data; the House version, for example, bans the sale of precise geolocation data. The 201 CMR 17.00 duty to keep a written security program comes from c. 93H and nothing in the public reporting on either bill removes it. Plan for both: the WISP stays, and a privacy notice and rights-request process may be added on top.
Frequently asked questions
What is 201 CMR 17.00?
The Massachusetts regulation, in force since 1 March 2010 under M.G.L. c. 93H, requiring every person that owns or licenses personal information about a Massachusetts resident to maintain a written comprehensive information security program with ten specified elements (17.03) and, for electronic records, eight computer system security requirements (17.04).
Does it apply to businesses outside Massachusetts?
Yes. The test is whether the person owns or licenses personal information about a Massachusetts resident — a customer, patient or employee — not where the business is located.
What counts as personal information?
A Massachusetts resident’s first name or 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 — excluding information lawfully obtained from public records.
Is encryption mandatory?
Section 17.04 requires, to the extent technically feasible, encryption of personal information transmitted across public networks or wirelessly and of all personal information stored on laptops or other portable devices.
Is a 201 CMR 17.00 WISP the same as an FTC Safeguards Rule WISP?
They overlap heavily and one document can satisfy both, but the scopes differ: the state rule covers any business with Massachusetts residents’ data, the federal rule covers financial institutions; the federal rule adds a Qualified Individual, specified testing, a written incident response plan and FTC breach notification at 500 consumers.
Is there a 201 CMR 17.00 certification?
No. There is no certificate, auditor accreditation or registration. You assess yourself, keep the evidence, and the Attorney General tests it, usually after a breach notice. A consultant’s “201 CMR 17.00 certified” badge has no legal standing.
What is the penalty for violating 201 CMR 17.00?
The Attorney General enforces it through c. 93A, which allows a civil penalty of up to $5,000 per violation plus costs and attorneys’ fees. Settlements combine a payment with mandatory security measures; the Peabody Properties settlement announced in August 2025 was $795,000.
Do I have to offer credit monitoring after a breach?
Only if Social Security numbers of Massachusetts residents were exposed. Then you must offer at least 18 months of free credit monitoring through a third-party vendor (42 months for a consumer reporting agency) and certify it to the AG and OCABR.
Does 201 CMR 17.00 apply to paper records?
Yes. 17.03 covers electronic, paper and other records, which is why locked storage, off-premises transport rules and physical access restrictions are part of the WISP. 17.04 adds the computer requirements for electronic records.
Where this leaves you
Treat 201 CMR 17.00 as the floor for any business that touches a Massachusetts resident’s name with a Social Security, license or account number: a written program with the ten 17.03 elements, the eight 17.04 technical requirements with encryption in transit and on every portable device, a named coordinator, an annual review and a documented incident process — and, for a financial institution, fold the FTC Safeguards Rule’s Qualified Individual, testing, incident response plan and 500-consumer notice into the same document, because the Attorney General and the FTC will each ask to see it.
References
- Mass.gov — 201 CMR 17.00: Standards for the protection of personal information of residents of the Commonwealth — The regulation text, sections 17.01–17.05.
- 16 CFR Part 314 — Standards for Safeguarding Customer Information (eCFR) — The FTC Safeguards Rule, for the comparison.
- OCABR — Requirements for Data Breach Notifications — The 201 CMR 17.00 compliance checklist and the 2019 breach-notice FAQs.
- Office of the Attorney General — Peabody Properties settlement, 19 August 2025 — The consent judgment terms.
More on WISP and the Safeguards Rule
- 201 CMR 17.00 — you are here
- The written information security plan: 10 elements
- Who the FTC Safeguards Rule applies to
- The Qualified Individual
- FTC Safeguards Rule penalties
- WISP for sole practitioners
The written information security plan covering both the 201 CMR 17.03 elements and the 16 CFR 314.4 elements, the 17.04 technical requirements checklist, the risk assessment, the vendor contract clause and the incident and breach-notice procedures are in the WISP Toolkit, or start with the free templates.