NIAP: Compliant Product
NIAP/CCEVS
  NIAP  »»  Product Compliant List  »»  Compliant Product  
Compliant Product - Junos OS 19.2R1 for NFX150

Certificate Date:  2020.02.24

Validation Report Number:  CCEVS-VR-VID11010-2020

Product Type:    Network Device

Conformance Claim:  Protection Profile Compliant

PP Identifier:    collaborative Protection Profile for Stateful Traffic Filter Firewalls Version 2.0 + Errata 20180314
  collaborative Protection Profile for Network Devices Version 2.0 + Errata 20180314
  Extended Package for Intrusion Prevention Systems Version 2.11
  Extended Package for VPN Gateways Version 2.1

CC Testing Lab:  Acumen Security


CC Certificate [PDF] Security Target [PDF] Validation Report [PDF]

Assurance Activity [PDF]

Administrative Guide [PDF]


Product Description

The Target of Evaluation (TOE) is Juniper Networks, Inc. Junos OS 19.2R1-S2 for NFX150 Network Services Platform.  The NFX150 is a network device that integrates routing, switching, and security functions on a single platform. 

The NFX150 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 between network nodes 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. 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 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 19.2R1-S2 for NFX150 TOE includes a hypervisor, which runs a virtual machine (VM) on an NFX150 series hardware model:

·         NFX150-C-S1

·         NFX150-S1

·         NFX150-S1E


Evaluated Configuration

The hardware model specifications are described in the table below.

Specification

NFX150-C-S1

NFX150-S1

NFX150-S1-E

Form Factor

Desktop

Rack-mount

CPU

Intel 4 Core ATOM C3500 series

Intel 8 Core ATOM C3700 series

Memory

8 GB DDR4

16 GB DDR4

32 GB DDR4

Storage

100 GB SSD

200 GB SSD

Kernel

FreeBSD 10.0

Max VNFs

1 - 2

2 – 3

Integrated network interfaces

4 x 10/100/1000BASE-T RJ-45 LAN ports

2 x 1GbE/10GbE SFP+ WAN ports

1 x 10/100/1000BASE-T RJ-45 management port

Out-of-band interfaces

RJ-45

Mini USB console port

USB 3.0 port

 


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 19.2R1-S2 was evaluated are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 4.  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 4.  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 NFX150 Network Services Platform Release 19.2R1, satisfies all of the security functional requirements stated in the Junos OS 19.2R1-S2 for NFX150 Security Target. The project underwent CCEVS Validator review.  The evaluation was completed in February 2020.  Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.


Environmental Strengths

The logical boundary of the TOE includes the following security functionality:

Security Functionality

Description

Protected Communications

The TOE provides an SSH server to support protected communications for administrators to establish secure sessions and to connect to external syslog servers.

The TOE also supports IPsec connections to provide multi-site virtual private network (VPN) gateway functionality and also as a tunnel for remote administrate SSH connections.  The TOE requires that applications exchanging information with it are successfully authenticated prior to any exchange (i.e. applications connecting over SSH and IPsec).

Telnet, File Transfer Protocol (FTP), and Secure Socket Layer (SSL) are out of scope.

The TOE includes cryptographic modules that provide the underlying cryptographic services, including key management and protection of stored keys, algorithms, random bit generation and crypto-administration.  The cryptographic modules provide confidentiality and integrity services for authentication and for protecting communications with adjacent systems. 

Administrator Authentication

Administrative users must provide unique identification and authentication data before any administrative access to the system is granted. Authentication data entered and stored on the TOE is protected. The TOE can be configured to terminate interactive user sessions and to present an access banner with warning messages prior to authentication.

Correct Operation

The TOE provides for both cryptographic and non-cryptographic self-tests and is capable of automated recovery from failure states.

Trusted Update

The administrator can initiate update of the TOE software.  The integrity of any software updates is verified prior to installation of the updated software.

Audit

TOE auditable events are stored in the syslog files in the VM filesystem and can be sent to an external log server (via Netconf over SSH). Auditable events include start-up and shutdown of the audit functions, authentication events, service requests, IPS events, as well as the events listed in Table 4 and Table 5 of the ST. Audit records include the date and time, event category, event type, username, and the outcome of the event (success or failure). Local (VM) syslog storage limits are configurable and are monitored. In the event of storage limits being reached the oldest logs will be overwritten.

Management

The TOE provides a Security Administrator role that is responsible for:

·         the configuration and maintenance of cryptographic elements related to the establishment of secure connections to and from the evaluated product

·         the regular review of all audit data;

·         initiation of trusted update function;

·         administration of VPN, IPS and Firewall functionality;

·         all administrative tasks (e.g., creating the security policy).

The devices are managed through a Command Line Interface (CLI). The CLI is accessible through local (serial) console connection or remote administrative (SSH) session.

The Security Administrator role includes the capability to manage all NFX150 services.  Access to manage the device’s FreeBSD host can only be gained through the JCP.

Packet Filtering/Stateful Traffic Filtering

The TOE provides stateful network traffic filtering based on examination of network packets and the application of information flow rules.

Intrusion Prevention

The TOE can be configured to analyze IP-based network traffic forwarded to the TOE’s interfaces and detect violations of administratively-defined IPS policies. The TOE is capable of initiating a proactive response to terminate/interrupt an active potential threat, and to initiate a response in real time that would cause interruption of the suspicious traffic flow.

User Data Protection/Information Flow Control

The TOE is designed to forward network packets (i.e., information flows) from source network entities to destination network entities based on available routing information using Virtual Routers. This information is either provided directly by TOE users or indirectly from other network entities (outside the TOE) configured by the TOE users. The TOE has the capability to regulate the information flow across its interfaces; traffic filters can be set in accordance with the presumed identity of the source, the identity of the destination, the transport layer protocol, the source service identifier, and the destination service identifier (TCP or UDP port number).

 


Vendor Information


Juniper Networks, Inc.
Ray Tom
(408)745-2000
(408) 745-2100
rtom@juniper.net

www.juniper.net
Site Map              Contact Us              Home