<Past |
Future> |
2.0 |
Divest [1] |
Divest [1, 2] |
Divest [1, 2] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.1 |
Approved w/Constraints [1] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Divest [3, 4] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
2.2 |
Approved w/Constraints [1] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [3, 4] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
2.3 |
Approved w/Constraints [1] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [3, 4] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5, 6] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
2.4 |
Approved w/Constraints [1] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [3, 4] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
2.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5, 6] |
Approved w/Constraints [3, 4, 5] |
Divest [3, 4, 5] |
Divest [3, 4, 5] |
3.2.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
Approved w/Constraints [3, 4, 5] |
3.4.4 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | 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. | | [2] | 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). | | [3] | 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). | | [4] | 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. | | [5] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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. |
|
Note: |
At the time of writing, version 4.0 is the most current version, released 07/11/2022. |