<Past |
Future> |
L.01.04 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
M.00.03 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
M.04.02 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
15.3.0 |
DIVEST [6, 7, 8, 10, 11, 12, 13] |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
15.3.1 |
DIVEST [6, 7, 8, 10, 11, 12, 13] |
DIVEST [6, 7, 8, 10, 11, 12, 13] |
DIVEST [6, 7, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
16.0.1 |
Approved w/Constraints [6, 7, 8, 10, 11, 12, 13] |
Approved w/Constraints [6, 7, 8, 10, 11, 12, 13] |
Approved w/Constraints [6, 7, 8, 10, 11, 12, 13] |
Authorized w/ Constraints [6, 7, 8, 10, 11, 12, 13] |
Authorized w/ Constraints [6, 7, 8, 10, 11, 12, 13] |
Authorized w/ Constraints (DIVEST) [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints (POA&M) |
18.0.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints [6, 7, 10, 11, 12, 13, 14] |
Authorized w/ Constraints [6, 7, 10, 11, 12, 13, 14] |
Note: |
At the time of writing, version 18.0.0 is the most current version of the technology, released 09/06/2024. |
| | [6] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [7] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | [8] | This technology can be connected to a medical device directly or via a network using standard Local Area Network (LAN) technology. If no network is available or the available network cannot be used, a cross-over LAN cable can be utilized to connect the LAN interface card of the PC to a medical device. Users will then be able to communicate with the patient monitor and the devices connected to it.
Though this technology appears to not be active on the VA network, there have been recent user-driven update requests for this technology, which indicate this technology may not be detected by current scans. This technology should continue being supported.
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.
Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. | | [10] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [11] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | [12] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. | | [13] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [14] | This technology can be connected to a medical device directly or via a network using standard Local Area Network (LAN) technology. If no network is available or the available network cannot be used, a cross-over LAN cable can be utilized to connect the LAN interface card of the PC to a medical device. Users will then be able to communicate with the patient monitor and the devices connected to it.
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.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol requires a POA&M for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) |
|