| 9.5.x |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Divest
[2, 3, 5, 6, 9] |
Divest
[2, 3, 5, 6, 10] |
Divest
[2, 3, 5, 6, 10] |
Divest
[2, 3, 5, 6, 10] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| 9.6.x |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Approved w/Constraints
[2, 3, 5, 6, 9] |
Approved w/Constraints
[2, 3, 5, 6, 10] |
Approved w/Constraints
[2, 3, 5, 6, 10] |
Divest
[2, 3, 5, 6, 10] |
Divest
[2, 3, 11, 12, 13] |
Divest
[2, 3, 11, 12, 13] |
Divest
[2, 3, 11, 12, 13, 14] |
Divest
[2, 3, 11, 12, 13, 14] |
| | | | [1] | 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). | | | [2] | 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. | | | [3] | 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. | | | [4] | Use of this technology must strictly conform to the DISA STIG guidelines for versions 9.x and VA Handbook 6500 related policies while VA finalizes an enterprise baseline. Once published in the coming months, all users will be required to conform to the new enterprise baseline. | | | [5] | 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). | | | [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] | 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. | | | [8] | Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. | | | [9] | Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in Information Technology Operations and Services (ITOPS) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. | | | [10] | VA Configuration baseline and deployment standards for this technology must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. | | | [11] | VA Configuration baseline and deployment standards for this technology must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
Users must take note that the baseline configuration has been developed solely for Red Hat Enterprise Linux (RHEL) systems. Until a baseline configuration has been developed for other operating systems, PostgreSQL must only be used on RHEL systems. | | | [12] | 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). | | | [13] | 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. | | | [14] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. |
|
