| 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> |
| 3.5.x (Win) |
Approved w/Constraints
[1, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[1, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[1, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[5, 6, 7, 9, 10, 11, 12, 13] |
Approved w/Constraints
[5, 7, 9, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 7, 9, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 7, 9, 10, 11, 12, 13, 14] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
| 3.6.x (Mac) |
Approved w/Constraints
[1, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[1, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[1, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[5, 6, 7, 9, 10, 11, 12, 13] |
Approved w/Constraints
[5, 7, 9, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 7, 9, 10, 11, 12, 13, 14] |
Approved w/Constraints
[5, 7, 9, 10, 11, 12, 13, 14] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
Authorized w/ Constraints
[5, 7, 9, 10, 12, 13, 14, 15] |
| | | | [1] | Users must Divest the use of Internet Explorer with this technology. Other authorized internet browsers are available. See Category Tab for details.
Users must ensure that Google Chrome, Microsoft Internet Explorer (IE), and Firefox are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Application Security Assessment Review, users must abide by the following constraints:
- The administrator shall disable automatic update checking from the application.
- The ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
- OSS may be used if there is adequate maintenance and support. As a condition of certification, Sponsor/Software admin personnel shall maintain and monitor the distribution of IBM Security Trusteer Rapport v3.5.x software. The software shall be physically stored in Sponsor/Software admin software library for quality control.
Per the Browser Extension Security Assessment Review, users must abide by the following constraints:
- IBM Security Rapport Browser Extension uses permissions that give the extension access to privileged fields of the Tab objects used by several APIs including chrome.tabs and chrome.windows. In many circumstances extensions will not need to declare the `tabs` permission to make use of these APIs. IBM Security Rapport also uses permissions that give the extension access to all hosts. It may be possible to avoid declaring any host permissions by using the activeTab permission. IBM Security Rapport also uses the webRequest, tabs, and tabCapture permissions. In many circumstances extensions will not need to declare the these permissions to make use of these APIs.
| | | [2] | 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. | | | [3] | 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. | | | [4] | 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. | | | [5] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. | | | [6] | 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). | | | [7] | 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. | | | [8] | 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. | | | [9] | 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. | | | [10] | 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. | | | [11] | Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must ensure that Google Chrome, Microsoft Edge, and Firefox are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Application Security Assessment Review, users must abide by the following constraints:
- The administrator shall disable automatic update checking from the application.
- The ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
- OSS may be used if there is adequate maintenance and support. As a condition of certification, Sponsor/Software admin personnel shall maintain and monitor the distribution of IBM Security Trusteer Rapport v3.5.x software. The software shall be physically stored in Sponsor/Software admin software library for quality control.
Per the Browser Extension Security Assessment Review, users must abide by the following constraints:
- IBM Security Rapport Browser Extension uses permissions that give the extension access to privileged fields of the Tab objects used by several APIs including chrome.tabs and chrome.windows. In many circumstances extensions will not need to declare the `tabs` permission to make use of these APIs. IBM Security Rapport also uses permissions that give the extension access to all hosts. It may be possible to avoid declaring any host permissions by using the activeTab permission. IBM Security Rapport also uses the webRequest, tabs, and tabCapture permissions. In many circumstances extensions will not need to declare the these permissions to make use of these APIs.
| | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [13] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. | | | [14] | 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). | | | [15] | Users must ensure that Google Chrome, Microsoft Edge, and Firefox are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Application Security Assessment Review, users must abide by the following constraints:
- The administrator shall disable automatic update checking from the application.
- The ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
- OSS may be used if there is adequate maintenance and support. As a condition of certification, Sponsor/Software admin personnel shall maintain and monitor the distribution of IBM Security Trusteer Rapport v3.5.x software. The software shall be physically stored in Sponsor/Software admin software library for quality control.
Per the Browser Extension Security Assessment Review, users must abide by the following constraints:
- IBM Security Rapport Browser Extension uses permissions that give the extension access to privileged fields of the Tab objects used by several APIs including chrome.tabs and chrome.windows. In many circumstances extensions will not need to declare the `tabs` permission to make use of these APIs. IBM Security Rapport also uses permissions that give the extension access to all hosts. It may be possible to avoid declaring any host permissions by using the activeTab permission. IBM Security Rapport also uses the webRequest, tabs, and tabCapture permissions. In many circumstances extensions will not need to declare the these permissions to make use of these APIs.
|
|
| Note: |
At the time of writing, version 3.5.2309 for Windows is the most current version and released 09/12/2024.
At the time of writing, version 3.6.1945 for MacOS is the most current version and updated 09/12/2024. |
