11-Decision | HCP: Decide on continued use and review security documentation | 0 |
11-Education | HCP: Train staff on secure use of legacy devices | 0 |
11-T1-Anti-malware | HCP: Install anti-malware on legacy devices after manufacturer consultation | 0 |
11-T1-Backup-and-restore | HCP: Maintain backup and restore for legacy devices | 0 |
11-T1-Firewall | HCP: Protect legacy device with a firewall | 0 |
11-T1-Monitoring | HCP: Monitor legacy devices and networks for suspicious activity | 0 |
11-T1-Network-isolation | HCP: Isolate legacy device from hospital networks | 0 |
11-T1-Network-segregation | HCP: Place legacy device on a dedicated VLAN | 0 |
11-T1-Physical-access | HCP: Restrict physical access to legacy devices | 0 |
11-T1-Remote-access | HCP: Remove remote access from legacy devices | 0 |
11-T1-Removable-media | HCP: restrict removable media on legacy devices | 0 |
4-Communication | Timely and active life cycle communication | 0 |
4-Shared-Risk-Management | Risk management shared by manufacturers and providers | 0 |
4-TPLC | Planning cybersecurity for the whole product life cycle | 0 |
5-Trigger-1 | MDM: Assess Risk After Component End of Life | 0 |
5-Trigger-2 | MDM: cut risk while the device is in Support | 0 |
5-Trigger-3 | MDM: decide on a move to Limited Support | 0 |
6.1.1 | MDM: Use HCP feedback in future device design | 0 |
6.1.2 | HCP: Share clinical and cyber needs in development | 0 |
6.2.1.1 | MDM: Build in maintainable security across device life cycle | 0 |
6.2.1.2 | MDM: Weigh third-party component end of support | 0 |
7.1.1.1 | MDM: Provide product security documentation | 0 |
7.1.1.2 | MDM: Communicate key life cycle milestones | 0 |
7.1.1.3 | MDM: Update security and life cycle documents | 0 |
7.1.1.4 | MDM: Share vulnerability and patching information | 0 |
7.1.1.5 | MDM: Manage third-party component support | 0 |
7.1.1.6 | MDM: Share end-of-life dates with patients | 0 |
7.1.2.1 | HCP: set out the information it needs | 0 |
7.1.2.2 | HCP: Request pre-procurement security information | 0 |
7.1.2.3 | HCP: Prepare for ongoing vendor communications | 0 |
7.2.1.1 | MDM: Assess third-party component risk | 0 |
7.2.1.2 | MDM: Communicate end-of-life planning information | 0 |
7.2.1.3 | MDM: Meet post-market obligations | 0 |
7.2.1.4 | MDM: Monitor risk profile until end of support | 0 |
7.2.2.1 | HCP: Baseline security controls | 0 |
7.2.2.2 | HCP: Operating environment risk management | 0 |
7.2.2.3 | HCP: Device access controls | 0 |
7.2.2.4 | HCP: Network segmentation impact | 0 |
7.2.2.5 | HCP: Multifactor authentication | 0 |
7.2.2.6 | HCP: Network activity monitoring | 0 |
7.2.2.7 | HCP: Inventory and EOS planning | 0 |
7.2.2.8 | HCP: handle vulnerabilities on a risk basis | 0 |
7.2.2.9 | HCP: Decommissioning or risk acceptance | 0 |
7.3.1.1 | MDM: EOS transition notice | 0 |
7.3.1.2 | MDM: Transition path and upgrade options | 0 |
7.3.2.1 | HCP: judge its capability to manage the device | 0 |
7.3.2.2 | HCP: look for third-party support | 0 |
7.3.2.3 | HCP: weigh up replacement | 0 |
7.3.2.4 | HCP: find further support resources | 0 |
8.1.1.1 | MDM: Notify customers of limited support status | 0 |
8.1.1.2 | MDM: Publish device support status publicly | 0 |
8.1.1.3 | MDM: Continue prior services and vulnerability notices | 0 |
8.1.1.4 | MDM: Share life cycle planning timelines | 0 |
8.1.1.5 | MDM: Provide product security documentation for reduced support | 0 |
8.1.2 | HCP: Continue dialogue with manufacturer on limited support | 0 |
8.2.1 | MDM: Continue post-market monitoring in limited support | 0 |
8.2.2.1 | HCP: Assess end of life risk before buying resold devices | 0 |
8.2.2.2 | HCP: Prepare for end of support | 0 |
8.3.1.1 | MDM: Identify software updates available at transition | 0 |
8.3.1.2 | MDM: Document security controls for provider networks | 0 |
8.3.1.3 | MDM: State ports and IP addresses required | 0 |
8.3.1.4 | MDM: Enable provider to harden device traffic | 0 |
8.3.1.5 | MDM: Supply product security documentation including SBOM | 0 |
8.3.1.6 | MDM: Share broader medical device security practices | 0 |
8.3.1.7 | MDM: Communicate available limited support options | 0 |
8.3.2.1 | HCP: Monitor the device for cybersecurity events | 0 |
8.3.2.2 | HCP: Manage vulnerabilities on the device | 0 |
8.3.2.3 | HCP: Apply compensating controls | 0 |
8.3.2.4 | HCP: Confirm the deployment environment secures the device | 0 |
8.3.2.5 | HCP: Put an incident response plan in place | 0 |
8.3.2.6 | HCP: Establish a business continuity plan | 0 |
8.3.2.7 | HCP: Run regular risk assessments on the device | 0 |
9.1.1.1 | MDM: Provide product security information for maintenance | 0 |
9.1.1.2 | MDM: Publish public notice of EOS status | 0 |
9.1.1.3 | MDM: Share patient risks found after market | 0 |
9.1.2 | HCP: Question EOS information from manufacturer | 0 |
9.2.1 | MDM: Keep post-market risk duties after EOS | 0 |
9.2.2.1 | HCP: Weigh EOL and EOS risk when buying resold devices | 0 |
9.2.2.2 | HCP: controls for running a device after EOS | 0 |
9.3.1 | MDM: confirm the handover at EOS | 0 |
9.3.2 | HCP: Accept risk or move to a new device | 0 |
CL1 | Introduction to the legacy device cybersecurity guidance | 0 |
CL10 | Who is responsible at each life cycle stage | 0 |
CL2 | Scope of the legacy device guidance | 0 |
CL3 | Definitions applied in this guidance | 0 |
CL5 | The four TPLC stages at a glance | 0 |
CL6.2.2 | HCP: Risk management recommendations do not apply yet | 0 |