| 6.1.x |
Unapproved |
Approved w/Constraints
[6, 14, 15, 16, 17, 18, 19, 20] |
Approved w/Constraints
[6, 14, 15, 16, 17, 18, 19, 20] |
Approved w/Constraints
[6, 14, 15, 17, 18, 19, 20, 21] |
Approved w/Constraints
[6, 14, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints
[6, 14, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints
[6, 14, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints
[6, 14, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints
[6, 14, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints
[6, 14, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints
[6, 14, 15, 17, 19, 20, 21, 22] |
Approved w/Constraints
[6, 14, 15, 17, 19, 20, 21, 22] |
| | | | [1] | Approval is limited to use within Office of Information Technology (OIT)-controlled software test laboratories in order to support interface testing processes only. Use of this interface engine as a substitute to already-approved and/or nationally implemented interface engines is not allowed. Production use of this software outside of software test laboratories is not approved. | | | [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] | Approval is limited to use within Office of Information Technology (OIT)-controlled software test laboratories in order to support interface testing processes only. Use of this interface engine as a substitute to already-approved and/or nationally implemented interface engines is not allowed. Production use of this software outside of software test laboratories is not approved.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [4] | Approval is limited to use within Office of Information Technology (OIT)-controlled software test laboratories in order to support interface testing processes only. Use of this interface engine as a substitute to already-approved and/or nationally implemented interface engines is not allowed. Production use of this software outside of software test laboratories is not approved.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product can be configured with Microsoft Access and MySQL, which currently have TRM constraints for VA sensitive data and internet usage, respectively. If Microsoft Access or MySQL is selected for use with this product, these factors must be considered. (Refer to Microsoft Access and MySQL TRM entries for more details.) | | | [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] | 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. | | | [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] | Approval is limited to use within Office of Information Technology (OIT)-controlled software test laboratories in order to support interface testing processes only. Use of this interface engine as a substitute to already-approved and/or nationally implemented interface engines is not allowed. Production use of this software outside of software test laboratories is not approved.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product can be configured with Microsoft Access and MySQL, which currently have TRM constraints for VA sensitive data and internet usage, respectively. If Microsoft Access or MySQL is selected for use with this product, these factors must be considered. (Refer to Microsoft Access and MySQL TRM entries for more details.) | | | [9] | Approval is limited to use within Office of Information Technology (OIT)-controlled software test laboratories in order to support interface testing processes only. Use of this interface engine as a substitute to already-approved and/or nationally implemented interface engines is not allowed. Production use of this software outside of software test laboratories is not approved.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product can be configured with Microsoft Access and MySQL, which currently have TRM constraints for VA sensitive data and internet usage, respectively. If Microsoft Access or MySQL is selected for use with this product, these factors must be considered. (Refer to Microsoft Access and MySQL TRM entries for more details.)
Users must ensure that Microsoft Internet Explorer (IE) is implemented with VA-approved baselines. | | | [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] | Approval is limited to use within Office of Information Technology (OIT)-controlled software test laboratories in order to support interface testing processes only. Use of this interface engine as a substitute to already-approved and/or nationally implemented interface engines is not allowed. Production use of this software outside of software test laboratories is not approved.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize the Maria Database (MariaDB) Server, as it is unapproved for use on the TRM.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
Users must ensure that Google Chrome, Firefox, Oracle Database, Microsoft Structured Query Language (SQL) Server, Microsoft Access, My Structured Query Language (MySQL) Database - Commercial Editions, and PostgreSQL are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [13] | 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. | | | [14] | 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. | | | [15] | 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. | | | [16] | 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. | | | [17] | 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. | | | [18] | 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). | | | [19] | Approval is limited to use within Office of Information Technology (OIT)-controlled software test laboratories in order to support interface testing processes only. Use of this interface engine as a substitute to already-approved and/or nationally implemented interface engines is not allowed. Production use of this software outside of software test laboratories is not approved.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize the Maria Database (MariaDB) Server, as it is unapproved for use on the TRM.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
Users must ensure that Oracle Database, Microsoft Structured Query Language (SQL) Server, Microsoft Access, and My Structured Query Language (MySQL) Database - Commercial Editions are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [20] | 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. | | | [21] | 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. | | | [22] | 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. |
|
