| 1.x |
Approved w/Constraints
[1, 3, 5, 6, 7] |
Approved w/Constraints
[1, 3, 5, 6, 7] |
Approved w/Constraints
[1, 3, 5, 6, 7] |
Approved w/Constraints
[1, 3, 5, 6, 7] |
Approved w/Constraints
[1, 3, 5, 6, 7] |
Approved w/Constraints
[3, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 5, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 5, 6, 7, 8, 9, 10] |
| | | | [1] | This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
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, users must abide by the following constraints:
- Quest Quanum Utilities Browser Extension uses permissions that give the extension access to privileged fields of the Tab objects used by several APIs including chrome.tabs and chrome.windows. In many circumstances extensions will not need to declare the `tabs` permission to make use of these APIs. Quest Quanum Utilities also uses the nativeMessaging, which is considered medium risk. This permission gives the extension access to the native messaging API.
| | | [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] | 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] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [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] | 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. | | | [7] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [8] | This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Users must ensure that Google Chrome is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
User must not download this technology from Google Chrome Web store, as it is disabled for general use on the VA network.
Users must not utilize Java Communications Application Programming Interface (API), as it is at the time of writing, unapproved in the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
- Quest Quanum Utilities Browser Extension uses permissions that give the extension access to privileged fields of the Tab objects used by several APIs including chrome.tabs and chrome.windows. In many circumstances extensions will not need to declare the `tabs` permission to make use of these APIs. Quest Quanum Utilities also uses the nativeMessaging, which is considered medium risk. This permission gives the extension access to the native messaging API.
| | | [9] | 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. | | | [10] | 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. |
|
