| 6.1.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[2, 3, 4, 5, 6, 7] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
Approved w/Constraints
[2, 3, 4, 6, 7, 8] |
| | | | [1] | Users must ensure that Google Chrome is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
System owners should use FIPS compliant software to ensure VA sensitive
data containing PII/PHI is protected with FIPS 140-2 validated technology when
applicable.
Due to potential information security risks, SaaS/PaaS solutions must complete
the Veterans-Focused Integration Process Request (VIPR) process where a
collaborative effort between Demand Management (DM), Enterprise Program
Management Office Information Assurance (EPMO IA), Project Special Forces
(PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer
(CTO), and stakeholders determines the SaaS/PaaS category during the
Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are
routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical
oversight, acquisition, production, and sustainment provided by PSF.
When using third party applications with BlazeMeter, it is advised System
owners use the most up to date tools to ensure there are no outstanding
vulnerabilities. | | | [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] | 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:
The BlazeMeter v6.0.0 Chrome Extensions dependencies are outdated and pose a security risk to VA data. VA systems using this Chrome Extension will be more vulnerable to Ransomware attacks, malware and data breaches.
The BlazeMeter v6.0.0 Chrome Extension uses permissions that may not be necessary for the extension to function. One critical, three high, two medium, and three low 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 BlazeMeter v6.0.0 Chrome Extension, to potential vulnerabilities and addition risk that could otherwise be avoided by
disabling nonessential permissions.
BlazeMeter’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. You can do this by adding `require-trusted-types-for `script`` to your policy. Consider restricting object-src to `none` only if possible. | | | [4] | 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. | | | [5] | 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 with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [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] | 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. | | | [8] | 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). |
|
