<Past |
Future> |
2013.4.4.0 |
Approved w/Constraints [2, 3, 4] |
Unapproved |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
2014.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2015.x |
Approved w/Constraints [2, 3, 4] |
Unapproved |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
2016.x |
Approved w/Constraints [2, 3, 4] |
Unapproved |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
2017.x |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
2018.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
2019.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
2020.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2021.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2022.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2023.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2024.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, Federal Information Processing Standard (FIPS) 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption in not used, additional mitigating controls must be documented in an approved System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)), unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. | | [2] | 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. | | [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] | 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] | 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. | | [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). |
|
Note: |
At the time of writing, version 2024.100.3.2 is the most current version, released 01/01/2024. |