<Past |
Future> |
2.0.x |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 6, 7] |
Approved w/Constraints [1, 3, 6, 7] |
Divest [3, 6, 7, 8, 9, 10] |
Divest [3, 6, 7, 8, 9, 10] |
Divest [3, 6, 7, 8, 9, 10] |
Divest [3, 6, 7, 8, 9, 10] |
Divest [3, 6, 7, 8, 9, 10] |
Divest [3, 6, 7, 8, 9, 10] |
Unapproved |
7.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 6, 7, 8, 9, 10] |
Approved w/Constraints [3, 6, 7, 8, 9, 10] |
Approved w/Constraints [3, 6, 7, 8, 9, 10] |
Approved w/Constraints [3, 6, 7, 8, 9, 10] |
Approved w/Constraints [3, 6, 7, 8, 9, 10] |
Approved w/Constraints [3, 6, 7, 8, 9, 10] |
Approved w/Constraints [3, 6, 7, 8, 9, 10] |
| | [1] | Users must ensure that Firefox and Google Chrome are implemented with VA-approved 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] | 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] | 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. | | [4] | 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. | | [5] | 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. | | [6] | 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. | | [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-approved 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] | 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. | | [10] | 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. |
|
Note: |
At the time of writing, version 7.2.11.0 is the most current version, released 03/12/2024. |