Solicitation Attachment B - NEMA MDS2 Worksheet.xlsx
XLSX spreadsheet 44 KB Posted
- Attached to
- Nationwide Infusion Pump Requirement Federal contract opportunity
- Solicitation number
- 36C24125R0070_1
About this file
The file is a NEMA MDS2 Worksheet, a comprehensive medical device security assessment form designed to evaluate the cybersecurity characteristics of medical devices. The extensive spreadsheet contains detailed sections covering multiple security domains including personally identifiable information management, authentication mechanisms, malware protection, network connectivity, software updates, data encryption, remote service capabilities, and physical security controls. The worksheet is structured to systematically document a medical device's security features across various international standards including IEC TR 80001-2-2:2012, NIST SP 800-53 Rev. 4, ISO 27002:2013, and others, with specific focus on healthcare technology security considerations.
The form requires manufacturers to provide granular details about device security capabilities, such as user authentication methods, audit logging, emergency access features, data integrity mechanisms, third-party component management, software bill of materials, and potential vulnerabilities. Key areas of assessment include node authentication, transmission confidentiality, system hardening, access controls, encryption capabilities, remote service protocols, and potential security update processes. The comprehensive nature of the worksheet indicates a rigorous approach to evaluating medical device cybersecurity, ensuring potential users can thoroughly understand a device's security posture before implementation.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 36C24125R0070 0003.docx | DOCX document | |
| Amendment 0003 Attachment - Questions and Answers.xlsx | XLSX spreadsheet | |
| 36C24125R0070 0002.pdf | ||
| 36C24125R0070 0001.pdf | ||
| Amendment 0001 Attachment - Revised Statement of Work.pdf | ||
| Amendment 0001 Attachment - Questions and Answers.xlsx | XLSX spreadsheet | |
| Amendment 0001 Attachment - Revised FAR 52.212-1 Instructions to Offerors.pdf | ||
| Amendment 0001 Attachment - Revised FAR 52.212-2 Evaluation.pdf | ||
| Solicitation Attachment A - Pricing Worksheet.xlsx | XLSX spreadsheet | |
| Solicitation Attachment C - VA Directive 6550 Appendix A.pdf | ||
| 36C24125R0070.pdf |
Show all 11
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
mds2-form
| Manufacturer Disclosure Statement for Medical Device Security -- MDS2 | ||||||
| ______ | ______ | ______ | ______ | |||
| Question ID | Question | See note | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |
| DOC-1 | Manufacturer Name | ______ | __ | |||
| DOC-2 | Device Description | ______ | __ | |||
| DOC-3 | Device Model | ______ | __ | |||
| DOC-4 | Document ID | ______ | __ | |||
| DOC-5 | Manufacturer Contact Information | ______ | __ | |||
| DOC-6 | Intended use of device in network-connected environment: | ______ | __ | |||
| DOC-7 | Document Release Date | ______ | __ | |||
| DOC-8 | Coordinated Vulnerability Disclosure: Does the manufacturer have a vulnerability disclosure program for this device? | ______ | __ | |||
| DOC-9 | ISAO: Is the manufacturer part of an Information Sharing and Analysis Organization? | ______ | __ | |||
| DOC-10 | Diagram: Is a network or data flow diagram available that indicates connections to other system components or expected external resources? | __ | ||||
| DOC-11 | SaMD: Is the device Software as a Medical Device (i.e. software-only, no hardware)? | ______ | __ | |||
| DOC-11.1 | Does the SaMD contain an operating system? | ______ | __ | |||
| DOC-11.2 | Does the SaMD rely on an owner/operator provided operating system? | ______ | __ | |||
| DOC-11.3 | Is the SaMD hosted by the manufacturer? | ______ | ||||
| DOC-11.4 | Is the SaMD hosted by the customer? | ______ | __ |
Yes, No, N/A, or
| See Note | Note # | ||||||
| MANAGEMENT OF PERSONALLY IDENTIFIABLE INFORMATION | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | ||||
| MPII-1 | Can this device display, transmit, store, or modify personally identifiable information (e.g. electronic Protected Health Information (ePHI))? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-2 | Does the device maintain personally identifiable information? | ______ | AR-2 | A.15.1.4 | |||
| MPII-2.1 | Does the device maintain personally identifiable information temporarily in volatile memory (i.e., until cleared by power-off or reset)? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-2.2 | Does the device store personally identifiable information persistently on internal media? | ______ | __ | ||||
| MPII-2.3 | Is personally identifiable information preserved in the device’s non-volatile memory until explicitly erased? | ______ | __ | ||||
| MPII-2.4 | Does the device store personally identifiable information in a database? | ______ | __ | ||||
| MPII-2.5 | Does the device allow configuration to automatically delete local personally identifiable information after it is stored to a long term solution? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-2.6 | Does the device import/export personally identifiable information with other systems (e.g., a wearable monitoring device might export personally identifiable information to a server)? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-2.7 | Does the device maintain personally identifiable information when powered off, or during power service interruptions? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-2.8 | Does the device allow the internal media to be removed by a service technician (e.g., for separate destruction or customer retention)? | ______ | __ | ||||
| MPII-2.9 | Does the device allow personally identifiable information records be stored in a separate location from the device’s operating system (i.e. secondary internal drive, alternate drive partition, or remote storage location)? | ______ | AR-2 | A.15.1.4 | |||
| MPII-3 | Does the device have mechanisms used for the transmitting, importing/exporting of personally identifiable information? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-3.1 | Does the device display personally identifiable information (e.g., video display, etc.)? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-3.2 | Does the device generate hardcopy reports or images containing personally identifiable information? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-3.3 | Does the device retrieve personally identifiable information from or record personally identifiable information to removable media (e.g., removable-HDD, USB memory, DVD-R/RW,CD-R/RW, tape, CF/SD card, memory stick, etc.)? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-3.4 | Does the device transmit/receive or import/export personally identifiable information via dedicated cable connection (e.g., RS-232, RS-423, USB, FireWire, etc.)? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-3.5 | Does the device transmit/receive personally identifiable information via a wired network connection (e.g., RJ45, fiber optic, etc.)? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-3.6 | Does the device transmit/receive personally identifiable information via a wireless network connection (e.g., WiFi, Bluetooth, NFC, infrared, cellular, etc.)? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-3.7 | Does the device transmit/receive personally identifiable information over an external network (e.g., Internet)? | ______ | __ | AR-2 | A.15.1.4 | ||
| MPII-3.8 | Does the device import personally identifiable information via scanning a document? | ______ | |||||
| MPII-3.9 | Does the device transmit/receive personally identifiable information via a proprietary protocol? | ______ | |||||
| MPII-3.10 | Does the device use any other mechanism to transmit, import or export personally identifiable information? | ______ | __ | AR-2 | A.15.1.4 | ||
| Management of Private Data notes: | AR-2 | A.15.1.4 | |||||
| AUTOMATIC LOGOFF (ALOF) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | ||||
| The device's ability to prevent access and misuse by unauthorized users if device is left idle for a period of time. | |||||||
| ALOF-1 | Can the device be configured to force reauthorization of logged-in user(s) after a predetermined length of inactivity (e.g., auto-logoff, session lock, password protected screen saver)? | ______ | __ | Section 5.1, ALOF | AC-12 | None | |
| ALOF-2 | Is the length of inactivity time before auto-logoff/screen lock user or administrator configurable? | ______ | __ | Section 5.1, ALOF | AC-11 | A.11.2.8, A.11.2.9 |
| AUDIT CONTROLS (AUDT) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability to reliably audit activity on the device. | ||||||
| AUDT-1 | Can the medical device create additional audit logs or reports beyond standard operating system logs? | ______ | __ | Section 5.2, AUDT | AU-1 | A.5.1.1, A.5.1.2, A.6.1.1, A.12.1.1, A.18.1.1, A.18.2.2 |
| AUDT-1.1 | Does the audit log record a USER ID? | ______ | __ | |||
| AUDT-1.2 | Does other personally identifiable information exist in the audit trail? | Section 5.2, AUDT | AU-2 | None | ||
| AUDT-2 | Are events recorded in an audit log? If yes, indicate which of the following events are recorded in the audit log: | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.1 | Successful login/logout attempts? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.2 | Unsuccessful login/logout attempts? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.3 | Modification of user privileges? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.4 | Creation/modification/deletion of users? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.5 | Presentation of clinical or PII data (e.g. display, print)? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.6 | Creation/modification/deletion of data? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.7 | Import/export of data from removable media (e.g. USB drive, external hard drive, DVD)? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.8 | Receipt/transmission of data or commands over a network or point-to-point connection? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.8.1 | Remote or on-site support? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.8.2 | Application Programming Interface (API) and similar activity? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.9 | Emergency access? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.10 | Other events (e.g., software updates)? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-2.11 | Is the audit capability documented in more detail? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-3 | Can the owner/operator define or select which events are recorded in the audit log? | Section 5.2, AUDT | AU-2 | None | ||
| AUDT-4 | Is a list of data attributes that are captured in the audit log for an event available? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-4.1 | Does the audit log record date/time? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-4.1.1 | Can date and time be synchronized by Network Time Protocol (NTP) or equivalent time source? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-5 | Can audit log content be exported? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-5.1 | Via physical media? | ______ | __ | |||
| AUDT-5.2 | Via IHE Audit Trail and Node Authentication (ATNA) profile to SIEM? | ______ | __ | |||
| AUDT-5.3 | Via Other communications (e.g., external service device, mobile applications)? | ______ | __ | |||
| AUDT-5.4 | Are audit logs encrypted in transit or on storage media? | ______ | __ | |||
| AUDT-6 | Can audit logs be monitored/reviewed by owner/operator? | ______ | __ | |||
| AUDT-7 | Are audit logs protected from modification? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUDT-7.1 | Are audit logs protected from access? | |||||
| AUDT-8 | Can audit logs be analyzed by the device? | ______ | __ | Section 5.2, AUDT | AU-2 | None |
| AUTHORIZATION (AUTH) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability of the device to determine the authorization of users. | ||||||
| AUTH-1 | Does the device prevent access to unauthorized users through user login requirements or other mechanism? | ______ | __ | Section 5.3, AUTH | IA-2 | A.9.2.1 |
| AUTH-1.1 | Can the device be configured to use federated credentials management of users for authorization (e.g., LDAP, OAuth)? | ______ | __ | Section 5.3, AUTH | IA-2 | A.9.2.1 |
| AUTH-1.2 | Can the customer push group policies to the device (e.g., Active Directory)? | ______ | __ | Section 5.3, AUTH | IA-2 | A.9.2.1 |
| AUTH-1.3 | Are any special groups, organizational units, or group policies required? | ______ | __ | Section 5.3, AUTH | IA-2 | A.9.2.1 |
| AUTH-2 | Can users be assigned different privilege levels based on 'role' (e.g., user, administrator, and/or service, etc.)? | ______ | __ | Section 5.3, AUTH | IA-2 | A.9.2.1 |
| AUTH-3 | Can the device owner/operator grant themselves unrestricted administrative privileges (e.g., access operating system or application via local root or administrator account)? | ______ | __ | Section 5.3, AUTH | IA-2 | A.9.2.1 |
| AUTH-4 | Does the device authorize or control all API access requests? | ______ | __ | Section 5.3, AUTH | IA-2 | A.9.2.1 |
| AUTH-5 | Does the device run in a restricted access mode, or ‘kiosk mode’, by default? | ______ | __ |
| CYBER SECURITY PRODUCT UPGRADES (CSUP) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | ||||||
| The ability of on-site service staff, remote service staff, or authorized customer staff to install/upgrade device's security patches. | |||||||||
| CSUP-1 | Does the device contain any software or firmware which may require security updates during its operational life, either from the device manufacturer or from a third-party manufacturer of the software/firmware? If no, answer “N/A” to questions in this section. | ______ | __ | ||||||
| CSUP-2 | Does the device contain an Operating System? If yes, complete 2.1-2.4. | ______ | __ | ||||||
| CSUP-2.1 | Does the device documentation provide instructions for owner/operator installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-2.2 | Does the device require vendor or vendor-authorized service to install patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-2.3 | Does the device have the capability to receive remote installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-2.4 | Does the medical device manufacturer allow security updates from any third-party manufacturers (e.g., Microsoft) to be installed without approval from the manufacturer? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-3 | Does the device contain Drivers and Firmware? If yes, complete 3.1-3.4. | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-3.1 | Does the device documentation provide instructions for owner/operator installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-3.2 | Does the device require vendor or vendor-authorized service to install patches or software updates? | ______ | __ | ||||||
| CSUP-3.3 | Does the device have the capability to receive remote installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-3.4 | Does the medical device manufacturer allow security updates from any third-party manufacturers (e.g., Microsoft) to be installed without approval from the manufacturer? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-4 | Does the device contain Anti-Malware Software? If yes, complete 4.1-4.4. | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-4.1 | Does the device documentation provide instructions for owner/operator installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-4.2 | Does the device require vendor or vendor-authorized service to install patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-4.3 | Does the device have the capability to receive remote installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-4.4 | Does the medical device manufacturer allow security updates from any third-party manufacturers (e.g., Microsoft) to be installed without approval from the manufacturer? | ______ | __ | ||||||
| CSUP-5 | Does the device contain Non-Operating System commercial off-the-shelf components? If yes, complete 5.1-5.4. | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-5.1 | Does the device documentation provide instructions for owner/operator installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-5.2 | Does the device require vendor or vendor-authorized service to install patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-5.3 | Does the device have the capability to receive remote installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-5.4 | Does the medical device manufacturer allow security updates from any third-party manufacturers (e.g., Microsoft) to be installed without approval from the manufacturer? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-6 | Does the device contain other software components (e.g., asset management software, license management)? If yes, please provide details or refernce in notes and complete 6.1-6.4. | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-6.1 | Does the device documentation provide instructions for owner/operator installation of patches or software updates? | ______ | __ | ||||||
| CSUP-6.2 | Does the device require vendor or vendor-authorized service to install patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-6.3 | Does the device have the capability to receive remote installation of patches or software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-6.4 | Does the medical device manufacturer allow security updates from any third-party manufacturers (e.g., Microsoft) to be installed without approval from the manufacturer? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-7 | Does the manufacturer notify the customer when updates are approved for installation? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-8 | Does the device perform automatic installation of software updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-9 | Does the manufacturer have an approved list of third-party software that can be installed on the device? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-10 | Can the owner/operator install manufacturer-approved third-party software on the device themselves? | ______ | __ | ||||||
| CSUP-10.1 | Does the system have mechanism in place to prevent installation of unapproved software? | ______ | __ | ||||||
| CSUP-11 | Does the manufacturer have a process in place to assess device vulnerabilities and updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-11.1 | Does the manufacturer provide customers with review and approval status of updates? | ______ | __ | Y/N | Y/N | Y/N | |||
| CSUP-11.2 | Is there an update review cycle for the device? | ______ | __ | Y/N | Y/N | Y/N | |||
| Device Software | Device Firmware | Security Addons |
| HEALTH DATA DE-IDENTIFICATION (DIDT) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability of the device to directly remove information that allows identification of a person. | ||||||
| DIDT-1 | Does the device provide an integral capability to de-identify personally identifiable information? | ______ | __ | Section 5.6, DIDT | None | ISO 27038 |
| DIDT-1.1 | Does the device support de-identification profiles that comply with the DICOM standard for de-identification? | ______ | __ | Section 5.6, DIDT | None | ISO 27038 |
| DATA BACKUP AND DISASTER RECOVERY (DTBK) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability to recover after damage or destruction of device data, hardware, software, or site configuration information. | ||||||
| DTBK-1 | Does the device maintain long term primary storage of personally identifiable information / patient information (e.g. PACS)? | ______ | __ | |||
| DTBK-2 | Does the device have a “factory reset” function to restore the original device settings as provided by the manufacturer? | ______ | __ | Section 5.7, DTBK | CP-9 | A.12.3.1 |
| DTBK-3 | Does the device have an integral data backup capability to removable media? | ______ | __ | Section 5.7, DTBK | CP-9 | A.12.3.1 |
| DTBK-4 | Does the device have an integral data backup capability to remote storage? | |||||
| DTBK-5 | Does the device have a backup capability for system configuration information, patch restoration, and software restoration? | |||||
| DTBK-6 | Does the device provide the capability to check the integrity and authenticity of a backup? | ______ | __ | Section 5.7, DTBK | CP-9 | A.12.3.1 |
| EMERGENCY ACCESS (EMRG) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability of the device user to access personally identifiable information in case of a medical emergency situation that requires immediate access to stored personally identifiable information. | ||||||
| EMRG-1 | Does the device incorporate an emergency access (i.e. “break-glass”) feature? | ______ | __ | Section 5.8, EMRG | SI-17 | None |
| HEALTH DATA INTEGRITY AND AUTHENTICITY (IGAU) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| How the device ensures that the stored data on the device has not been altered or destroyed in a non-authorized manner and is from the originator. | ||||||
| IGAU-1 | Does the device provide data integrity checking mechanisms of stored health data (e.g., hash or digital signature)? | ______ | __ | Section 5.9, IGAU | SC-28 | A.18.1.3 |
| IGAU-2 | Does the device provide error/failure protection and recovery mechanisms for stored health data (e.g., RAID-5)? | ______ | __ | Section 5.9, IGAU | SC-28 | A.18.1.3 |
| MALWARE DETECTION/PROTECTION (MLDP) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability of the device to effectively prevent, detect and remove malicious software (malware). | ||||||
| MLDP-1 | Is the device capable of hosting executable software? | ______ | __ | Section 5.10, MLDP | ||
| MLDP-2 | Does the device support the use of anti-malware software (or other anti-malware mechanism)? Provide details or reference in notes. | ______ | __ | Section 5.10, MLDP | SI-3 | A.12.2.1 |
| MLDP-2.1 | Does the device include anti-malware software by default? | ______ | __ | Section 5.10, MLDP | CM-5 | A.9.2.3, A.9.4.5, A.12.1.2, A.12.1.4, A.12.5.1 |
| MLDP-2.2 | Does the device have anti-malware software available as an option? | ______ | __ | Section 5.10, MLDP | AU-6 | A.12.4.1, A.16.1.2, A.16.1.4 |
| MLDP-2.3 | Does the device documentation allow the owner/operator to install or update anti-malware software? | ______ | __ | Section 5.10, MLDP | CP-10 | A.17.1.2 |
| MLDP-2.4 | Can the device owner/operator independently (re-)configure anti-malware settings? | ______ | __ | Section 5.10, MLDP | AU-2 | None |
| MLDP-2.5 | Does notification of malware detection occur in the device user interface? | ______ | ||||
| MLDP-2.6 | Can only manufacturer-authorized persons repair systems when malware has been detected? | ______ | ||||
| MLDP-2.7 | Are malware notifications written to a log? | ______ | ||||
| MLDP-2.8 | Are there any restrictions on anti-malware (e.g., purchase, installation, configuration, scheduling)? | ______ | ||||
| MLDP-3 | If the answer to MLDP-2 is NO, and anti-malware cannot be installed on the device, are other compensating controls in place or available? | ______ | __ | Section 5.10, MLDP | SI-2 | A.12.6.1, A.14.2.2, A.14.2.3, A.16.1.3 |
| MLDP-4 | Does the device employ application whitelisting that restricts the software and services that are permitted to be run on the device? | ______ | __ | Section 5.10, MLDP | SI-3 | A.12.2.1 |
| MLDP-5 | Does the device employ a host-based intrusion detection/prevention system? | ______ | __ | Section 5.10, MLDP | SI-4 | None |
| MLDP-5.1 | Can the host-based intrusion detection/prevention system be configured by the customer? | ______ | __ | Section 5.10, MLDP | CM-7 | A.12.5.1 |
| MLDP-5.2 | Can a host-based intrusion detection/prevention system be installed by the customer? | ______ | __ | Section 5.10, MLDP |
| NODE AUTHENTICATION (NAUT) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability of the device to authenticate communication partners/nodes. | ||||||
| NAUT-1 | Does the device provide/support any means of node authentication that assures both the sender and the recipient of data are known to each other and are authorized to receive transferred information (e.g. Web APIs, SMTP, SNMP)? | ______ | __ | Section 5.11, NAUT | SC-23 | None |
| NAUT-2 | Are network access control mechanisms supported (E.g., does the device have an internal firewall, or use a network connection white list)? | ______ | __ | Section 5.11, NAUT | SC-7 | A.13.1.1, A.13.1.3, A.13.2.1,A.14.1.3 |
| NAUT-2.1 | Is the firewall ruleset documented and available for review? | ______ | __ | |||
| NAUT-3 | Does the device use certificate-based network connection authentication? | ______ | __ |
| CONNECTIVITY CAPABILITIES (CONN) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| All network and removable media connections must be considered in determining appropriate security controls. This section lists connectivity capabilities that may be present on the device. | ||||||
| CONN-1 | Does the device have hardware connectivity capabilities? | ______ | __ | |||
| CONN-1.1 | Does the device support wireless connections? | ______ | __ | |||
| CONN-1.1.1 | Does the device support Wi-Fi? | ______ | __ | |||
| CONN-1.1.2 | Does the device support Bluetooth? | ______ | __ | |||
| CONN-1.1.3 | Does the device support other wireless network connectivity (e.g. LTE, Zigbee, proprietary)? | ______ | __ | |||
| CONN-1.1.4 | Does the device support other wireless connections (e.g., custom RF controls, wireless detectors)? | ______ | __ | |||
| CONN-1.2 | Does the device support physical connections? | ______ | __ | |||
| CONN-1.2.1 | Does the device have available RJ45 Ethernet ports? | ______ | __ | |||
| CONN-1.2.2 | Does the device have available USB ports? | ______ | __ | |||
| CONN-1.2.3 | Does the device require, use, or support removable memory devices? | ______ | __ | |||
| CONN-1.2.4 | Does the device support other physical connectivity? | ______ | __ | |||
| CONN-2 | Does the manufacturer provide a list of network ports and protocols that are used or may be used on the device? | ______ | __ | |||
| CONN-3 | Can the device communicate with other systems within the customer environment? | ______ | __ | |||
| CONN-4 | Can the device communicate with other systems external to the customer environment (e.g., a service host)? | ______ | __ | |||
| CONN-5 | Does the device make or receive API calls? | ______ | __ | |||
| CONN-6 | Does the device require an internet connection for its intended use? | ______ | __ | |||
| CONN-7 | Does the device support Transport Layer Security (TLS)? | ______ | __ | |||
| CONN-7.1 | Is TLS configurable? | |||||
| CONN-8 | Does the device provide operator control functionality from a separate device (e.g., telemedicine)? | ______ | __ |
| PERSON AUTHENTICATION (PAUT) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability to configure the device to authenticate users. | ||||||
| PAUT-1 | Does the device support and enforce unique IDs and passwords for all users and roles (including service accounts)? | ______ | __ | Section 5.12, PAUT | IA-2 | A.9.2.1 |
| PAUT-1.1 | Does the device enforce authentication of unique IDs and passwords for all users and roles (including service accounts)? | ______ | __ | Section 5.12, PAUT | IA-2 | A.9.2.1 |
| PAUT-2 | Is the device configurable to authenticate users through an external authentication service (e.g., MS Active Directory, NDS, LDAP, OAuth, etc.)? | ______ | __ | Section 5.12, PAUT | IA-5 | A.9.2.1 |
| PAUT-3 | Is the device configurable to lock out a user after a certain number of unsuccessful logon attempts? | ______ | __ | Section 5.12, PAUT | IA-2 | A.9.2.1 |
| PAUT-4 | Are all default accounts (e.g., technician service accounts, administrator accounts) listed in the documentation? | ______ | __ | Section 5.12, PAUT | SA-4(5) | A.14.1.1, A.14.2.7, A.14.2.9, A.15.1.2 |
| PAUT-5 | Can all passwords be changed? | ______ | __ | Section 5.12, PAUT | ||
| PAUT-6 | Is the device configurable to enforce creation of user account passwords that meet established (organization specific) complexity rules? | ______ | __ | Section 5.12, PAUT | IA-2 | A.9.2.1 |
| PAUT-7 | Does the device support account passwords that expire periodically? | ______ | __ | |||
| PAUT-8 | Does the device support multi-factor authentication? | ______ | __ | |||
| PAUT-9 | Does the device support single sign-on (SSO)? | ______ | __ | Section 5.12, PAUT | IA-2 | A.9.2.1 |
| PAUT-10 | Can user accounts be disabled/locked on the device? | ______ | __ | Section 5.12, PAUT | IA-2 | A.9.2.1 |
| PAUT-11 | Does the device support biometric controls? | ______ | __ | Section 5.12, PAUT | IA-2 | A.9.2.1 |
| PAUT-12 | Does the device support physical tokens (e.g. badge access)? | ______ | __ | |||
| PAUT-13 | Does the device support group authentication (e.g. hospital teams)? | ______ | __ | |||
| PAUT-14 | Does the application or device store or manage authentication credentials? | ______ | __ | |||
| PAUT-14.1 | Are credentials stored using a secure method? | ______ | __ |
| PHYSICAL LOCKS (PLOK) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| Physical locks can prevent unauthorized users with physical access to the device from compromising the integrity and confidentiality of personally identifiable information stored on the device or on removable media | ||||||
| PLOK-1 | Is the device software only? If yes, answer “N/A” to remaining questions in this section. | ______ | __ | Section 5.13, PLOK | PE- 3(4) | A.11.1.1, A.11.1.2, A.11.1.3 |
| PLOK-2 | Are all device components maintaining personally identifiable information (other than removable media) physically secure (i.e., cannot remove without tools)? | ______ | __ | Section 5.13, PLOK | PE- 3(4) | A.11.1.1, A.11.1.2, A.11.1.3 |
| PLOK-3 | Are all device components maintaining personally identifiable information (other than removable media) physically secured behind an individually keyed locking device? | ______ | __ | Section 5.13, PLOK | PE- 3(4) | A.11.1.1, A.11.1.2, A.11.1.3 |
| PLOK-4 | Does the device have an option for the customer to attach a physical lock to restrict access to removable media? | ______ | __ | Section 5.13, PLOK | PE- 3(4) | A.11.1.1, A.11.1.2, A.11.1.3 |
| ROADMAP FOR THIRD PARTY COMPONENTS IN DEVICE LIFE CYCLE (RDMP) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| Manufacturer’s plans for security support of third-party components within the device’s life cycle. | ||||||
| RDMP-1 | Was a secure software development process, such as ISO/IEC 27034 or IEC 62304, followed during product development? | ______ | __ | Section 5.14, RDMP | CM-2 | None |
| RDMP-2 | Does the manufacturer evaluate third-party applications and software components included in the device for secure development practices? | ______ | __ | Section 5.14, RDMP | CM-8 | A.8.1.1, A.8.1.2 |
| RDMP-3 | Does the manufacturer maintain a web page or other source of information on software support dates and updates? | ______ | __ | Section 5.14, RDMP | CM-8 | A.8.1.1, A.8.1.2 |
| RDMP-4 | Does the manufacturer have a plan for managing third-party component end-of-life? | ______ | __ | Section 5.14, RDMP | CM-8 | A.8.1.1, A.8.1.2 |
| SOFTWARE BILL OF MATERIALS (SBoM) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| A Software Bill of Material (SBoM) lists all the software components that are incorporated into the device being described for the purpose of operational security planning by the healthcare delivery organization. This section supports controls in the RDMP section. | ||||||
| SBOM-1 | Is the SBoM for this product available? | ______ | __ | |||
| SBOM-2 | Does the SBoM follow a standard or common method in describing software components? | ______ | __ | |||
| SBOM-2.1 | Are the software components identified? | ______ | __ | |||
| SBOM-2.2 | Are the developers/manufacturers of the software components identified? | ______ | __ | |||
| SBOM-2.3 | Are the major version numbers of the software components identified? | ______ | __ | |||
| SBOM-2.4 | Are any additional descriptive elements identified? | ______ | __ | |||
| SBOM-3 | Does the device include a command or process method available to generate a list of software components installed on the device? | ______ | __ | |||
| SBOM-4 | Is there an update process for the SBoM? | ______ | __ |
| SYSTEM AND APPLICATION HARDENING (SAHD) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The device's inherent resistance to cyber attacks and malware. | CM-7 | A.12.5.1* | ||||
| SAHD-1 | Is the device hardened in accordance with any industry standards? | ______ | __ | Section 5.15, SAHD | AC-17(2)/IA-3 | A.6.2.1, A.6.2.2, A.13.1.1, A.13.2.1, A.14.1.2/None |
| SAHD-2 | Has the device received any cybersecurity certifications? | ______ | __ | Section 5.15, SAHD | SA-12(10) | A.14.2.7, A.15.1.1, A.15.1.2, A.15.1.3 |
| SAHD-3 | Does the device employ any mechanisms for software integrity checking | ______ | __ | |||
| SAHD-3.1 | Does the device employ any mechanism (e.g., release-specific hash key, checksums, digital signature, etc.) to ensure the installed software is manufacturer-authorized? | ______ | __ | |||
| SAHD-3.2 | Does the device employ any mechanism (e.g., release-specific hash key, checksums, digital signature, etc.) to ensure the software updates are the manufacturer-authorized updates? | ______ | __ | Section 5.15, SAHD | CM-8 | A.8.1.1, A.8.1.2 |
| SAHD-4 | Can the owner/operator perform software integrity checks (i.e., verify that the system has not been modified or tampered with)? | ______ | __ | Section 5.15, SAHD | AC-3 | A.6.2.2, A.9.1.2, A.9.4.1, A.9.4.4, A.9.4.5, A.13.1.1, A.14.1.2, A.14.1.3, A.18.1.3 |
| SAHD-5 | Is the system configurable to allow the implementation of file-level, patient level, or other types of access controls? | ______ | __ | Section 5.15, SAHD | CM-7 | A.12.5.1* |
| SAHD-5.1 | Does the device provide role-based access controls? | ______ | __ | Section 5.15, SAHD | CM-7 | A.12.5.1* |
| SAHD-6 | Are any system or user accounts restricted or disabled by the manufacturer at system delivery? | ______ | __ | Section 5.15, SAHD | CM-8 | A.8.1.1, A.8.1.2 |
| SAHD-6.1 | Are any system or user accounts configurable by the end user after initial configuration? | ______ | __ | Section 5.15, SAHD | CM-7 | A.12.5.1* |
| SAHD-6.2 | Does this include restricting certain system or user accounts, such as service technicians, to least privileged access? | ______ | __ | Section 5.15, SAHD | CM-7 | A.12.5.1* |
| SAHD-7 | Are all shared resources (e.g., file shares) which are not required for the intended use of the device disabled? | ______ | __ | Section 5.15, SAHD | CM-7 | A.12.5.1* |
| SAHD-8 | Are all communication ports and protocols that are not required for the intended use of the device disabled? | ______ | __ | Section 5.15, SAHD | SA-18 | None |
| SAHD-9 | Are all services (e.g., telnet, file transfer protocol [FTP], internet information server [IIS], etc.), which are not required for the intended use of the device deleted/disabled? | ______ | __ | Section 5.15, SAHD | CM-6 | None |
| SAHD-10 | Are all applications (COTS applications as well as OS-included applications, e.g., MS Internet Explorer, etc.) which are not required for the intended use of the device deleted/disabled? | ______ | __ | Section 5.15, SAHD | SI-2 | A.12.6.1, A.14.2.2, A.14.2.3, A.16.1.3 |
| SAHD-11 | Can the device prohibit boot from uncontrolled or removable media (i.e., a source other than an internal drive or memory component)? | ______ | __ | |||
| SAHD-12 | Can unauthorized software or hardware be installed on the device without the use of physical tools? | ______ | __ | |||
| SAHD-13 | Does the product documentation include information on operational network security scanning by users? | ______ | __ | |||
| SAHD-14 | Can the device be hardened beyond the default provided state? | ______ | __ | |||
| SAHD-14.1 | Are instructions available from vendor for increased hardening? | |||||
| SHAD-15 | Can the system prevent access to BIOS or other bootloaders during boot? | |||||
| SAHD-16 | Have additional hardening methods not included in 2.3.19 been used to harden the device? | ______ | __ | |||
| SECURITY GUIDANCE (SGUD) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| Availability of security guidance for operator and administrator of the device and manufacturer sales and service. | ||||||
| SGUD-1 | Does the device include security documentation for the owner/operator? | ______ | __ | Section 5.16, SGUD | AT-2/PL-2 | A.7.2.2, A.12.2.1/A.14.1.1 |
| SGUD-2 | Does the device have the capability, and provide instructions, for the permanent deletion of data from the device or media? | ______ | __ | Section 5.16, SGUD | MP-6 | A.8.2.3, A.8.3.1, A.8.3.2, A.11.2.7 |
| SGUD-3 | Are all access accounts documented? | ______ | __ | Section 5.16, SGUD | AC-6,IA-2 | A.9.1.2, A.9.2.3, A.9.4.4, A.9.4.5/A.9.2.1 |
| SGUD-3.1 | Can the owner/operator manage password control for all accounts? | ______ | __ | |||
| SGUD-4 | Does the product include documentation on recommended compensating controls for the device? | ______ | __ | |||
| HEALTH DATA STORAGE CONFIDENTIALITY (STCF) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability of the device to ensure unauthorized access does not compromise the integrity and confidentiality of personally identifiable information stored on the device or removable media. | ||||||
| STCF-1 | Can the device encrypt data at rest? | ______ | __ | Section 5.17, STCF | SC-28 | A.8.2.3 |
| STCF-1.1 | Is all data encrypted or otherwise protected? | |||||
| STCF-1.2 | Is the data encryption capability configured by default? | |||||
| STCF-1.3 | Are instructions available to the customer to configure encryption? | |||||
| STCF-2 | Can the encryption keys be changed or configured? | ______ | __ | Section 5.17, STCF | SC-28 | A.8.2.3 |
| STCF-3 | Is the data stored in a database located on the device? | ______ | __ | |||
| STCF-4 | Is the data stored in a database external to the device? | ______ | __ |
| TRANSMISSION CONFIDENTIALITY (TXCF) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability of the device to ensure the confidentiality of transmitted personally identifiable information. | ||||||
| TXCF-1 | Can personally identifiable information be transmitted only via a point-to-point dedicated cable? | ______ | __ | Section 5.18, TXCF | CM-7 | A.12.5.1 |
| TXCF-2 | Is personally identifiable information encrypted prior to transmission via a network or removable media? | ______ | __ | Section 5.18, TXCF | CM-7 | A.12.5.1 |
| TXCF-2.1 | If data is not encrypted by default, can the customer configure encryption options? | ______ | __ | |||
| TXCF-3 | Is personally identifiable information transmission restricted to a fixed list of network destinations? | ______ | __ | Section 5.18, TXCF | CM-7 | A.12.5.1 |
| TXCF-4 | Are connections limited to authenticated systems? | ______ | __ | Section 5.18, TXCF | CM-7 | A.12.5.1 |
| TXCF-5 | Are secure transmission methods supported/implemented (DICOM, HL7, IEEE 11073)? | ______ | __ |
| TRANSMISSION INTEGRITY (TXIG) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| The ability of the device to ensure the integrity of transmitted data. | ||||||
| TXIG-1 | Does the device support any mechanism (e.g., digital signatures) intended to ensure data is not modified during transmission? | ______ | __ | Section 5.19, TXIG | SC-8 | A.8.2.3, A.13.1.1, A.13.2.1, A.13.2.3, A.14.1.2, A.14.1.3 |
| TXIG-2 | Does the device include multiple sub-components connected by external cables? | ______ | __ |
| REMOTE SERVICE (RMOT) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 | |||
| Remote service refers to all kinds of device maintenance activities performed by a service person via network or other remote connection. | ||||||
| RMOT-1 | Does the device permit remote service connections for device analysis or repair? | ______ | __ | AC-17 | A.6.2.1, A.6.2.2, A.13.1.1, A.13.2.1, A.14.1.2 | |
| RMOT-1.1 | Does the device allow the owner/operator to initiative remote service sessions for device analysis or repair? | ______ | __ | |||
| RMOT-1.2 | Is there an indicator for an enabled and active remote session? | ______ | __ | |||
| RMOT-1.3 | Can patient data be accessed or viewed from the device during the remote session? | ______ | __ | AC-17 | A.6.2.1, A.6.2.2, A.13.1.1, A.13.2.1, A.14.1.2 | |
| RMOT-2 | Does the device permit or use remote service connections for predictive maintenance data? | ______ | __ | |||
| RMOT-3 | Does the device have any other remotely accessible functionality (e.g. software updates, remote training)? | ______ | __ |
| OTHER SECURITY CONSIDERATIONS (OTHR) | IEC TR 80001-2-2:2012 | NIST SP 800-53 Rev. 4 | ISO 27002:2013 |
| NONE |
Notes:
Note 1 Example note. Please keep individual notes to one cell. Please use separate notes for separate information
ACME ABC123 1/1/2020
File details come from the government source that posted it. Updated .