| 4.x |
Approved w/Constraints
[1] |
Approved w/Constraints
[1] |
Approved w/Constraints
[2, 3, 4, 5, 6] |
Approved w/Constraints
[2, 3, 4, 5, 6] |
Approved w/Constraints
[2, 3, 4, 5, 6] |
Approved w/Constraints
[2, 3, 4, 5, 6] |
Approved w/Constraints
[3, 5, 7, 8] |
Approved w/Constraints
[3, 5, 7, 8] |
Approved w/Constraints
[3, 5, 7, 8] |
Approved w/Constraints
[3, 5, 7, 8] |
Approved w/Constraints
[3, 5, 7, 8] |
Approved w/Constraints
[5, 7, 8, 9] |
| | | | [1] | National Service Desk (NSD) standards for IT service (help) desk should be followed if used within the Office of Information and Technology (OI&T) for support of IT systems. Note: As of this writing, this technology depends on a MySQL database and MySQL is currently restricted to intranet application use only in TRM. Please see the MySQL TRM entry for full details and current restrictions.
Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to encrypt data in transit and at rest if Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information is involved or additional mitigating controls must be documented in an approved System Security Plan (SSP). Additionally, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)).
| | | [2] | National Service Desk (NSD) standards for IT service (help) desk should be followed if used within the Office of Information and Technology (OI&T) for support of IT systems.
As of this writing, this technology depends on a MySQL database and MySQL is currently restricted to intranet application use only in TRM. Please see the MySQL TRM entry for full details and current restrictions. | | | [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] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | | [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] | 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.
This product can be configured with a My Structured Query Language (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 have to 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] | 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. |
|
