Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to,
VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information
Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users
should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology
(OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. |
The VA Decision Matrix displays the current and future VAIT
position regarding different releases of a TRM entry. These decisions are
based upon the best information available as of the most current date. The consumer of this information has the
responsibility to consult the organizations responsible for the desktop, testing, and/or production environments
to ensure that the target version of the technology will be supported.
|
|
Legend: |
White |
Authorized: The technology/standard has been authorized for use.
|
Yellow |
Authorized w/ Constraints: The technology/standard can be used within the specified constraints located
below the decision matrix in the footnote[1] and on the General tab.
|
Gray |
Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by
the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee
and based upon a recommendation from the POA&M Compliance Enforcement,
has been granted to the project team or organization that wishes to use the technology.
|
Orange |
Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard.
As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of
the technology/standard. Additional information on when the entry is projected to become unauthorized may be
found on the Decision tab for the specific entry.
|
Black |
Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
|
Blue |
Authorized w/ Constraints (PLANNING/EVALUATION): The period of time 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. If a customer would like to use this technology, please work with
your local or Regional OI&T office and contact the appropriate evaluation office
displayed in the notes below the decision matrix. The Local or Regional OI&T
office should submit an
inquiry to the TRM
if they require further assistance or if the evaluating office is not listed in the notes below.
|
|
Release/Version Information: |
VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.
|
For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision
would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.
|
VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than
what is specified but is not to exceed or affect previous decimal places.
|
For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401
is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.
|
Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M). |
<Past |
Future> |
XP Pro SP2 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
XP Pro SP3 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Embed POSReady 2009 |
Unapproved |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Vista |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Vista SP1 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Vista SP2 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Windows 7 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Windows 7 SP1 |
Unapproved |
DIVEST [7, 12, 16] |
DIVEST [7, 12, 16] |
DIVEST [7, 12, 16] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Embedded POSReady 7 |
Approved w/Constraints [7, 12, 15] |
Approved w/Constraints [7, 12, 16] |
Approved w/Constraints [7, 12, 16] |
DIVEST [7, 12, 16] |
DIVEST [7, 16, 17] |
DIVEST [7, 16, 17] |
DIVEST [7, 15, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Prohibited |
Windows 8 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Windows 8.1 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Embedded Handheld6.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Win 10 (LTSB 1507) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Win 10 (LTSB 1607) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Win 10 (LTSC 1809) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Windows 10 (FU 1709) |
DIVEST [7, 12, 15] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Windows 10 (FU 1803) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Windows 10 (FU 1809) |
Approved w/Constraints [7, 12, 15] |
Approved w/Constraints [7, 12, 16] |
Approved w/Constraints [7, 12, 16] |
DIVEST [7, 12, 16] |
DIVEST [7, 16, 17] |
DIVEST [7, 16, 17] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Prohibited |
Prohibited |
Windows 10 (FU 1903) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Windows 10 (FU 1909) |
Unapproved |
Unapproved |
Approved w/Constraints [7, 12, 16] |
Approved w/Constraints [7, 12, 16] |
Approved w/Constraints [7, 16, 17] |
Approved w/Constraints [7, 16, 17] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Prohibited |
Prohibited |
Windows 10 (FU 2004) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
DIVEST [7, 16, 17] |
Approved w/Constraints [7, 15, 17, 18] |
DIVEST [7, 17, 18, 19] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Windows 10 (FU 20H2) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Windows 10 (FU 21H1) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints (PLANNING/EVALUATION) [1, 7, 15, 17, 18] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 7, 17, 18, 19] |
Approved w/Constraints [7, 17, 18, 19] |
Approved w/Constraints [7, 17, 18, 19] |
Unapproved |
Unapproved |
Windows 10 (FU 21H2) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints (PLANNING/EVALUATION) [1, 7, 17, 18, 19] |
Approved w/Constraints [7, 17, 18, 19] |
Approved w/Constraints [7, 17, 18, 19] |
Approved w/Constraints [7, 17, 18, 20] |
Windows 10 (FU 22H2) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints (PLANNING/EVALUATION) [1, 7, 17, 18, 20] |
Windows 11 (FU 21H2) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints (PLANNING/EVALUATION) [1, 7, 17, 18, 19] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 7, 17, 18, 20] |
Windows 11 (FU 22H2) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints (PLANNING/EVALUATION) [1, 7, 17, 18, 20] |
Windows 11 (FU 23H2) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Windows 11 (FU 24H2) |
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] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows desktop images 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 by Client Services or the Architecture Engineering Review Board (AERB).
The use of Windows BitLocker disc encryption that is integrated into the Windows Operating System is not allowed without a waiver from the Client Services organization within VA Enterprise Systems Engineering or the AERB. | | [3] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images 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 by the Architecture Engineering Review Board (AERB).
No new installs of deprecated versions are allowed. The installation of Windows Vista is currently prohibited. Windows 8 and 8.1 are currently not authorized for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of the these versions as authorized by ESE Client Services or an AERB waiver while under evaluation.
The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions is not allowed without a waiver from the AERB.
The use of Remote Server Administration Tools for authorized Windows Client versions is authorized for use following the configuration and deployment standards maintained by the ESE Client Services organization. | | [4] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images 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 by the Architecture Engineering Review Board (AERB).
The Windows Virtual PC component of Windows 7 is authorized for use, but all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use.
The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions is not allowed without an AERB waiver.
No new installs of Deprecated Versions are allowed. Windows XP becomes TRM unapproved on 4/8/2015 when VA`s extended support contract expires. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in planning and only Enterprise System Engineering (ESE) Client Services may use the technology at this time for planning purposes. Windows 8.1 is currently not authorized for production except as part of an official ESE production pilot or production test of this version as authorized by ESE Client Services or an AERB waiver while under evaluation. No production deployment dates for Windows 8.1 or 10 have been set as of this writing. | | [5] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images 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 by the Architecture Engineering Review Board (AERB).
The Windows Virtual PC component of Windows 7 is authorized for use, but all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use.
The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines. Contact ESE Client Services (Mail: VA IT Engineering CS Desktop Technologies Team) for more information on the use of BitLocker.
No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in planning and only Enterprise System Engineering (ESE) Client Services may use the technology at this time for planning purposes. Windows 8.1 is currently not authorized for production except as part of an official ESE production pilot or production test of this version as authorized by ESE Client Services or an AERB waiver while under evaluation. No production deployment dates for Windows 8.1 or 10 have been set as of this writing. | | [6] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images 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 by the Architecture Engineering Review Board (AERB).
The Windows Virtual PC component of Windows 7 is authorized for use, but all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use.
The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines. Contact ESE Client Services (Mail: VA IT Engineering CS Desktop Technologies Team) for more information on the use of BitLocker.
No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in Evaluation and only Enterprise System Engineering (ESE) Client Services may use the technology at this time for evaluation purposes. Windows 8.1 is currently not authorized for production except as part of an official ESE production pilot or production test of this version as authorized by ESE Client Services or an AERB waiver while under evaluation. No production deployment dates for Windows 8.1 or 10 have been set as of this writing. | | [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. | | [8] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) images which are defined and maintained by the Endpoint Engineering organization within VA Solution Delivery must be followed and adhered to unless an appropriate waiver is granted by the STAT Board.
The Windows Virtual PC component of Windows 7 is authorized for use, but all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use.
The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines.
No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in Evaluation and only Solution Delivery may use the technology at this time for evaluation purposes. Windows 8.1 is being removed from the VA environment because Windows 10 will be the next Windows Client standard. No production deployment date for Windows 10 has been set as of this writing. | | [9] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) baselines which are defined and maintained by the Endpoint Engineering organization within VA Solution Delivery must be followed and adhered to unless an appropriate waiver is granted by the STAT Board.
The Windows Virtual PC component of Windows 7 is not authorized for use, and all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use.
The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines.
No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in IOC Testing and there is limited deployment and testing at other non-IOC sites. The production deployment date for Windows 10 is tentatively scheduled to start in October 2018 and last 18 months. The exact schedule is not published. | | [10] | This product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for Windows Client (desktop) baselines which are defined and maintained by the Endpoint Engineering organization within VA Solution Delivery must be followed and adhered to unless an appropriate waiver is granted by the STAT Board.
The Windows Virtual PC component of Windows 7 is not authorized for use, and all older named editions of this component (Microsoft Virtual PC 2007, Microsoft Virtual PC 2004, and Connectix Virtual PC) are prohibited from use.
The use of Windows BitLocker disc encryption that is integrated into the Windows Client versions can only be used when configured with the required enterprise settings and centralized management per the Windows configuration baseline. See the reference section for more information on Windows baselines.
No new installs of Deprecated Versions are allowed. The installation of Windows Vista and Windows 8 is currently prohibited. Windows 10 is in IOC Testing and there is limited deployment and testing at other non-IOC sites. The production deployment date for Windows 10 is tentatively scheduled to start in October 2018 and last 18 months. The exact schedule is not published. | | [11] | The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows images produced by Endpoint Engineering. | | [12] | 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. | | [13] | The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering. | | [14] | Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one.
Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering.
VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards. | | [15] | Users must ensure that Microsoft .NET Framework and Microsoft Internet Explorer are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one.
Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering.
VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards.
The following constraints apply to the Embedded Handheld edition of this technology:
Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information.
According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date.
Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated. | | [16] | Windows 7 ended traditional support in January 2020. VA has ceased support for imaging new Win 7 PCs and other routine support functions. Because there are a few hundred Win 7 machines that must remain due to legacy application migration delays, VA purchased extended support through 2020 and all Windows machines must be removed from VA as soon as possible. TRM has extended divest status though 2020 while these migrations are finished and it will not be extended further.
Users must ensure that Microsoft .NET Framework and Microsoft Internet Explorer are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one.
Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering.
VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards.
The following constraints apply to the Embedded Handheld edition of this technology:
Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information.
According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date.
Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated. | | [17] | 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. | | [18] | 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. | | [19] | Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one.
Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering.
VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards.
The following constraints apply to the Embedded Handheld edition of this technology:
Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information.
According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date.
Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated. | | [20] | Hyper-V on Windows 10 is currently unapproved due to VA standardization and the lack of a required VA baseline. DISA states the following: `Microsoft has produced a security guide for Hyper-V. However, due to funding constraints, this is listed on the unfunded STIG development list. When a STIG does not exist, organizations may use a vendor developed guide to use to configure their systems. Organizations using the Hyper-V software need to also review the appropriate Windows Server STIG when setting up their Hyper-V system.` The only security guides listed are for Server 2012 and 2016. No guideline was found for Windows 10 and the vendor was unable to provide one.
Due to potential information security risks, Software as a Service/ Platform as a Service (SaaS/PaaS) solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
The Windows App Store is currently disabled by VA policy and the only Windows Apps that are allowed to be used are those bundled with and are part of official VA Windows baselines produced by Endpoint Engineering.
VA security configuration baseline standards and deployment standards for Windows Client images, including standards for Active Directory must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information and links to the official standards.
The following constraints apply to the Embedded Handheld edition of this technology:
Due to the lack of documentation and vendor support, there is no way to determine if Windows Embedded Handheld is FIPS 140-2 certified. Windows Embedded Handheld cannot be used for processing any data containing Personal Health Information (PHI), Personally Identifiable Information (PII), or VA sensitive information.
According to the vendor, an Original Equipment Manufacturer (OEM) such as Zebra would be responsible for support after the EOL date. The OEM cannot confirm or demonstrate an acceptable level of support after Windows Embedded Handheld EOL date.
Neither the vendor nor the OEM can demonstrate a support model in which the devices would be patched or updated.
Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. |
|
Note: |
At the time of writing, Windows 11 (FU 24H2) is the most current version, released 03/01/2025. A standard configuration of this technology was developed by the DDE team. The standard version is Windows 11 (FU 23H2), and version Windows 11 (FU 24H2) is under testing and development for six weeks from 11/08/2024. |