Healthcare cybersecurity · IoMT / device risk
Asimily
Asimily is an IoMT and connected-device risk platform for health systems. It inventories medical devices on the network and helps biomed and security teams prioritize remediations. It is not a clinical identity or SSO product.
Strong fit
- Health systems inventorying connected medical devices and prioritizing IoMT risk with biomed and security together
- Teams that can act on vulnerability and utilization insights without taking clinical devices offline casually
- Organizations comparing IoMT vendors on risk scoring and remediation workflow
Weak fit
- Buyers seeking clinical identity/SSO as the primary need (Imprivata lane)
- Organizations with no biomed owner for device remediation
- Teams that want a block-everything posture that ignores clinical uptime
Bottom line
Asimily earns a Recommend for IoMT and connected-device risk buyers who will staff biomed and security remediation together. Outcomes are inventory coverage, prioritized risk, and closed remediations that do not break clinical uptime. Product focus overlaps Claroty and Cynerio more than Imprivata. Implementation needs network visibility and device-owner workflows. Pricing is enterprise-custom. Score sits just below Cynerio on our cybersecurity board.
Score breakdown
Weights: Outcomes 35% · Product 30% · Implementation 20% · Pricing clarity 15%.
Asimily competes in connected medical device and IoMT risk management. Diligence belongs beside Claroty and Cynerio: discovery coverage, risk prioritization, and whether biomed can actually patch or segment without breaking care.
Identity-focused buyers should stay on Imprivata. IoMT buyers should ask for evidence on utilization-aware risk and remediation workflow, not only CVE counts.
Score is a solid mid-7 Recommend in a crowded IoMT peer set, with implementation and pricing clarity in the ordinary enterprise range.
Competitor landscape
| Vendor | Overall | Ease of implementation |
|---|---|---|
| Asimily | 7.2 | 6.8 |
| Claroty | 7.5 | 7.1 |
| Cynerio | 7.3 | 7.0 |
| Imprivata | 7.8 | 7.4 |
Pricing
| Item | Detail |
|---|---|
| Model | Enterprise IoMT security platform licensing; often tied to device counts or sites. |
| What usually drives cost | Device and site scope, sensors or collectors, and professional services. |
| What to ask in diligence | Cost at your connected-device estimate, with remediation ownership named before purchase. |
| Published pricing | Public list price: not published. Expect a custom quote; confirm total cost at your device footprint. |
Prerequisites for purchase
| Need | Why it matters |
|---|---|
| What you need to get Asimily to function | |
| Biomed and security owners working the same remediation queue | IoMT tools fail when tickets bounce between teams. |
| Network visibility path for connected device discovery | Without discovery coverage, risk scores are fiction. |
| Clinical uptime constraints documented for remediation | Block-everything postures break care. |
| Device inventory estimate for commercial scoping | Quotes without footprint guesses go sideways. |
| Willingness to act on prioritized risk, not only view dashboards | Shelfware security tools are common. |
| What will maximize your value | |
| Start with high-acuity device classes | Early wins build biomed trust. |
| Tie risk scores to utilization where possible | Unused devices should not dominate panic. |
| Track closed remediations and exceptions monthly | Open-forever queues erase value. |
| Coordinate change windows with clinical departments | Surprise patches create incident tickets. |
| Compare overlapping IoMT vendors on workflow, not logo slides | Claroty/Cynerio overlap is real. |
| Deal-breakers | |
| You mainly need clinical identity/SSO (Imprivata lane). | |
| No biomed owner will remediate devices. | |
| Leadership wants block-everything without clinical uptime rules. | |
| No network discovery path exists. | |
| Security will only view dashboards, not close work. | |
Value creation time frame
| # | Stage | Typical range |
|---|---|---|
| 1 | Contract signed → kickoff | 3–8 weeks (security review, network design, biomed engagement) |
| 2 | Kickoff → first live workflow | 8–16 weeks for discovery and risk views on a first site or zone |
| 3 | First live workflow → steady value | 4–9 months of remediation across the connected-device footprint |
Methodology
| Weight | Factor | What it measures |
|---|---|---|
| 35% | Customer outcomes | Whether buyers get measurable operational or clinical-workflow results after go-live |
| 30% | Product | Capability depth, reliability, and fit for the job the category actually buys |
| 20% | Implementation | How hard it is to stand up, integrate, train, and stabilize |
| 15% | Pricing clarity | Whether a buyer can model total cost without a mystery quote |
| Label | Meaning |
|---|---|
| Highly recommend | Strong outcomes and product with manageable caveats |
| Recommend | Solid fit for the right buyer; know the tradeoffs |
| Conditional | Only with a specific use case or heavy caveats |
| Not recommended | Avoid for most buyers in this category |
Read our full methodology for how we weight scores and assign recommend labels.