Security Risk Assessment Checklist for Ophthalmic OCT Device Manufacturers
An ophthalmic optical coherence tomography (OCT) system combines image acquisition, software, data storage, and clinical interfaces. A cybersecurity risk assessment should therefore consider how compromise could affect not only confidentiality, but also scan integrity, device availability, clinical decisions, and care workflows.
Use this checklist to organize your assessment across the device lifecycle. Tailor it to your OCT system’s intended use, connections, operating environment, and applicable regulatory obligations.
How should manufacturers define the OCT device system boundary and intended use?
Start with a clear description of the OCT device system, its intended users, and the environment in which it will operate. Identify which components you control and which depend on the customer’s network, third-party suppliers, or external services. The FDA’s current premarket cybersecurity guidance recommends considering the device system and its connections, not just the device enclosure.
- List system components: Include the scanner, optical and electronic subsystems, embedded controllers, firmware, acquisition and analysis software, workstation, storage, accessories, service tools, and any cloud or remote-support services.
- Map connections and data flows: Document wired and wireless network links, USB ports, removable media, software-update channels, and interfaces to imaging archives, electronic health records, or other clinical systems. Include the direction and purpose of each data flow.
- Define trust boundaries: Mark where data or commands cross between the scanner, workstation, clinic network, external systems, manufacturer services, and third-party components.
- Describe intended use and foreseeable misuse: Account for how staff acquire scans, review results, export images, service the equipment, and recover from a network or system outage.
- Record assumptions: State expected network configurations, user roles, physical access, and external dependencies. Identify assumptions that may not hold in less-secure deployment environments.
Use IEC 81001-5-1 as a reference for security activities across health software development and maintenance. Apply it within your established quality and risk-management processes; do not treat a standard reference as proof that a particular device is secure.
Which cybersecurity threats apply to OCT scanners and connected workstations?
Use threat modeling to identify how an attacker, compromised component, or accidental failure could affect the OCT system. Assess each threat in the context of the actual interfaces, deployment environment, and clinical use rather than relying on a generic list.
- Unauthorized access: Stolen, shared, or weak credentials could expose patient information or permit changes to device settings, software, or stored studies.
- Malware and ransomware: A compromised workstation or connected network could disrupt scan acquisition, analysis, image access, or related clinic operations.
- Data manipulation or misassociation: Altered, incomplete, or incorrectly linked scans, measurements, or patient identifiers could undermine the reliability of the clinical record.
- Service and update compromise: An attacker could target remote support, maintenance accounts, removable media, update infrastructure, or firmware installation paths.
- Network and interface attacks: Exposed ports, insecure protocols, misconfigured interfaces, or excessive connectivity could enable access, lateral movement, or denial of service.
- Supply-chain vulnerabilities: Operating systems, libraries, drivers, databases, and other third-party software may introduce weaknesses or reach end of support.
- Physical access and insider misuse: Unattended workstations, service ports, shared accounts, or unauthorized configuration changes may bypass intended controls.
For each scenario, describe the threat path, affected assets, existing protections, and possible effects on device safety, essential performance, data, and care delivery. FDA recommends threat modeling that covers system elements, interfaces, supply-chain risks, and lifecycle activities.
How can manufacturers assess patient data and clinical workflow risks?
Connect each security scenario to its possible clinical and privacy consequences. OCT images and derived measurements can be sensitive, while interruptions or unreliable results may affect how clinicians review a patient’s condition and plan follow-up. Consider the entire path from patient identification and scan acquisition to storage, review, export, and retrieval.
- Confidentiality: Identify patient-linked images, reports, credentials, and other sensitive information stored on the scanner or workstation or transmitted to connected systems. Assess unauthorized viewing, copying, or disclosure.
- Integrity: Evaluate whether scans, metadata, patient identifiers, measurements, or configuration settings could be changed, corrupted, or linked to the wrong record without detection.
- Availability: Assess how a system outage, ransomware event, failed update, or network disruption could delay acquisition, review, access to prior scans, or clinic operations.
- Clinical consequences: Consider how unavailable, delayed, corrupted, or misassociated data could affect interpretation, longitudinal comparison, diagnosis, or treatment decisions.
- Multi-device and multi-patient effects: Determine whether a shared network, server, or update mechanism could expose multiple OCT systems or patients to the same event.
- Recovery and continuity: Define how staff can identify affected studies, restore authorized data, continue or pause workflows safely, and verify that records are complete after recovery.
Assess privacy and patient-safety impacts separately where useful, then connect them in the overall risk analysis. Applicable privacy obligations depend on the manufacturer’s role and relationships; do not assume that every manufacturer has the same obligations as a healthcare provider.
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk AssessmentWhat security controls should be verified across device software and interfaces?
Translate identified risks into verifiable security requirements. The control set should address the OCT system’s design and intended environment, and testing should show that the controls work as specified without creating unacceptable safety or workflow risks.
- Authentication and authorization: Verify unique user accounts where appropriate, role-based permissions, least privilege, secure service access, credential protections, and a controlled process for account recovery.
- Interface security: Minimize exposed services and ports, document necessary communication paths, restrict destinations and protocols, and provide configuration guidance for deploying the device on clinic networks.
- Data protection: Protect data in transit and at rest where appropriate. Secure cryptographic keys and verify that access controls cover stored scans, reports, and system configuration.
- Code and firmware integrity: Evaluate secure boot and related integrity checks where supported by the design. Verify that firmware and software updates are cryptographically authenticated and that unauthorized or tampered updates are rejected.
- Update safety: Test update installation, failure handling, recovery, and protection against unauthorized rollback. Confirm that security updates do not impair essential functions or clinical workflows.
- Logging and detection: Record relevant security events, protect logs from unauthorized alteration, and give users sufficient information to investigate incidents without exposing unnecessary patient information.
- Resilience and recovery: Test behavior during network loss, service interruptions, storage limitations, and failed updates. Verify backup, restore, and recovery procedures, including how restored data and settings are authenticated.
- Security testing: Use risk-based software and system testing, including analysis of third-party components and interfaces. Record test scope, methods, results, unresolved findings, and the rationale for any accepted residual risk.
FDA’s February 2026 premarket guidance identifies security objectives that include authenticity and integrity, authorization, availability, confidentiality, and secure, timely updateability and patchability. It also recommends authenticated firmware and software updates, including protections against unauthorized downgrade or rollback.
How should manufacturers document risk analysis and residual risk?
Integrate cybersecurity with, but do not confuse it with, safety risk management. FDA’s recognition information for ISO 14971 describes the standard’s lifecycle risk-management process. FDA’s 2026 cybersecurity guidance recommends a separate, accompanying security risk assessment connected to the safety risk assessment.
- Maintain a system description: Keep current architecture diagrams, asset inventories, interfaces, data flows, trust boundaries, deployment assumptions, and software and firmware versions.
- Record threat analysis: Document threat scenarios, affected assets, vulnerabilities, attack paths, potential patient harms, and the rationale for the threat-modeling method selected.
- Assess risk and controls: For each scenario, record pre-control and residual risk, the control selected, verification evidence, acceptance criteria, and the person or function responsible for review.
- Use CVSS appropriately: CVSS vulnerability scoring can help describe technical exploitability and prioritize investigation. Do not use a CVSS score alone as a measure of patient harm or as the final device risk decision; consider the OCT system’s exposure, clinical role, and compensating controls.
- Maintain a software bill of materials: Track manufacturer-developed and third-party components, dependencies, versions, and support status. For devices meeting the statutory definition of a cyber device, FDA explains that section 524B requires an SBOM covering commercial, open-source, and off-the-shelf software components.
- Preserve traceability: Link threats and risks to requirements, design controls, test results, unresolved anomalies, labeling, and postmarket monitoring records.
- Reassess over time: Update the assessment when software, hardware, interfaces, suppliers, deployment assumptions, vulnerabilities, or clinical workflows change.
FDA recommends that cybersecurity documentation scale with device risk and include a clear residual-risk conclusion and traceability among the threat model, risk assessment, SBOM, and testing records.
How can manufacturers manage vulnerabilities and postmarket security updates?
Plan for vulnerability handling before the OCT system is released. For a device that meets the definition of a cyber device, section 524B includes requirements for a postmarket vulnerability plan, processes to support cybersecurity and make updates and patches available, and an SBOM. Check the FDA cybersecurity FAQs for the scope of those statutory provisions.
- Monitor components and reports: Track supplier advisories, vulnerability databases, security researcher reports, customer feedback, and relevant exploited-vulnerability information. Use the SBOM to identify affected device versions and related products.
- Operate a coordinated vulnerability disclosure process: Publish a way to report vulnerabilities, assign responsibility for intake and triage, acknowledge reports, protect sensitive information, and coordinate remediation communications with reporters and users.
- Triage for device and patient impact: Assess exploitability, exposure, potential harm, affected versions, existing mitigations, and effects on safety and essential performance. CVSS can inform triage but should not replace device-specific risk analysis.
- Validate and distribute mitigations: Test patches or compensating controls against the vulnerability and for unintended effects. Provide users with deployment instructions, affected versions, residual-risk information, and any necessary interim actions.
- Define support and update expectations: Document update channels, authorized software sources, support periods, patch communication processes, and how users can verify an update’s authenticity and version.
- Review regulatory and quality-system actions: Assess whether a change or incident triggers applicable reporting, corrective-action, or premarket considerations. Do not assume every security patch has the same regulatory treatment.
FDA’s postmarket cybersecurity guidance recommends a coordinated vulnerability disclosure policy and timely risk-based response. Manufacturers should validate remediations and assess whether a security fix introduces new risks or affects device function.
In practice, an effective OCT cybersecurity assessment connects system boundaries and threat scenarios to patient and workflow impacts, verified controls, traceable residual-risk decisions, and an active postmarket response process.
FAQs
What cybersecurity assets should an ophthalmic OCT risk assessment include?
Include scanner hardware and firmware, acquisition and analysis software, workstations, stored scans and reports, patient identifiers, credentials, service tools, update mechanisms, network interfaces, connected clinical systems, third-party components, and cloud or remote-support services where present. Include the people, processes, and external systems that can access or affect these assets.
How should manufacturers assess third-party software vulnerabilities in an OCT device?
Maintain a current SBOM or equivalent component inventory, monitor supplier advisories and vulnerability sources, and identify which product versions contain affected components. Evaluate exploitability in the OCT system’s actual deployment context and assess potential effects on patient data, device performance, and clinical workflows. Document mitigations, supplier support status, and plans to update or replace components that are unsupported or cannot be remediated.
What documentation should support an OCT device cybersecurity risk assessment?
Keep the system and architecture description, data-flow and interface diagrams, threat model, cybersecurity risk assessment, risk-control requirements, verification and security-testing evidence, SBOM, component support information, unresolved-anomaly assessments, residual-risk rationale, update and vulnerability-management plans, and relevant user-facing security information. Maintain traceability between identified risks, controls, tests, and postmarket actions.
How should manufacturers handle postmarket vulnerabilities in an ophthalmic OCT system?
Receive and acknowledge reports through a defined coordinated vulnerability disclosure process, determine affected components and device versions, and assess exploitability and potential patient harm. Select and validate a patch or compensating control, communicate affected versions and recommended actions to users, and document the decision and residual risk. Reassess related devices and software versions, and evaluate applicable quality-system and regulatory obligations.
Table of Contents
- How should manufacturers define the OCT device system boundary and intended use?
- Which cybersecurity threats apply to OCT scanners and connected workstations?
- How can manufacturers assess patient data and clinical workflow risks?
- What security controls should be verified across device software and interfaces?
- How should manufacturers document risk analysis and residual risk?
- How can manufacturers manage vulnerabilities and postmarket security updates?
-
FAQs
- What cybersecurity assets should an ophthalmic OCT risk assessment include?
- How should manufacturers assess third-party software vulnerabilities in an OCT device?
- What documentation should support an OCT device cybersecurity risk assessment?
- How should manufacturers handle postmarket vulnerabilities in an ophthalmic OCT system?
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk Assessment