| 4.x |
Approved w/Constraints
[2, 3, 4, 5] |
Approved w/Constraints
[2, 3, 4, 5] |
Approved w/Constraints
[2, 3, 4, 5] |
Approved w/Constraints
[2, 3, 4, 5] |
Approved w/Constraints
[2, 3, 6, 7, 8] |
Approved w/Constraints
[2, 6, 7, 8, 9, 10] |
Approved w/Constraints
[2, 6, 7, 8, 9, 10] |
Approved w/Constraints
[2, 6, 7, 8, 9, 10] |
Approved w/Constraints
[2, 6, 7, 8, 9, 10] |
Approved w/Constraints
[2, 6, 7, 8, 9, 10] |
Approved w/Constraints
[2, 6, 7, 8, 9, 10] |
Approved w/Constraints
[2, 6, 7, 8, 9, 10] |
| | | | [1] | CVE-2012-2926 specifies a security vulnerability on older versions of Crucible. Implementers must not install any version of Crucible earlier than version 2.9, which allowed remote attackers to read arbitrary files or cause a denial of service. Due to its advertised inability to run in a virtual environment such as the CAG, implementers must consider impact on project operations/processes by VA contractors and staff if intending to implement Crucible inside the VA environment. | | | [2] | 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. | | | [3] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product has been identified as supporting multiple options when selecting its underlying database. Implementers MUST select a database that is approved on the TRM, or is approved with constraints, providing the implementer can satisfy the constraints placed on use of the selected database. | | | [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] | 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). | | | [8] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details. | | | [9] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product has been identified as supporting multiple options when selecting its underlying database. Implementers MUST select a database that is approved on the TRM, or is approved with constraints, providing the implementer can satisfy the constraints placed on use of the selected database.
Users must ensure that Microsoft Internet Explorer (IE), PostgreSQL, Google Chrome, and FireFox are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. | | | [10] | If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details. |
|
