The items below are offered as general guidance, are for general consideration only, and must be reviewed in alignment with any posted Philips Service Bulletin with Philips service support to ensure all defined testing and verification processes are followed within product specification and regulatory requirements.
Work with Philips services support to identify and review:
1. Philips products that have been patched to protect against the SMB vulnerability being exploited by the Petya malware.
2. Philips products that may still be vulnerable to impact from the Petya malware.
3. For Philips products that are potentially vulnerable to the Petya malware, consider the following options or combination of options (where applicable and in accordance with authorized Philips service):
-Arrange for Philips service teams to apply any available Philips-approved patches or updates to your system per standard procedures.
-Consider implementing anti-virus access protection rules (Example: Per McAfee Guidance https://kc.mcafee.com/corporate/index?page=content&id=KB89540&actp=null&viewlocale=en_US&showDraft=false&platinum_status=false&locale=en_US).
-Consider blocking SMB and RDP ports per Microsoft guidance.
-Consider disabling SMBv1 on our devices if authorized by Philips for your product.
Other General Points for Customer Awareness:
1. Re-imaging an infected machine will likely overwrite/destroy information on that device.
2. Making payment to ransomware is not a Philips recommendation. Reportedly, ransom payments in response to Petya infections have not resulted in restored access to a Petya infected files or systems. If payment is made in an effort to decrypt the system, then
-Data, if and when available, should be backed up to a safe location with appropriate restoration procedures.
-Reinstall the system applications with at least one of the recommended actions to prevent re-infection to the device.
-Network segmentation will help prevent harm to the device as long as the SMB and RDP are not utilized and blocked.
SUPPORT OF MICROSOFT GENERAL RECOMMENDATIONS
On June 28th Microsoft posted their “Update on Petya malware attacks” which included Microsoft recommendations for Windows users to consider toward the identification, prevention, and mitigation of the risk of compromise from reported Windows vulnerabilities being exploited by Petya. The advisory included options for users to consider for deployment of Windows security updates and other changes to system configuration as potential countermeasures.
Philips is committed to ensuring the safety, security, integrity, and regulatory compliance of our products to be deployed and to operate within Philips approved product specifications. Therefore, in accordance with Philips policy and regulatory requirements, all changes of configuration or software to Philips products (including Windows security updates and patches) are implemented only in accordance with Philips product-specific, verified & validated, authorized, and communicated customer procedures or field actions.
Philips policy, the U.S. FDA post-market guidance, and other regulatory jurisdiction requirements state that all critical vulnerabilities must be assessed and mitigated. In the case of WannaCry and Petya, a number of Philips products are deployed with default security hardening that securely mitigates the risk of WannaCry and Petya vulnerabilities due to firewall configuration, closed ports, anti-virus/whitelisting, or other security features designed into the product architectures. In those specific cases, Philips will not require Windows security patching to mitigate against WannaCry or Petya threats since those products are not assessed to be vulnerable to exploit from WannaCry or Petya when deployed and operated within specification. Likewise, the same product-by-product assessment is made by Philips relative to other countermeasures like network port blocking that may be recommended by Microsoft but might not be applicable to all Philips products or product versions. Philips product teams therefore assess all published Windows critical vulnerabilities on a product-by-product basis routinely and document product vulnerability status into product MDS2 forms and vulnerability tables. If a product does require Microsoft security updates, configuration changes, or other actions to be taken by our customer or by Philips Customer Services, product-specific service documentation is produced by Philips product teams and made available to Philips service delivery platforms such as the Philips InCenter Customer Portal. Once posted by Philips product teams, all of these materials are accessible to contract-entitled customers, licensed representatives, and Philips Customer Service teams.
Customers entitled by service-contract to use Philips InCenter are encouraged to request and attain InCenter access and reference product-specific information posted on Philips InCenter. All customers with and without service contracts are encouraged to contact their local service support team or regional product service support as needed for current information specific to their products or Philips deployed installations as information becomes available.
Philips manufactures, sells and helps you maintain highly complex medical devices and systems. Per policy, only Philips authorized changes are allowed to be made to these systems, either by Philips personnel or under Philips explicit published direction.
Please contact your Philips service representative for specific information about potential vulnerabilities and the availability of patches for your equipment configuration.