Meet 201 CMR 17.00 and build your WISP with less effort
201 CMR 17.00 is the Massachusetts regulation that sets minimum standards for protecting personal information about Massachusetts residents. Issued under Chapter 93H of the Massachusetts General Laws, it requires a written comprehensive information security program (WISP) with administrative, technical and physical safeguards. It also sets specific computer security requirements, including secure authentication, access control, encryption and system monitoring.
Is 201 CMR 17.00 right for your organisation?
Any organisation that owns or licenses personal information about a Massachusetts resident must comply, wherever it is based, including data held about employees. Personal information means a name combined with a Social Security number, driver's licence or state ID number, or a financial account or payment card number. Compliance has been required since 1 March 2010, so it applies from the moment you hold such data.
It is a legal or regulatory requirement for organisations in scope.
- Issued by
- Massachusetts Office of Consumer Affairs and Business Regulation
- Legal basis
- Massachusetts General Laws Chapter 93H
- Compliance deadline
- 1 March 2010
- Applies to
- Anyone owning or licensing personal information about Massachusetts residents
- Enforced by
- Massachusetts Attorney General, via Chapter 93A
- Maximum penalty
- Up to $5,000 per violation under Chapter 93A, Section 4
- Assessment route
- No certification; self-assessed and enforced by the Attorney General
- Type
- Regulation (mandatory)
- Region
- Massachusetts, US
- In OneClickComply
- Supported today
OneClickComply makes it simple
201 CMR 17.00 is mapped in OneClickComply's control library and available on request. OneClickComply generates your WISP and supporting policies from your real environment, collects evidence for authentication, encryption, patching and monitoring controls automatically, and tracks service providers in vendor risk management. Because controls are mapped across frameworks, work done for ISO 27001 or SOC 2 counts towards the Massachusetts requirements too.
Requirements covered
Five sections, with the WISP requirements in Section 17.03 (ten mandatory program elements) and eight computer system security requirements in Section 17.04.
Manual 201 CMR 17.00 vs. OneClickComply
- Writing a WISP from a template that does not reflect how your business really works
- Chasing screenshots to prove password, lockout and encryption settings
- Tracking which service providers hold personal information and what their contracts say
- Remembering the annual review and keeping records of incidents and post-incident reviews
- Duplicating the same security work across ISO 27001, SOC 2 and state privacy rules
- Policies generated from your actual systems, ready for you to review and adopt
- Evidence collected automatically from your identity, device and cloud tools
- One vendor register with risk assessments and contract requirements recorded
- Scheduled reviews, incident records and a risk register kept in one place
- Controls mapped once so evidence counts towards every framework you follow
Everything you need for 201 CMR 17.00
AutoComplete generates your WISP and security policies from your real environment
Automated evidence for authentication, access control and account lockout settings
Encryption checks for laptops, portable devices and data in transit
OneClickFix corrects supported misconfigurations with the change logged as evidence
Vendor risk management to select, contract and oversee service providers
Continuous monitoring with alerts when patching, malware or access controls drift
Three steps to 201 CMR 17.00 compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against 201 CMR 17.00 and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates 201 CMR 17.00-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
Massachusetts 201 CMR 17.00 requirements
Every section of 201 CMR 17.00, with each WISP element in Section 17.03 and each computer system security requirement in Section 17.04.
| Reference | Requirement |
|---|---|
| 17.01 | Purpose and scope |
| 17.02 | Definitions, including personal information and service provider |
| 17.03(1) | Written comprehensive information security program (WISP) |
| 17.03(1)(a) | Safeguards appropriate to the size, scope and type of business |
| 17.03(1)(b) | Safeguards appropriate to available resources |
| 17.03(1)(c) | Safeguards appropriate to the amount of stored data |
| 17.03(1)(d) | Safeguards appropriate to the need to protect consumer and employee information |
| 17.03(2) | Minimum elements of every comprehensive information security program |
| 17.03(2)(a) | Designate one or more employees to maintain the program |
| 17.03(2)(b) | Identify and assess reasonably foreseeable internal and external risks |
| 17.03(2)(b)1 | Ongoing employee training, including temporary and contract staff |
| 17.03(2)(b)2 | Employee compliance with policies and procedures |
| 17.03(2)(b)3 | Means for detecting and preventing security system failures |
| 17.03(2)(c) | Policies on storing, accessing and transporting records off premises |
| 17.03(2)(d) | Disciplinary measures for program violations |
| 17.03(2)(e) | Prevent terminated employees from accessing personal information |
| 17.03(2)(f) | Oversee service providers |
| 17.03(2)(f)1 | Select and retain service providers capable of appropriate security |
| 17.03(2)(f)2 | Require service providers by contract to maintain security measures |
| 17.03(2)(g) | Reasonable restrictions on physical access to records |
Always check the official 201 CMR 17.00 text for the exact wording.
201 CMR 17.00 FAQs
What is 201 CMR 17.00?
201 CMR 17.00 is the Massachusetts regulation that sets minimum standards for protecting personal information about Massachusetts residents. Issued by the Office of Consumer Affairs and Business Regulation under Chapter 93H of the Massachusetts General Laws, it requires a written information security program with administrative, technical and physical safeguards, plus specific computer security controls such as authentication, access control, encryption and monitoring.
Who must comply with 201 CMR 17.00?
Any person or organisation that owns or licenses personal information about a Massachusetts resident must comply, wherever it is based. Personal information means a name combined with a Social Security number, driver's licence or state ID number, or a financial account or payment card number. That includes data held about employees, so most businesses with Massachusetts staff or customers are in scope.
What is a WISP under 201 CMR 17.00?
A WISP is the written information security program that Section 17.03 requires. It must be documented in one or more readily accessible parts and scaled to the size of the business, its resources, the amount of data it holds and the need to protect customer and employee information. It must name responsible staff, assess risks, cover training, discipline, offboarding, service providers, physical access, monitoring, annual review and incident documentation.
What are the penalties for breaching 201 CMR 17.00?
The Massachusetts Attorney General enforces Chapter 93H, and the data security rules behind 201 CMR 17.00, through the state consumer protection law, Chapter 93A. Under Section 4 of Chapter 93A, a court can order civil penalties of up to $5,000 for each violation, together with injunctions and the costs of investigation and litigation. The Attorney General has used consent judgments to settle data security cases.
Does 201 CMR 17.00 require encryption?
Yes, in specific cases. Section 17.04 requires encryption, where technically feasible, of personal information sent across public networks, all personal information transmitted wirelessly, and all personal information stored on laptops or other portable devices. It does not set a blanket requirement to encrypt every system at rest, but encryption is the expected safeguard for these higher-risk situations.
How does 201 CMR 17.00 relate to ISO 27001 and SOC 2?
201 CMR 17.00 is a legal requirement, while ISO 27001 and SOC 2 are voluntary frameworks. There is strong overlap: risk assessment, access control, encryption, monitoring, supplier management, training and incident response all appear in each. An ISO 27001 information security management system or SOC 2 programme can support a WISP, but you should still confirm every specific Massachusetts element, such as encryption of portable devices, is documented.
How long does it take to comply with 201 CMR 17.00?
It depends on your size, how much personal information you hold and what security controls already exist. The regulation itself is short, with two operative sections, so a business with existing security policies may mainly need to write or update its WISP and close specific gaps. Organisations starting from nothing will need longer to put technical controls and supplier contracts in place.
Does OneClickComply support 201 CMR 17.00?
201 CMR 17.00 is mapped in OneClickComply's control library and is available on request. Because its controls map to frameworks such as ISO 27001 and SOC 2, evidence and policies you already manage in OneClickComply can count towards the Massachusetts requirements. Contact the team to enable it for your account and discuss your scope with our in-house audit team.
Related standards
All standards- HIPAA Administrative Simplification RegulationsRegulation · US
- NISPOM (32 CFR Part 117)Regulation · US
- NYDFS Cybersecurity Regulation (23 NYCRR Part 500)Regulation · US
- HIPAA Security RuleRegulation · US
- Unclassified Naval Nuclear Propulsion Information (U-NNPI)Regulation · US
- TSA Security Directive 1580/82-2022-01: Rail Cybersecurity Mitigation Actions and TestingRegulation · US
- FTC Safeguards Rule (GLBA, 16 CFR Part 314)Regulation · US
- 45 CFR 155.260 (ACA Exchange Privacy and Security)Regulation · US
Get 201 CMR 17.00 ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.