| 3.x |
Approved w/Constraints
[3, 4, 5, 6] |
Approved w/Constraints
[3, 4, 5, 6] |
Approved w/Constraints
[3, 7, 8, 9] |
Approved w/Constraints
[3, 7, 8, 9] |
Approved w/Constraints
[3, 7, 8, 9] |
Approved w/Constraints
[3, 7, 8, 9] |
Approved w/Constraints
[3, 7, 8, 9] |
Approved w/Constraints
[7, 8, 9, 10] |
Approved w/Constraints
[7, 8, 9, 10] |
Approved w/Constraints
[7, 8, 9, 10] |
Approved w/Constraints
[8, 9, 10, 11] |
Approved w/Constraints
[8, 9, 10, 11] |
| | | | [1] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | | [2] | Version 2.x of this product is prohibited due to a high security vulnerability. | | | [3] | 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. | | | [4] | 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. | | | [5] | Version 2.x of this product is prohibited due to a high security vulnerability.
This technology depends on MySQL which may only be used for Intranet applications and my not be used with PII/PHI/VA Sensitive information as of this writing. MySQL TRM constraints also apply to this product. See the MySQL TRM entry for more information. | | | [6] | 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). | | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Due to National Institute of Standards and Technology (NIST) vulnerabilities or VA Network Security Operations Center (NSOC) bulletins, versions 2.x and older are prohibited from use.
This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If 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 the MySQL Database TRM entry for more details. | | | [8] | 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. | | | [9] | 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. | | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Due to National Institute of Standards and Technology (NIST) vulnerabilities or VA Network Security Operations Center (NSOC) bulletins, versions 2.x and older are prohibited from use.
This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If 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 the MySQL Database TRM entry for more details. |
|
