<Past |
Future> |
8.2.x |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [5, 6, 7, 8] |
Divest [5, 6, 8, 9] |
Divest [5, 6, 8, 9] |
Divest [5, 6, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.3.x |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [5, 6, 7, 8] |
Divest [5, 6, 8, 9] |
Divest [5, 6, 8, 9] |
Divest [5, 6, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.4.x |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Divest [5, 6, 8, 9] |
Divest [5, 6, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
8.5.x |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Divest [5, 6, 8, 9] |
Divest [5, 6, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
2017.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5, 6, 7, 8] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Approved w/Constraints [5, 6, 8, 9] |
Divest [5, 8, 9] |
Divest [5, 8, 9] |
Unapproved |
2019.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [5, 8, 9] |
Divest [5, 8, 9] |
Unapproved |
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 |
| | [1] | Public cloud features of this software may not be used without Enterprise Security Change Control Board (ESCCB) review and approval to ensure that confidential organization and/or PII/PHI data are not compromised. Use of public cloud storage may require documented Federal Risk and Authorization Management Program (FedRAMP) compliance and/or a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review if sensitive information is involved. Users interested in using these features should consult their local ISO or OIT representative for additional information. | | [2] | 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. | | [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] | 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] | 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. | | [7] | Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [8] | 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). | | [9] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
Note: |
At the time of writing, version 2022.3.1 is the most current version. |