12.x |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
| | [1] | This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. | | [2] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | [3] | If this technology is an FDA certified medical device or is categorized by the Department as a networked medical device then it must be isolated and protected in accordance with The Medical Device Isolation Architecture (MDIA) 2015 Guidance. This guideline stipulates that if the device meets ANY of the following criteria, then it must be isolated:
- If the device cannot have the VA standard desktop security suite loaded on it. This includes but is not limited to Anti-Virus, HIPS, USB Access controls, software/hardware inventory, automated software updates/patches and Group Policy Objects (GPOs)
- If the device is a Windows device and cannot be part of the domain
- If the device is not part of the regular IT patched management process
- Non Windows devices (UNIX, Linux, MAC/Apple, etc.)
The criteria should be applied to both FDA certified and non-FDA certified devices which must maintain medical/clinical functionality. An example would be a PC that is not running the current supported operating system in order to manage medication-dispensing devices. While these may not be considered strictly medical devices, they are still vulnerable to attack and need to be protected. For guidance and assistance in security networked medical devices, please contact the Medical Device Isolation Architecture (MDIA) Working Group. | | [4] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [5] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. |
|