<Past |
Future> |
2012 (SP2) |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3] |
Approved w/Constraints [2, 3, 5] |
Approved w/Constraints [2, 3, 5] |
Approved w/Constraints [2, 3, 5] |
Approved w/Constraints [2, 3, 5] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Divest [6, 8, 9, 10] |
2016 |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 2, 3, 5] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 5, 6, 7] |
Approved w/Constraints [1, 5, 6, 7] |
Approved w/Constraints [1, 5, 6, 7] |
Divest [6, 8, 9, 10] |
1801 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [6, 8, 9, 10] |
1807 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [6, 8, 9, 10] |
2019 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | [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] | 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. | | [4] | 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). | | [5] | Microsoft System Center Service Manager (SCSM) 2016 is in Evaluation and only Enterprise System Engineering (ESE) Client Services may use the technology at this time for evaluation purposes. This product is currently not approved for production except as part of an official ESE production pilot or production test of this version as approved by ESE Client Services or an AERB waiver while under evaluation. No production deployment dates for Microsoft System Center Service Manager (SCSM) 2016 has been set as of this writing. | | [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] | 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. | | [8] | Only Enterprise System Engineering (ESE) Client Services may use Microsoft System Center Service Manager (SCSM) 2016 for evaluation purposes. The 2016 version is currently not approved for production except as part of an official ESE production pilot or production test of this version as approved by ESE Client Services or a waiver while under evaluation. No production deployment dates for Microsoft System Center Service Manager (SCSM) 2016 has been set as of this writing. | | [9] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | [10] | 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 this, version 2019 is the latest version. |