<Past |
Future> |
7.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [2, 3, 4, 5] |
Divest [2, 3, 4, 5] |
Divest [2, 3, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [2, 3, 4, 5] |
Divest [2, 3, 4, 5] |
Divest [2, 3, 4, 5] |
Divest [2, 3, 5, 6] |
Divest [2, 5, 6, 7] |
Divest [2, 6, 7, 8] |
Unapproved |
Unapproved |
10.0 |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 5, 6] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
10.5 |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 5, 6] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
10.6 |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 5, 6] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
11.0 |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 5, 6] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
11.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 5, 6] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
Approved w/Constraints [2, 6, 7, 8] |
11.6 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
12.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [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] | 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. | | [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] | 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] | Configuration and deployment standards for Cisco Unified Contact Center Express (UCCX) images and their host Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a Systems Engineering Design Review (SEDR) (contact VA e-mail: VA IT ESE SEDR SEG) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [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] | Configuration and deployment standards for Cisco Unified Contact Center Express (UCCX) images and their host Server images are defined and maintained by the VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact assessment (contact VA e-mail: OIT ITOPS SD Engagement Requests) prior to implementation to ensure proper compliance to VA network design and usage requirements. |
|
Note: |
At the time of writing, version 12.5(1) SU 2 is the most current version, released 05/02/2022. |