The TOE is the Juniper Networks LN1000-V Mobile Secure Router and SRX650 Services Gateway, Running Junos 11.2S4. The Juniper Networks LN1000-V and SRX650 devices are routing, firewalling, and IDS systems that support a variety of high-speed interfaces for network applications. They are built on a common architecture, share a common operating system, and provide identical security functionality. The routers are physically self-contained, housing the software, firmware and hardware necessary to perform all routing, firewalling, and intrusion detection functions.
\r\nThe LN1000-V is intended for deployment in an environment requiring a rugged network router with a small footprint in a transportable package, such as Defense communities and Public sector safety organizations.
\r\nThe SRX650 is intended for deployment at remote and branch locations in the network to provide all-in-one secure WAN connectivity, IP telephony, and connection to local PCs and servers via integrated Ethernet switching.
","evaluation_configuration":null,"security_evaluation_summary":"The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process. The criteria against which the TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 3. 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 3. Science Applications International Corporation (SAIC) determined that the evaluation assurance level (EAL) for the product is the EAL4 assurance requirements package, augmented with ALC_FLR.2. The product satisfies all of the security functional requirements stated in the Juniper Networks LN1000-V Mobile Secure Router and SRX650 Services Gateway, Running Junos 11.2S4 Security Target, when configured as specified in the supplied guidance documentation.
\r\nA validation team on behalf of the CCEVS Validation Body monitored the evaluation carried out by SAIC. The evaluation was completed in March 2013. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10402-2013), prepared by CCEVS.
","environmental_strengths":"Juniper Networks LN1000-V Mobile Secure Router and SRX650 Services Gateway, Running Junos 11.2S4 provide a moderate to high level of independently assured security in a conventional TOE and are suitable for a relatively benign environment with good physical access security and competent administrators.
\r\nJuniper Networks LN1000-V Mobile Secure Router and SRX650 Services Gateway, Running Junos 11.2S4 support the following security functions:
\r\nSecurity audit events related to router and firewall functionality are stored in a circular in-memory buffer—the requirements for auditing are met by local in-memory storage. IDS events are similarly stored in a separate in-memory IDS event trail. The TOE provides the capability of analyzing potential intrusions via signature analysis, which uses patterns corresponding to known attacks, and by detecting protocol anomalies. The TOE implements two roles related to the security audit function: the Audit Administrator; and the IDS Audit Administrator. The audit log can be viewed by all administrators, but the IDS audit log can be viewed only by the IDS Administrator. Search and sort facilities are provided. In conjunction with the audit capabilities, the TOE provides an alarm mechanism that provides immediate notification of potential security violations and potential intrusions.
\r\nThe TOE devices constitute cryptographic modules that satisfy the requirements of FIPS 140-2 Security Level 2. The cryptographic module provides confidentiality, integrity, and authentication services in support of the following cryptographic protocols: Secure Shell (SSH), used for remote administrator access to the appliance; and IPsec/IKE, used for secure communications between the appliance and external peer routers.
\r\nThe TOE is designed to forward network packets from source network entities to destination network entities based on available routing information. This information is either provided directly by administrators or indirectly from other network entities (outside the TOE) configured by the administrators. 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).
\r\nThe TOE provides an authentication mechanism for administrative users through an internal authentication database. Administrative login is supported through the locally connected console, when enabled, or remotely via an SSH protected communication channel.
\r\nA known administrator user id and its corresponding authentication data must be entered correctly in order for the administrator to successfully logon and thereafter gain access to administrative functions. For local authentication, all administrator user name and password pairs are managed in a database internal to the TOE. Excessive failed login attempts while initiating a remote administration session can cause the session being created to be closed.
\r\nThe TOE supports four separate and distinct administrative roles: Audit Administrator; Cryptographic Administrator; IDS Administrator; and Security Administrator. When configured in accordance with the supplied guidance documentation, the TOE ensures administrators are restricted to performing functions allowed by their assigned role.
\r\nThe TOE provides a command line administrative interface and supports remote administration through an SSH command line interface. To execute the CLI, the administrator can establish a trusted SSH connection to the TOE and utilize the CLI offered through the SSH connection. Regardless of the interface, the authorized administrator must be successfully identified and authenticated before they are permitted to perform any security management functions on the TOE.
\r\nThe TOE is a hardware and firmware device that protects itself largely by offering only a minimal logical interface to the network and attached nodes. Junos is a special purpose OS that provides no general purpose programming capability. The TOE also preserves its configuration for trusted recovery in the event that the configuration has been modified and not saved or if the TOE has been ungracefully shutdown.
\r\nThe TOE provides a recovery and self testing mechanism. The recovery mechanism allows administrators to return the TOE to a secure state, while the self test mechanism allows administrators to verify the integrity of the TOE and its cryptographic functions.
\r\nThe TOE provides features to protect itself from Denial of Service attacks. These features limit TCP connections and offer administrators the ability to limit the number of resources a particular address or set of addresses can use over a specified time period.
\r\nThe TOE provides the ability to restrict the establishment of an administrative session based on a schedule or based upon the originating source IP address (or subnet). The TOE also provides inactivity timeouts and logon banners that can be configured by administrators.
\r\nThe TOE creates trusted channels between itself and remote trusted authorized IT product 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":[]}