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> |
2.115.99.8 |
Authorized w/ Constraints (POA&M) |
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) |
1.x |
Authorized w/ Constraints (POA&M) |
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) |
2.0.x |
Authorized w/ Constraints (POA&M) |
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) |
3.0.x |
Authorized w/ Constraints (POA&M) |
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) |
3.6.x |
Authorized w/ Constraints (POA&M) |
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) |
| | [1] | 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. | | [2] | 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. | | [3] | This product falls under the Category 2 risk categories as defined by the Department of Defense (DoD). Category 2 mobile code technologies have full functionality, allowing mediated or controlled access to workstation, server, and remote system services and resources. Category 2 mobile code technologies can pose a moderate threat to VA information systems. Category 2 mobile code technologies must only be used when the Category 2 restrictions in the VA Mobile Code Policy are implemented.
Google Chrome using WebRTC is the recommended way to use BlueJeans. Windows Media Format (WMF) staff has found many vulnerabilities in the non-WebRTC version (the BlueJeans plugin) and has advised against its use. To use WebRTC with Google Chrome, open the BlueJeans meeting link from within the browser. Users must review the Google Chrome and WebRTC IPRs before use for additional information or constraints on the BlueJeans Browser Plugin for Chrome and its components. | | [4] | Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements. | | [5] | 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. | | [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] | This product falls under the Category 2 risk categories as defined by the Department of Defense (DoD). Category 2 mobile code technologies have full functionality, allowing mediated or controlled access to workstation, server, and remote system services and resources. Category 2 mobile code technologies can pose a moderate threat to VA information systems. Category 2 mobile code technologies must only be used when the Category 2 restrictions in VA Mobile Code Policy are implemented.
Google Chrome using WebRTC is the recommended way to use BlueJeans. Windows Media Format (WMF) staff has found many vulnerabilities in the non-WebRTC version (the BlueJeans plugin) and has advised against its use. To use WebRTC with Google Chrome, open the BlueJeans meeting link from within the browser. Users must review the Google Chrome and WebRTC IPRs before use for additional information or constraints on the BlueJeans Browser Plugin for Chrome and its components. | | [8] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product falls under the Category 2 risk categories as defined by the Department of Defense (DoD). Category 2 mobile code technologies have full functionality, allowing mediated or controlled access to workstation, server, and remote system services and resources. Category 2 mobile code technologies can pose a moderate threat to VA information systems. Category 2 mobile code technologies must only be used when the Category 2 restrictions in VA Mobile Code Policy are implemented.
Google Chrome using WebRTC is the recommended way to use BlueJeans. Windows Media Format (WMF) staff has found many vulnerabilities in the non-WebRTC version (the BlueJeans plugin) and has advised against its use. To use WebRTC with Google Chrome, open the BlueJeans meeting link from within the browser. Users must review the Google Chrome and WebRTC IPRs before use for additional information or constraints on the BlueJeans Browser Plugin for Chrome and its components. | | [9] | 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. | | [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Google Chrome is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This product falls under the Category 2 risk categories as defined by the Department of Defense (DoD). Category 2 mobile code technologies have full functionality, allowing mediated or controlled access to workstation, server, and remote system services and resources. Category 2 mobile code technologies can pose a moderate threat to VA information systems. Category 2 mobile code technologies must only be used when the Category 2 restrictions in VA Mobile Code Policy are implemented.
Google Chrome using WebRTC is the recommended way to use BlueJeans. Windows Media Format (WMF) staff has found many vulnerabilities in the non-WebRTC version (the BlueJeans plugin) and has advised against its use. To use WebRTC with Google Chrome, open the BlueJeans meeting link from within the browser. Users must review the Google Chrome and WebRTC IPRs before use for additional information or constraints on the BlueJeans Browser Plugin for Chrome and its components.
Per the Initial Product Review, users must abide by the following constraints:
- For all BlueJeans meetings, it is strongly recommended that WebRTC must not be enabled or used until WebRTC is reviewed and authorized for use within the VA.
- The VA should only consider solutions with similar functionality if the current authorized solutions do not meet all of VA’s needs or requirements.
- VA requires vendor support with a Service Level Agreement that meets VA support requirements. In order to use BlueJeans Browser Extension for Chrome, the VA must establish Enterprise level support.
| | [11] | Use of this technology is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners). VA users must leverage the organization`s preferred teleconferencing solutions, Microsoft Teams or WebEx, for internal hosted conferences. VA has selected Microsoft Teams and WebEx as its preferred teleconferencing solutions. No waiver or review is required for JOINING 3rd Party BlueJeans Browser Extension meetings.
Any use of this technology to host a VA event must be authorized by a Plan of Action and Milestones (POAM) waiver. There are no exceptions to the required waiver process for any reason. The POAM Board must seek guidance and/or approval from the Enterprise Security Change Control Board (ESCCB) as needed when a waiver is granted to host conferences.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Google Chrome is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This product falls under the Category 2 risk categories as defined by the Department of Defense (DoD). Category 2 mobile code technologies have full functionality, allowing mediated or controlled access to workstation, server, and remote system services and resources. Category 2 mobile code technologies can pose a moderate threat to VA information systems. Category 2 mobile code technologies must only be used when the Category 2 restrictions in VA Mobile Code Policy are implemented.
Google Chrome using WebRTC is the recommended way to use BlueJeans. Windows Media Format (WMF) staff has found many vulnerabilities in the non-WebRTC version (the BlueJeans plugin) and has advised against its use. To use WebRTC with Google Chrome, open the BlueJeans meeting link from within the browser. Users must review the Google Chrome and WebRTC IPRs before use for additional information or constraints on the BlueJeans Browser Plugin for Chrome and its components.
Per the Initial Product Review, users must abide by the following constraints:
- For all BlueJeans meetings, it is strongly recommended that WebRTC must not be enabled or used until WebRTC is reviewed and authorized for use within the VA.
- The VA should only consider solutions with similar functionality if the current authorized solutions do not meet all of VA’s needs or requirements.
- VA requires vendor support with a Service Level Agreement that meets VA support requirements. In order to use BlueJeans Browser Extension for Chrome, the VA must establish Enterprise level support.
| | [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. |
|
Note: |
At the time of writing, version 3.6.3.56 is the most current version and was released 12/20/2022. |