2.x |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Approved w/Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
Authorized w/ Constraints [2, 3, 4, 5, 6] |
| | [1] | Product permissions should be 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 Siteimprove Accessibility Checker Browser Extension, to potential vulnerabilities and addition risk that could otherwise be avoided by disabling nonessential permissions.
To secure DOM XSS injection sinks, consider requiring Trusted Types for scripts. This can be achieved by including the phrase `require-trusted-types-for `script`` in user policy. Where possible, take into account constraining object-src to `none.`
Users must ensure that Google Chrome is implemented with VA-authorized baselines.
Users must not utilize Opera (Opera Desktop) as it currently unapproved on TRM | | [2] | Per the Security Assessment Review, users must abide by the following constraints:
- The Siteimprove Accessibility Checker Browser Extension uses permissions that
may not be necessary for the extension to function. One medium risk permission
was 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 Siteimprove Accessibility Checker Browser Extension, to
potential vulnerabilities and addition risk that could otherwise be avoided by
disabling nonessential permissions.
- Siteimprove Accessibility Checker’s use of ‘self’ can be problematic if you host
JSONP, Angular or user uploaded files. `unsafe-eval` allows the execution of code injected into DOM APIs such as eval(). Consider requiring Trusted Types
for scripts to lock down DOM XSS injection sinks. This can be done by adding
`require-trusted-types-for `script`` to your policy. Consider restricting object-src to
`none` only if possible.
Users must ensure that Google Chrome, Firefox, and Microsoft Edge are implemented with VA-authorized baselines.
Users must not utilize Opera (Opera Desktop), as it, at the time of writing, requires a POA&M. | | [3] | 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. | | [4] | 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). | | [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] | 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. |
|