1.0.x |
Unapproved |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 3, 4, 5] |
Approved w/Constraints [1, 3, 4, 5] |
Approved w/Constraints [1, 3, 4, 5] |
Approved w/Constraints [1, 3, 4, 5] |
Approved w/Constraints [1, 3, 4, 5] |
Approved w/Constraints [1, 3, 4, 5] |
Approved w/Constraints [1, 3, 4, 5] |
Authorized w/ Constraints (DIVEST) [3, 4, 5, 6, 7] |
| | [1] | Users must ensure that Google Chrome is 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:
- Angular DevTools Chrome Extension uses permissions that give the extension access to all ftp, http, and https sites. It is recommended to avoid declaring any host permissions by using the active Tab permission.
| | [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 authorized and the user should take the proper steps to decline those installations. | | [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] | 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. | | [5] | 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. | | [6] | Users must ensure that Google Chrome is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
User must not download this technology from Google Chrome Web store, as it requires a POA&M for use on the VA network and is disabled.
Per the Security Assessment Review, users must abide by the following constraints:
- Angular DevTools Browser Extension will require a 3rd party FIPS 140-2 certified solution for any data containing Protected Health Information (PHI) / Personally Identifiable Information (PII) or VA sensitive information.
- The Angular DevTools Browser Extension program/executable should never be run as a root or administrative user.
- The system user or administrator initiating the Angular DevTools Browser Extension process should have robust authentication credentials that prevent unauthorized or casual access.
- Angular DevTools Browser Extension is designed to run in “trusted environments”, and the database does not enable authentication or “Secure Mode” by default.
| | [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. |
|