<Past |
Future> |
2007 |
Approved w/Constraints [3] |
Approved w/Constraints [3] |
Approved w/Constraints [3] |
Approved w/Constraints [3] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [5] |
Divest [5] |
Approved w/Constraints [5] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [7, 8, 9] |
2012 |
Approved w/Constraints [3] |
Approved w/Constraints [3] |
Approved w/Constraints [3] |
Approved w/Constraints [3] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [5] |
Approved w/Constraints [5] |
Approved w/Constraints [5] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [7, 8, 9] |
1511 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5] |
Approved w/Constraints [1, 5] |
Approved w/Constraints [1, 5] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 7, 8, 9] |
1602 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5] |
Approved w/Constraints [5] |
Approved w/Constraints [5] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [5, 7, 8] |
Approved w/Constraints [7, 8, 9] |
1606 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 5] |
Approved w/Constraints [1, 5] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 7, 8, 9] |
1607 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 5] |
Approved w/Constraints [1, 5] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 7, 8, 9] |
1608 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 5] |
Approved w/Constraints [1, 5] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 5, 7, 8] |
Approved w/Constraints [1, 7, 8, 9] |
1710 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1802 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1806 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1810 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1902 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1906 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1910 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2002 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2006 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2103 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2107 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2111 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2203 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2207 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2211 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2303 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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] | Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities. Additionally, if PII/PHI/VA sensitive information is involved, FIPS 140-2 certified encryption must be used to encrypt data in transit and the technology must be implemented within the VA production network (not in a DMZ) or additional mitigating controls must be documented in an approved System Security Plan (SSP). Finally, configuration and deployment standards for Microsoft Systems Center Configuration Manager (SCCM) which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted. | | [3] | Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities.
Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to encrypt data in transit and at rest if Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information is involved or additional mitigating controls must be documented in an approved System Security Plan (SSP). Additionally, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)).
Finally, configuration and deployment standards for Microsoft Systems Center Configuration Manager (SCCM), which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted. | | [4] | Configuration and deployment standards for Microsoft Systems Center Configuration Manager (SCCM) which are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering (Mail: VA IT Engineering CS Desktop Technologies Team) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. | | [5] | 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. | | [6] | 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. | | [7] | Versions newer than 2012 which are listed in an evaluation status are under evaluation and are currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test as approved by ESE. | | [8] | 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. | | [9] | 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. |
|
Note: |
At the time of writing, version 2303 (5.00.9106.1022) is the most current version, released 04/10/2023.
A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 2211 (5.00.9096.1024), and version 2303 (5.00.9106.1022) is under testing and development for 4-6 weeks from 09/20/2023 |