1.0.0 |
Authorized w/ Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [1, 2, 3, 4] |
| | [1] | User must not download this technology from Google Chrome Web store, as it is disabled for general use on the VA network.
Users must ensure that Google Chrome is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review (SAR), users must abide by the following constraints:
- Clear Cache for Current Tab Chrome Extension is not Federal Information Processing standards (FIPS) 140-2 (or its successor) certified and will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- Clear Cache for Current Tab Chrome Extension uses permissions that may not be necessary for the extension to function. One medium and one low risk permission for Chrome was 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 Clear Cache for Current Tab, to potential vulnerabilities and additional risks that could otherwise be avoided by disabling nonessential permissions. Two findings regarding Chrome permissions were found:
• Medium:
o activeTab - The activeTab permission gives an extension temporary
access to the currently active tab when the user invokes the extension -
for example by clicking its browser action. Access to the tab lasts while
the user is on that page, and is revoked when the user navigates away
or closes the tab.
• Low:
o BrowsingData - The chrome.browsingData API is used for removing
browsing data from a user`s local profile.
- The browser extension was last updated 22 months ago. Security Engineering conducted vulnerability scans and did not find any active Common Vulnerabilities and Exposures (CVE’s). The developer, an individual, was contacted and stated that the extension is currently supported and receiving updates as needed. However, this does present a risk. The individual could abandon the project at any time, as there is no vendor or development team. Unsupported software products should not be used because fixes to newly
identified bugs will not be implemented by the developer. The lack of security updates can result in potential vulnerabilities.
| | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [3] | 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. | | [4] | 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. |
|