1.x |
Approved w/Constraints [1, 3, 4, 5] |
Approved w/Constraints [3, 4, 5, 6, 7, 8] |
Approved w/Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
Authorized w/ Constraints [3, 4, 5, 6, 7, 8] |
| | [1] | Users must ensure that Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
The Microsoft store is unapproved for use on the VA network and is disabled. Because of this, technology that is ONLY available through the MS store cannot be authorized because it is impossible to obtain.
Per Section 7 of the Security Assessment Review (SAR), users must abide by the following constraint:
- For browser plugins/extensions to be included in the national standard configuration, a request and a business justification must be submitted to Desktop and Device Engineering at the following URL: https://dvagov.sharepoint.com/sites/oitdde/SitePages/Requests.aspx
| | [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 Firefox, Microsoft Edge, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not download this technology from Microsoft Store, as it is unapproved for use on the VA network and is disabled.
Per the Security Assessment Review (SAR), users must abide by the following constraint:
- OneTab Browser Extension uses permissions that give the extension access to privileged fields of the Tab objects used by several APIs including chrome.storage. In many circumstances extensions will not need to declare the `tabs` permission to make use of these APIs.
| | [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] | 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. |
|