Coastline is a penetration testing firm based in Massachusetts. We test networks, applications and people for businesses, healthcare organizations, financial institutions, utilities and municipalities across New England, and we work remotely with clients nationwide.
Massachusetts businesses that hold residents’ personal information must monitor that their security program is working (201 CMR 17.00). A penetration test is one of the clearest ways to show it.
Being local means we can be on site when a test needs it. Our core services include:
On-site or remote testing of your internal network and Wi-Fi, from a single office to multiple locations.
Your internet-facing systems, web applications and APIs, tested the way a real attacker would.
Our testers do original research. Google recently credited us with CVEs in Android and Chrome. Learn more about Coastline.
A clear report with every finding, its risk and how to fix it. Whether you are in Boston, Worcester, the South Coast or anywhere in New England, we will scope the right test for your environment.
Not by name. 201 CMR 17.00 applies to any business that owns or licenses personal information about Massachusetts residents, wherever it is based. It requires a written information security program (WISP), regular monitoring that it is working, and a review at least once a year or whenever your business practices change materially. A penetration test is one of the clearest ways to show your WISP’s controls actually hold up.
Yes, when a test needs it. Wireless testing and some internal network tests work best on site, and being based in Massachusetts makes that easy. Most other testing can be done remotely.
All of it, plus the rest of New England. That includes Greater Boston, the Route 128 and I-495 corridors, MetroWest, Worcester and the South Coast. We also work remotely with clients nationwide.
A scan automatically lists known weaknesses. In a penetration test, a person tries to use those weaknesses to break in, so you learn which ones actually put your data at risk.
At least once a year and after major changes. That lines up with the annual review 201 CMR 17.00 already requires.
We agree on timing and rules of engagement before testing starts and schedule around your critical systems. Anything that could affect production is coordinated with your team first.
OSCP-certified testers who also do original security research. Google recently credited us with CVEs in Android and Chrome.