Security and MDS Form: White Paper ACUSON Redwood Ultrasound System, Release VA10
Security and MDS Form: White Paper ACUSON Redwood Ultrasound System, Release VA10
Vulnerability and incident management Siemens Healthineers requests that any cybersecurity
or privacy incidents are reported by email to:
Siemens Healthineers cooperates with government
productsecurity@[Link]
agencies and cybersecurity researchers concerning
reported potential vulnerabilities. Our communications For all other communication with Siemens Healthineers
policy strives for coordinated disclosure. We work in about product and solution security:
this way with our customers and other parties, when [Link]@
appropriate, in response to potential vulnerabilities [Link]
and incidents in our medical devices, no matter what
the source. Yours sincerely,
2 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Contents
Basic Information ����������������������������������������������������� 4
Abbreviations ���������������������������������������������������������� 33
Disclaimer According to IEC 80001-1 ����������������������� 34
[Link]/redwood 3
Product and solution security white paper · ACUSON Redwood VA10
Basic Information
1
[Link]
2
[Link]
4 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
[Link]/redwood 5
Product and solution security white paper · ACUSON Redwood VA10
Network Information
SRS
Smart
Router Remote
Services
VPN
IN, OUT:
TCP, UCP Remote Service
Access Server
IN, OUT:
DICOM
OUT:
TCP
Network Share
6 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
[Link]/redwood 7
Product and solution security white paper · ACUSON Redwood VA10
Security Controls
• Whitelisting (Microsoft Device Guard) • You are responsible for the physical protection of the
ACUSON Redwood system VA10 software, e.g., by
Controlled use of administrative privileges operating it in a room with access control. Please note
that the system contains patient data and should be
• The system distinguishes between clinical and
protected against tampering and theft.
administrative roles. Clinical users do not require
administrative privileges. • The system is protected by Secure Boot, which blocks
unsigned boot media.
• Authorization as administrator is required for
administrative tasks. • It is possible to change the BIOS password. Please
contact Siemens Healthineers Service for support.
Authentication authorization controls
Data protection controls
• The ACUSON Redwood system VA10 software supports
Health Insurance Portability and Accountability • The system is not intended to be an archive (data at rest).
Act (HIPPA) regulation with role-based privilege
• PHI is protected by both role-based access control as
assignment and access control.
well as hard drive encryption (optional).
• The user interface of the ACUSON Redwood system
• Hard drive encryption is an optional feature that is
VA10 software provides a screen lock functionality that
implemented through Microsoft Bitlocker technology
can be engaged manually or automatically after a
and use of the TPM (Trusted Platform Module) chip
certain inactivity time. For details, please refer to the
on the system’s motherboard.
User Manual.
• The system provides auditing of PHI access control.
Continuous vulnerability assessment and remediation
• Optionally, confidentiality and integrity of PHI/PII data
• Continuous vulnerability assessment and remediation can be protected by encryption of DICOM nodes.
is performed. Note: In the VA10 software release for the ACUSON
Redwood system, encrypted communication can be
Hardening used if all connected DICOM nodes support it.
• In case of a denial of service (DoS) or malware attack, Incident response and management
the system can be taken off the network and operated
• The incident handling process is defined and executed
in a stand-alone state.
on demand to deal with incidents as mandated by the
United States FDA Post-Market Guidance documents.
8 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
The following table comprises the most relevant third-party technologies used (general drivers not included).
Open Source
Jpeg image codec used by RendererVOB and
[Link] libjpeg-turbo 1.5.2
PIMS to encode/decode image data.
[Link]
[Link]/redwood 9
Product and solution security white paper · ACUSON Redwood VA10
The following table comprises the most relevant third-party technologies used (general drivers not included).
Open Source
(Apache Software Log4net [Link] Logging library
Foundation)
Ultrasound
Siemens Ultrasound TeamViewer
[Link] Remote service tool
USA Core VA10B
(ver [Link])
10 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Open Source
cycler 0.10.0 A data processing framework.
[Link]
Open Source
[Link] SIP2 Python Client: Simple Interchange
sip 4.19.8
[Link]/ Protocol Client for Python
software/sip/download
Open Source
This package contains some modules used
[Link] logilab-common 1.2.0
by different Logilab projects.
project/logilab-common
[Link]/redwood 11
Product and solution security white paper · ACUSON Redwood VA10
The following table comprises the most relevant third-party technologies used (general drivers not included).
Open Source
Character encoding auto-detection in
[Link] chardet 2.3.0
Python. As smart as your browser.
[Link]/en/latest/
Open Source
Requests is the only Non-GMO HTTP library
[Link] Python requests 2.10.0
for Python, safe for human consumption.
kennethreitz/requests
Open Source
Installed automatically when pywin32 (220)
[Link] adodbapi 2.0
is installed.
projects/adodbapi/files/
Open Source
Installed automatically when matplotlib
[Link] mpl_toolkits N/A
(1.5.1) is installed.
1.5.1/users/[Link]
12 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Open Source
Easily download, build, install, upgrade, and
[Link] setuptools 39.2.0
uninstall Python packages.
pypa/setuptools
[Link]/redwood 13
Product and solution security white paper · ACUSON Redwood VA10
The following table comprises the most relevant third-party technologies used (general drivers not included).
Microsoft Visual
The Microsoft Visual C++ 2012
Microsoft Corporation C++ 2015 2015
Redistributable
Redistributable
Microsoft SQL
Microsoft Corporation 12.0.4232.1 PIMS Database Engine
Server
Cariac SR
Tomtec [Link]
(DicomConverter)
64 Bit HP CIO
HP Inc. Components 20.2.1 HP Print Driver
Installer
14 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Intel® Chipset
[Link] Chipset
Device Software
Intel Corporation
Intel® Processor
1.20.16.4599 Graphic driver
Graphics
Microsoft ODBC
Driver 11 for SQL 12.1.4232.0 SQL Server
Microsoft Corporation Server
Microsoft SQL
Server 2008
10.3.5500.0 SQL Server
Setup Support
Files
Microsoft SQL
Server 2012 11.0.2100.60 SQL Server
Native Client
[Link]/redwood 15
Product and solution security white paper · ACUSON Redwood VA10
The following table comprises the most relevant third-party technologies used (general drivers not included).
Microsoft SQL
Server 2014 12.1.4232.0 SQL Server
Express LocalDB
Microsoft SQL
Server 2014 RsFx 12.1.4100.1 SQL Server
Driver
Microsoft SQL
Server 2014 12.1.4232.0 SQL Server
Setup (English)
Microsoft SQL
Server 2014
12.1.4100.1 SQL Server
Transact-SQL
ScriptDom
16 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Microsoft Visual
Microsoft Corporation
C++ 2012
The Microsoft Visual C++ 2012
Redistributable 11.0.61030.0
Redistributable
(x64) –
11.0.61030
Microsoft Visual
C++ 2012 x64
The Microsoft Visual C++ 2012
Additional 11.0.61030
Redistributable
Runtime –
11.0.61030
Microsoft Visual
C++ 2012 x64
The Microsoft Visual C++ 2012
Minimum 11.0.61030
Redistributable
Runtime –
11.0.61030
Microsoft Visual
C++ 2013
The Microsoft Visual C++ 2013
Redistributable 12.0.30501.0
Redistributable
(x64) –
12.0.30501
[Link]/redwood 17
Product and solution security white paper · ACUSON Redwood VA10
The following table comprises the most relevant third-party technologies used (general drivers not included).
Microsoft Visual
C++ 2013 x64
The Microsoft Visual C++ 2013
Additional 12.0.21005
Redistributable
Runtime –
12.0.21005
Microsoft Visual
C++ 2013 x64
The Microsoft Visual C++ 2013
Minimum 12.0.21005
Redistributable
Runtime –
12.0.21005
Microsoft Visual
C++ 2015
The Microsoft Visual C++ 2015
Redistributable 14.0.24215.1
Redistributable
(x64/x64) –
14.0.24215
Microsoft Visual
C++ 2015 x64
The Microsoft Visual C++ 2015
Additional 14.0.24215
Redistributable
Microsoft Corporation Runtime –
14.0.24215
Microsoft Visual
C++ 2015 x64
The Microsoft Visual C++ 2015
Minimum 14.0.24215
Redistributable
Runtime –
14.0.24215
Microsoft VSS
Writer for SQL 12.1.4100.1 Database Engine
Server 2014
Microsoft Web
2.0.1070 WebDriver
Deploy 2.0
Microsoft Web
Farm Framework 2.2.1341 WebDriver
Version 2.2
Microsoft Web
Platform Installer 3.0.5 WebDriver
3.0
NVIDIA Graphics
NVIDIA Corporation 425.31 Graphics Driver
Driver 425.31
18 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Open Source
Python Software Python 3.6.5 Python Script
Foundation
The IT Machine
Blue Elephant Systems
with correlation 1.2.5
GmbH
module
Windows 10
Microsoft Corporation Enterprise 2016 2016 LTSB Operation System
lTSB
Realtek High
Realtek 6.0.1.8036 HD audio driver
Definition Audio
Open Source
muParser 2.2.5 Math expression parser library
(Ingo Berg)
[Link]/redwood 19
Product and solution security white paper · ACUSON Redwood VA10
The following table comprises the most relevant third-party technologies used (general drivers not included).
MSXML Parser
Microsoft Corporation 4.20.9849.0 Microsoft XML Parser
and SDK 4 SP2
20 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Open Source
Multimedia framework, able to decode,
[Link]
encode, transcode, mux, demux, stream,
[Link]/blog/2015/01/20/ ffmpeg 2.7.2
filter and play pretty much anything that
compiling-ffmpeg-with-
humans and machines have created.
windows-tools/
Sony
Sony UP-D711MD BW [Link] Black and white thermal printer driver
Printer Driver
Intel® Ethernet
Intel Connection [Link] Gigabit ethernet adapter driver
I218-LM
[Link]/redwood 21
Product and solution security white paper · ACUSON Redwood VA10
1-1 The device is connected via Ethernet cable or wireless protocol to the hospital using a TCP/IP network with
1Gb/s performance:
• If the network is down, the network services (see below) are not available which can lead to the risks stated
below.
• If the network is unavailable, medical images cannot be transferred for remote c onsultation.
• If the wireless network is incorrectly protected (for example, open Wi-Fi configuration), the attack surface of
all the connected devices is much larger, which can lead to the risks stated below.
• If the recommended network performance (1Gbit/s) is not provided, the transfer of images is extended, and
availability of images at destinations (e.g., for consulting) is delayed.
• Only the protocols shown in the table of used ports are needed for communication.
22 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
2-1 Connection of the system to a network that includes other equipment could result in previously unidentified
risks to patients, operators or third parties. The RESPONSIBLE ORGANIZATION should identify, evaluate and
control these risks.
2-2 Subsequent changes to the network could introduce new RISKS and require additional analysis.
2-4 The RESPONSIBLE ORGANIZATION is fully responsible for the security of the network to which the device is
connected.
2-5 The RESPONSIBLE ORGANIZATION is fully responsible to ensure staff who have access to the device do not
have the opportunity to provide any harm to the system.
2-6 The RESPONSIBLE ORGANIZATION has to ensure that the internal network cannot be accessed physically by
non-authorized persons.
2-7 Staff of the RESPONSIBLE ORGANIZATION has to be trained in security. The RESPONSIBLE ORGANIZATION is
responsible for providing this.
2-8 The RESPONSIBLE ORGANIZATION is fully responsible to ensure that only authorized medical/administrative
staff shall have access to the device.
2-9 The RESPONSIBLE ORGANIZATION is fully responsible to ensure that visitors/patients do not have unsupervised
physical access to the system.
2-10 The RESPONSIBLE ORGANIZATION shall provide access to the system for device administrators and device
service engineers.
2-11 The RESPONSIBLE ORGANIZATION has at least one staff person with administrative rights who has access to
the system.
2-12 The RESPONSIBLE ORGANIZATION shall ensure that neither access from the public internet or the
organization’s intranet to the device is possible.
2-13 The RESPONSIBLE ORGANIZATION is responsible to ensure physical security for the device.
2-14 The RESPONSIBLE ORGANIZATION shall ensure that access to services for the device from other equipment is
possible only on a need-to-do basis. An adequate network topology with appropriate firewall settings shall be
used.
2-15 The RESPONSIBLE ORGANIZATION is responsible for a secure infrastructure that makes it impossible to
change, prevent, or tamper with data in transit in any way.
2-17 The RESPONSIBLE ORGANIZATION is responsible for the hard drive encryption keys and for preventing the
theft or loss of those keys.
[Link]/redwood 23
Product and solution security white paper · ACUSON Redwood VA10
3-1 To integrate the system into the clinical workflow, the whole ultrasound system will interact as a DICOM node
in the clinical network.
3-2 The system is DICOM-compliant, allowing it to be connected to a network with other compliant devices for
the exchange of images. Networking allows the transmission of images acquired to other DICOM-compatible
review stations or PACS. A list of all patients ever imaged can be kept on the Radiology PACS making future
retrievals fast and easy.
3-3 The system connects to the network through an Ethernet cable or a wireless protocol. The network interfaces
allow DICOM connections to specific clinical systems such as a Radiology PACS or printer. Patient demographic
data will be received via DICOM; acquired images will be sent to the Radiology PACS or DICOM workstations
for detailed viewing and long-term storage.
24 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
[Link]/redwood 25
Product and solution security white paper · ACUSON Redwood VA10
26 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
A Can this device display, transmit, or maintain private data (including electronic Protected Health Yes
Information [ePHI])?
B.1 Demographic (e.g., name, address, location, unique identification number)? Yes –
B.2 Medical record (e.g., medical record #, account #, test or treatment date, device identification number)? Yes –
B.3 Diagnostic/therapeutic (e.g., photo/radiograph, test results, or physiologic data with identifying Yes –
characteristics)?
C.1 Maintain private data temporarily in volatile memory (i.e., until cleared by power-off or reset)? Yes –
D Mechanisms used for the transmitting, importing/exporting of private data – Can the device:
D.3 Retrieve private data from or record private data to removable media (e.g., disk, DVD, CD-ROM, tape, Yes –
CF/SD card, memory stick, etc.)?
D.4 Transmit/receive or import/export private data via dedicated cable connection (e.g., IEEE 1073, Yes –
serial port, USB, FireWire, etc.)?
D.5 Transmit/receive private data via a wired network connection (e.g., LAN, WAN, VPN, intranet, Yes –
Internet, etc.)?
D.6 Transmit/receive private data via an integrated wireless network connection (e.g., WiFi, Bluetooth, Yes –
infrared, etc.)?
[Link]/redwood 27
Product and solution security white paper · ACUSON Redwood VA10
Security capabilities
Refer to Section 2.3.2 of this standard for the proper interpretation of information requested in this form. Yes, No, Note #
N/A, or
See Note
1-1 Can the device be configured to force reauthorization of logged-in user(s) after a predetermined Yes –
length of inactivity (e.g., auto-logoff, session lock, password protected screen saver)?
1-1.1 Is the length of inactivity time before auto-logoff/screen lock user or administrator configurable? Yes 1
(Indicate time [fixed or configurable range] in notes.)
1-1.2 Can auto-logoff/screen lock be manually invoked (e.g., via a shortcut key or proximity sensor, etc.) Yes –
by the user?
2-2 Indicate which of the following events are recorded in the audit log:
2-3 Indicate what information is used to identify individual events recorded in the audit log:
AUTH notes: Log items are encrypted as they are added to the audit log.
3 Authorization (AUTH)
The ability of the device to determine the authorization of users.
3-1 Can the device prevent access to unauthorized users through user login requirements or other Yes –
mechanism?
3-2 Can users be assigned different privilege levels within an application based on ‘roles’ (e.g., guests, Yes –
regular users, power users, administrators, etc.)?
3-3 Can the device owner/operator obtain unrestricted administrative privileges (e.g., access operating No –
system or application via local root or admin account)?
28 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Refer to Section 2.3.2 of this standard for the proper interpretation of information requested in this form. Yes, No, Note #
N/A, or
See Note
4-1 Can the device owner/operator reconfigure product security capabilities? Yes –
CNFS notes: The admin via the security system configuration screen can configure the security system such as
firewall. In addition, only the admin can configure data export capabilities including: DICOM and
Network Share
5-1 Can relevant OS and device security patches be applied to the device as they become available? Yes 1
CSUP notes: 1. Only security patches that become available through Siemens are subject to be installed in the
system.
2. Siemens Remote Service can push patches to system which are then installed once approved
by the user.
6-1 Does the device provide an integral capability to de-identify private data? Yes –
DIDT notes: There is a feature in Patient Browser which will clear the patient banner and clear the DICOM tags
identifying a specific patient.
7-1 Does the device have an integral data backup capability (i.e., backup to remote storage or Yes –
removable media such as tape, disk)?
DTBK notes: A patient data is uploaded to PACS either during or after each exam. A patient data can be backed up to
USB or DVD. The system configuration can be backed up to USB.
8-1 Does the device incorporate an emergency access (“break-glass”) feature? Yes –
EMRG notes: The system will allow for an emergency exam to be performed. Access to main aspects of the system
other than that required to perform the exam are restricted.
9-1 Does the device ensure the integrity of stored data with implicit or explicit error detection/correction No –
technology?
[Link]/redwood 29
Product and solution security white paper · ACUSON Redwood VA10
Refer to Section 2.3.2 of this standard for the proper interpretation of information requested in this form. Yes, No, Note #
N/A, or
See Note
10-1 Does the device support the use of anti-malware software (or other anti-malware mechanism)? Yes –
10-1.2 Does notification of malware detection occur in the device user interface? Yes –
10-1.3 Can only manufacturer-authorized persons repair systems when malware has been detected? Yes –
10-3 Can the device owner/operator (technically/physically) update virus definitions on N/A –
manufacturer-installed antivirus software?
MLDP notes: DeviceGuard is incorporated into the system. Only software signed by Siemens can execute.
11-1 Does the device provide/support any means of node authentication that assures both the sender and Yes –
the recipient of data are known to each other and are authorized to receive transferred information?
NAUT notes: ommunication to a PACS can be configured to use TLS certificates. Only if encrypted DICOM
C
functionality is being used.
12-1 Does the device support user/operator-specific username(s) and password(s) for at least one user? Yes –
12-1.1 Does the device support unique user/operator-specific IDs and passwords for multiple users? Yes –
12-2 Can the device be configured to authenticate users through an external authentication service No –
(e.g., MS Active Directory, NDS, LDAP, etc.)?
12-3 Can the device be configured to lock out a user after a certain number of unsuccessful logon Yes –
attempts?
12-6 Can the device be configured to enforce creation of user account passwords that meet established Yes –
complexity rules?
12-7 Can the device be configured so that account passwords expire periodically? Yes –
PAUT notes: Accounts and passwords for those accounts are configured by the administrator of the system. The
password aging can be configured from 0 (never expires) to 999 days. The default setting is 42 days.
13-1 Are all device components maintaining private data (other than removable media) physically Yes –
secure (i.e., cannot remove without tools)?
30 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Refer to Section 2.3.2 of this standard for the proper interpretation of information requested in this form. Yes, No, Note #
N/A, or
See Note
14-1 In the notes section, list the provided or required (separately purchased and/or delivered) See Note –
operating system(s) – including version number(s).
14-2 Is a list of other third party applications provided by the manufacturer available? Yes –
15-1 Does the device employ any hardening measures? Please indicate in the notes the level of Yes 1
conformance to any industry-recognized hardening standards.
15-2 Does the device employ any mechanism (e.g., release-specific hash key, checksums, etc.) to ensure Yes –
the installed program/update is the manufacturer-authorized program or software update?
15-3 Does the device have external communication capability (e.g., network, modem, etc.)? Yes –
15-4 Does the file system allow the implementation of file-level access controls (e.g., New Technology Yes –
File System (NTFS) for MS Windows platforms)?
15-5 Are all accounts which are not required for the intended use of the device disabled or deleted, Yes –
for both users and applications?
15-6 Are all shared resources (e.g., file shares) which are not required for the intended use of the device, disabled? Yes –
15-7 Are all communication ports which are not required for the intended use of the device closed/disabled? Yes –
15-8 Are all services (e.g., telnet, file transfer protocol [FTP], internet information server [IIS], etc.), which Yes –
are not required for the intended use of the device deleted/disabled?
15-9 Are all applications (COTS applications as well as OS-included applications, e.g., MS Internet Explorer, Yes –
etc.) which are not required for the intended use of the device deleted/disabled?
15-10 Can the device boot from uncontrolled or removable media (i.e., a source other than an internal Yes 2
drive or memory component)?
15-11 Can software or hardware not authorized by the device manufacturer be installed on the device No –
without the use of tools?
16-1 Are security-related features documented for the device user? Yes –
16-2 Are instructions available for device/media sanitization (i.e., instructions for how to achieve Yes –
the permanent deletion of personal or other sensitive data)?
SGUD notes: The manual of Service Configuration explains how to delete study data
[Link]/redwood 31
Product and solution security white paper · ACUSON Redwood VA10
Refer to Section 2.3.2 of this standard for the proper interpretation of information requested in this form. Yes, No, Note #
N/A, or
See Note
STCF notes: Microsoft BitLocker can be enabled at the factory or after customer installation
18 Transmission confidentiality (TXCF)
The ability of the device to ensure the confidentiality of transmitted private data.
18-1 Can private data be transmitted only via a point-to-point dedicated cable? No –
18-2 Is private data encrypted prior to transmission via a network or removable media? See Note –
(If yes, indicate in the notes which encryption standard is implemented.)
18-3 Is private data transmission restricted to a fixed list of network destinations? Yes –
TXCF notes: Encryption via industry standards is available with wireless networking. Application layer encryption is
available only if encrypted DICOM functionality is being used. Secure DICOM can be configured to use
TLS 1.0, 1.1 or 1.2. DICOM is encrypted by TLS_RSA_WITH_128_CBC_SHA or TLS_RSA_WITH_3DES_
EDE_CBC_SHA.
19 Transmission integrity (TXIG)
The ability of the device to ensure the integrity of transmitted private data.
19-1 Does the device support any mechanism intended to ensure data is not modified during transmission? No –
(If yes, describe in the notes section how this is achieved.)
TXIG notes: N/A
20-2 Can the device restrict remote access to/from specified devices or users or network locations (e.g., Yes –
specific IP addresses)?
20-2.1 Can the device be configured to require the local user to accept or initiate remote access? Yes –
32 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Abbreviations
[Link]/redwood 33
Product and solution security white paper · ACUSON Redwood VA10
34 [Link]/redwood
ACUSON Redwood VA10 · Product and solution security white paper
Statement on FDA
Cybersecurity Guidance
[Link]/redwood 35
Please note that the learning material is for training purposes only!
For the proper use of the software or hardware, please always use the Operator Manual
or Instructions for Use (hereinafter collectively “Operator Manual”) issued by Siemens
Healthineers. This material is to be used as training material only and shall by no means
substitute the Operator Manual. Any material used in this training will not be updated
on a regular basis and does not necessarily reflect the latest version of the software and
hardware available at the time of the training.
The Operator's Manual shall be used as your main reference, in particular for relevant
safety information like warnings and cautions.
Note: Some functions shown in this material are optional and might not be part of your
system.
ACUSON Redwood and UltraArt universal image processing are trademarks of Siemens
Medical
Solutions USA, Inc.
All names and data of patients, parameters and configuration dependent designations
are fictional and examples only.
All rights, including rights created by patent grant or registration of a utility model or
design, are reserved.
Published by Siemens Medical Solutions USA, Inc. · 8392 1219 online · © Siemens Medical Solutions USA, Inc., 2019