<Past |
Future> |
3.2.x |
Approved w/Constraints [1, 3, 4, 5, 7, 8] |
Approved w/Constraints [1, 3, 4, 5, 7, 8] |
Approved w/Constraints [3, 5, 7, 9] |
Approved w/Constraints [3, 5, 7, 9] |
Approved w/Constraints [3, 5, 7, 9] |
Divest [3, 5, 7, 9] |
Divest [3, 5, 7, 9] |
Divest [3, 5, 7, 9] |
Divest [3, 5, 7, 9] |
Divest [3, 4, 5, 7, 10, 11] |
Divest [3, 4, 5, 7, 10, 11] |
Unapproved |
3.4.x |
Unapproved |
Unapproved |
Approved w/Constraints [3, 5, 7, 9] |
Approved w/Constraints [3, 5, 7, 9] |
Approved w/Constraints [3, 5, 7, 9] |
Approved w/Constraints [3, 5, 7, 9] |
Approved w/Constraints [3, 5, 7, 9] |
Approved w/Constraints [3, 5, 7, 9] |
Approved w/Constraints [3, 5, 7, 9] |
Divest [3, 4, 5, 7, 10, 11] |
Divest [3, 4, 5, 7, 10, 11] |
Unapproved |
3.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 4, 5, 7, 10, 11] |
Divest [3, 4, 5, 7, 10, 11] |
Unapproved |
| | [1] | Users must not allow this software to send automatic updates to the enterprise. Users must also take precautions when Perl modules are downloaded.
This technology has a dependency on the MySQL database. As such the constraints from the MySQL database apply to this entry:
- Product may only be used for Intranet applications.
- Use of this product to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website (https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx). Any use of this product for PHI/PII/VA-sensitive information must be waivered for use by the AERB waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition.
- This technology was added to TRM in 2010 and currently does not have a Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) or an approved VA baseline which is a current VA requirement for the use of this and similar technology. Users of this technology are responsible to document the risk of operating without a VA security baseline in their official risk documentation and have it reviewed by their ISO. DISA currently has plans to release a STIG for this technology in FY 2017 and VA will follow a few months later with a VA security baseline. Once the security baseline is established for this technology, all users of this technology must adhere with that baseline.
| | [2] | 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. | | [3] | 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. | | [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] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. | | [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] | 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] | 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. | | [9] | 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 should be considered especially when an instance of this product will be considered a Moderate or High Risk system (Refer to MySQL Database TRM entry for more details) | | [10] | 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 should be considered especially when an instance of this product will be considered a Moderate or High Risk system (Refer to MySQL Database TRM entry for more details)
Users must ensure that this technology is configured using MySQL - Commercial Edition as the other database technologies, Maria Database (MariaDB) Server and My Structured Query Language (MySQL) Database - Commercial Editions are unapproved technologies. | | [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). |
|
Note: |
At the time of writing, version 3.5.7 is the most current version, released 09/26/2021. |