| 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.0.x |
Approved w/Constraints
[1, 2, 5, 6] |
Approved w/Constraints
[1, 2, 5, 6] |
Approved w/Constraints
[1, 2, 5, 6] |
Approved w/Constraints
[1, 2, 5, 7] |
Approved w/Constraints
[1, 2, 5, 7] |
DIVEST
[2, 5, 7, 8, 9, 10] |
DIVEST
[2, 5, 7, 8, 9, 10] |
DIVEST
[2, 5, 7, 8, 9, 10] |
Authorized w/ Constraints (DIVEST)
[2, 5, 7, 8, 9, 10] |
DIVEST
[2, 5, 7, 8, 9, 10] |
DIVEST
[2, 5, 7, 8, 9, 10] |
Unapproved |
| 7.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[2, 5, 7, 8, 9, 10] |
Approved w/Constraints
[2, 5, 7, 8, 9, 10] |
Approved w/Constraints
[2, 5, 7, 8, 9, 10] |
Authorized w/ Constraints
[2, 5, 7, 8, 9, 10] |
Approved w/Constraints
[2, 5, 7, 8, 9, 10] |
Approved w/Constraints
[2, 5, 7, 8, 9, 10] |
Approved w/Constraints
[2, 5, 7, 8, 9, 10] |
| | | | [1] | Users must ensure that Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints:
- FIPS 140-2 protection will rely on a third-party module or the web browser and should be verified the protection is enabled.
- It is advised that a Privacy Impact Assessment be conducted to review the vendors privacy policy.
- Only well supported solutions should be utilized within the department. Lack of support could result in outdated code and dependencies that could pose a risk if not mitigated in a timely manner.
- The JAWSInspect Browser Extension 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.
- The JAWSInspect Browser Extension dependencies are outdated and pose a
security risk to VA data. VA systems using this Extension will be more
vulnerable to Ransomware attacks, malware and data breaches.
- Ensure that JAWSInspect Browser Extension is obtained from the authentic Google or Firefox webstore with a verifiable web certificate.
| | | [2] | 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. | | | [3] | 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. | | | [4] | 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. | | | [5] | 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 ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | | [7] | 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. | | | [8] | Users must ensure that Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints:
- The JAWSInspect Firefox Extension may no longer supported by the
developer, as there have not been updates to the extension since Jan 6, 2021.
Using outdated unsupported software exposes the VA to potential
vulnerabilities and potential risk of compromise.
- The JAWSInspect Browser Extension uses permissions that may not be
necessary for the extension to function. One Critical and one medium risk
permissions for Chrome and Firefox were noted. It is advised that permissions
are verified with the developer and removed if they are not necessary for the
extension to function. Using permissions that are not essential to the
extension’s functionality expose the system, using the JAWSInspect Browser
Extension, to potential vulnerabilities and additional risks that could otherwise
be avoided by disabling nonessential permissions.
- The JAWSInspect Browser Extension will require a 3rd party FIPS 140-2
certified solution for any data containing PHI/PII or VA sensitive information.
- Browser plug-ins and extensions may only be installed by VA Desktop and
Device Engineering and must be used with official VA browser installation
packages. Browser extensions must be kept up to date with security patches
and enhancements. All vulnerability findings must be remediated prior to use
on the VA network.
| | | [9] | 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. | | | [10] | 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. |
|
| Note: |
At the time of writing, version 7.2.11.0 is the most current version, released 03/12/2024. |
