The Target of Evaluation (TOE) is a network device (router/switch), and includes the following network devices running Junos OS 14.2R3:
\r\nEach Juniper Networks Mx-series and PTX-series routing platform is a complete routing system that supports a variety of high-speed interfaces (only Ethernet is within scope of the evaluation) for medium/large networks and network applications. Similarly, the EX-series 9200 switches provide high-performance, carrier-class networking solutions, supporting a variety of high-speed Ethernet interfaces for medium/large networks.
\r\nThe TOE consists of the following IT components:
\r\nThe TOE is comprised of the Junos OS 14.2R3.8 firmware running on the appliance chassis listed below in Table 1 (including the software implementing the Routing Engine and the software and ASICs implementing the Packet Forwarding Engine). Hence the TOE is contained within the physical boundary of the specified appliance chassis.
\r\nThe hardware has two components: the router/switch chassis and the PICs, DPCs and Line Cards that have been installed in the appliance. The various PICs, DPCs, MPCs, MICs and FPCs that have been installed in the appliance allow it to communicate with the different types of networks that may be required within the environment where the router/switch will be used[2]; however, they are considered non-TOE hardware and consequently, do not fall within the evaluated scope of the TOE.
\r\nThe physical boundary of the TOE is detailed in Table 1 below:
\r\n| \r\n Series \r\n | \r\n\r\n Model \r\n | \r\n\r\n Slots[3] \r\n | \r\n\r\n Firmware[4] \r\n | \r\n
| \r\n Mx-Series \r\n | \r\n\r\n Mx240 \r\n | \r\n\r\n 3 x MPCs and DPCs \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n
| \r\n Mx480 \r\n | \r\n\r\n 6 x MPCs and DPCs \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n|
| \r\n Mx960 \r\n | \r\n\r\n 12 x MPCs and DPCs \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n|
| \r\n Mx2010 \r\n | \r\n\r\n 10 x 480 line-rate 10GbE ports \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n|
| \r\n Mx2020 \r\n | \r\n\r\n 20 x 960 line-rate 10GbE ports \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n|
| \r\n PTX-Series \r\n | \r\n\r\n PTX3000 \r\n | \r\n\r\n 9 x Switch Interface Boards \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n
| \r\n PTX5000 \r\n | \r\n\r\n 9 x Switch Interface Boards \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n|
| \r\n EX-Series \r\n | \r\n\r\n EX9204 \r\n | \r\n\r\n 4 slots of up to 260 Gbps (full duplex) per slot fabric capacity \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n
| \r\n EX9208 \r\n | \r\n\r\n 8 slots of up to 260 Gbps (full duplex) per slot fabric capacity \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n|
| \r\n EX9214 \r\n | \r\n\r\n 14 slots of up to 260 Gbps (full duplex) per slot fabric capacity \r\n | \r\n\r\n Junos 14.2R3.8 \r\n | \r\n
Table 1 - TOE Physical Boundary
\r\n[1] The network interface components form the lower layers of the PFE (the DPC, PICs, DPCs, MPCs and FPCs network interface components) which simply deal with physical interfaces mechanics.
\r\n[2] These network interfaces are required for the TOE to operate. However, they are not relied upon for the enforcement security functionality necessary to satisfy the requirements of [NDPP] and so do not fall within the scope of the TSF. Therefore, the network interfaces are considered to be non-TOE hardware/software/firmware entities.
\r\n[3] The fabric/cards plugged into the chassis slots are considered to be non-TOE hardware/software/firmware entities as discussed above.
\r\n[4] The firmware version reflects the detail reported for the components of the Junos OS when the show version command is executed on the appliance.
\r\nThe evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The evaluation demonstrated that the TOE meets the security requirements contained in the Security Target, based on the Security Functional Requirements of the Network Devices Protection Profile, Version 1.1.
\r\nThe criteria for which the TOE was evaluated against, are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1. The methodology used by the evaluation team to conduct the evaluation is contained in the Common Methodology for Information Technology Security Evaluation, Version 3.1.
\r\nInfoGard Laboratories, Inc. determined that the TOE, configured as specified in the operational guidance, satisfies all of the security functional requirements stated in the Security Target.
","environmental_strengths":"\r\n\r\nThe evaluation of the TOE, provides assurance that the Security Functional Requirements (SFR) of the Network Devices Protection Profile, Version 1.1, has been met. A summary of the SFRs are as follows:
\r\nJunos auditable events are stored in the syslog files, 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, as well as the events listed in the table in Section 8 of the Security Target. Audit records include the date and time, event category, event type, username, and the outcome of the event (success or failure). Local syslog storage limits are configurable and are monitored. In the event of storage limits being reached the oldest logs will be overwritten.
\r\nThe TOE includes a baseline cryptographic module that provides confidentiality and integrity services for authentication and for protecting communications with adjacent systems.
\r\nThe TOE is designed to process network packets and forward them as appropriate. The packet handling is implemented in such a manner as to prevent the leakage of user data from one packet into other packet(s) that was not intended by the originator.
\r\nThe TOE requires users to provide unique identification and authentication data before any administrative access to the system is granted. .The devices also require that applications exchanging information with them successfully authenticate prior to any exchange. This covers all services used to exchange information, including Secure Shell (SSH).
\r\nTelnet, File Transfer Protocol (FTP), and Secure Socket Layer (SSL) are out of scope and are not used in the evaluated configuration.
\r\nThe TOE provides an Authorized Administrator role that is responsible for:
\r\nThe TOE is managed through a Command Line Interface (CLI). The CLI is accessible through a remote administrative session, as well as a local console session.
\r\nThe TOE provides protection mechanisms for its security functions. One of the protection mechanisms is to protect TSF data (e.g. cryptographic keys, administrator passwords). Another protection mechanism is to ensure the integrity of any software/firmware updates which can be verified utilizing a digital signature prior to installation on the TOE. The TOE provides for both cryptographic and non-cryptographic self-tests, and is capable of automated recovery from failure states. The TOE maintains a real-time clock to provide reliable timestamp for its own use.
\r\nThe TOE can be configured to terminate interactive user sessions after a user defined time-out variable is set. In addition, the TOE is able to present an access banner with warning messages prior to authentication. The TOE also allows the user to manually terminate an interactive session.
\r\nThe TOE creates trusted channels between itself and remote trusted authorized IT product (e.g. syslog server) entities that protect the confidentiality and integrity of communications. The TOE creates trusted paths between itself and remote administrators and users that protect the confidentiality and integrity of communications.
","features":[]}