| v4.x |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Approved w/Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
| | | | [1] | Users must ensure that Google Chrome, Microsoft Edge, and Firefox are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology can potentially use Tox, which is not in the TRM.
Per the Security Assessment Review, users must abide by the following constraints:
-
Vulnerability exists because Windows Smart Screen blocks the install/download of the application due to Unknown Publisher. To mitigate, System Owners/Administrators need to be aware the Windows SmartScreen blocks the installation of the product. Once the file is downloaded, the unblock option must be checked in the file properties to allow installation. System Owners/Administrators must also be aware that Microsoft Edge will not allow the download to complete due to an Unknown Publisher and to use Google Chrome.
-
A vulnerability exists because Plover is an open-source solution that uses open-source SQLite, OpenGL, and Python. To mitigate, System owners must ensure any third-party open-source software used with Plover is authorized in the VA TRM and is configured according to VA authorized baseline standards.
-
A vulnerability exists because Plover installs 18 .exe files without a digital signature. This prevents the verification of the control`s publisher and assurance that it has not been tampered with since being published. To mitigate, an administrator shall monitor the .exe files used by the application with a file integrity checker to ensure no unauthorized changes occur.
-
A vulnerability exists because Plover installs OpenSSL versions 1.1.1b and 1.1.1l. OpenSSL 1.1.1d and 1.1.1l are listed as Unapproved on the VA Technical Reference Model (TRM) v24.3. Both versions have multiple published vulnerabilities. To mitigate, System owners should use the latest version of these roducts where possible and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities. Unapproved: his technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as esignated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
| | | [2] | 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. | | | [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] | 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. | | | [5] | 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. | | | [6] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. |
|
