4.x |
Approved w/Constraints [2, 4, 6, 7] |
Approved w/Constraints [2, 4, 6, 7] |
Approved w/Constraints [2, 4, 6, 7] |
Approved w/Constraints [2, 4, 6, 8] |
Approved w/Constraints [2, 4, 6, 8] |
Approved w/Constraints [2, 6, 8, 9, 10, 11, 12] |
Approved w/Constraints [2, 6, 8, 9, 10, 11, 12] |
Authorized w/ Constraints [2, 6, 8, 9, 10, 11, 12] |
Authorized w/ Constraints [2, 6, 8, 9, 10, 11, 12] |
Authorized w/ Constraints [2, 6, 8, 9, 10, 11, 12] |
Authorized w/ Constraints [2, 6, 8, 9, 10, 11, 12] |
Authorized w/ Constraints [2, 6, 8, 9, 10, 11, 12] |
| | [1] | 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. | | [2] | 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. | | [3] | 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. | | [4] | Per the Initial Product Review, users must abide by the following constraints:
- Deque axe DevTools will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- 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.
- Browser Extensions must be authorized on the TRM and supported by Solution Delivery, Desktop and Device Engineering.
- The system user or administrator initiating Deque axe DevTools must have robust authentication credentials, which includes PIV-compliant two-factor authentication (2FA), to prevent unauthorized or casual execution of the application.
| | [5] | 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. | | [6] | 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. | | [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 VA Handbook 6500. | | [8] | 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. | | [9] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Firefox, Google Chrome, and Microsoft Edge are 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:
- The Axe DevTools Browser Extension uses permissions that may not be necessary for the extension to function. A combined total of two critical, three high, three medium and one low risk permissions for Chrome, Firefox 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 Axe DevTools Browser Extension to potential vulnerabilities and additional risks that could otherwise be avoided by disabling nonessential permissions.
- xe DevTools Browser Extension will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- Browser plug-ins and extensions may only be installed by VA Desktop and Device Engineering and must be used with official VA browser installation packages. Browser extensions must be kept up to date with security patches and enhancements. All vulnerability findings must be remediated prior to use on the VA network.
| | [10] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [11] | 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. | | [12] | 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. |
|