6.6.x |
Unapproved |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
Approved w/Constraints [3, 4, 5, 6, 7] |
| | [1] | Per the Initial Product Review, users must abide by the following constraints:
- Vue.js Devtools will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information where applicable.
- Vue.js Devtools uses permissions that give the extension access to run on all http and https sites. It may be possible to avoid declaring any host permissions by using the activeTab permission.
- Vue.js Devtools is an open source technology. Product updates and support may be limited. System Owners/Administrators should verify the latest version of the stable product is being used.
Users must ensure that Firefox and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [2] | 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 approved and the user should take the proper steps to decline those installations. | | [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] | 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 approved and the user should take the proper steps to decline those installations. | | [5] | Users must ensure that Firefox, Microsoft Edge, 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 Vue.js devtools v6.5.1 Browser Extension uses permissions that may not be necessary for the extension to function. One Critical and one medium risk permissions for Chrome and Edge 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 Vue.js devtools v6.5.1 Browser Extension, to potential vulnerabilities and additional risks that could otherwise be avoided by disabling nonessential permissions.
| | [6] | 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. | | [7] | 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. |
|