<Past |
Future> |
8.x |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.x |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 4, 5] |
Divest [2, 5, 6] |
Divest [2, 5, 6] |
Divest [2, 5, 6] |
Divest [2, 5, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.x |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 5, 6] |
Approved w/Constraints [2, 5, 6] |
Divest [2, 5, 6] |
Divest [2, 5, 7] |
Divest [2, 5, 8, 9] |
Divest [2, 5, 8, 9] |
Unapproved |
Unapproved |
11.x |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 5, 6] |
Approved w/Constraints [2, 5, 6] |
Approved w/Constraints [2, 5, 6] |
Approved w/Constraints [2, 5, 7] |
Approved w/Constraints [2, 5, 8, 9] |
Approved w/Constraints [2, 5, 8, 9] |
Approved w/Constraints [2, 5, 8, 9] |
Approved w/Constraints [2, 5, 8, 9] |
12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 5, 6] |
Approved w/Constraints [2, 5, 6] |
Approved w/Constraints [2, 5, 6] |
Approved w/Constraints [2, 5, 7] |
Approved w/Constraints [2, 5, 8, 9] |
Approved w/Constraints [2, 5, 8, 9] |
Approved w/Constraints [2, 5, 8, 9] |
Approved w/Constraints [2, 5, 8, 9] |
14.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Due to several NIST security vulnerabilities, product must remain properly patched in order to mitigate known and future vulnerabilities. | | [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] | 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. | | [4] | Configuration and deployment standards for Cisco Unity Connection 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. | | [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] | Configuration and deployment standards for Cisco Unity Connection images and their host Server images are defined and maintained by the Infrastructure Engineering Organization (contact OIT ITOPS SD IE Managers) within VA ITOPS Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted.
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. | | [7] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: OIT ITOPS SD Engagement Requests) prior to implementation to ensure proper compliance to VA network design and usage requirements. Version 12.X is not for general production use unless approved via coordination with the IO UCIS Standards Team. | | [8] | Version 12.X is not for general production use unless approved via coordination with the IO UCIS Standards Team.
Functionality using the Oracle Java Runtime Environment must not be used. | | [9] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (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 14.0 Service Update 1 (SU1) is the most current version released on 10/27/2021. |