| 1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
| | | | [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, and Microsoft Edge are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Bitmap Image File (BMP) with this technology.
Per the Security Assessment Review (SAR), users must abide by the following constraints:
- A vulnerability exists because MedVantage Edit and Configure v1.11.4768
installs .exe and .dll 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 and .dll files used by the application with a file integrity
checker to ensure no unauthorized changes occur
- A vulnerability exists because MedVantage Edit and Configure v1.11.4768
installs Open-Source software; Open Graphics Library (OpenGL), SQLite,
and the QT Development Framework. To mitigate, 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
January 04, 2024 For Internal VA Use Only Page 7 of 20
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
- A vulnerability exists because MedVantage Edit and Configure v1.11.4768
cannot be configured to enforce VA password standards. To mitigate,
MedVantage Edit and Configure must have policies in place to have users
comply with a minimum password based authentication standards per VA
Knowledge Service Control IA-5(1).
- A vulnerability exists because MedVantage Edit and Configure v1.11.4768
has the ability to connect to remote Elizabeth Stewart Hands and Associates
(ESHA) Nutritional data sources. To mitigate, the ISSO shall educate and
prohibit users from using the integrated cloud service capability until the VA
Cloud Security Requirements have been met and the affected A&A package
has been appropriately updated
| | | [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] | 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] | 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. | | | [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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [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. |
|
