| 3.6.x |
Approved w/Constraints
[3, 6, 7, 8, 9] |
Approved w/Constraints
[3, 6, 7, 8, 9] |
Approved w/Constraints
[3, 6, 7, 8, 9] |
Approved w/Constraints
[3, 6, 7, 8, 9] |
Approved w/Constraints
[3, 7, 9, 10, 11] |
Approved w/Constraints
[3, 7, 9, 10, 11] |
Divest
[3, 4, 10, 11, 12, 13] |
Divest
[3, 4, 10, 11, 12, 13] |
Divest
[3, 4, 10, 11, 12, 13] |
Divest
[3, 4, 10, 11, 12, 13] |
Divest
[3, 4, 10, 11, 12, 13] |
Divest
[3, 4, 10, 11, 12, 13] |
| 3.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[3, 4, 10, 11, 12, 13] |
Approved w/Constraints
[3, 4, 10, 11, 12, 13] |
Approved w/Constraints
[3, 4, 10, 11, 12, 13] |
Approved w/Constraints
[3, 4, 10, 11, 12, 13] |
Approved w/Constraints
[3, 4, 10, 11, 12, 13] |
Approved w/Constraints
[3, 4, 10, 11, 12, 13] |
| | | | [1] | Projects must use version 3.0.5 or greater and ensure that all patches and updates are applied in accordance with VA Handbook 6500 policy to mitigate known and future security vulnerabilities, or additional mitigating controls must be documented in an approved System Security Plan (SSP). | | | [2] | Projects using this technology must ensure that project build configurations are interoperable with the VA enterprise-level build technology, Rational Build Forge. | | | [3] | 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. | | | [4] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | | [5] | 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. | | | [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] | 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. | | | [8] | 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). | | | [9] | This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Use a FIPS 140-2 validated cryptographic module to secure VA sensitive data in development projects that use Maven. It may be possible to leverage the cryptographic module of the underlying Operating System or use a FIPS 140-2 validated cryptographic service provider.
- Developers need to stay on top of the Maven development activities to ensure software updates and patches to the Maven software are tested and installed in a timely manner. Additionally, developers need to constantly monitor the various resources within the Apache community to get the most up to date information on Maven vulnerabilities as well as solutions to mitigate and remediate the vulnerabilities.
- Ensure the latest version of Java is installed for use with Maven.
| | | [10] | 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. | | | [11] | 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). | | | [12] | This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Maven will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- Users should check with their supervisor, 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.
- Ensure the latest version of Java is installed for use with Maven.
| | | [13] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. |
|
