Typical clinical uses
- OCT, fundus, and slit-lamp imaging systems
- Refractive and cataract surgical lasers
- Visual-field and electrophysiology diagnostics
- AI-assisted DR / AMD / glaucoma screening
- Surgical guidance and IOL planning systems
Cybersecurity for surgical, diagnostic, and therapeutic ophthalmic devices.
Ophthalmic devices range from precision surgical lasers to OCT scanners and connected diagnostic platforms. We tailor cyber engagements to the specific clinical workflow and image data pipeline.
Ophthalmic systems blend imaging, laser, and increasingly AI - networked into clinic workflows that often run on aging Windows hardware with limited IT support. The combination drives the cyber program: harden the device, but also ship safe defaults for a flat clinic network.
Typical clinical uses
Key data flows & integrations
Ophthalmic imaging vendors frequently expose DICOM services with weak authentication.
Maintenance interfaces over USB, Ethernet, and serial need authenticated lockdown for shipped product.
Ophthalmic devices combine an imaging or laser front-end with a clinician workstation and increasingly a cloud sync path. The laser energy path requires the same essential-performance treatment as a robotic system.
Layers shown outermost (top) to innermost (bottom). Dashed rows are part of the surrounding system but out of scope for this view.
Ophthalmic platforms inherit imaging, PACS, and DICOM history. A growing number of advisories now apply to the workstations and cloud platforms ophthalmic vendors integrate with.
Historical incidents
Public research showed that valid DICOM files (used widely in OCT, fundus, and surgical-planning platforms) can embed executable payloads in the 128-byte preamble while remaining standards-compliant - persisting inside images that traverse PACS and clinical archives.
FDA and CISA have issued repeated advisories affecting Philips imaging and diagnostic platforms (privilege escalation, hardcoded credentials, weak authentication). Many ophthalmic workflows integrate against these platforms or similar from other vendors.
Multiple CISA ICSMA advisories, 2018-2023
The 2019 URGENT/11 advisory affected real-time OS components used in a wide range of clinical imaging and laser-control systems. FDA directed manufacturers across imaging categories to assess and disclose exposure.
FDA Safety Communication, Oct 2019
Active threat scenarios
Malformed DICOM objects or weaponized preambles compromising the receiving workstation.
Default or shared service credentials on ophthalmic workstations and instruments remain a recurring finding.
Service tunnels into clinic networks are a frequent path of least resistance.
Patient data export workflows over USB without policy or logging are a documented compliance and cyber concern.
What FDA reviewers cite
Ophthalmic systems blend imaging, laser, and increasingly AI - networked into clinic workflows that often run on aging hardware.
10+ year deployed lifetimes mean OSes go end-of-support mid-life; postmarket compensating controls are mandatory.
Your design has to be defensible on flat clinic networks, not just on hardened hospital VLANs.
Adding AI modules to existing devices triggers new threat-modeling and possibly a new submission pathway.
What FDA scrutinizes
10+ year deployed lifetimes mean OSes go end-of-support mid-life; postmarket compensating controls are mandatory.
Adding AI modules to existing devices may trigger new threat-modeling and a new submission pathway.
Designs must be defensible on flat clinic networks, not just hardened hospital VLANs.
Standards & deliverables
Six deliverables FDA and notified bodies expect across MedTech, with the ophthalmic-specific wrinkle on each row. Use it as a scoping checklist before you brief vendors or your QA team.
Machine-readable SBOM (CycloneDX/SPDX) plus VEX feed for every CVE that touches a listed component.
Continuous CVE / advisory monitoring against the SBOM, with a documented triage and disclosure path.
Black/grey-box testing across device, wireless interfaces, mobile apps, cloud APIs, and service tooling.
STRIDE-per-interface threat model with documented mitigations and residual-risk acceptance.
Signed firmware/software updates with rollback protection, integrity verification, and staged rollout.
Public CVD policy, intake channel, and SLAs for triage, fix, and customer communication.
Yes. OCT, fundus cameras, perimetry systems, and ophthalmic surgical platforms almost universally use DICOM (with a strong dose of Eye Care-specific service classes), so DICOM service fuzzing, authorization tests across C-STORE/C-FIND/C-MOVE, and parser memory-safety evidence are part of the scope. DICOM toolkits have a long CVE history and reviewers expect explicit testing rather than narrative claims of conformance.
We focus on the control system (laser parameter authorization, energy-delivery integrity, foot-pedal and treatment-pattern interfaces), the service interfaces (USB, serial, vendor remote support), and any networked planning workflow that feeds the device. Safety-critical control paths are exercised on staging hardware only and coordinated with the device's IEC 60601-1 (and applicable -2-22 for laser surgical) and IEC 14971 risk file. The SPDF captures every interface, its authentication, and its failure mode.
Cloud-stored ophthalmic images are PHI and frequently sensitive (they reveal systemic conditions beyond ophthalmology). We test encryption at rest and in transit, key custody, tenant isolation, and authorization on every read path - including image-sharing flows between practices and reading centers. The SPDF documents storage regions, retention, and any cross-border data flow so reviewers, hospital procurement, and privacy counsel see one coherent story.
Yes. Service ports (USB, RS-232, Ethernet service VLAN, vendor proprietary) are a common path to privileged access on ophthalmic platforms, and they're a frequent FDA finding when left enabled by default. We verify that they're authenticated, locked down on shipped product, gated by physical or procedural controls, and properly documented in labeling. The threat model treats them as untrusted local interfaces regardless of how 'internal' the vendor considers them.
Standard premarket cyber package: STRIDE-based threat model, SBOM in SPDX or CycloneDX with VEX, security architecture views, authenticated penetration testing focused on DICOM, network, service, and (when present) cloud surfaces, MDS2, labeling content, and a postmarket cybersecurity management plan under section §524B. Everything is packaged for eSTAR and cross-references the IEC 14971 risk file.
When the workstation is part of the cleared system or recommended configuration, OS hardening, application allowlisting, update mechanisms, and remote-access exposure are all in scope. End-of-life Windows is documented with compensating controls (segmentation, allowlisting, restricted services) plus a migration plan - reviewers accept that combination but reject silence on it.
AI ophthalmic SaMD is treated like other AI/SaMD: model supply-chain controls (signing, version pinning, load-time verification), training-data lineage in the SPDF, adversarial-input testing where clinically meaningful, and PCCP-aware change control if you have one. The DICOM ingestion path is fuzzed and authorization-tested separately from the model so issues in either layer are isolated and traceable.
Reading centers and tele-ophthalmology partners are modeled as explicit external trust boundaries with documented authentication, authorization, and data-retention controls. We test the case-routing and image-sharing APIs for cross-tenant isolation and stale-session access, and we verify that revocation flows actually terminate the partner's access. These integrations frequently surface authorization findings if not designed deliberately.
Surgical platforms are scoped as connected systems within the OR sub-network: console, foot pedal, irrigation/aspiration controllers, energy modules, navigation, and any imaging integration. We model the OR network with explicit trust boundaries, exercise vendor remote-service tunnels for MFA/jump-host/session-recording compliance, and pen-test the service paths end-to-end - the same playbook applied to surgical robotics, scaled to ophthalmic specifics.
Typical baseline: FDA 2026 final premarket cybersecurity guidance, AAMI SW96, AAMI TIR57, IEC 62304 (often Class B or C depending on indication), ISO 14971, IEC 60601-1 with applicable particulars (e.g., -2-22 for laser surgical, -2-57 for ophthalmic light sources), and DICOM-specific test cases. EU manufacturers add MDR Annex I §17.2 and MDCG 2019-16; we map across both regimes.
A formal postmarket cybersecurity management plan under section §524B: continuous SBOM monitoring across device firmware, embedded OS, in-clinic workstation, and any cloud components; CVD intake with severity-based SLAs; controlled patching through the QMS; and a secure update mechanism (signed, anti-rollback, atomic, recovery-safe) that respects clinic uptime constraints.
Imaging interface, cloud, and mobile companion testing for diagnostic and surgical ophthalmic devices.
"Blue Goat Cyber's depth of expertise was impressive. We had no in-house cybersecurity experience, and their team guided us through every step of the FDA process. The penetration testing and SBOM testing were thorough and gave us complete confidence."
Cybersecurity for surgical, diagnostic, and therapeutic ophthalmic devices.
