| 2023.1.x |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
Approved w/Constraints
[3, 10, 13, 14, 15] |
| | | | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [2] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) 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 compliant encryption 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 compliant full disk encryption (FOE) must be implemented on the hard drive 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 Security Officer (ISO) 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). | | | [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] | 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. | | | [5] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) 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 compliant encryption 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 compliant full disk encryption (FOE) must be implemented on the hard drive 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 Security Officer (ISO) 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). | | | [6] | 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. | | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
Ensure that MyEclipse and the CVS Server have been configured to supply FIPS 140-2 data encryption. Data encryption shall be enforced using a FIPS-approved algorithm provided by the underlying FIPS-compliant OS. The applications that are developed using MyEclipse must be FIPS compliant to prevent unauthorized disclosure of information and protect sensitive data at rest and during transmission, including PII acknowledged in the end user license as collected, transformed, and used by the licensor, Genuitec.
In addition to isolating the development environment in a separate enclave, appropriate authentication and access control must be enforced to ensure only authorized staff have access to it. The CVS server must be configured to utilize Secure Shell version 2 (SSH2) protocol. | | | [8] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Ensure that MyEclipse and the CVS Server have been configured to supply FIPS 140-2 data encryption. Data encryption shall be enforced using a FIPS-approved algorithm provided by the underlying FIPS-compliant OS. The applications that are developed using MyEclipse must be FIPS compliant to prevent unauthorized disclosure of information and protect sensitive data at rest and during transmission, including PII acknowledged in the end user license as collected, transformed, and used by the licensor, Genuitec.
In addition to isolating the development environment in a separate enclave, appropriate authentication and access control must be enforced to ensure only authorized staff have access to it. The CVS server must be configured to utilize SSH2 protocol. | | | [9] | 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. | | | [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
This technology cannot use Docker which is unapproved at the time of this writing.
Per the Initial Product Review, users must abide by the following constraints:
- This product should be used with a VA approved container platform that has a developed and approved baseline configuration with specific hardening guidance regarding the secure implementation of Genuitec MyEclipse. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information.
- Ensure that MyEclipse and the CVS Server have been configured to supply FIPS 140-2 data encryption. Data encryption shall be enforced using a FIPS-approved algorithm provided by the underlying FIPS-compliant OS. The applications that are developed using MyEclipse must be FIPS compliant to prevent unauthorized disclosure of information and protect sensitive data at rest and during transmission, including PII acknowledged in the end user license as collected, transformed, and used by the licensor, Genuitec.
- In addition to isolating the development environment in a separate enclave, appropriate authentication and access control must be enforced to ensure only authorized staff have access to it. The CVS server must be configured to utilize SSH2 protocol.
| | | [11] | 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 approved and the user should take the proper steps to decline those installations. | | | [12] | 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. | | | [13] | 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. | | | [14] | 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. | | | [15] | 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. |
|
