The MMA10G-EXE Series II switches are Internet Protocol (IP) switches optimized for video-over-IP traffic (compressed or uncompressed). The TOE is classified as a network device (a generic infrastructure device that can be connected to a network). Models of the EXE included in the evaluation provide identical functionality. The only differences between them are the supported speed, the physical size, and the number of physical interfaces supported, and the processor. These differences are detailed at the end of this section.
\r\nThe EXE builds on the capabilities of the existing Evertz line of video routing switches. Video routers receive video signals in various formats, such as Serial Digital Interface (SDI), Serial Data Transport Interface (SDTI), or Asynchronous Serial Interface (ASI), and switch dedicated physical input ports to dedicated physical output ports based on external commands. The EXE provides the same capability within the context of packet-based networks using shared network infrastructure.
\r\nThe TOE provides a packet-based switching fabric from a video perspective, rather than relying on traditional packet-based network architecture.
\r\nA typical EXE installation will also include a standard video routing switch software platform (such as Evertz Magnum) to route data between program streams in a manner sufficient to meet broadcast video standards for signal availability and integrity. Equipment to prepare video for IP transport, or to convert it into other video formats, and non-network-based video switching/processing, 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\nThe TOE provides secure remote management using an HTTPS/TLS web interface. Administrators only may access EXE via a dedicated management workstation operating over an Out-of-Band Management (OOBM) network. Sites may close this OOBM network or may operate EXE within an existing OOBM as long as the topology is compliant with the security parameters listed below. Users and administrators may also access EXE software via direct connection using a terminal session.
\r\nThe TOE generates audit logs and transmits the audit logs to a remote syslog server over an authenticated TLS channel. The TOE verifies the authenticity of software updates by verifying the digital signature prior to installing any update.
\r\n\r\n
The TOE hardware devices are the Evertz:
\r\nTable 1 – TOE hardware models
\r\n| \r\n\r\n | \r\n\r\n AV/ \r\nBroadcast \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 NATX-8-100G-CC \r\n | \r\n\r\n broadcast \r\n | \r\n\r\n 4 x DD QSFP (QSFP200G) \r\n | \r\n\r\n 1 \r\n | \r\n\r\n DragonFire frame \r\n | \r\n\r\n N/A \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n NATX-16-100G-CC \r\n | \r\n\r\n broadcast \r\n | \r\n\r\n 8 x DD QSFP (QSFP200G) \r\n | \r\n\r\n 1 \r\n | \r\n\r\n DragonFire frame \r\n | \r\n\r\n N/A \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n NATX-32-100G-1-CC \r\n | \r\n\r\n broadcast \r\n | \r\n\r\n 16 x DD QSFP (QSFP200G) \r\n | \r\n\r\n 1 \r\n | \r\n\r\n DragonFire frame \r\n | \r\n\r\n N/A \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n NATX-64-100G-2-CC \r\n | \r\n\r\n broadcast \r\n | \r\n\r\n 32 x DD QSFP (QSFP200G) \r\n | \r\n\r\n 1 \r\n | \r\n\r\n DragonFire frame \r\n | \r\n\r\n N/A \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n MMA10G-NATX-8-CC \r\n | \r\n\r\n AV \r\n | \r\n\r\n 4 x DD QSFP (QSFP200G) \r\n | \r\n\r\n 1 \r\n | \r\n\r\n DragonFire frame \r\n | \r\n\r\n N/A \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n MMA10G-NATX-16-CC \r\n | \r\n\r\n AV \r\n | \r\n\r\n 8 x DD QSFP (QSFP200G) \r\n | \r\n\r\n 1 \r\n | \r\n\r\n DragonFire frame \r\n | \r\n\r\n N/A \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n MMA10G-NATX-32-CC \r\n | \r\n\r\n AV \r\n | \r\n\r\n 16 x DD QSFP (QSFP200G) \r\n | \r\n\r\n 1 \r\n | \r\n\r\n DragonFire frame \r\n | \r\n\r\n N/A \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n MMA10G-NATX-64-CC \r\n | \r\n\r\n AV \r\n | \r\n\r\n 32 x DD QSFP (QSFP200G) \r\n | \r\n\r\n 1 \r\n | \r\n\r\n DragonFire frame \r\n | \r\n\r\n N/A \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n MMA10G-IPX128 \r\n | \r\n\r\n AV \r\n | \r\n\r\n 32 x QSFP+ \r\n | \r\n\r\n 3 or 6 \r\n | \r\n\r\n EV Frame \r\n | \r\n\r\n ev3-FC or ev6-FC \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n 3080IPX-48-25G-CC \r\n | \r\n\r\n AV/ broadcast \r\n | \r\n\r\n 12 x QSFP+ \r\n | \r\n\r\n 3 or 6 \r\n | \r\n\r\n EV Frame \r\n | \r\n\r\n ev3-FC or ev6-FC \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \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
The EXE firmware version 1.5 will be referred to as EXE throughout this document.
\r\nThe EXE appliances are Ethernet switches optimized for video content.
","evaluation_configuration":"The summary of the evaluated functionality provided by the TOE includes the following:
\r\nThe evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the Evertz MMA10G-EXE Series II was evaluated are 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 MMA10G-EXE Series II Administrative Guide Addendum for Common Criteria, version 1.5, satisfies all of the security functional requirements stated in the MMA10G-EXE Series II Security Target version 1.2. The project underwent CCEVS Validator review. The evaluation was completed in August 2024. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
\r\nThe TOE is comprised of several security features. Each of the security features identified above consists of several security functionalities, as identified below.
\r\n\r\n
The TOE provides the security functions required by the Collaborative Protection Profile for Network Devices, hereafter referred to as NDcPP v2.2e or NDcPP.
\r\n\r\n
Security Audit
\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. The Audit events generated by the TOE include:
The TOE can store the generated audit data on itself, and it can be configured to send syslog 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 are authorized to edit them, 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 local console. 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 basis.
\r\n\r\n
Cryptographic Support
\r\nThe TOE includes an OpenSSL library (Version 1.1.1k with Fedora Patches) that implements CAVP validated cryptographic algorithms for random bit generation, encryption/decryption, authentication, and integrity protection/verification. 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. The cryptographic services provided by the TOE are described below:
\r\n\r\n
Table 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 establishment for TLS. | \r\n
| \r\n ECDSA \r\n | \r\n\r\n Provides components for EC-DH key establishment. | \r\n
| \r\n RSA \r\n | \r\n\r\n Provide key establishment, key generation and signature generation and verification | \r\n
Each of these cryptographic algorithms have been validated for conformance to the requirements specified in their respective standards, as identified below and are part of the EXE Cryptographic Module.
\r\n\r\n
Table 3 – CAVP Algorithm Testing References
\r\n| \r\n Algorithm \r\n | \r\n\r\n Standard \r\n | \r\n\r\n CAVP Certificate # \r\n | \r\n\r\n Processors \r\n | \r\n
| \r\n AES 128/256-bit CBC, GCM, CTR \r\n | \r\n\r\n ISO 10116 (CBC and CTR) \r\nIOS 19772 (GCM) \r\n | \r\n\r\n A2573 \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n CTR DRBG using AES 256 \r\n | \r\n\r\n ISO/IEC 18031:2011 \r\n | \r\n\r\n A2573 \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n EC-DH \r\nP-256, P-384, P-521 \r\n | \r\n\r\n NIST SP 800-56A (key establishment) \r\n | \r\n\r\n A2573 \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n ECDSA \r\nP-256, P-384, P-521 \r\n | \r\n\r\n FIPS PUB 186-4 (key generation) \r\n | \r\n\r\n A2573 \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n HMAC-SHA-1/256/384 \r\n | \r\n\r\n ISO/IEC 9797-2:2011 \r\n | \r\n\r\n A2573 \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n SHA-1/256/384 \r\n | \r\n\r\n ISO/IEC 10118-3:2004 \r\n | \r\n\r\n A2573 \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
| \r\n RSA 2048/3072/4096 \r\n | \r\n\r\n FIPS PUB 186-4 (key generation and Digital Signature) \r\nISO/IEC 9796-2 (digital signature) \r\n | \r\n\r\n A2573 \r\n | \r\n\r\n Intel(R) Core (TM) i3-6102E \r\n | \r\n
\r\n
Identification and Authentication
\r\nAll 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” EXE users do not access EXE directly; they control IP video switching through the EXE using a switch control system, such as Evertz’s Magnum. The switching of those IP video transport streams 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. If the user fails to provide the correct authentication credentials, the user will be locked out after a configurable threshold until the user is manually unlocked by an Administrator.
\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 EXE 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 uses X.509v3 certificates as defined by RFC 5280 to support authentication for TLS/HTTPS connections.
\r\n\r\n
Security Management
\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 these management functions are restricted to Security Administrators who are authorized to administer the TOE via a local CLI and a remote web interface. Administrators are individuals who manage specific types of administrative tasks. The EXE implements role-based access control of these management functions to users that have been identified, authenticated, and authorized with the Security Administrator role.
\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 these services can be managed from the interface, which uses a menu-driven navigation system.
\r\nThere is also a very simple serial-based connection (DB9) 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\n\r\n
Protection of the TSF
\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 is 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\nAn administrator initiates update processes from the web interface for all update installations. EXE automatically uses the RSA digital signature mechanism to confirm the integrity of the product before installing the update.
\r\n\r\n
TOE Access
\r\nAside from the automatic Administrators session termination due to inactivity described 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\n\r\n
Trusted Path/Channels
\r\nThe TOE allows the establishment of a trusted channel between a video control system (such as Evertz’ Magnum) and the EXE. The TOE also establishes a secure connection for sending syslog data to a syslog server using TLS.
\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":2901,"feature_name":"Asymmetric Key Generation"},{"id":2897,"feature_name":"Auditing"},{"id":2913,"feature_name":"Certificate Authentication"},{"id":2907,"feature_name":"Certificate Validation"},{"id":2904,"feature_name":"Cryptographic Hashing"},{"id":2902,"feature_name":"Cryptographic Key Establishment"},{"id":2903,"feature_name":"Cryptographic Signature Verification"},{"id":2899,"feature_name":"DRBG"},{"id":2911,"feature_name":"HTTPS Client"},{"id":2912,"feature_name":"HTTPS Server without Mutual Authentication"},{"id":2898,"feature_name":"Key Destruction"},{"id":2906,"feature_name":"Keyed-hash message authentication"},{"id":2915,"feature_name":"TLS 1.2"},{"id":2910,"feature_name":"TLS Client"},{"id":2909,"feature_name":"TLS Server with Mutual Authentication"},{"id":2900,"feature_name":"Virtual Network Device"}]}