Managed cybersecurity means an outside team runs layered security controls for you: MFA, endpoint detection and response, email security, patching, backups, training, network security and incident response planning. Boston IT Services Group provides this for small and midsize Boston and Massachusetts organizations, including help meeting the state's data security regulation (201 CMR 17.00) and planning for its breach notification law.
Our cybersecurity Boston service runs the layered controls that stop most attacks on small and midsize organizations: MFA, endpoint detection and response, email security, patching, backups, training and a plan for the bad day. The cyber security Boston firms need most is unglamorous work done every week, and it has to hold up when an insurer, a client or the Attorney General's office asks what you had in place. We manage those controls, document them and map them to NIST CSF 2.0 and Massachusetts rules.
What the current numbers say
Three recent reports give a fair picture of the risk.
- Massachusetts residents filed 22,936 complaints with the FBI's Internet Crime Complaint Center in 2025 and reported $410,924,066 in losses, according to the 2025 IC3 Internet Crime Report.
- The 2026 Verizon Data Breach Investigations Report found that 31% of breaches now start with software vulnerabilities, ahead of stolen passwords as the top way attackers get in.
- IBM's Cost of a Data Breach Report 2026 put the global average cost of a breach at $4.99 million, which it describes as a record high.
The Verizon finding has a practical meaning for small offices. If software flaws are the most common way in, then how quickly you patch internet-facing systems such as firewalls, VPNs and remote access tools matters as much as how strong your passwords are.
Layered controls in our cybersecurity Boston service
No single tool stops every attack, so we run several layers, each there to catch what the last one missed. The table lists each control and where it falls short.
| Control | What it does | Honest limits |
|---|---|---|
| MFA (multifactor authentication) | Requires a second proof of identity at sign-in. CISA calls phishing-resistant MFA such as FIDO the standard to aim for, with number matching as a fallback. | Text-message codes and simple push approvals can still be phished or spammed |
| Conditional access | Rules in Microsoft Entra that allow or block sign-ins based on device, location and risk | Needs careful setup so it does not lock out legitimate staff |
| EDR / MDR | EDR watches device behavior and can isolate a machine. MDR adds analysts who investigate alerts and act. | EDR alone records threats; someone still has to respond |
| Email security | Filters phishing, malware and impersonation attempts, and checks sender authentication records (SPF, DKIM, DMARC) | Some phishing always gets through, which is why training matters |
| Patching | Operating system, browser and application updates on a schedule, with known exploited flaws first using CISA's KEV catalog | Some vendor devices need manual updates and planned downtime |
| Vulnerability scanning | Regular scans of devices and internet-facing systems for missing patches and weak settings | Finds problems; fixing them is separate work |
| Backups | Copies kept separate from the network, with tested restores | A backup nobody has tested is a guess |
| Security awareness training and phishing simulation | Short training plus realistic test emails, with follow-up for people who click | Reduces risk; never removes it |
| Firewall and network security | Next-generation firewall, segmented networks, secured WiFi and remote access | Only as good as its rules and firmware |
| Incident response planning | A written plan: who to call, how to isolate systems, when to involve counsel and insurers | Has to be practiced to be useful |
| Dark web monitoring | Alerts when credentials tied to your domain show up in breach data | Tells you after exposure; does not prevent anything |
On dark web monitoring, we prefer to be blunt. It is a useful prompt to reset specific passwords and a good training example. It is not protection by itself, and it should never be the main reason you buy a security service.
Network security Boston offices rely on starts at the firewall but does not end there. Older buildings often have network closets nobody has opened in years, flat networks where the guest WiFi can see the file server, and remote access set up in a hurry. Our computer network support team handles that side.
How these controls map to NIST CSF 2.0
The NIST Cybersecurity Framework 2.0, published February 26, 2024, organizes security outcomes into six functions. Mapping your controls to them shows gaps quickly, and it gives insurers and auditors a structure they recognize.
| CSF 2.0 function | What it covers | Controls we manage |
|---|---|---|
| Govern | Setting, communicating and monitoring the security strategy, expectations and policy | WISP, security policies, roles, vendor oversight, quarterly reviews |
| Identify | Knowing your assets, data and risks | Device and software inventory, risk assessment, data mapping |
| Protect | Safeguards that reduce the chance and impact of an attack | MFA, conditional access, patching, email security, training, encryption, firewall |
| Detect | Finding and analyzing possible attacks | EDR, MDR, sign-in monitoring, vulnerability scanning, dark web alerts |
| Respond | Acting on a detected incident | Incident response plan, device isolation, account lockdown, coordination with counsel |
| Recover | Restoring systems and operations | Tested backups, disaster recovery plans, post-incident review |
Recover depends on backups that restore when you need them. Our data backup and disaster recovery service covers that in depth.
Massachusetts requirements: 201 CMR 17.00 and chapter 93H
Massachusetts has two rules that shape IT security Boston businesses run, whatever their industry.
201 CMR 17.00 applies to any person that owns or licenses personal information about a Massachusetts resident. Under 17.03, that business must develop, implement and maintain a written information security program (WISP). The program has to name who maintains it, assess foreseeable risks, train employees, cut off former employees' access, oversee service providers by contract, restrict physical access, and be reviewed at least annually. Section 17.04 adds computer requirements, to the extent technically feasible: secure authentication, access controls, encryption of personal information sent across public networks or wirelessly, encryption on laptops and portable devices, monitoring, reasonably current firewall protection and security patches, malware protection with current updates, and training. Our article on 201 CMR 17.00 goes through each item.
M.G.L. c. 93H, section 3 covers breach notification. A business that experiences a breach involving residents' personal information generally must notify the Attorney General, the Director of Consumer Affairs and Business Regulation, and the affected residents, "as soon as practicable and without unreasonable delay." Amendments effective April 11, 2019 require the regulator notice to say whether the business maintains a WISP, and require at least 18 months of free credit monitoring when Social Security numbers are involved, per MIT's summary of the amendments. Our guide to the Massachusetts data breach notification law has more detail.
We help you build and maintain the technical side of a WISP and plan for breach response. We are not your lawyers. Confirm your obligations with your attorney or compliance advisor.
How to compare Boston cybersecurity companies
Boston cybersecurity companies range from large security firms that sell to enterprises to IT providers that bundle a few tools into a managed agreement. Boston cybersecurity firms that fit a 30-person office usually sit in between. These questions help sort them.
- Which framework do you map controls to, and will you show us the mapping?
- Does a person review security alerts, or only software? Who responds outside business hours?
- Does the contract say who owns detection and incident response? CISA's guidance for MSP customers recommends putting exactly that in writing.
- How do you secure your own access to our systems?
- Will you help write and maintain our WISP, and produce evidence for cyber insurance applications? Our post on cyber insurance requirements lists what carriers commonly ask about.
- What do your monthly or quarterly security reports show?
Cybersecurity solutions Boston vendors sell as products (a firewall, an antivirus subscription) are not the same as a managed service where someone runs them and answers for the results. Many cyber security companies Boston firms talk to will quote tools. The managed cybersecurity services Boston organizations need usually come down to people watching, patching and testing every week. For most small offices, security works best inside a managed IT services agreement, so the team that patches the laptop is the same team that watches it.
Cybersecurity Boston practices and professional firms face
Some industries carry extra rules on top of 201 CMR 17.00. Medical and dental practices have HIPAA. Tax preparation firms are listed as covered financial institutions under the FTC Safeguards Rule. Law firms hold client files that opposing parties, and criminals, would pay for. The controls in the table above are the same, but the documentation, the vendor contracts and the evidence you keep differ by industry. Our pages on healthcare IT support and accounting firm IT support cover those requirements.
What these offices share is a small headcount and a large amount of sensitive data per person. A ten-person practice can hold thousands of patient or client records, and one phished mailbox can expose years of them. That ratio is why we treat cybersecurity Boston clients buy as part of everyday IT, rather than an annual project that gets revisited after something goes wrong.
How our cybersecurity services Boston onboarding works
- Assessment. We inventory devices, accounts, admin rights, internet-facing systems and where personal information lives, then score gaps against CSF 2.0.
- Quick fixes. MFA everywhere, stale accounts removed, admin rights cut back, risky sharing links closed.
- Tooling. EDR or MDR on every device, email security, conditional access policies, backup verification.
- Baseline scan. Vulnerability scans of devices and external systems, with a remediation plan by priority.
- People. Security awareness training and phishing simulations, with results reported to you.
- Documentation. Your WISP, incident response plan and security policies, written or updated with your input.
- Ongoing review. Regular reports on patches, alerts, training results and open risks, and an annual WISP review.
If you are not sure where your organization stands, start with the assessment. It gives you a gap list mapped to CSF 2.0 and the Massachusetts requirements, which is useful whether you work with us or not.
Frequently asked questions
What cybersecurity does a small business in Boston need?
Start with the controls that stop the most common attacks: MFA on every account, endpoint detection and response on every device, email filtering, prompt patching, backups kept separate from the network, and security awareness training. Massachusetts businesses that hold personal information about residents also need a written information security program under 201 CMR 17.00. Add vulnerability scanning, conditional access and an incident response plan as the next layer.
What is the difference between EDR and MDR?
EDR (endpoint detection and response) is software on each computer and server that watches for suspicious behavior and can isolate a device. MDR (managed detection and response) adds people: a security team that reviews EDR alerts, investigates them and takes action. EDR without anyone watching the alerts often means threats are recorded but not stopped. For most small businesses, MDR is how EDR becomes useful.
What does 201 CMR 17.00 require?
201 CMR 17.00 requires anyone who owns or licenses personal information about Massachusetts residents to maintain a written information security program (WISP) with administrative, technical and physical safeguards. Technical requirements include secure authentication, access controls, encryption of personal information sent over public networks or stored on laptops, monitoring, firewalls, patches, malware protection and employee training. Confirm your specific obligations with your attorney or compliance advisor.
Who must be notified after a data breach in Massachusetts?
Under M.G.L. c. 93H, section 3, a business that experiences a breach of Massachusetts residents' personal information generally must notify the Attorney General, the Director of the Office of Consumer Affairs and Business Regulation, and the affected residents. If Social Security numbers were involved, the law requires offering free credit monitoring for at least 18 months. Work with your attorney on any actual incident, since the details matter.
Is dark web monitoring worth paying for?
It has a narrow use. Dark web monitoring alerts you when credentials tied to your domain appear in breach dumps or criminal marketplaces. That tells you which passwords to reset, but only after the data is already exposed, and it cannot see everything. It does not prevent attacks. Treat it as a trigger for password resets and a training example, not as a security control on its own.
What should I ask cyber security companies Boston businesses are considering?
Ask which framework they map controls to, such as NIST CSF 2.0. Ask whether a person reviews security alerts or only software, who responds to an incident outside business hours, and how the contract assigns responsibility for detection and response. Ask how they secure their own access to your systems, whether they help write your WISP, and what their regular security reports show.
How does cybersecurity map to the NIST Cybersecurity Framework?
NIST CSF 2.0 organizes security into six functions: Govern, Identify, Protect, Detect, Respond and Recover. Policies and the WISP sit under Govern. Asset inventories and risk assessments sit under Identify. MFA, patching, training and email security sit under Protect. EDR, MDR and log monitoring sit under Detect. Incident response plans sit under Respond, and tested backups sit under Recover.
Sources and references
- FBI Internet Crime Complaint Center: 2025 Internet Crime Report
- Verizon 2026 Data Breach Investigations Report
- IBM Cost of a Data Breach Report 2026
- NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29
- 201 CMR 17.00: Standards for the protection of personal information of residents of the Commonwealth
- 201 CMR 17.03: Duty to protect and standards for protecting personal information (Cornell LII)
- 201 CMR 17.04: Computer system security requirements (Cornell LII)
- M.G.L. c. 93H, Section 3: Duty to report known security breach or unauthorized use of personal information
- MIT Office of the General Counsel: Massachusetts Amends Data Breach Law
- FTC: FTC Safeguards Rule, What Your Business Needs to Know
- CISA: More than a Password (multifactor authentication)
- CISA: Known Exploited Vulnerabilities Catalog
- CISA Advisory AA22-131A: Protecting Against Cyber Threats to Managed Service Providers and their Customers