The TOE (Internet Protocol Crosspoint (IPX) switch) is a network-based audio video distribution system and is classified as a network device (a generic infrastructure device that can be connected to a network). It is a 10 Gigabit (Gb) Internet Protocol (IP) switch optimized for video-over-IP traffic (compressed or uncompressed). For the MMA10G and 3080 models, each IPX card occupies two (2) slots (16- and 32-port IPX cards) or four (4) slots (64-port IPX cards) in an Evertz Modular Crosspoint (EMX) frame. The 9080 models include the IPX cards and frame in a 1RU form factor. All IPX-compatible cards may be inserted into any IPX frame configuration provided there are sufficient contiguous free slots available.
\r\nSince video by nature has a unidirectional flow, and multiple copies of a single incoming video stream are often sent to multiple output destinations, the IPX exclusively uses multicast IP addressing. Equipment to prepare video for IP transport, or to convert it into other video formats, is outside the scope of this TOE. Such equipment includes, but is not limited to, cameras, KVMs, codecs, video servers and video displays. Equipment to perform functions such as embedding audio and/or other information within the video stream is also outside the scope of this TOE.
\r\n\r\n
The TOE provides secure remote management using an HTTPS/TLS web interface. Administrators only may access IPX via a dedicated management workstation operating over an Out-of-Band Management (OOBM) network. Sites may close this OOBM network or may operate IPX within an existing OOBM, as long as the topology is compliant with the security parameters listed below. Users and administrators may also access IPX software via direct connection using a terminal session.
\r\n\r\n
The TOE generates audit logs and transmits the audit logs to a remote syslog server over a TLS channel. The TOE verifies the authenticity of software updates by verifying the digital signature prior to installing any update.
\r\n\r\n
","evaluation_configuration":"
The evaluated configuration is the MMA10G-IPX-16-CC running MMA10G-IPX-16-CC Version 3.5. All other TOE models are included by equivalency. The TOE evaluation Environment Components are shown in Table 3 below:
\r\n\r\n
Table 3- IT Testing Environment Components
\r\n| \r\n Component \r\n | \r\n\r\n Required \r\n | \r\n\r\n Purpose/Description \r\n | \r\n
| \r\n Syslog Server \r\n | \r\n\r\n Yes \r\n\r\n | \r\n\r\n
| \r\n
| \r\n Management Workstation with web browser \r\n\r\n | \r\n\r\n Yes \r\n\r\n | \r\n\r\n
| \r\n
| \r\n Local Management Workstation \r\n | \r\n\r\n Yes \r\n | \r\n\r\n Computer with terminal emulation software to access the console interface (CLI) \r\n | \r\n
| \r\n CRL Server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n
| \r\n
| \r\n MAGNUM Client \r\n | \r\n\r\n Yes \r\n | \r\n\r\n
| \r\n
| \r\n Media Gateway \r\n | \r\n\r\n No \r\n | \r\n\r\n
| \r\n
| \r\n Video Source devices \r\n | \r\n\r\n No \r\n | \r\n\r\n
| \r\n
| \r\n Video Destination devices \r\n | \r\n\r\n No \r\n | \r\n\r\n
| \r\n
The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the MMA10G-IPX Series v3.5 was evaluated is described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 5. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 rev 5. The product, when delivered and configured as identified in the Common Criteria Administrator Guidance, satisfies all of the security functional requirements stated in the MMA10G-IPX Series v3.5 Security Target. The project underwent CCEVS Validator review. The evaluation was completed in June 2025. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
\r\nThe physical boundaries of the TOE are outlined in Table 1. The media and video components of the IT environment are NOT part of the TOE physical boundary. The TOE is shipped to the customer via commercial courier.
\r\n\r\n
Table 1 – TOE Physical Boundary Components
\r\n| \r\n Model \r\n | \r\n\r\n Software \r\n | \r\n\r\n AV/Broadcast \r\n | \r\n\r\n Supported Ports \r\n | \r\n\r\n Form Factor \r\n | \r\n\r\n Chassis Supported \r\n | \r\n\r\n Frame Controller \r\n | \r\n\r\n Processor \r\n | \r\n
| \r\n MMA10G-IPX-16-CC \r\n | \r\n\r\n MMA10G-IPX-16-CC v3.5 \r\n | \r\n\r\n AV \r\n | \r\n\r\n 16 SFP ports \r\n\r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n MMA10G-IPX-32-CC \r\n | \r\n\r\n MMA10G-IPX-32-CC v3.5 \r\n | \r\n\r\n AV \r\n | \r\n\r\n 32 SFP ports \r\n\r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n MMA10G-IPX-64-CC \r\n | \r\n\r\n MMA10G-IPX-64-CC v3.5 \r\n | \r\n\r\n AV \r\n | \r\n\r\n 64 SFP ports \r\n\r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-16-G3-CC \r\n | \r\n\r\n MMA10G-IPX-16-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 16 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-32-G3-CC \r\n | \r\n\r\n MMA10G-IPX-32-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 32 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-64-G6-CC \r\n | \r\n\r\n MMA10G-IPX-64-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 64 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-16-10G-CC \r\n | \r\n\r\n MMA10G-IPX-16-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 16 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-32-10G-CC \r\n | \r\n\r\n MMA10G-IPX-32-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 32 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-64-10G-CC \r\n | \r\n\r\n MMA10G-IPX-64-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 64 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-16-10G-HW- CC \r\n | \r\n\r\n MMA10G-IPX-16-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 16 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-32-10G-HW- CC \r\n | \r\n\r\n MMA10G-IPX-32-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 32 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-64-10G-HW- CC \r\n | \r\n\r\n MMA10G-IPX-64-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 64 SFP ports \r\n(GbE or 10GbE) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-16GE-CC \r\n | \r\n\r\n MMA10G-IPX-16-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 16 GbE ports \r\n(GbE only) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-32GE-CC \r\n | \r\n\r\n MMA10G-IPX-32-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 32 GbE ports \r\n(GbE only) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-64GE-CC \r\n | \r\n\r\n MMA10G-IPX-64-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 64 GbE ports \r\n(GbE only) \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-16GE-RJ45-CC \r\n | \r\n\r\n MMA10G-IPX-16-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 16 RJ45 GbE ports \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-32GE-RJ45-CC \r\n | \r\n\r\n MMA10G-IPX-32-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 32 RJ45 GbE ports \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 3080IPX-64GE-RJ45-CC \r\n | \r\n\r\n MMA10G-IPX-64-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 64 RJ45 GbE ports \r\n | \r\n\r\n modular \r\n | \r\n\r\n EMX1-FR \r\nEMX3-FR \r\nEMX6-FR \r\n | \r\n\r\n EMX-FC \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 9080IPX-16-12RJ45-4SFP10GE-CC \r\n | \r\n\r\n MMA10G-IPX-16-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 12 RJ45 GbE ports \r\n4 SFP ports (GbE or 10GbE) \r\n | \r\n\r\n 1RU \r\n | \r\n\r\n N/A \r\n | \r\n\r\n None \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 9080IPX-16GE-12RJ45-4SFP-CC \r\n | \r\n\r\n MMA10G-IPX-16-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 12 RJ45 GbE ports \r\n4 SFP ports (GbE or 10GbE) \r\n | \r\n\r\n 1RU \r\n | \r\n\r\n N/A \r\n | \r\n\r\n None \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 9080IPX-32-28RJ45-4SFP10GE-CC \r\n | \r\n\r\n MMA10G-IPX-32-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 28 RJ45 GbEports \r\n4 SFP ports (10GbE) \r\n | \r\n\r\n 1RU \r\n | \r\n\r\n N/A \r\n | \r\n\r\n None \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
| \r\n 9080IPX-32-28RJ45-4SFP-CC \r\n | \r\n\r\n MMA10G-IPX-32-CC v3.5 \r\n | \r\n\r\n Broadcast \r\n | \r\n\r\n 28 RJ45 GbE ports \r\n4 SFP ports (GbE or 10GbE) \r\n | \r\n\r\n 1RU \r\n | \r\n\r\n N/A \r\n | \r\n\r\n None \r\n | \r\n\r\n PowerQUICC® II Pro MPC8377E \r\n | \r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
","environmental_strengths":"
The TOE provides the security functions required by the Collaborative Protection Profile for Network Devices, hereafter referred to as NDcPP v3.0e or NDcPP.
\r\nThe TOE’s Audit security function supports audit record generation and review. The TOE provides date and time information that is used in audit timestamps. Very broadly, the Audit events generated by the TOE include:
\r\n\r\n
The TOE stores generated audit data on itself and sends audit events to a syslog server, using a TLS protected collection method. Logs are classified into various predefined categories. The logging categories help describe the content of the messages that they contain. Access to the logs is restricted to only Security Administrators, who has no access to edit them, only to copy or delete (clear) them. Audit records are protected from unauthorized modifications and deletions.
\r\nThe TSF provides the capability to view audit data by using the Syslog tab in the web browser. The log records the time, host name, facility, application, and “message” (the log details). The previous audit records are overwritten when the allocated space for these records reaches the threshold on a FIFO bsis.
\r\nThe TOE includes an OpenSSL library (Version 3.0.14 with Linux 4.19.319) that implements CAVP validated cryptographic algorithms for random bit generation, encryption/decryption, authentication, and integrity protection/verification. The cryptographic implementation for IPX relies on the IPX Cryptographic Module version 3.5. These algorithms are used to provide security for the TLS/HTTPs connections for secure management and secure connections to a syslog and authentication servers. TLS and HTTPs are also used to verify firmware updates.
\r\nTable 2 – TOE Cryptographic Protocols
\r\n| \r\n Cryptographic Protocol \r\n | \r\n\r\n Use within the TOE \r\n | \r\n
| \r\n HTTPS/TLS (client) \r\n | \r\n\r\n Secure connection to syslog | \r\n
| \r\n HTTPS/TLS (server) \r\n | \r\n\r\n Peer connections to MAGNUM and remote management | \r\n
| \r\n AES \r\n | \r\n\r\n Provides encryption/decryption in support of the TLS protocol. | \r\n
| \r\n DRBG \r\n | \r\n\r\n Deterministic random bit generation use to generate keys. | \r\n
| \r\n Secure hash \r\n | \r\n\r\n Used as part of digital signatures and firmware integrity checks. | \r\n
| \r\n HMAC \r\n | \r\n\r\n Provides keyed hashing services in support of TLS. | \r\n
| \r\n EC-DH \r\n | \r\n\r\n Provides key generation and key establishment for TLS. | \r\n
| \r\n RSA \r\n | \r\n\r\n Provide key establishment, key generation and signature generation and verification | \r\n
\r\n
All Administrators wanting to use TOE services are identified and authenticated prior to being allowed access to any of the services other than the display of the warning banner. (“Regular” IPX users do not access IPX directly; they control IP video switching through the IPX using a switch control system, such as Evertz’ Magnum. The switching of those IP video transport stream is outside the scope of the TOE.)
\r\nOnce an Administrator attempts to access the management functionality of the TOE, the TOE prompts the Administrator for a username and password for password-based authentication. The identification and authentication credentials are confirmed against a local user database. Only after the Administrator presents the correct identification and authentication credentials will access to the TOE functionality be granted. The TOE uses X.509v3 certificates as defined by RFC 5280 to support authentication for TLS/HTTPS connections.
\r\nThe TOE provides the capability to set password minimum length rules. This is to ensure the use of strong passwords in attempts to protect against brute force attacks. The TOE also accepts passwords composed of a variety of characters to support complex password composition. During authentication, no indication is given of the characters composing the password.
\r\nRemote administrators are locked out after a configurable number of unsuccessful authentication attempts.
\r\nThe IPX requires a password-protected serial connection to perform initial configuration of the system IP address(es). Once each address is established, administrators use IP connectivity for all further administrative actions, including configuration, operations, and monitoring.
\r\nThe TOE provides secure administrative services for management of general TOE configuration and the security functionality provided by the TOE. All TOE administration occurs either through a secure session or a local console connection. The TOE provides the ability to perform the following actions:
\r\n\r\n
All of these management functions are restricted to an Administrator, which covers all administrator roles. Administrators are individuals who manage specific type of administrative tasks. In IPX, only the admin role exists, since there is no provision for “regular” users to access IPX directly (as described above), and the portion of IPX they access and control are outside the scope of the TOE.
\r\nPrimary management is done using the Webeasy web-based interface using HTTPS. This provides a network administration console from which one can manage various identity services. These services include authentication, authorization, and reporting. All of these services can be managed from the web browser, which uses a menu-driven navigation system.
\r\nThere is also a very simple serial-based connection (RS-232) that provides a simple menu interface. This is used to configure the IP interface (IP address, etc.). It is password-protected, and is typically only used once, for initial set-up.
\r\nThe TOE will terminate inactive sessions after an Administrator-configurable time period. Once a session has been terminated the TOE requires the user to re-authenticate to establish a new session. The TOE provides protection of TSF data (authentication data and cryptographic keys). In addition, the TOE internally maintains the date and time. This date and time are used as the time stamp that is applied to TOE generated audit records. The TOE also ensures firmware updates are from a reliable source. Finally, the TOE performs testing to verify correct operation.
\r\nIn order for updates to be installed on the TOE, an administrator initiates the process from the web interface. IPX automatically uses the digital signature mechanism to confirm the integrity of the product before installing the update.
\r\nAside from the automatic Administrators session termination due to inactivity describes above, the TOE also allows Administrators to terminate their own interactive session. Once a session has been terminated the TOE requires the user to re-authenticate to establish a new session.
\r\nThe TOE will display an Administrator-specified banner on the web browser management interface prior to allowing any administrative access to the TOE.
\r\nThe TOE allows the establishment of a trusted path between a video control system (such as Evertz’ Magnum) and the IPX. The TOE also establishes a secure connection for sending audit data to a syslog server using TLS and other external authentication stores using TLS-protected communications.
\r\nThe TOE uses HTTPS/TLS to provide a trusted path between itself and remote administrative users. The TOE does not implement any additional methods of remote administration. The remote administrative users are responsible for initiating the trusted path when they wish to communicate with the TOE.
","features":[{"id":3240,"feature_name":"Asymmetric Key Generation"},{"id":3334,"feature_name":"Auditing"},{"id":3243,"feature_name":"Cryptograhic Hashing"},{"id":3241,"feature_name":"Cryptographic Key Establishment"},{"id":3242,"feature_name":"Cryptographic Signature Verification"},{"id":3239,"feature_name":"DRBG"},{"id":3333,"feature_name":"Flaw Remediation"},{"id":3244,"feature_name":"Keyed-hash message authentication"}]}