The Bivio 6310-NC (Target of Evaluation, or TOE) is a network device providing highly variable network functionality. It achieves this by leveraging RHEL8.2 to provide full hardware access to the networking applications, allowing them to address the high-performance hardware devices directly.
\r\nThe Bivio 6310-NC device can be used to run a variety of applications for processing network data. There are many such applications, both commercial and open source. It is out of scope for this certification process to include all these applications for evaluation, so a standard application factory-installed to all Bivio 6310-NC devices as part of the base BiviOS will be provided. This application provides the following non-evaluated functionality:
\r\n· Inspects packets and will either drop them or forward them based on configuration.
\r\n· Uses the default mechanisms for packet handling and represents other packet processing applications that a customer may choose to install.
\r\nModels of the TOE are identified with a part number in the format:
\r\n1. B6310-NC-C(x,y)M(1,2,3,4,5)D(1,2,3,4,5,6)N(1,2,3,4)
\r\na. This chassis is the “standard” product chassis.
\r\n2. B6310R-NC-C(x,y)M(1,2,3)D(1,2,3,4,5,6)N(1,2,4)
\r\na. This chassis is a shorter, ruggedized chassis
\r\n3. PacStar 451
\r\na. This chassis does not have configuration options and will always use the “C04” processor specification (defined below) and no others.
\r\nThe first digit ‘x’ following ‘C’ is indicative of the processor family (0 – Broadwell, 1 – Skylake, 2 – Cascade Lake), and the second digit ‘y’ (following the digit ‘x’) is selected to match Bivio’s hardware model numbering.
\r\nThe naming conventions specified above reference the following hardware:
\r\n| \r\n\r\n | \r\n|
| \r\n Part Number \r\n | \r\n\r\n Processor \r\n | \r\n
| \r\n Options with C11 \r\n | \r\n\r\n Dual Intel Xeon Gold 6148, 2.4 GHz w/ 27Mb Cache \r\n | \r\n
| \r\n Options with C13 \r\n | \r\n\r\n Dual Intel Xeon Silver 4110, 2.1 GHz w/ 11Mb Cache \r\n | \r\n
| \r\n Options with C15 \r\n | \r\n\r\n Dual Intel Xeon Gold 6138, 2.0 GHz w/27Mb Cache \r\n | \r\n
| \r\n Options with C21 \r\n | \r\n\r\n Dual Intel Xeon Silver 4215, 2.5Ghz with 11Mb cache \r\n | \r\n
| \r\n Options with C22 \r\n | \r\n\r\n Dual Intel Xeon Silver 4214, 2.5Ghz with 11Mb cache \r\n | \r\n
| \r\n Options with C23 \r\n | \r\n\r\n Dual Intel Xeon Silver 4208, 2.1Ghz with 11Mb cache \r\n | \r\n
| \r\n Options with C24 \r\n | \r\n\r\n Dual Intel Xeon Gold 5222, 3.8Ghz with 16.5 Mb cache \r\n | \r\n
| \r\n Options with C25 \r\n | \r\n\r\n Dual Intel Xeon Gold 6242, 2.8Ghz with 22Mb cache \r\n | \r\n
| \r\n Options with C26 \r\n | \r\n\r\n Dual Intel Xeon Gold 6252, 2.5Ghz with 35.75Mb cache \r\n | \r\n
| \r\n Options with C04 \r\n | \r\n\r\n Intel Xeon D 1541, 2.1Ghz with 12MB cache \r\n | \r\n
| \r\n Part Number \r\n | \r\n\r\n Installed RAM \r\n | \r\n
| \r\n Options with M1 \r\n | \r\n\r\n 256GB DDR4-2666 memory \r\n | \r\n
| \r\n Options with M2 \r\n | \r\n\r\n 512GB DDR4-2666 memory \r\n | \r\n
| \r\n Options with M3 \r\n | \r\n\r\n 384GB DDR4-2666 memory \r\n | \r\n
| \r\n Options with M4 \r\n | \r\n\r\n 768GB DDR4-2666 memory \r\n | \r\n
| \r\n Options with M5 \r\n | \r\n\r\n 1536GB DDR4-2666 memory \r\n | \r\n
| \r\n Part Number \r\n | \r\n\r\n Installed Storage \r\n | \r\n
| \r\n Options with D1 \r\n | \r\n\r\n 2x 1TB SSD storage \r\n | \r\n
| \r\n Options with D2 \r\n | \r\n\r\n 2x 2TB SSD storage \r\n | \r\n
| \r\n Options with D3 \r\n | \r\n\r\n 4x 2TB SSD storage \r\n | \r\n
| \r\n Options with D4 \r\n | \r\n\r\n 8x 2TB SSD storage \r\n | \r\n
| \r\n Options with D5 \r\n | \r\n\r\n 4x 3.8TB SSD storage \r\n | \r\n
| \r\n Options with D6 \r\n | \r\n\r\n 8x 3.8TB SSD storage \r\n | \r\n
| \r\n Part Number \r\n | \r\n\r\n Installed NIC Interfaces \r\n | \r\n
| \r\n Options with N1 \r\n | \r\n\r\n 2x 10GbE Fiber interfaces and 4x 1GbE Copper interfaces \r\n | \r\n
| \r\n Options with N2 \r\n | \r\n\r\n 4x 10GbE Fiber interfaces and 4x 1GbE Copper interfaces \r\n | \r\n
| \r\n Options with N3 \r\n | \r\n\r\n 6x 10GbE Fiber interfaces and 2x 1GbE Copper interfaces \r\n | \r\n
| \r\n Options with N4 \r\n | \r\n\r\n 4x 10GbE Fiber interfaces and 2x 1GbE Copper interfaces \r\n | \r\n
All “M”, “D”, and “N” options are configuration options which do not affect validation, but are part of the model number.
Running the following software:
\r\nBiviOS 8.5.1 V: Version 8.5.1 (Build 202006181129) V: Version 8.5.1-104-bv (Patch 202009191230) V: Version 8.5.1-103-rh (Patch 202008311617)
\r\nThe guidance documentation is also part of the TOE. A list of the guidance documents can be found in Table 12 of the [ST].
\r\nThe TOE’s Operational Environment must provide the following services to support the secure operation of the TOE:
\r\n· Local Console
\r\n· Syslog Server
\r\n· An SSHv2 Client
\r\n· A TLSv1.2 client
","evaluation_configuration":"The TOE was configured for evaluation per the provided Administrative Guidance, using all claimed TOE functionality, specifically management through SSH, Local console and TLS-enabled telnet and time synchronization using NTP, and remote syslog server as a remote audit storage.
","security_evaluation_summary":"The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) processes and procedures. Bivio 6310-NC was evaluated against the criteria contained in the Common Criteria for Information Technology Security Evaluation, Version 3.1 Revision 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 Revision 5. The TOE, when installed and configured per the instructions provided in the preparative and administrative guidance, satisfies all the security functional requirements stated in the Bivio 6310-NC Security Target. The evaluation underwent CCEVS Validator review. The evaluation was completed in December 2020.
","environmental_strengths":"Audit
\r\n· The TOE will audit all events and information defined in Table 4: Auditable Events of the Security Target
\r\n· The TOE will also include the identity of the user that caused the event (if applicable), date and time of the event, type of event, and the outcome of the event.
\r\n· The TOE protects storage of audit information from unauthorized deletion.
\r\n· The TOE prevents unauthorized modifications to the stored audit records.
\r\n· The TOE can transmit audit data to an external IT entity using SSH protocol.
\r\nCryptographic Operations
\r\nThe TSF performs the following cryptographic operations:
\r\nFor TLS:
\r\n· AES-128 in CBC mode for data ciphering, using SHA-1 hashing and RSA key exchange.
\r\n· AES-256 in GCM mode for data ciphering, using SHA-384 hashing and ECDHE key exchange.
\r\n· HMAC-SHA2-384 for keyed hash
\r\nFor SSH:
\r\n· AES-128 or AES-256 in CBC mode, HMAC-SHA2-256 or HMAC-SHA2-512 hashing and DH key exchange.
\r\n· Public key authentication via SSH-RSA, RSA-SHA2-256 and RSA-SHA2-512 using HMAC-SHA1, HMAC-SHA2-256 and HMAC-SHA2-512 hashing algorithms.
\r\n· The TOE supports NTP v4 (RFC 5905). For NTP, the TOE uses the Symmetric key Method to ensure authenticity and integrity; supporting SHA1, SHA 512 and SHA256 MACs.
\r\n· TOE Random bit generation utilizes CTR_DRBG as defined by NIST SP 800-90A. This is not configurable, and there are no other cryptographic engines provided in the TOE.
\r\n· To support SSH for trusted path and trusted channel, the TOE cryptographic module implements RSA key generation with key sizes of 2048-bits and finite-field cryptography with modulus sizes of 2048 bits (Diffie-Hellman Group14).
\r\n· To support TLS, the TOE cryptographic module implements Elliptic-Curve key generation over NIST curve secp256r1 and RSA key generation using 2048-bit keys.
\r\n· The TOE supports Trusted Update by allowing the administrator to download update files from Bivio. Any software installed on the TOE will become active immediately and is authenticated using a published hash. Trusted update uses SHA-256 hash function in its algorithm.
\r\n· The TSF zeroizes all plaintext secret and private cryptographic keys and CSPs once they are no longer required.
\r\nIdentification and Authentication
\r\n· The TSF supports passwords consisting of alphanumeric and special characters. The TSF also allows administrators to set a minimum password length and support passwords with 9 characters or more.
\r\n· The TSF requires all administrative users to authenticate before allowing the user to perform any actions other than:
\r\no Display the warning banner in accordance with FTA_TAB.1;
\r\no Responding to ICMP echo requests
\r\no Responding to ARP requests with ARP replies
\r\no Establishing TLS connection on TCP port 27777
\r\no Automated generation of cryptographic keys
\r\nSecurity Management
\r\n· The TSF stores and protects the following data:
\r\no Syslog data, user account data, and local authentication data (such as administrator passwords).
\r\no Cryptographic keys including pre-shared keys, symmetric keys, and private keys.
\r\n· There is one class of user on the TOE: The Admin user
\r\no The Admin user has full control over the TOE.
\r\n· Management of the TSF:
\r\no The administrator can perform manual updates, determine the behavior of or modify the behavior of the handling of audit data, modify the behavior of the TSF, enable or disable services offered by the TOE, determine the behavior of or modify the behavior of audit functionality when local audit storage is full, manage TSF data, modify, delete, generate or import cryptographic keys, configure the access banner, and configure the session inactivity timeout period.
\r\no The administrator may perform these functions locally or remotely using the trusted path provided by SSH and defined in FTP_TRP.1.
\r\nProtection of the TSF
\r\n· The TSF protects TSF data from disclosure when the data is transmitted between different parts of the TOE.
\r\n· The TSF prevents the reading of secret and private keys.
\r\n· The TOE provides reliable time stamps for itself.
\r\n· The TOE runs a suite of self-tests during the initial start-up (upon power on) to demonstrate the correct operation of the TSF.
\r\n· The TOE provides a means to verify firmware/software updates to the TOE using a published hash prior to installing those updates.
\r\nTOE Access
\r\n· The TOE, for local interactive sessions, will terminate the session after an Authorized Administrator-specified period of session inactivity.
\r\n· The TOE terminates a remote interactive session after an Authorized Administrator-configurable period of session inactivity.
\r\n· The TOE allows Administrator-initiated termination of the Administrator’s own interactive session.
\r\n· Before establishing an administrative user session, the TOE is capable of displaying an Authorized Administrator-specified advisory notice and consent warning message regarding unauthorized use of the TOE.
\r\nTrusted Path/Channels
\r\n· The TOE uses SSH to provide a trusted communication channel between itself and all authorized IT entities that is logically distinct from other communication channels and provides assured identification of its end points and protection of the channel data from disclosure and detection of modification of the channel data.
\r\n· The TOE permits the TSF, or the authorized IT entities to initiate communication via the trusted channel.
\r\n· The TOE permits remote administrators to initiate communication via the trusted path.
\r\n· The TOE requires the use of the trusted path for initial administrator authentication and all remote administration actions.
","features":[]}