ApprovedProductsList.pdf

DEFENSE INFORMATION SYSTEMS AGENCY

P. O. BOX 549

FORT MEADE, MARYLAND 20755-0549

IN REPLY

REFER TO: Network Services (NSP) 18 Jul 2014

MEMORANDUM FOR DISTRIBUTION

SUBJECT: Department of Defense (DoD) Unified Capabilities (UC) Approved Products List

(APL) approval of the Avaya (formerly Radvision) Scopia Elite Family with Software Release (SR) 7.5.1.11.19 and the Avaya (formerly Radvision) Scopia 100 S40 with SR 5.7.2.0.G Tracking number (TN) 1028101 as a Video Teleconferencing (VTC) system

Reference: (a) DoDI 8100.04, “DoD Unified Capabilities,” 09 Dec 2010

(b) DoD CIO “Unified Capabilities Requirements (UCR 2008, Change 3),” Sep

1. DoD UC APL approval of the Avaya Scopia Elite Family SR 7.5.1.11.19 and the Avaya Scopia 100 S40 SR 5.7.2.0.G TN 1028101 as a VTC system has been granted. The following components were certified:

Model Software version Avaya Scopia Elite 5230 7.5.1.11.9

7.5.1.11.19 Avaya Scopia Elite 5110

Avaya Scopia Elite 5115

The Field Security Operations (FSO) recommended certification on 07 Jul 2011 based on the security testing completed by the Air Force Test Facility, Telecommunication Systems Security Assessment Program (TSSAP)-led Information Assurance (IA) test teams. This solution achieved Interoperability Certification (IOC) from the Joint Interoperability Test Command (JITC) on 20 Jul 2011. This approval is effective upon the date of this memorandum and expires 18 Jul 2017 unless a critical issue is identified that invalidates either the Interoperability (IO) or the IA posture of this product as determined by the JITC or the Chief Information Officers for Combatant Commands, Services, and Agencies. Please note that Services and Agencies are required to recertify and reaccredit their systems every three years. Please refer to the UC APL for official posting of this solution at the following URL: https://aplits.disa.mil.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’ Designated Accrediting Authority (DAA):

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the Defense/IA Security Accreditation Working Group (DSAWG) and the Program Management Office (PMO).

DISA Memo, NSP, UC APL Approval Memo, Avaya Scopia Elite Family SR 7.5.1.11.19 and the Avaya Scopia 100 S40 SR 5.7.2.0.G TN 1028101, 18 Jul 2014.

b. The configuration must be in compliance with the Avaya Scopia Elite Family SR

7.5.1.11.19 and the Avaya Scopia 100 S40 SR 5.7.2.0.G TN 1028101’s military-unique features deployment guide.

c. Enable secure mode for the Avaya Scopia Elite SR 7.5.1.11.19 system. The system shall operate in secure mode when connected to the network. See deployment guide to configure the system in secure mode.

d. Remote management services such as Hypertext Transfer Protocol (HTTP) and Secure Shell (SSH) are not allowed to be used. Turning on these services can open potential security holes.

e. Local management done via serial port interface is not allowed to be use.

f. Device management workstation must be Common Access Card (CAC) enabled.

3. The IOC letter containing detailed configuration on this product is available at the following URL: http://jitc.fhu.disa.mil/tssi/cert_pdfs/radvision_scopia_elite_jul11.pdf On 25 Jan 2012, the following extension was approved via Desktop Review (DTR) #1 (to change the System Under Test (SUT)’s software from SR 7.5.1.11.9 to SR 7.5.1.11.19. The DTR also closed the following IA findings based on the vendor Plan of Action and Milestone (POA&M):

the SUT was not Public Key Infrastructure (PKI)-enabled, it was not IPv6 compliant per UCR 2008, Change 3, and it did not implement a warning message when log messages were full):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/radvision_vtc_dtr1_feb12.pdf On 09 Nov 2012, the following extension was approved via DTR #2 (to include the name of Avaya Scopia 100 S40 as the gateway. The Polycom Serial Gateway S4GW, which has been certified, is identical to the Avaya Scopia 100 S40, except for product labeling, so this is a change in product name from Polycom Serial Gateway S4GW to Avaya Scopia 100 S40):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/radvision_scopia_vtc_dtr2_nov12.pdf On 18 Jul 2014, the following extension was approved via DTR #3 (requested to extend the listing of this solution on the UC APL for an additional 3 years.)

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contains the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government civilian or uniformed military personnel.

E-Mail: disa.meade.ns.list.unified-capabilities-certification-office@mail.mil UCCO Process Manager: (571) 359-4363

For:

JESSIE L. SHOWERS, JR., PMP

Vice Director for Network Services

-2-

P. O. BOX 4502

ARLINGTON, VIRGINIA 22204-4502

REFER TO: Network Services (NS231) 15 Sep 2014

(APL) approval of the Lifesize Express, Lifesize Express 200 and Lifesize Express 220 with Software Release (Rel.) 4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) Tracking number (TN) 1031301 as a Video Teleconferencing (VTC) system.

Reference: (a) DoDI 8100.04, “DoD Unified Capabilities,” 09 Dec 2010.

1. DoD UC APL approval of the Lifesize Express, Lifesize Express 200 and Lifesize Express 220 Rel. 4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) TN 1031301 as a VTC system has been granted. The Field Security Operations (FSO) recommended certification on 25 May 2011 based on the security testing completed by Defense Information Systems Agency (DISA)-led Information Assurance test teams. This solution achieved Interoperability Certification (IOC) from the Joint Staff (JS) on 16 Jun 2011. This approval is effective upon the date of this memorandum and expires 15 Sep 2017 unless a critical issue is identified that invalidates either the Interoperability or the IA posture of this product as determined by the JS or the Defense Information Systems Network (DISN) Designated Approving Authority (DAA). Please note that Services and Agencies are required to recertify and reaccredit their systems every three years.

Please refer to the UC APL for official posting of this solution at the following URL:

http://www.disa.mil/ucco.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’

DAA:

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the DSAWG and the Program Management Office (PMO).

b. The configuration must be in compliance with the Lifesize Express’s military-unique features deployment guide.

c. Remote management services such as HTTP, SSH, SNMP, and serial port (if available) shall not be used do to security vulnerabilities discovered during APL testing.

d. Disable remote camera monitoring. This function requires a remote management service to be enabled to transmit the camera view. This function was disabled for APL testing.

e. Certain functions, such as software updates, require the HTTP server to be enabled. The proper procedure for this is to remove the System Under Test (SUT) from the Defense Switched Network (DSN), enable the applicable services per the vendor documentation, perform the function, follow the vendor deployment guide to re-harden the SUT, and then reconnect the SUT to the DSN.

DISA Memo, NS231, UC APL Approval Memo, Lifesize Express, Lifesize Express 200 and Lifesize Express 220 Rel. 4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) TN 1031301, 15 Sep 2014.

f. The Lifesize Video System must be implemented with specific installation and configurations because alert messages for crucial settings are not included at this time. These specific installation instructions will be included in the Lifesize Deployment Guide.

g. Fielding physical access to the Lifesize Video Codec must be protected to ensure IP address information cannot be read by un-cleared personnel.

h. An Intrusion Prevention System (IPS) with automated virus-scanning capability must be deployed in-line between the Lifesize Video System and other IP networks.

i. A network-based firewall must be deployed to filter ICMPv6 echo-requests and echo-replies specifically destined to and from the Lifesize Video System.

3. The IOC letter containing detailed configuration on this product is available at the following URL: http://jitc.fhu.disa.mil/tssi/cert_pdfs/lifesizeexpress_jun11.pdf On 15 Sep 2014, the following extension was approved via Desktop Review (DTR) #1 (requested to extend the listing of this solution on the UC APL for an additional 3 years)

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contained the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government civilian or uniformed military personnel.

(APL) approval of the Lifesize Room, Lifesize Room 200 and Lifesize Room 220 with Software Release (Rel.) 4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) Tracking number (TN) 1031302 as a Video Teleconferencing (VTC) system.

1. DoD UC APL approval of the Lifesize Room, Lifesize Room 200 and Lifesize Room 220 Rel. 4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) TN 1031302 as a VTC system has been granted. The Field Security Operations (FSO) recommended certification on 25 May 2011 based on the security testing completed by Defense Information Systems Agency (DISA)-led Information Assurance test teams. This solution achieved Interoperability Certification (IOC) from the Joint Staff (JS) on 16 Jun 2011. This approval is effective upon the date of this memorandum and expires 15 Sep 2017 unless a critical issue is identified that invalidates either the Interoperability or the IA posture of this product as determined by the JS or the Defense Information Systems Network (DISN) Designated Approving Authority (DAA). Please note that Services and Agencies are required to recertify and reaccredit their systems every three years.

Please refer to the UC APL for official posting of this solution at the following URL:

http://www.disa.mil/ucco.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’

DAA:

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the DSAWG and the Program Management Office (PMO).

b. The configuration must be in compliance with the Lifesize Room’s military-unique features deployment guide.

c. Remote management services such as HTTP, SSH, SNMP, and serial port (if available) shall not be used do to security vulnerabilities discovered during APL testing.

d. Disable remote camera monitoring. This function requires a remote management service to be enabled to transmit the camera view. This function was disabled for APL testing.

e. Certain functions, such as software updates, require the HTTP server to be enabled. The proper procedure for this is to remove the System Under Test (SUT) from the Defense Switched Network (DSN), enable the applicable services per the vendor documentation, perform the

DISA Memo, NS231, UC APL Approval Memo, Lifesize Room, Lifesize Room 200 and Lifesize Room 220 Rel. 4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) TN 1031302, 15 Sep 2014.

specific installation instructions will be included in the Lifesize Deployment Guide.

g. Fielding physical access to the Lifesize Video Codec must be protected to ensure IP address information cannot be read by un-cleared personnel.

h. An Intrusion Prevention System (IPS) with automated virus-scanning capability must be deployed in-line between the Lifesize Video System and other IP networks.

i. A network-based firewall must be deployed to filter ICMPv6 echo-requests and echo-replies specifically destined to and from the Lifesize Video System.

3. The IOC letter containing detailed configuration on this product is available at the following URL: http://jitc.fhu.disa.mil/tssi/cert_pdfs/lifesizeroom_jun11.pdf On 15 Sep 2014, the following extension was approved via Desktop Review (DTR) #1 (requested to extend the listing of this solution on the UC APL for an additional 3 years)

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contained the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government civilian or uniformed military personnel.

(APL) approval of the Lifesize Team, Lifesize Team 200 and Lifesize Team 220 with Software Release (Rel.) 4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) Tracking number (TN) 1031303 as a Video Teleconferencing (VTC) system.

1. DoD UC APL approval of the Lifesize Team, Lifesize Team 200 and Lifesize Team 220 Rel.

4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) TN 1031303 as a VTC system has been granted.

The Field Security Operations (FSO) recommended certification on 25 May 2011 based on the security testing completed by Defense Information Systems Agency (DISA)-led Information Assurance test teams. This solution achieved Interoperability Certification (IOC) from the Joint Staff (JS) on 16 Jun 2011. This approval is effective upon the date of this memorandum and expires 15 Sep 2017 unless a critical issue is identified that invalidates either the Interoperability or the IA posture of this product as determined by the JS or the Defense Information Systems Network (DISN) Designated Approving Authority (DAA). Please note that Services and Agencies are required to recertify and reaccredit their systems every three years. Please refer to the UC APL for official posting of this solution at the following URL: http://www.disa.mil/ucco.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’

DAA:

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the DSAWG and the Program Management Office (PMO).

b. The configuration must be in compliance with the Lifesize Team’s military-unique features deployment guide.

c. Remote management services such as HTTP, SSH, SNMP, and serial port (if available) shall not be used do to security vulnerabilities discovered during APL testing.

d. Disable remote camera monitoring. This function requires a remote management service to be enabled to transmit the camera view. This function was disabled for APL testing.

e. Certain functions, such as software updates, require the HTTP server to be enabled. The proper procedure for this is to remove the System Under Test (SUT) from the Defense Switched Network (DSN), enable the applicable services per the vendor documentation, perform the

DISA Memo, NS231, UC APL Approval Memo, Lifesize Team, Lifesize Team 200 and Lifesize Team 220 Rel. 4.7.9(2) and Lifesize Networker Rel. 3.1.1(4) TN 1031303, 15 Sep 2014.

specific installation instructions will be included in the Lifesize Deployment Guide.

g. Fielding physical access to the Lifesize Video Codec must be protected to ensure IP address information cannot be read by un-cleared personnel.

h. An Intrusion Prevention System (IPS) with automated virus-scanning capability must be deployed in-line between the Lifesize Video System and other IP networks.

i. A network-based firewall must be deployed to filter ICMPv6 echo-requests and echo-replies specifically destined to and from the Lifesize Video System.

3. The IOC letter containing detailed configuration on this product is available at the following URL: http://jitc.fhu.disa.mil/tssi/cert_pdfs/lifesizeteam_jun11.pdf On 15 Sep 2014, the following extension was approved via Desktop Review (DTR) #1 (requested to extend the listing of this solution on the UC APL for an additional 3 years)

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contained the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government civilian or uniformed military personnel.

REFER TO: Infrastructure Directorate (IE) 13 Oct 2015

(APL) approval of the Polycom High Definition Experience (HDX) Family with Software Release (Rel.) 2.7.3.3_J Tracking Number (TN) 1034102 as a Video Teleconferencing (VTC) System

(b) DoD CIO “Unified Capabilities Requirements (UCR) 2013,” Jul 2013

1. DoD UC APL approval of the Polycom HDX Family Rel. 2.7.3.3_J TN 1034102 as a VTC system has been granted. The following components were certified:

Model Certified by similarity Software Version

Polycom HDX 9004, 9006 Polycom HDX 9002

2.7.3.3_J

Polycom HDX 9001

Polycom HDX 8000 HD (Rev A and B)

Polycom HDX 8006 Polycom HDX 8004 Polycom HDX 8002

Polycom HDX 7000 HD (Rev A, B, and C)

Polycom HDX 7002 Polycom HDX 7001

Polycom HDX 6000 HD NA

Polycom HDX 4000 HD Polycom HDX 4002 Polycom HDX 4001

The Field Security Operations (FSO) granted Information Assurance (IA) certification on 28 Jul 2011 based on the security testing completed by the Defense Information Systems Agency (DISA)-led IA test teams. This solution achieved Interoperability (IO) certification from the Joint Interoperability Test Command (JITC) on 26 Jul 2011. This approval is effective upon the date of this memorandum and expires 11 Jun 2017 unless a critical issue is identified that invalidates either the IO or the IA posture of this product as determined by the JITC or the Chief Information Officers (CIO) for Combatant Commands, Services, and Agencies. Please note that Services and Agencies are required to recertify and reaccredit their systems every three years.

Please refer to the UC APL for official posting of this solution at the following URL:

https://aplits.disa.mil/apl.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security

DISA Memo, IE, UC APL Approval Memo, Polycom HDX Family Rel. 2.7.3.3_J TN 1034102, 13 Oct 2015 measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’ Authorizing Official (AO)/Designated Accrediting Authority (DAA):

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the Defense/IA Security Accreditation Working Group (DSAWG) and the Program Management Office (PMO).

b. The configuration must be in compliance with the Polycom HDX Family Rel. 2.7.3.3_J TN 1034102’s military-unique features deployment guide.

c. The system must be incorporated in the site’s Public Key Infrastructure (PKI).

d. A Network Time Protocol (NTP) Server is required for proper system operation as tested.

This is needed to provide the correct time and date for the HDX 700 Family, HDX 6000 Family, HDX 9000 Family and HDX 8000 Family.

e. The system must be integrated into the site’s Active Directory (AD) environment for authentication and authorization requirements.

f. Site must deploy solution on separate Virtual Local Area Networks (VLANs) and behind the site’s firewall.

g. Site must deploy solution in a secure area.

3. The IO certification letter containing detailed configuration on this product is available at the following URL: http://jitc.fhu.disa.mil/tssi/cert_pdfs/polycomhdx270j_tn1034102.pdf On 22 Dec 2011, the following extension was approved via Desktop Review (DTR) #1 (to upgrade from version 2.7.0_J to 2.7.1_J to correct TDRs 27J003 and 27J006):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/polycom_vtc_rel_270_j_dtr1_dec11.pdf On 12 Dec 2013, the following extension was approved via DTR #3 (to include Rel. 2.7.3_J):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/polycom_hdx_r2_7_3_J_dtr3_dec13.pdf On 28 Mar 2014, the following extension was approved via DTR #4 (include Release 2.7.3.1_J, which includes additional API commands based on customer request):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/polycom_hdx_r2_7_0_J_dtr4_mar14.pdf On 11 Jun 2014, the following extension was approved via DTR #5 (requested to extend the APL approval status for an additional three years).

On 07 Jan 2015, the following extension was approved via DTR#6 (requested to update the System Under Test (SUT) from Rel. 2.7.3.1_J to Rel. 2.7.3.2_J):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Polycom_HDX_Rel_2_7_0_J_TN1034102_DTR6_Jan15.pd f On 05 Oct 2015, the following extension was approved via DTR#7 (requested to update the SUT from Rel. 2.7.3.2_J to Rel. 2.7.3.3_J):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Polycom_HDX_Rel_2_7_0_J_TN1034102_CMA_DTR7_O ct15.pdf

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contains the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government civilian or uniformed military personnel.

-2-https://snap.dod.mil/index.cfm http://jitc.fhu.disa.mil/tssi/cert_pdfs/polycomhdx270j_tn1034102.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/polycom_vtc_rel_270_j_dtr1_dec11.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/polycom_hdx_r2_7_3_J_dtr3_dec13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/polycom_hdx_r2_7_0_J_dtr4_mar14.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Polycom_HDX_Rel_2_7_0_J_TN1034102_DTR6_Jan15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Polycom_HDX_Rel_2_7_0_J_TN1034102_DTR6_Jan15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Polycom_HDX_Rel_2_7_0_J_TN1034102_CMA_DTR7_Oct15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Polycom_HDX_Rel_2_7_0_J_TN1034102_CMA_DTR7_Oct15.pdf

DISA Memo, IE, UC APL Approval Memo, Polycom HDX Family Rel. 2.7.3.3_J TN 1034102, 13 Oct 2015

E-Mail: disa.meade.ie.list.unified-capabilities-certification-office@mail.mil

JESSIE L. SHOWERS, JR.

Infrastructure Executive

-3-mailto:disa.meade.ie.list.unified-capabilities-certification-office@mail.mil

REFER TO: Infrastructure Directorate (IE) 17 Aug 2015

(APL) approval of the Cisco TelePresence C-series, EX-series, and MX-series Video Codecs Release (Rel.) TC 7.3, the Integrated Services Digital Network (ISDN) Link Rel. IL1.1.5, and Video Communication Server (VCS) Rel. X7.2.2, Tracking Number (TN) 1127303 as a Video Teleconferencing Unit (VTU)

1. DoD UC APL approval of the Cisco TelePresence C-series, EX-series, and MX-series Video Codecs TC 7.3, ISDN Link IL1.1.5, and VCS X7.2.2 TN 1127303 as a VTU has been granted.

Model Software Version Cisco Telepresence C90, Quickset C20, EX90, EX60.

MX200, MX300 Series Codecs, SX20, MX200G2, MX300G2, MX700, MX800, MX800 Dual, SX10, SX80, VX Tactical, Avizia VX Tactical, and VX Clinical Assistant codecs

TC 7.3

ISDN Link Gateway IL1.1.5

VCS X7.2.2

The Field Security Operations (FSO) granted Information Assurance (IA) certification on 21 Sep 2012 based on the security testing completed by the Defense Information Systems Agency (DISA)-led IA test teams. This solution achieved Interoperability (IO) certification from the Joint Interoperability Test Command (JITC) on 11 Dec 2012. This approval is effective upon the date of this memorandum and expires 21 Jan 2018 unless a critical issue is identified that invalidates either the IO or the IA posture of this product as determined by the JITC or the Chief Information Officers (CIO) for Combatant Commands, Services, and Agencies. Please note that Services and Agencies are required to recertify and reaccredit their systems every three years.

Please refer to the UC APL for official posting of this solution at the following URL:

https://aplits.disa.mil/apl.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security

DISA Memo, IE, UC APL Approval Memo, Cisco TelePresence C-series, EX-series, and MX-series Video Codecs TC 7.3, ISDN Link IL1.1.5, and VCS X7.2.2 TN 1127303, 17 Aug 2015.

measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’ Authorizing Official (AO) / Designated Approving Authority (DAA):

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the Defense/IA Security Accreditation Working Group (DSAWG) and the Program Management Office (PMO).

b. The configuration must be in compliance with the Cisco TelePresence C-series, EX-series, and MX-series Video Codecs TC 7.3, ISDN Link IL1.1.5, and VCS X7.2.2 TN 1127303’s military-unique features deployment guide.

c. The system must be incorporated in the site’s Public Key Infrastructure (PKI).

d. The system must use Active Directory (AD) for authentication.

e. The site must use a SysLog device for auditing purposes.

f. The FIPS mode must be enabled after configuration of the ISDN Link. There will be no direct access to the ISDN Link allowed once configuration is complete and FIPS mode is enabled.

3. The IO certification letter containing detailed configuration on this product is available at the following URL: http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_codecTC5_0_x7_1_dec12.pdf On 13 Feb 2013, the following extension was approved via Desktop Review (DTR) #1 (to extend the expiration date of the IO certification from 7 Nov 2013 to 07 Nov 2015. This request for extension is based on this product receiving Federal Information Processing Standard (FIPS) 140-2 certification by the National Institute of Standards and Technology (NIST)):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_codec_TC5_0_x7_1_dtr1_feb13.pdf On 15 May 2013, the following extension was approved via DTR #2 (to update the System Under Test (SUT) codec software from version TC 5.0.2 to TC 6.1.0) and DTR#4 (to include the SX20, VX Tactical, and VX Clinical Assistant codecs):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_codec_tc5_0_x7_1_dtrs2_4_may13.pdf On 30 Jul 2013, the following extension was approved via DTR #5 (to update the VCS from version X7.1 to X7.2.2): http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_codec_tc5_0_dtr5_jul13.pdf On 20 Sep 2013, the following extension was approved via DTR #3 (to update the ISDN Link from version IL 1.0.0 to IL1.1):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_tc6_1_0_vtc_codec_dtr3_sep13.pdf On 07 Nov 2013, the following extension was approved via DTR #7 (to include the Avizia VX Tactical by similarity to the Cisco VX Tactical):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_tc5_0_vtc_codec_isdn_link_dtr7_nov13.pdf On 27 Dec 2013, the following extension was approved via DTR#8 (to include the MX300G2 by similarity to the SX20):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_r_tc5_0_vtc_codec_dtr_8_dec13.pdf On 23 Jan 2014, the following extension was approved via DTR #6 (to include TC 7.0.1 on the video codecs, which includes IO fixes):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_tc5_0_codec_rtc_6_1_0_dtr6_jan14.pdf https://snap.dod.mil/index.cfm http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_codecTC5_0_x7_1_dec12.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_codec_TC5_0_x7_1_dtr1_feb13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_codec_tc5_0_x7_1_dtrs2_4_may13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_codec_tc5_0_dtr5_jul13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_tc6_1_0_vtc_codec_dtr3_sep13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_tc5_0_vtc_codec_isdn_link_dtr7_nov13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_r_tc5_0_vtc_codec_dtr_8_dec13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_tc5_0_codec_rtc_6_1_0_dtr6_jan14.pdf

DISA Memo, IE, UC APL Approval Memo, Cisco TelePresence C-series, EX-series, and MX-series Video Codecs TC 7.3, ISDN Link IL1.1.5, and VCS X7.2.2 TN 1127303, 17 Aug 2015.

On 23 Oct 2014, the following extension was approved via DTR #10 (requested to updated the software version for the SUT video codecs from TC 7.0.1 to TC 7.2):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_VTC_ISDN_TN1127303_DTR10_Oct14.pdf On 18 Dec 2014, the following extension was approved via DTR #9 (requested to include the MX 700, MX 800, SX10, SX80 and MX200G2 codecs):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Rel_TC5_0_VTC_TN1127303_DTR9_Dec14.pdf On 21 Jan 2014, the following extension was approved via DTR #11 (requested to extend this solutions listing on the UC APL by an additional 3 years):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_VTC_TC5_0_TN1127303_DTR_11_Mar15.pdf On 01 Jul 2015, the following extension was approved via DTR #12 (the C40 & C60 components have reached Cisco’s End-of-Sale as of 08-Jun-2015 and are no longer approved for new purchase) On 13 Aug 2015, the following extension was approved via DTR #13 (requested to update the SUT TC software from TC 7.2 to TC 7.3, and update the ISDN Link software from IL 1.1.2 to IL 1.1.5):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_TC5_0_VTC_TN1127303_DTRs_13_14_Aug15.pdf On 13 Aug 2015, the following extension was approved via DTR #14 (requested to include the Codec MX800 Dual via similarity to the SX80):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_TC5_0_VTC_TN1127303_DTRs_13_14_Aug15.pdf

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contains the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government civilian or uniformed military personnel.

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_VTC_ISDN_TN1127303_DTR10_Oct14.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Rel_TC5_0_VTC_TN1127303_DTR9_Dec14.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_VTC_TC5_0_TN1127303_DTR_11_Mar15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_TC5_0_VTC_TN1127303_DTRs_13_14_Aug15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_TC5_0_VTC_TN1127303_DTRs_13_14_Aug15.pdf

REFER TO: Infrastructure Directorate (IE) 09 Feb 2016

(APL) approval of the Cisco TelePresence Media Service Engine (MSE) 8000 with Specified Circuit Card Assemblies, the Cisco Video Communication Server (VCS), and TelePresence Management Suite (TMS), Tracking Number (TN) 1127304 as a Video Teleconferencing System (VTC)

1. DoD UC APL approval of the Cisco TelePresence MSE 8000 with Specified Circuit Card Assemblies, the Cisco VCS, and TMS TN 1127304 as a VTC system has been granted. The following components were certified:

MSE Cisco TelePresence Infrastructure

Hardware Software

TelePresence Management Suite (TMS)

V15.0 Windows 2008 R2

ESXi 4.1.0 Kernel 348481 Supervisor MSE 8050 2.3(1.31)

MSE 8510 MCU 4.3(1.68)

MSE 8321 ISDN Gateway 2.1(1.56)P

VCS X8.2

MCU5320 4.5

MSE 8330 Serial Gateway Blade 1.0(1.34)

Certified by similarity Cisco 3340 Serial Gateway 1.0(1.34)

MCU5310 4.5

ISDN GW 3241 2.1(1.56)P

The Field Security Operations (FSO) recommended certification on 21 Sep 2012 based on the security testing completed by the Defense Information Systems Agency (DISA)-led information assurance (IA) test teams. This solution achieved interoperability (IO) certification from the Joint Interoperability Test Command (JITC) on 21 Dec 2012. This approval is effective upon the date of this memorandum and expires 21 Jan 2018 unless a critical issue is identified that invalidates either the IO or the IA posture of this product as determined by the JITC or the Chief Information Officers for Combatant Commands, Services, and Agencies. Please note that

DISA Memo, IE, UC APL Approval Memo, Cisco TelePresence MSE 8000 with Specified Circuit Card Assemblies, the Cisco VCS, and TMS TN 1127304, 09 Feb 2016

Services and Agencies are required to recertify and reaccredit their systems every three years.

Please refer to the UC APL for official posting of this solution at the following URL:

https://aplits.disa.mil/apl.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’ Authorizing Official (AO)/Designated Accrediting Authority (DAA):

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the Defense/IA Security Accreditation Working Group (DSAWG) and the Program Management Office (PMO).

b. The configuration must be in compliance with the Cisco TelePresence Infrastructure Multiple Release TN 1127304’s military-unique features deployment guide.

c. The system must be incorporated in the site’s Public Key Infrastructure (PKI).

d. The system must be incorporated into the site’s Active Directory (AD) environment.

e. The site must use a SysLog device for auditing purposes.

f. The system must be installed in a physically secure location that offers firewall protection and uses PKI-enabled workstations to access the management web interface via PKI-enabled, two-factor authentication and Hypertext Transport Protocol (HTTP) over Secure Socket Layer (SSL) encryption.

g. The site must use role-based security for user access and management of the vendor’s device.

h. The site must disable all local user accounts on the device after initial setup/configuration with the exception of one emergency administrative account.

i. The site must ensure that the emergency administrative account’s userid and password are locked up in separate safes, both of which are not accessible by any one individual, and procedures implemented to log all access and usage.

j. The site must ensure that the emergency administrative account meets all DoD userid and password requirements.

k. The site must ensure that all unused open ports will be closed.

3. The IOC letter containing detailed configuration on this product is available at the following URL: http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_telepresence_mse_r2_2_1_17_dec12.pdf On 15 May 2013, the following extension was approved via Desktop Review (DTR) #1 (to include the 3241) and DTR #2 (to update the VCS software from X7.1 to X7.2.2):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_telepres_r2_2_1_17_vtc_dtrs1_2_may13.pdf On 07 Aug 2013, the following extension was approved via DTR #4 (to update the MSE 8050 Supervisor from Rel. 2.2(1.17) to 2.3(1.31)):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_telepres_r2_2_1_17_vtc_dtr4_aug13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_telepresence_mse_r2_2_1_17_dec12.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_telepres_r2_2_1_17_vtc_dtrs1_2_may13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/cisco_telepres_r2_2_1_17_vtc_dtr4_aug13.pdf

DISA Memo, IE, UC APL Approval Memo, Cisco TelePresence MSE 8000 with Specified Circuit Card Assemblies, the Cisco VCS, and TMS TN 1127304, 09 Feb 2016

On 27 May 2014, the following extension was approved via DTR#3 (requested to include the MCU5310 and MCU5320 with Software Release 4.4(3.49)):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_System_TN1127304_ DTR3_27MAY14.pdf On 23 Oct 2014, the following extension was approved via DTR #6 (requested to update the MCU5310 and MCU5320 from Rel. 4.4(3.49) to Rel. 4.5 and update the VCS from Rel. X.7.2.2 to Rel. 8.2):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_TN1127304_DTR6_ Oct14.pdf On 21 Jan 2015, the following extension was approved via DTR #7 (requested to extend this solutions listing on the UC APL by an additional 3 years).

On 06 Jul 2015, the following extension was approved via DTR #8 (requested to include the MSE 8330 Serial Gateway and the Cisco 3340 Serial Gateway):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rl_2_2_1_17_VTC_TN1127304_DTR8_Ju l15.pdf On 09 Feb 2016, the following extension was approved via DTR #9 (requested to update the TMS from Rel. 14.0.0 to Rel. 15.0 running on Windows 7 (Service Pack 1), and to add the TMS Extension for Microsoft Exchange (TMS XE) Ver 5.0, running on Windows Server 2012):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_TN1127304_DTR9_J an16.pdf

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contains the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_System_TN1127304_DTR3_27MAY14.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_System_TN1127304_DTR3_27MAY14.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_TN1127304_DTR6_Oct14.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_TN1127304_DTR6_Oct14.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rl_2_2_1_17_VTC_TN1127304_DTR8_Jul15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rl_2_2_1_17_VTC_TN1127304_DTR8_Jul15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_TN1127304_DTR9_Jan16.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/Cisco_Telepres_Rel_2_2_1_17_VTC_TN1127304_DTR9_Jan16.pdf

REFER TO: Infrastructure Directorate (IE) 20 Jan 2016

(APL) approval of the PESA Cheetah Release (Rel.) 5.2 Tracking Number (TN) 1206801 as a closed Video Distribution System (VDS)

1. DoD UC APL approval of the PESA Cheetah Rel. 5.2 TN 1206801 as a closed VDS has been granted. The Field Security Operations (FSO) granted Information Assurance (IA) certification on 20 Dec 2012 based on the security testing completed by the Defense Information Systems Agency (DISA)-led IA test teams. This solution achieved Interoperability (IO) certification from the Joint Interoperability Test Command (JITC) on 07 Jan 2013. This approval is effective upon the date of this memorandum and expires 21 Oct 2018 unless a critical issue is identified that invalidates either the IO or the IA posture of this product as determined by the JITC or the Chief Information Officers (CIO) for Combatant Commands, Services, and Agencies. Please note that Services and Agencies are required to recertify and reaccredit their systems every three years. Please refer to the UC APL for official posting of this solution at the following URL: https://aplits.disa.mil/apl.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’ Authorizing Official (AO)/Designated Accrediting Authority (DAA):

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the Defense/IA Security Accreditation Working Group (DSAWG) and the Program Management Office (PMO).

b. The configuration must be in compliance with the PESA Cheetah Rel. 5.2 TN 1206801’s military-unique features deployment guide.

c. The PESA solution must be deployed closed network with no external connectivity outside of the PESA system. If the PESA system is not deployed in this manner, the following findings will be included in the site’s architecture:

• AC31.030 for management workstations

• AC34.070 for management workstations

• APP3280 for Cattrax 3.2.1 application

d. The management work station must be co-located with the PESA solution. Therefore, the PESA solution can only be managed locally. There will be no remote access to the PESA solution.

DISA Memo, IE, UC APL Approval Memo, PESA Cheetah Rel. 5.2 TN 1206801, 20 Jan 2016

e. There will be no Internet Protocol (IP) connectivity to the PESA solution or back to the Site’s network from the PESA solution.

f. The PESA solution cannot cross the converged Local Area Network (LAN).

g. The following protocols must be disabled on the VIDBLOX component within the PESA solution:

• Simple Network Management Protocol (SNMP)

• Hypertext Transfer Protocol (HTTP)

• Trivial File Transfer Protocol (TFTP)

• File Transfer Protocol (FTP)

3. The IO certification letter containing detailed configuration on this product is available at the following URL: http://jitc.fhu.disa.mil/tssi/cert_pdfs/pesa_cheetah_vds_r_5_1_jan13.pdf On 29 Nov 2013, the following extension was approved via Desktop Review (DTR) #1 (to include the following changes: (1) Add the 81906533350 input buffer card, which was omitted from the original list of cards to be certified by similarity. This card uses the same firmware and revision as the previously certified input buffer cards. (2) Update the VidBlox firmware as noted in Table 1 of the IO certification letter. This firmware revision includes support for additional video standards and to correct minor bugs. (3) Update the Frame Controller (81906523970), from Revision 5.1 to 5.5 with DTR 1. This firmware supports new features over existing communication channels with no protocol changes. (4) Update the Cattrax software from Release 3.2.1 to 3.3.0. This software update adds features, fixes minor bugs, and allows the SUT to recognize new products):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/pesa_cheetah_vds_r5_1_dtr1_nov13.pdf On 24 Jun 2014, the following extension was approved via DTR #2 (was requested to update the System Under Test from Rel. 5.1 to 5.2, and to include the following changes: (1) Update the Cattrax J from Version 3.3.0 to Version 3.3.0.1, which added a missing .ini file to the installation Compact Disc. (2) Update the 144NE FPGA Source Code from Revision 2 to Revision 3. (3) Update the CH-MATRIX144-3G from Revision 1 to Revision 8. (4) Update Cheetah Output Combiner Coax 3G with Reclockers Gennum from Revision 17 to Revision 18. (5) Corrects the CHNE-INPUT-3G-BNC card from Revision 1 to Revision A. The card has always been Revision A. (6) Update SD/HD/3G Fiber LC was updated from Revision 17 to Revision 20. (7) Corrects the PERC2000 from Rel. 3.0 to Revision F. This card has always been Revision F. (8) Corrects the Quadbox Transport Media Conversion Modules From Rel. 2.1.04 to Rel. 2.1.05.

These modules have always been Rel. 2.1.05):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/PESA_Cheetah_TN1206801DTR2_30Jun14.pdf On 21 Oct 2015, the following extension was approved via DTR #4 (requested to extend this solution’s listing on the UC APL by an additional 3 years):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/PESA_Cheetah_VDS_Rel_5_1_TN1206801_DTR4_Dec15.

pdf On 30 Nov 2015, the following extension was approved via DTR #3 (requested to upgrade firmware of minor system components to improve reliability and performance):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/PESA_Cheetah_VDS_Rel_5_1_TN1206801_DTR3_Nov15.

pdf

-2-http://jitc.fhu.disa.mil/tssi/cert_pdfs/pesa_cheetah_vds_r_5_1_jan13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/pesa_cheetah_vds_r5_1_dtr1_nov13.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/PESA_Cheetah_TN1206801DTR2_30Jun14.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/PESA_Cheetah_VDS_Rel_5_1_TN1206801_DTR4_Dec15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/PESA_Cheetah_VDS_Rel_5_1_TN1206801_DTR4_Dec15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/PESA_Cheetah_VDS_Rel_5_1_TN1206801_DTR3_Nov15.pdf http://jitc.fhu.disa.mil/tssi/cert_pdfs/PESA_Cheetah_VDS_Rel_5_1_TN1206801_DTR3_Nov15.pdf

DISA Memo, IE, UC APL Approval Memo, PESA Cheetah Rel. 5.2 TN 1206801, 20 Jan 2016

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contains the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government

REFER TO: Network Services (NSP) 14 Jan 2015

(APL) approval of the AMX Enova DVX-3155HD with Software Release (Rel.)

4.7.313 Tracking Number (TN) 1307901 as a closed Video Distribution System

(VDS)

1. DoD UC APL approval of the AMX Enova DVX-3155HD Rel. 4.7.313 TN 1307901 as a closed VDS has been granted. The following components were certified:

System Under Test

Tested Component

Components to be Certified by Similarity

Software/Firmware Version

AMX Enova

DVX-3155

HD-SP

Release 4.7.313

DXLink Multi- Format WP Tx

FG1010-325-

BL

DXLink Multi-Format WP Tx

FG1010-320-WH

Freescale MQX 3.62 DXLink Multi-Format WP Tx

FG1010-320-BL

DXLink Multi-Format WP Tx

FG1010-325-WH

AMX DVX-

3155HD-SP

FG1905-16

AMX DVX-3156HD-SP

FG1905-22

VxWorks 6.8 Skelmir 3.0.14

Knopflerfish 2.4.0 OSGi R 4.1.13

HTTP-Server 3.1.2 NetLinx 3.3.325

AMX DVX-3156HD-T

FG1905-24

AMX DVX-3155HD-T

FG1905-18

AMX DVX-3150HD-SP

FG1905-15

AMX DVX-3150HD-T

FG1905-17

AMX DVX-2155HD-SP

FG1905-12

AMX DVX-2155HD-T

FG1905-14

AMX DVX-2150HD-SP

FG1905-11

AMX DVX-2150HD-T

FG1905-13

DISA Memo, NSP, UC APL Approval Memo, AMX Enova DVX-3155HD Rel. 4.7.313 TN 1307901, 14 Jan 2015.

System Under Test

Tested Component

Components to be Certified by Similarity

Software/Firmware Version

AMX Enova

DVX-3155

HD-SP

Release 4.7.313

(continued)

AMX DVX-

3155HD-SP

FG1905-16

(continued)

AMX DVX-2100HD-SP

FG1905-04

VxWorks 6.8 Skelmir 3.0.14

Knopflerfish 2.4.0 OSGi R 4.1.13

HTTP-Server 3.1.2 NetLinx 3.3.325

AMX DVX-2100HD-T

FG1905-05

MXT-1900L-

PAN-NC

FG5968-21

MXT-2000XL-PAN-NC

FG5968-32

Linux 2.6.35.3 Dropbear 0.52

AMX VTG 2.105.15

MXD-2000XL-PAN-P-NC

FG5968-33

MXD-2000XL-PAN-L-NC

FG5968-34

MXD-1900L-PAN-P-NC

FG5968-22

MXD-1900L-PAN-L-NC

FG5968-23

MXT-1000-NC

FG5968-24

MXD-1000-P-NC

FG5968-25

MXD-1000-L-NC

FG5968-26

MXT-700-NC

FG5968-27

MXD-700-P-NC

FG5968-28

MXD-700-L-NC

FG5968-29

The Field Security Operations (FSO) granted Information Assurance (IA) certification on 13 Feb 2014 based on the security testing completed by the Defense Information Systems Agency (DISA)-led IA test teams. This solution achieved Interoperability (IO) certification from the Joint Interoperability Test Command (JITC) on 13 Feb 2014. This approval is effective upon the date of this memorandum and expires 24 Feb 2017 unless a critical issue is identified that invalidates either the IO or the IA posture of this product as determined by the JITC or the Chief Information Officers (CIO) for Combatant Commands, Services, and Agencies. Please note that Services and Agencies are required to recertify and reaccredit their systems every three years.

Please refer to the UC APL for official posting of this solution at the following URL:

https://aplits.disa.mil.

2. This product/solution must be implemented only in the configuration that was tested and approved. When the system is deployed into an operational environment, the following security measures (at a minimum) must be implemented to ensure an acceptable level of risk for the sites’ Designated Accrediting Authority (DAA):

a. The site must register the system in the Systems Networks Approval Process (SNAP) Database https://snap.dod.mil/index.cfm as directed by the Defense/IA Security Accreditation Working Group (DSAWG) and the Program Management Office (PMO).

b. The configuration must be in compliance with the AMX Enova DVX-3155HD Rel.

4.7.313 TN 1307901’s military-unique features deployment guide.

c. The AMX solution must be deployed on a closed network with no external connections.

If the solution is not deployed as stated, the following findings will be included in the site’s architecture:

• AC31.030 for Modero X MXT-1900L-PAN-NC and Enova DVX-3155HD-SP

• AC34.070 for Modero X MXT-1900L-PAN-NC and Enova DVX-3155HD-SP

• EN005 for Modero X MXT-1900L-PAN-NC and Enova DVX-3155HD-SP

• NET0445 for Modero X MXT-1900L-PAN-NC and Enova DVX-3155HD-SP

d. The system must be configured with Telnet disabled.

e. The system must be configured with File Transfer Protocol (FTP) disabled.

f. The workstation must be co-located with the AMX solution. Therefore, it can only be managed locally. There will be no remote access to the solution.

g. There will be no Internet Protocol (IP) connections to the AMX solution or back to the site’s network from the solution.

h. The AMX solution cannot cross the converged Local Area Network (LAN).

3. The IO certification letter containing detailed configuration on this product is available at the following URL:

http://jitc.fhu.disa.mil/tssi/cert_pdfs/amx_enova_dvx3150hd_r4_7_301_feb14.pdf On 10 Dec 2014, the following extension was approved via Desktop Review (DTR) #1:

(requested to update the System Under Test (SUT) From Rel. 4.7.301 to Rel. 4.7.313):

http://jitc.fhu.disa.mil/tssi/cert_pdfs/AMX_Enova_DVX3150HD_Release4_7_350_VDS_TN13 07901_DTR1_Dec14.pdf

4. Due to the sensitivity of the information, the Information Assurance Assessment Package (IAAP) that contains the approved configuration and deployment guide for this solution must be requested directly from the Unified Capabilities Certification Office (UCCO) by government

-4-

REFER TO: Infrastructure Directorate (IE) 23 Mar 2015

(APL) approval of the Thinklogical, LLC. Velocity Closed Video Matrix Switching Solution Release (Rel.) 4 Tracking Number (TN) 1324203 as a Video Distribution System (VDS)

1. DoD UC APL approval of the Thinklogical, LLC. Velocity Closed Video Matrix Switching Solution Rel. 4 TN 1324203 as a VDS has been granted. The Field Security Operations (FSO) granted Information Assurance (IA) certification on 18 Feb 2015 based on the security testing completed by the Navy Space and Naval War System Command (SPAWAR)-led IA test teams.

This solution achieved…