Compliant Product - Junos OS 20.1R2 for NFX250
Certificate Date: 2021.09.07CC Certificate Security Target Validation Report
Validation Report Number: CCEVS-VR-VID11152-2021
Product Type: Network Device
Conformance Claim: Protection Profile Compliant
PP Identifier: collaborative Protection Profile for Network Devices Version 2.1
Extended Package for Intrusion Prevention Systems Version 2.11
collaborative Protection Profile Module for Stateful Traffic Filter Firewalls v1.3
PP-Module for Virtual Private Network (VPN) Gateways, Version 1.0
CC Testing Lab: Acumen Security
The Target of Evaluation (TOE) is Juniper Networks, Inc. Junos OS 20.1R2 for NFX250 Network Services Platform. The NFX250 is a network device that integrates routing, switching, and security functions on a single platform.
The NFX250 supports the definition of, and enforces, information flow policies among network nodes, also providing for stateful inspection of every packet that traverses the network and central management to manage the network security policy. All information flow from one network node to another passes through an instance of the TOE. Information flow is controlled on the basis of network node addresses, protocol, type of access requested, and services requested. In support of the information flow security functions, the TOE ensures that security-relevant activity is audited, that their own functions are protected from potential attacks, and provides the security tools to manage all of the security functions. The TOE provides multi-site virtual private network (VPN) gateway functionality, and also implements Intrusion Prevention System functionality, capable of monitoring information flows to detect potential attacks based on pre-defined attack signature and anomaly characteristics in the traffic.
The deployment of the Junos OS 20.1R2 for NFX250 TOE includes a hypervisor, which runs a virtual machine (VM) on an NFX250 series hardware model:
The hardware model specifications are described in the table below:
Table 1 TOE Hardware Specifications
The JCP’s FreeBSD kernel uses the kernel-based virtual machine (KVM) as a virtualization infrastructure. KVM is part of the standard NFX250 distribution and can be used to create multiple virtual machines (VMs) and to install security and networking appliances. The TOE uses Open vSwitch as a backplane between these VMs. However, in the TOE evaluated configuration, only a single VM is running and no security or networking appliances may be installed. Therefore, in the evaluated configuration the KVM functions simply as a pass-through layer.
The interfaces on the NFX250 devices include of physical interfaces and virtual interfaces.
The physical interfaces represent the physical ports on the NFX250 chassis. The physical interfaces include network and management ports:
· Network ports NFX250 chassis —
o 8 x 10/100/1000BASE-T RJ-45 LAN ports
o 2 x 10/100/1000BASE-T RJ-45 LAN/WAN ports
o 2 x 100/1000BASE-X small form-factor pluggable transceiver (SFP) WAN ports
o 2 x 1GbE/10GbE SFP+ WAN ports
o 1 x 10/100/1000BASE-T RJ-45 management port
o ADSL2/VDSL2 SFP
· Management port – NFX250 device has a dedicated management ports which functions as the out-of-band management interface –
o RJ-45 console port
o Mini USB console port
o USB 2.0 port
Each physical network port has four virtual functions (VFs) enabled by default, where the virtual functions (VFs) of the NIC ports are used to bypass the host OS and provide direct NIC-to-VM connectivity.
The virtual interfaces on the NFX250 device include the following:
· Virtual layer 2 interfaces – used to configure layer 2 switching of traffic for ethernet
· Virtual layer 3 interfaces – used to configure layer 3 features such as routing protocols and QoS
· Virtual SXE interfaces – two static interfaces connect the layer 2 dataplane to the Open vSwitch backplane
Physical ports on the front panel of the NFX250 device can be mapped to layer 2 or layer 3 interfaces or Virtualized Network Functions (VNF)s. There is a dedicated IPsec VPN interface.
NFX250 supports numerous routing standards for flexibility and scalability as well as IETF IPSec protocols. These functions can all be managed through the Junos OS software, either from a connected console on the management interface or via a network connection. Network management can be secured using IPsec, and SSH protocols. All management, whether from a user connecting to a console or from the network, requires successful authentication. In the evaluated deployment Network management (using the CLI) is secured using the SSH protocol, which can be tunnelled over IPsec.
In the evaluated configuration the TOE is managed and configured via Command Line Interface either via a directly connected console or using SSH connections (optionally tunnelled over IPsec).
 Raw capacity; actual capacity will be lower due to overprovisioning.
 ADSL2/VDSL2 interfaces are provided by a small form-factor pluggable transceiver which can be used in any SFP port on the NFX250.
 Maximum throughput mode
Security Evaluation Summary
The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the Junos OS 20.1R2 for NFX250 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. Acumen Security determined that the evaluation assurance level (EAL) for the product is EAL 1. The product, when delivered configured as identified in the Common Criteria Configuration Guide for NFX250 Network Services Platform, satisfies all of the security functional requirements stated in the Security Target Junos OS 20.1R2 for NFX250. The project underwent CCEVS Validator review. The evaluation was completed in August 2021. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
Juniper Networks, Inc.