| 6.x (Gen 6) |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
Approved w/Constraints
[3, 6, 7, 8, 9, 10] |
| | | | [1] | Users must not use Secure Sockets Layer. Users must use Open Secure Socket Layer.
Users must not deploy this software with PuTTY. Users must use CyberArk.
This software is configured with a dated version of PostgreSQL and Apache Tomcat. Users must deploy this technology with TRM-approved versions of PostgreSQL and Apache Tomcat. | | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 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 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). | | | [5] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [6] | Users must not use Secure Sockets Layer. Users must use Open Secure Socket Layer.
Users must not deploy this technology with PuTTY as recommended by the vendor`s literature. Users must use an approved alternative to SSH into the server, such as CyberArk.
This technology is, by default, configured with dated and unapproved versions of PostgreSQL and Apache Tomcat (See `Updated System Requirements` in the `Reference` tab). Users must deploy this technology with TRM-approved versions of PostgreSQL and Apache Tomcat.
Users must ensure that PostgreSQL, Firefox, Google Chrome, and Microsoft Internet Explorer (IE) are implemented within VA-approved baselines. | | | [7] | 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. | | | [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] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | | [10] | 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. |
|
