| 9.3.x |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
Approved w/Constraints
[3, 6, 9, 10, 11, 12, 13] |
| | | | [1] | Users must ensure that Microsoft .NET Framework, PostgreSQL, Microsoft Structured Query Language (SQL) Server, Oracle Database, Firefox, Google Chrome, and MongoDB Advanced Enterprise 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 Development Kit (JDK) - Oracle.
This technology must not utilize PostgreSQL version 13.3 as it is not approved on the TRM for use. (refer to Category` tab under `Runtime Dependencies`).
This technology must not utilize MongoDB Advanced Enterprise version 5.2.0 as it is not approved on the TRM for use. (refer to Category` tab under `Runtime Dependencies`).
This technology must not utilize AdoptOpen Java Development Kit (JDK) as it is not approved on the TRM for use. (refer to Category` tab under `Runtime Dependencies`).
This technology must not utilize Open Java Development Kit (JDK) as it is not approved on the TRM for use. (refer to Category` tab under `Runtime Dependencies`).
Users must Divest the use of International Business Machines (IBM) Message Queue (MQ) with this technology. Other approved internet browsers are available. See Category Tab for details. | | | [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] | 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 with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [6] | 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. | | | [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 ISSO (Information System 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 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). | | | [9] | Users must ensure that PostgreSQL, Microsoft Structured Query Language (SQL) Server, Oracle Database, Firefox, Google Chrome, and MongoDB Advanced Enterprise 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 Development Kit (JDK) - Oracle.
This technology must not utilize PostgreSQL version 13.3 as it is not approved on the TRM for use. (refer to Category` tab under `Runtime Dependencies`).
This technology must not utilize MongoDB Advanced Enterprise version 5.2.0 as it is not approved on the TRM for use. (refer to Category` tab under `Runtime Dependencies`).
This technology must not utilize AdoptOpen Java Development Kit (JDK) as it is not approved on the TRM for use. (refer to Category` tab under `Runtime Dependencies`).
This technology must not utilize Open Java Development Kit (JDK) as it is not approved on the TRM for use. (refer to Category` tab under `Runtime Dependencies`). | | | [10] | 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. | | | [11] | 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. | | | [12] | 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). | | | [13] | 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. |
|
