<Past |
Future> |
1.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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) |
1.3.x |
DIVEST [15, 16, 17, 18, 19, 20] |
Unapproved |
Unapproved |
Unapproved |
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) |
1.4.x |
DIVEST [15, 16, 17, 18, 19, 20] |
Unapproved |
Unapproved |
Unapproved |
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) |
1.5.x |
Approved w/Constraints [15, 16, 17, 18, 19, 20] |
Approved w/Constraints [15, 16, 17, 18, 19, 20] |
Approved w/Constraints [15, 16, 17, 18, 19, 20] |
Approved w/Constraints [15, 16, 17, 19, 20, 21] |
DIVEST [15, 17, 19, 20, 21, 22] |
DIVEST [15, 17, 19, 20, 21, 22] |
DIVEST [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.6.x |
Unapproved |
Approved w/Constraints [15, 16, 17, 18, 19, 20] |
Approved w/Constraints [15, 16, 17, 18, 19, 20] |
Approved w/Constraints [15, 16, 17, 19, 20, 21] |
Approved w/Constraints [15, 17, 19, 20, 21, 22] |
DIVEST [15, 17, 19, 20, 21, 22] |
DIVEST [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (POA&M) |
1.7.x (Classic) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [15, 17, 19, 20, 21, 22] |
Approved w/Constraints [15, 17, 19, 20, 21, 22] |
Approved w/Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
23320.x (New) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints (PLANNING/EVALUATION) [1, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
24180.x (New) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (DIVEST) [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
24243.x (New) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
Authorized w/ Constraints [15, 17, 19, 20, 21, 22] |
| | [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] | This technology must not be updated silently.
This technology must not be downloaded from the Windows App store.
This technology is only authorized for use for testing and piloting under the strict control of the OIT ITOPS SD CIS Collaboration Team (VA Email: OIT ITOPS SD CIS Collaboration Team).
Per the Initial Product Review, users must abide by the following constraints:
Due to the untrusted search path vulnerability in the installer of Microsoft Teams, the product must have an application package created which will be deployed by a system administrator using System Center Configuration Manager (SCCM). Restrictions must be put into place to prevent users from connecting to unverified\unapproved tenants. SCCM will also monitor the product once deployed. VA must implement tenant policy enforcement to only allow what has been tested and authorized to be used. Microsoft Teams must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
Users must ensure that VA sensitive data, stored and transmitted in Microsoft Teams systems, is encrypted using FIPS 140-2 certified cryptographic module. If that is not technically possible then 3rd party encryption methods must be employed.
The VA must only consider solutions with similar functionality if the current authorized solutions do not meet all of VA`s needs or requirements. | | [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] | Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations. | | [5] | 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. | | [6] | 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. Contact your local CIO office if more information is needed in regards to the use of this technology. | | [7] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [8] | This technology must not be updated silently.
This technology must not be downloaded from the Windows App store.
Per the Initial Product Review, users must abide by the following constraints:
- Due to the untrusted search path vulnerability in the installer of Microsoft Teams, the product must have an application package created which will be deployed by a system administrator using System Center Configuration Manager (SCCM). Restrictions must be put into place to prevent users from connecting to unverified\unapproved tenants. SCCM will also monitor the product once deployed. VA must implement tenant policy enforcement to only allow what has been tested and authorized to be used. Microsoft Teams must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
- Ensure VA sensitive data, stored and transmitted in Microsoft Teams systems, is encrypted using FIPS 140-2 certified cryptographic module. If that is not technically possible then 3rd party encryption methods must be employed.
- The VA should only consider solutions with similar functionality if the current authorized solutions do not meet all of VA’s needs or requirements.
| | [9] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [10] | This technology must not be updated silently.
This technology must not be downloaded from the Windows App store.
Per the Initial Product Review, users must abide by the following constraints:
- Due to the untrusted search path vulnerability in the installer of Microsoft Teams, the product must have an application package created which will be deployed by a system administrator using System Center Configuration Manager (SCCM). Restrictions must be put into place to prevent users from connecting to unverified\unapproved tenants. SCCM will also monitor the product once deployed. VA must implement tenant policy enforcement to only allow what has been tested and authorized to be used. Microsoft Teams must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
- Ensure VA sensitive data, stored and transmitted in Microsoft Teams systems, is encrypted using FIPS 140-2 certified cryptographic module. If that is not technically possible then 3rd party encryption methods must be employed.
- Any plug-in, application, or service that interacts with the Teams client must be vetted by the VA Enterprise Messaging, Collaboration, Authentication and Office 365 Services (EMCAO) team.
| | [11] | 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. | | [12] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [13] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [14] | This technology must not be updated silently.
This technology must not be downloaded from the Windows App store.
Per the Initial Product Review, users must abide by the following constraints:
- Due to the untrusted search path vulnerability in the installer of Microsoft Teams, the product must have an application package created which will be deployed by a system administrator using System Center Configuration Manager (SCCM). Restrictions must be put into place to prevent users from connecting to unverified\unapproved tenants. SCCM will also monitor the product once deployed. VA must implement tenant policy enforcement to only allow what has been tested and authorized to be used. Microsoft Teams must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
- Ensure VA sensitive data, stored and transmitted in Microsoft Teams systems, is encrypted using FIPS 140-2 certified cryptographic module. If that is not technically possible then 3rd party encryption methods must be employed.
- Any plug-in, application, or service that interacts with the Teams client must be vetted by the VA Enterprise Messaging, Collaboration, Authentication and Office 365 Services (EMCAO) team.
| | [15] | 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. | | [16] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [17] | This technology must not be updated silently.
This technology must not be downloaded from the Windows App store.
Per the Initial Product Review, users must abide by the following constraints:
- Microsoft Teams must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
- Ensure VA sensitive data, stored and transmitted in Microsoft Teams systems, is encrypted using FIPS 140-2 certified cryptographic module. If that is not technically possible then 3rd party encryption methods must be employed.
- Any plug-in, application, or service that interacts with the Teams client must be vetted by the VA Enterprise Messaging, Collaboration, Authentication and Office 365 Services (EMCAO) team.
| | [18] | 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 VA Handbook 6500. | | [19] | 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. | | [20] | Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations. | | [21] | 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. | | [22] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
Note: |
A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 1.6.0.29964 (Classic), version 1.7.0.3653 (Classic), and 24180.205.2980.1757. Version 24243.1309.3132.617 (New) is under testing and development for six weeks from 10/09/2024 |