How to choose a medical device cybersecurity company: a buyer's guide
To choose a medical device cybersecurity company, match the provider type to your stage, then check five things: regulatory experience from the reviewer's side, a submission track record, coverage from premarket through postmarket, a working vulnerability disclosure program, and evidence you keep after the engagement ends. Most manufacturers combine two provider types. This guide shows how to compare them.
Types of medical device cybersecurity providers
Four kinds of provider do most of this work. Each fits a different stage, and each leaves a different gap.
| Provider type | What they do | Best for | Ask them about |
|---|---|---|---|
| Regulatory or security consultancy | Expert-led gap assessments, threat models and submission documents, delivered as a project | A first or one-off 510(k), De Novo or PMA; responding to a deficiency letter | Who keeps the threat model and SBOM current after clearance |
| Software platform | SBOM generation, vulnerability monitoring and evidence tracking across products | Portfolios with several products or frequent releases | Who applies regulatory judgment to what the tool flags |
| Penetration test lab | Independent security testing of the device, apps and interfaces | Testing evidence for a submission | How findings tie back to risk, fixes and retest evidence |
| Platform plus experts | A platform run alongside in-house practitioners, covering premarket through postmarket | Teams that need submission help now and ongoing monitoring later | Whether the experts are in-house or referred out |
Medcrypt is a platform-plus-experts provider. Most manufacturers pair two types, for example a consultancy for the submission and a platform for postmarket.
What to evaluate
Use the same criteria for every provider on your list.
| Criterion | What good looks like | Red flag |
|---|---|---|
| Regulatory experience | People who have reviewed submissions from the regulator's side and know what triggers a deficiency | Security skill only, no submission work |
| Submission track record | Clearances they can show, by device type and pathway | A feature list instead of outcomes |
| Lifecycle coverage | Threat model, SBOM, testing evidence and postmarket monitoring in one connected record | Work ends at clearance; postmarket is rebuilt from scratch |
| Vulnerability disclosure | A working CVD program: public intake, triage and communication timelines | A policy template only |
| Evidence you keep | Deliverables and a process your team keeps using after the engagement | Reports that go stale the day they ship |
| Standing in the field | Active in industry working groups such as HSCC or AAMI, published work, teaching | Credibility only from the vendor's own marketing |
| Pricing clarity | A fixed scope and price before work starts | Open-ended time and materials |
For reference, Medcrypt medical device penetration testing typically starts at $15,000, with most engagements between $20,000 and $25,000.
See penetration testingQuestions to ask any vendor
- Who on your team has reviewed submissions from the regulator's side?
- What is your clearance track record for devices like ours, and can you show it?
- Do you cover premarket, submission and postmarket, or will we need another vendor?
- What do we own when the engagement ends: the threat model, the SBOM, the tooling?
- How do pen test findings flow into risk, remediation and retest evidence?
- Do you run a working coordinated vulnerability disclosure program?
- Which working groups, such as HSCC or AAMI, are your people active in?
- Is the scope and price fixed before work starts?
How Medcrypt answers these
Naomi Schwartz, Medcrypt's regulatory lead, is a former FDA reviewer.
Medcrypt has a 100% FDA approval rate to date.
MSI connects the threat model, SBOM, submission documents and postmarket monitoring, and includes CVD.
Medcrypt is active in HSCC working groups, and Axel Wirth teaches medical device cybersecurity at UConn and for AAMI.
CoverageMedcrypt supports medical device manufacturers anywhere, with a focus on submissions to the FDA, under the EU MDR, and to Health Canada.
Questions about choosing a partner
They help manufacturers design secure devices, produce the cybersecurity documentation regulators expect (threat models, SBOMs, testing and risk assessments), and manage vulnerabilities after launch.
Consultancies, software platforms, penetration test labs, and providers that combine a platform with in-house experts. Consultancies suit one-off submissions, platforms suit ongoing SBOM and vulnerability work, and test labs supply independent testing evidence.
A consultancy fits a one-off submission or a deficiency response. A platform fits ongoing SBOM and vulnerability work across several products. If you need both, choose a provider that combines them, or make sure the two you hire share one record of the threat model and SBOM.
Look for people who have reviewed submissions from the regulator's side, not only security skill. They know what triggers a deficiency letter and how reviewers read a threat model.
No. Regulators expect a working program: a public intake channel, triage, and communication timelines. A policy document alone doesn't show that.
Medcrypt medical device penetration testing typically starts at $15,000, with most engagements between $20,000 and $25,000. Ask for a fixed scope and price before testing starts.
The threat model, the SBOM, the test evidence and a process to keep them current. If those live only in the vendor's files, postmarket work starts from scratch.