<Past |
Future> |
2008.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2011.1.2 |
Divest [5, 6] |
Divest [5, 6] |
Divest [5, 6] |
Divest [5, 6] |
Divest [5, 6] |
Divest [5, 6] |
Divest [5, 6] |
Divest [5, 6] |
Divest [5, 6] |
Unapproved |
Unapproved |
Unapproved |
2012.1 |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Unapproved |
Unapproved |
Unapproved |
2012.2 |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Unapproved |
Unapproved |
Unapproved |
2013.1.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2014.1.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2014.1.3 |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6] |
Unapproved |
Unapproved |
Unapproved |
2015.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2016.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2016.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2017.1.x |
Approved w/Constraints [1, 5, 6] |
Approved w/Constraints [1, 5, 6] |
Approved w/Constraints [1, 5, 6] |
Approved w/Constraints [1, 5, 6] |
Approved w/Constraints [1, 5, 6] |
Approved w/Constraints [1, 5, 6] |
Approved w/Constraints [1, 5, 6] |
Approved w/Constraints [1, 5, 6] |
Approved w/Constraints [1, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
2017.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2018.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [6, 7] |
Divest [6, 7] |
Unapproved |
| | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | [2] | Projects using this technology must meet Veterans Affairs (VA) Directive 6500 and implement Federal Information Processing Standards (FIPS 199) for all laptop devices and National Institute of Standards and Technology Special Publication 800-53 for all desktop devices when VA sensitive information is involved, or additional mitigating controls must be documented in an approved System Security Plan (SSP) to prevent potential disclosure of PII/PHI data. Additionally, projects which interface with external VA partners must have a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), which detail the security requirements for users and systems that share information and resources outside of the VA production network. | | [3] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [4] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards and an ISO Risk Based Decision (RBD) must be approved by the local ISO/CIO before it can be used in the VA Production Environment. 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 ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | [5] | 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. | | [6] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [7] | 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 ISO can provide assistance in reviewing the NIST vulnerabilities. |
|
Note: |
At the time of writing, version 2018.1.7 is the most current version. |