FIPS 140-2 SECURITY POLICY Juniper Networks NetScreen-500 HW P/N NS-500 VERSION 4110 FW VERSIONS SCREENOS 5.0.0R9.H, SCREENOS 5.0.0R9A.H AND SCREENOS 5.0.0R9B.H Juniper NS-500 Security Policy 1 Copyright Notice Copyright © 2005 Juniper Networks, Inc. May be reproduced only in its original entirety [without revision]. Juniper Networks, the Juniper Networks logo, NetScreen, NetScreen Technologies, GigaScreen, and the NetScreen logo are registered trademarks of Juniper Networks, Inc. NetScreen-5GT, NetScreen-5XP, NetScreen-5XT, NetScreen-25, NetScreen-50, NetScreen-100, NetScreen-204, NetScreen-208, NetScreen-500, NetScreen-5200, NetScreen-5400, NetScreen-Global PRO, NetScreen-Global PRO Express, NetScreen-Remote Security Client, NetScreen-Remote VPN Client, NetScreen-IDP 10, NetScreen-IDP 100, NetScreen-IDP 500, GigaScreen ASIC, GigaScreen-II ASIC, and NetScreen ScreenOS are trademarks of Juniper Networks, Inc. All other trademarks and registered trademarks are the property of their respective companies. Juniper Networks, Inc. ATTN: General Counsel 1194 N. Mathilda Ave.Sunnyvale, CA 95014 FCC Statement The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. The equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense. The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with NetScreen's installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Consult the dealer or an experienced radio/TV technician for help. Connect the equipment to an outlet on a circuit different from that to which the receiver is connected. Caution: Changes or modifications to this product could void the user's warranty and authority to operate this device. Disclaimer THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR NETSCREEN REPRESENTATIVE FOR A COPY. Juniper NS-500 Security Policy 2 TABLE OF CONTENTS A. SCOPE OF DOCUMENT ...................................................................................................................... 3 B. SECURITY LEVEL................................................................................................................................. 4 C. ROLES AND SERVICES ...................................................................................................................... 4 D. INTERFACES ......................................................................................................................................... 6 E. SETTING FIPS MODE........................................................................................................................... 8 F. OTHER PARAMETERS ...................................................................................................................... 10 G. FIPS CERTIFICATE VERIFICATION ............................................................................................... 13 H. CRITICAL SECURITY PARAMETER (CSP) DEFINITIONS......................................................... 13 I. PUBLIC KEY DEFINITIONS ................................................................................................................ 14 J. MATRIX CREATION OF CRITICAL SECURITY PARAMETER (CSP) VERSUS THE SERVICES (ROLES & IDENTITY) ......................................................................................................... 14 K. DEFINITIONS LIST.............................................................................................................................. 17 A. Scope of Document The Juniper Networks NetScreen-500 is an Internet security device that integrates firewall, virtual private networking (VPN) and traffic shaping functionalities. Juniper NS-500 Security Policy 3 Through the VPN, the NetScreen-500 provides the following: · IPSec standard security · Data security using the Data Encryption Standard (DES), Triple-DES and Advanced Encryption Standard (AES) algorithms Note: DES - for legacy systems only; transitional phase only - valid until May 19, 2007 · Manual and automated IKE (ISAKMP) · Use of RSA and DSA certificates The NetScreen-500 also provides an interface for users to configure or set policies through the console or network ports. The general components of the NetScreen-500 include firmware and hardware. The main hardware components consist of a main processor, memory, flash, ASIC (GigaScreen), 10/100 Mbps ethernet interface, GBIC network interface, console interface, backplane, redundant power supplies and fan tray. The entire case is defined as the cryptographic boundary of the modules. The NetScreen- 500's physical configuration is defined as a multi-chip standalone module. B. Security Level The NetScreen-500 meets the overall requirements applicable to Level 2 security of FIPS 140-2. Table 1: Module Security Level Specification Security Requirements Section Level Cryptographic Module Specification 2 Cryptographic Module Ports and Interfaces 2 Roles, Services, and Authentication 2 Finite State Model 2 Physical Security 2 Operational Environment N/A Cryptographic Key Management 2 EMI/EMC 2 Self-Tests 2 Design Assurance 2 Mitigation of Other Attacks N/A C. Roles and Services TheNetScreen-500 supports five distinct roles: Juniper NS-500 Security Policy 4 · Cryptographic Officer Role (Root): The module allows one Crypto-Officer. This role is assigned to the first operator who logs on to the module using the default user name and password. Only the Crypto-Officer can create other administrators, and change to FIPS mode. · User Role (Admin): The Admin user can configure specific security policies. These policies provide the module with information on how to operate (for example, configure access policies and VPN encryption with Triple-DES). · Read-Only User Role (Admin): This role can only perform a limited set of services to retrieve information or status. This role cannot perform services to configure the box. · VSYS User Role: This role has the same operations as the User Role above, except that a VSYS user only operates within a particular virtual system. See the NetScreen Concept and Examples ScreenOS Reference Guide for more information about virtual systems. · VSYS Read-Only User Role: This role has the same operations as the Read- Only User Role above, except that a VSYS read-only user only operates within a particular virtual system. See the NetScreen Concept and Examples ScreenOS Reference Guide for more information about virtual systems. The module allows concurrent Admin users, either in a User Role or in a Read- Only Role. The root administrator can create a virtual system (vsys) administrator for each vsys, if the device has multiple virtual systems configured. The vsys administrator can function in either the "user" role or "read-only" role. A virtual system is the architecture that enables the device to respond with a different set of configurations for each vsys administrator. Therefore, a single box can appear to be several logical "virtual systems." The NetScreen-500 provides the following services: · Clear/Delete: Clear dynamic system info · Exec: Exec system commands · Exit: Exit command console · Get (Show Status): Get system information · Ping: Ping other host · Reset (Self-Tests): Reset system · Save: Save command · Set: Configure system parameters · Trace-route: Trace route · Unset: Unconfigure system parameters The NetScreen-500 supports both role-based and identity-based authentication. · All roles can be authenticated locally (within the NS-500); optionally, the module supports authentication via a RADIUS server for only the User role. Authentication by use of the RADIUS server is viewed as role- Juniper NS-500 Security Policy 5 based authentication; all other methods of authentication are identity- based. · All other forms of authentication (local database) are classified as identity based. · The module supports identity-based authentication for the Crypto-Officer (local database), the User Role (local database), the Read-Only User Role (local database), VSYS User Role, and VSYS Read-Only Role User Role. D. Interfaces The NetScreen-500 provides a number of interfaces: · LCD and Control Pad: A display with control keys that can be used to perform basic configurations and to view status reports through the LCD and control pad. The LCD displays two lines, each line capable of displaying up to 16 characters (Control Input, Status Output). · Two to four network cards. These may be either 10/100 Base T or GBIC interfaces (Data Input, Data Output, Control, Status). · HA-1: dedicated RJ-45 used for failover processing (Data Input, Data Output, Control, Status). · HA-2: backup dedicated RJ-45 used for failover processing if HA-1 fails (Data Input, Data Output, Control, Status). · MGT: dedicated RJ-45 used exclusively for management traffic, such as Telnet, SSH, or HTTP (Control, Status). · Console port: DB9 serial port connector (Control, Status). · Modem port: DB9 serial port connector. Disabled in FIPS mode. · PCMCIA interface for a memory flash card (Data Input). · Up to two power interfaces. · 22 LED status interfaces: 12 general, 4-interface module, and 6 port LEDs (Status). The following sections describe these LEDs. Table 2: Twelve General LEDs: LED Purpose Color Meaning Blinking STATUS System status Booting up normally amber Blinking Normal operation green Critical alarm - failure of hardware component or software module (such as a ALARM System alarm Red cryptographic algorithm) Green No alarm condition present Major alarm: o Low memory (<10% remaining) Amber o High CPU utilization (>90%) o Log memory full Juniper NS-500 Security Policy 6 o Sessions full o Maximum number of VPN tunnels reached o Firewall attacks detected o HA status changed or redundant group member not found Dark No alarm PWR1 Power Supply #1 Green Power supply #1 is functioning correctly Red Power supply failure, or bay is empty PWR2 Power Supply #2 Green Power supply #1 is functioning correctly Red Power supply failure, or bay is empty FAN Fan status Green All fans functioning properly Red One or more fans failed TEMP Temperature Green Temperature is within safety range Red Outside safety range HA High Availability Green Unit is master Blinking Redundant group member cannot be found green Amber Unit is slave Dark HA not configured FW Firewall alarm Green No alarm attacks Red Firewall alarm/event has occurred Blinking VPN VPN activity VPN activity - encrypting/decrypting traffic green Blinking VPN drops or denies traffic yellow VPN tunnels have reached 90%of the maximum number of simultaneously active Red IPSec SAs. Dark No VPN defined or no tunnels active Firewall session SESSION Green Sessions are < 70% utilization utilization Yellow Sessions are between 70% and 90% utilization. Red Sessions are >90% utilization. PCMCIA PC card status Green PC card is installed in PCMCIA slot. Blinking PC card is active green Red PC card is >90% full or read/write activity has failed. Dark PCMCIA slot is empty. SHAPE Traffic shaping Green Traffic shaping in operation Blinking Traffic shaping transmits packets green Blinking Traffic shaping drops packets yellow Red Configured guaranteed bandwidth > available interface bandwidth Dark No traffic shaping configured Juniper NS-500 Security Policy 7 · Four module status LEDs: Illuminates green to correspond to the position of the installed interface modules (Status): Green: Card operational Blinking Red: Card failed Dark: No card · Six network status LEDs for the MGT, HA-1 and HA-2 ports. Each Ethernet port has two LEDs: the left LED indicates 10Mbps or 100Mbps; the right LED indicates link and network activity (Status). E. Setting FIPS Mode By default, on the first power-up, the module is in non-FIPS mode. The commands "get config", or "get system" indicate if the system is in FIPS mode. The module can be set to FIPS mode only through the CLI. The module must be zeroized when toggling between FIPS and non-FIPS mode of operation. It is suggested that the module's configuration be saved prior to switching modes. To set the module to FIPS mode, execute "set FIPS-mode enable" through the CLI. Special note for firmware upgrade: if pre-5.0 firmware is upgraded to FIPS version 5.0 or higher, re-enable FIPS again by issuing the commands "unset FIPS-mode enable", "set FIPS-mode enable", and reboot the device. You must do this even if the device was previously in FIPS mode. This command will perform the following: · Disable administration via SSL · Disable the loading and output of the configuration file from the TFTP server · Disable the Global reporting agent · Disable administration via SNMP · Disable the debug service · Disable the modem port · Enforce amanagement via Telnet, HTTP (WebUI) and NetScreen Security Manager (NSM) only through a VPN with 256-bit AES encryption · Enforce management via SSH to use only 3DES · Disable the MD5 algorithm Execute the "save" command. Execute the "reset" command. Please note the following: · Configure the HA encryption key before using the HA link. · Telnet , HTTP (WEB UI) and NSM are allowed only through a VPN with 256-bit AES encryption. Juniper NS-500 Security Policy 8 · User names and passwords are case-sensitive. The password consists of at least six alphanumeric characters. Since there are 26 uppercase letters, 26 lowercase letters, and 10 digits, the total number of available characters is 62. The probability of someone guessing a password is 1/(626) = 1/56,800,235,584, which is far less than a 1/1,000,000 random success rate. If three login attempts from the console fail consecutively, the console will be disabled for one minute. If three login attempts from Telnet or the WebUI (through VPN with AES encryption) fail consecutively, any login attempts from that source will be dropped for one minute. · If there are multiple login failure retries within one minute and since the user is locked out after three contiguous login failures, the random success rate for multiple retries is 1/(626) + 1/626) + 1/(626) = 3/(626), which is far less than 1/100,000. · DSA-signed firmware image cryptographic strength analysis: the firmware is signed by a DSA private key, which is in the sole possession of Juniper Networks. The generated signature is attached to the firmware. In order for the device to accept an authorized image, the image has to have a correct 40-byte (320-bit) signature. The probability of someone guessing a signature correctly is 1/(2320), which is far less than 1/1,000,000. · The image download takes at least 23 seconds, so there can be no more than 3 download tries within one minute. Therefore, the random success rate for multiple retries is 1/(2 320) + 1/(2320) + 1/(2320) = 3/(2320), which is far less than 1/100,000. · In order for authentication data to be protected against disclosure, substitution and modification, the operator password is not echoed during entry. · The NetScreen-500 does not employ a maintenance interface or have a maintenance role. · When in FIPS mode, the NetScreen-500 WebUI only displays options that comply with the requirements of FIPS 140-2. · The output data path is logically disconnected from the circuitry and processes performing key generation, or key zeroization. · The NetScreen-500 provides a Show Status service via the GET service. · The NetScreen-500 cannot be accessed until the initialization process is complete. · The NetScreen-500 implements the following power-up self-tests: Device Specific Self-Tests: · Boot ROM firmware self-test is via DSA signature (Software Integrity Check) Juniper NS-500 Security Policy 9 · SDRAM read/write check · FLASH test Algorithm Self-Tests: · DES, CBC mode, encrypt/decrypt KAT · TDES, CBC mode, encrypt/decrypt KAT · SHA-1 KAT · RSA (encryption and signature) KAT · DSA Sign/Verify KAT · AES, CBC mode, encrypt/decrypt KAT · HMAC-SHA-1 KAT · DH key agreement test · ANSI X9.31 DRNG KAT The NetScreen-500 implements the following conditional tests: · DRNG continuous test · Hardware RNG continuous test · DSA pairwise consistency test · RSA pairwise consistency test · Bypass test · Firmware download DSA signature test (Software Load Test) F. Other Parameters Note the following: · The firmware can be loaded using the Trivial File Transfer Protocol (TFTP) or the PCMCIA port, where a firmware load test is performed via a DSA signature. · Keys are generated using the FIPS-approved ANSI X9.31 pseudo random number generator. · For every usage of the module's random number generator, a continuous RNG self-test is performed. Note that this is performed on both the FIPS-approved RNG and non-FIPS-approved RNG. · The NetScreen-500 enforces both identity-based and role-based authentication. Based on their identity, the operator assumes the correct role. · Operators must be authenticated using user names and passwords. Alternatively, the CO may also be authenticated via digital signature verification during the download of a new firmware image. Authentication will occur locally. As an option, the user can be authenticated via a RADIUS server. The RADIUS server provides an external database for user role administrators. The NetScreen-500 acts as a RADIUS proxy, forwarding the authentication request to the RADIUS server. The RADIUS server replies with either an accept or Juniper NS-500 Security Policy 10 reject message. See the log for authenticated logins. The RADIUS shared secret has to be at least 6 characters. · All logins through a TCP connection disconnect after three consecutive login failures, and an alarm is logged. · A separate session is assigned to each successful administrator login. · The first time an operator logs on to the module, the operator uses the default user name and password which is "netscreen", "netscreen". This user is assigned the Crypto-Officer role. · The Crypto-Officer is provided with the same set of services as the user with four additional services: (1) "set admin" and "unset admin". These two services allow the Crypto-Officer to create a new user, change a current user's user name and password, or delete an existing user. (2) "set FIPS enable" and "unset FIPS enable". These two services allow the Crypto-Officer to switch between FIPS mode and default mode. · HTTP can come through the VPN only with AES encryption. The default page timeout is set to 10 minutes; this is user configurable. The maximum number of HTTP connections, i.e., the maximum number of concurrent WebUI logins depends on how many TCP sockets are currently available in the system. The maximum number of available TCP sockets is 2048. This number is shared with other TCP connections. · There are a maximum of 22 sessions shared between Telnet and SSH. · Upon a telnet or console login failure, the next prompt will not come up for an estimated 5 seconds. · The NetScreen-500's chips are production-grade quality and include standard passivation techniques. · The NetScreen-500 is contained within a metal production-grade enclosure. Figure 1: Front of the NetScreen-500 Device · The enclosures are opaque to visible spectrum radiation. · The enclosure includes a removable cover and is protected by a tamper evident seal. The location of the tamper evident seal is shown in Figure 2. Juniper NS-500 Security Policy 11 Figure 2: Tamper Evident Seal · IKE, Diffie-Hellman (DH), and RSA encryption are employed for public key- based key distribution techniques, which are commercially available public key methods and are known to provide at least 80-bits of strength as implemented. · All keys and unprotected security parameters can be zeroized through the Unset, Clear,,Delete, and Reset commands. · The NetScreen-500 includes the following algorithms: · FIPS Approved: DSA SHA-1 TDES (CBC) DES (CBC) (for legacy systems only; transitional phase only - valid until May 19, 2007) AES (CBC) HMAC-SHA-1 RSA Sign/Verify (PKCS #1) ANSI X9.31 DRNG · Non-FIPS Approved: MD5 DH (key agreement, key establishment methodology provides 80 bits of encryption strength) RSA Encrypt/Decrypt (used for key wrapping only, key establishment methodology provides 80 bits of encryption strength) · The NetScreen-500 conforms to FCC part 15, class A. · On failure of any power-up self-test, the module enters and stays in either the Algorithm Error State, or Device specific error state, depending on the self-test failure. The console displays error messages and the status LED flashes red. It is the responsibility of Juniper NS-500 Security Policy 12 the Crypto-Officer to return the module to Juniper Networks for further analysis. · On failure of any conditional test, the module enters and stays in a permanent error state, depending on the type of failure: Bypass test failure, DH key agreement test failure, DSA pair-wise test failure, or RSA pair-wise agreement test failure. The console displays error messages and the status LED flashes red. It is the responsibility of the Crypto-Officer to return the module to Juniper Networks for further analysis. · On power down, previous authentications are erased from memory and need to be re-authenticated again on power-up. · Bypass tests are performed at power-up, and as a conditional test. Bypass state occurs when the administrator configures the box with a non-VPN policy and traffic matching this policy arrives at the network port. The bypass-enabled status can be found by retrieving the entire policy list. Two internal actions must exist in order for bypass to happen: (1) a non-VPN policy is matched for this traffic, and (2) a routing table entry exists for the traffic that matches this non-VPN policy. · In FIPS mode, SSH can use 3DES only to encrypt/decrypt commands. Also if the command from SSH is to set or get the AES manual key, it will fail and a message is logged. · HA traffic encryption is 256 bit AES. · If the VPN uses 3DES Encryption, the key exchange protocol IKE is enforced to use group 5 only. · The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. G. FIPS Certificate Verification In FIPS mode, during the loading of the X509 certificate, if the signing CA certificate cannot be found in the NetScreen-500, the following message is displayed on the console: Please contact your CA's administrator to verify the following finger print (in HEX) of the CA cert... xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx Do you want to accept this certificate y/[n]? Where x is one of (0, 1,2,3,4,5,6,7,8,9,A,B,C,D,E,F). Based on the result of the CA certificate fingerprint checking, the Crypto Officer accepts or denies the loaded certificates. H. Critical Security Parameter (CSP) Definitions Below is a list of Critical Security Parameter (CSP) definitions: · IPSEC HMAC SHA-1 Key: Used by IPsec for data integrity. · IPSEC ESP Key: DES, TDES, and AES for user traffic encryption. Juniper NS-500 Security Policy 13 · IKE Pre-Shared Key: Used during the IKE protocol to establish cryptographic keys to be used by IKE. · IKE Encryption Key: DES, TDES, and AES for peer-to-peer IKE message encryption. · IKE HMAC SHA-1 Key: Used by IKE for data integrity. · Password: Crypto-Officer and User passwords. · SSH Server/Host DSA Private Key: Used to create digital signatures. · SSH Encryption Key: TDES encryption key to encrypt telnet commands. · SSH HMAC SHA-1 Key: Used by SSH for data integrity. · HA Key: AES Encryption key for HA data. · IKE RSA/DSA Private Key: DSA/RSA key used in IKE identity authentication. · PRNG Algorithm Key: ANSI X9.31 algorithm key required to generate pseudo-random numbers. · Diffie Hellman Private Key Components: Used during the DH key agreement protocol. I. Public Key Definitions Below is a list of the public keys utilized by the module: · Firmware Authentication Key: Used by the device to verify DSA signatures over firmware images. · CA DSA/RSA Public Key: Used by IKE to authenticate a peer's certificate. · Local DSA/RSA Public Key: Used by the IKE peer to verify digital signatures. · SSH Server/Host DSA Public Key: Used by the SSH client to verify digital signatures. · SSH Client DSA Public Key: Used by the device to verify digital signatures. · Diffie Hellman Public Key Components: Used by the DH Key Agreement protocol. J. Matrix Creation of Critical Security Parameter (CSP) versus the Services (Roles & Identity) The following matrix defines the set of services to the CSPs of the module, providing information on generation, destruction and usage. It also correlates the User roles and the Crypto-Officer roles to the set of services to which they have privileges. The matrices use the following convention: Juniper NS-500 Security Policy 14 · G: Generate · D: Delete · U: Usage · N/A: Not Available Table 3: Crypto-Officer Crypto-Officer CSP \ Services Set UnsetClear/DeleteGetExecSavePingReset Exit Trace-route IPSEC HMAC SHA-1 Key G D N/A U N/A U N/A N/A N/A N/A IPSEC ESP Key G D N/A U N/A U N/A N/A N/A N/A IKE Pre-shared Key G D N/A U G U N/A N/A N/A N/A IKE Encryption Key N/A N/A D N/A N/A N/A N/A D N/A N/A IKE HMAC SHA-1 Key N/A N/A D N/A N/A N/A N/A D N/A N/A Password G1 D2 N/A U N/A U N/A N/A N/A N/A SSH Server/Host DSA Private Key G D D U G U N/A D N/A N/A (Server Key) SSH Encryption Key N/A N/A D N/A N/A N/A N/A D N/A N/A SSH HMAC SHA-1 Key N/A N/A D N/A N/A N/A N/A D N/A N/A HA Key G D N/A N/A U U N/A N/A N/A N/A IKE RSA/DSA Private Key N/A D N/A N/A G,D,U N/A N/A N/A N/A N/A PRNG Algorithm Key N/A N/A N/A N/A G,U N/A N/A D N/A N/A Diffie Hellman Private Key Components G N/A N/A N/A N/A N/A N/A D N/A N/A Juniper NS-500 Security Policy 15 Table 4: User and VSYS User User and VSYS User CSP \ Services Set Unset Clear/Delete Get Exec Save Ping Reset Exit Trace-route IPSEC HMAC SHA-1 Key G D N/A U N/A U N/A N/A N/A N/A IPSEC ESP Key G D N/A U N/A U N/A N/A N/A N/A IKE Pre-shared Key G D N/A U G U N/A N/A N/A N/A IKE Encryption Key N/A N/A D N/A N/A N/A N/A D N/A N/A IKE HMAC SHA-1 Key N/A N/A D N/A N/A N/A N/A D N/A N/A Password G3 N/A N/A U N/A U N/A N/A N/A N/A D SSH Server/Host DSA Private Key G D D U G U N/A (Server N/A N/A Key) SSH Encryption Key N/A N/A D N/A N/A N/A N/A D N/A N/A SSH HMAC SHA-1 Key N/A N/A D N/A N/A N/A N/A D N/A N/A HA Key G D N/A N/A U U N/A N/A N/A N/A IKE RSA/DSA Private Key N/A D N/A N/A G,D,U N/A N/A N/A N/A N/A PRNG Algorithm Key N/A N/A N/A N/A G,U N/A N/A D N/A N/A Diffie Hellman Private Key Components G N/A N/A N/A N/A N/A N/A D N/A N/A Table 5: Read-Only User and VSYS Read-Only User Read-Only User and VSYS Read-Only User CSP \ Services Get PingExitTrace-route IPSEC HMAC SHA-1 Key U N/A N/A N/A IPSEC ESP Key U N/A N/A N/A IKE Pre-shared Key U N/A N/A N/A IKE Encryption Key N/A N/A N/A N/A IKE HMAC SHA-1 Key N/A N/A N/A N/A Password U N/A N/A N/A SSH Server/Host DSA Private Key U N/A N/A N/A SSH Encryption Key N/A N/A N/A N/A SSH HMAC SHA-1 Key N/A N/A N/A N/A HA Key N/A N/A N/A N/A IKE RSA/DSA Private Key N/A N/A N/A N/A PRNG Algorithm Key N/A N/A N/A N/A Diffie Hellman Private Key Components N/A N/A N/A N/A 1. The Crypto-Officer is authorized to change all authorized operators' user names and passwords, but the user is only allowed to change his/her own user name and password 2. The Crypto-Officer is authorized to remove all authorized operators. 3. The Crypto-Officer is authorized to change all authorized operators' user names and passwords, but the user is only allowed to change his/her own user name and password. Juniper NS-500 Security Policy 16 K. Definitions List AES ­ Advance Encryption Standard CLI ­ Command Line Interface CSP ­ Critical Security Parameter DES ­ Data Encryption Standard DH ­ Diffie-Hellman DRNG ­ Deterministic RNG HA ­ High Availability IPSec ­ Internet Protocol Security IV ­ Initial Vector KAT ­ Known Answer Test NS ­ NetScreen NSM ­ NetScreen Security Manager PRNG ­ Pseudo RNG RNG ­ Random Number Generator ROM ­ Read Only Memory RSA ­ Rivest Shamir Adelman Algorithm SDRAM ­ Synchronous Dynamic Random Access Memory SSH ­ Secure Shell protocol TCP ­ Transmission Control Protocol TFTP ­ Trivial File Transfer Protocol VPN ­ Virtual Private Networking Juniper NS-500 Security Policy 17