| 2.1.x |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 3, 4, 5, 6] |
Approved w/Constraints
[1, 3, 4, 5, 6] |
Approved w/Constraints
[1, 3, 4, 5, 6] |
Approved w/Constraints
[1, 3, 4, 5, 6] |
Approved w/Constraints
[1, 3, 4, 5, 6] |
Approved w/Constraints
[1, 3, 4, 5, 6] |
Approved w/Constraints
[1, 3, 4, 5, 6] |
Approved w/Constraints
[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 Initial Product Review, users must abide by the following constraints:
- Ensure that the underlying infrastructure (Operating System (OS), Web Server, etc.) or a third party Federal Information Processing Standards (FIPS) 140-2 cryptographic module can protect the security of the application when it processes, stores, or transmits VA sensitive information.
- Access to this testing utility should be monitored accordingly to prevent unauthorized usage and possible modification to applications. In addition, this technology should not be used in the VA production environment.
| | | [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] | 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. | | | [4] | 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. | | | [5] | 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. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [7] | 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:
- The Page Diagnostics for SharePoint Browser Extension uses permissions that may not be necessary for the extension to function. Two critical, two high and two medium risk permissions were noted. It is advised that permissions are verified with the developer and removed if they are not absolutely necessary for the extension to function. Using permissions that are not essential to the extension’s functionality expose the system, using the Page Diagnostics for SharePoint Browser Extension, to potential vulnerabilities and addition risk that could otherwise be avoided by disabling nonessential permissions.
|
|
