Juniper SA6500 FIPS User guide

Junos Pulse Secure Access Service

SA Series 4500, 6500, and FIPS Appliances

Release

7.2

Published: 2012-05-15

Juniper Networks, Inc.

1194 North Mathilda Avenue

Sunnyvale, California 94089

USA

408-745-2000

www.juniper.net

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United

States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other

trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,

transfer, or otherwise revise this publication without notice.

Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are

owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,

6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.

Junos Pulse Secure Access Service SA Series 4500, 6500, and FIPS Appliances

Release 7.2

The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the

year 2038. However, the NTP application is known to have some difficulty in the year 2036.

END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks

software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at

http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions

of that EULA.

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Part 1 Overview

Chapter 1 Appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

SA4500 and SA6500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Standard Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

SA Series 6500 Field-Replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2 FIPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

SA FIPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

SA FIPS Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

FIPS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Part 2 Planning

Chapter 3 Network Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Secure Access Appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 4 Name and Password Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Name and Password Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 5 Security World . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Creating a New Security World . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Recovering an Archived Security World . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Part 3 Installation

Chapter 6 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing Secure Access Appliance Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 7 Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Joining a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Deploying a Cluster in a Secure Access FIPS Environment . . . . . . . . . . . . . . . . . . 28

Chapter 8 Keystores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Initializing a Keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Reinitializing the Keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Binary Importing and Exporting of the Keystore . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 9 Device Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Importing Device Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 10 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Basic Setup for Secure Access Appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Licensing and Configuring Your Secure Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Part 4 Maintenance

Chapter 11 Hardware Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Replacing the Cooling Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Replacing a Hard Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Replacing IOC Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Replacing a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 12 LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Device Status LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Ethernet Port LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

FIPS Device Status LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 13 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Changing the Security Officer Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Changing the Web User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 14 HSM Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Upgrading the HSM Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 15 Administrator Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Creating Administrator Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Part 5 Troubleshooting

Chapter 16 HSM Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Resetting the HSM Card In Case Of An Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Part 6 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SA Series 4500, 6500, and FIPS Appliances

List of Tables

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Part 2 Planning

Chapter 4 Name and Password Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Table 3: Security Officer Name and Username Requirements . . . . . . . . . . . . . . . . 15

Part 3 Installation

Chapter 10 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table 4: Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Part 4 Maintenance

Chapter 12 LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 5: Device Status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 6: 4-Port Copper Gigabit Ethernet LEDs (available on IC4500 and

IC6500) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Table 7: Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

SA Series 4500, 6500, and FIPS Appliances

About the Documentation

•

Documentation and Release Notes on page vii

•

Supported Platforms on page vii

•

Documentation Conventions on page vii

•

Documentation Feedback on page ix

•

Requesting Technical Support on page ix

Documentation and Release Notes

To obtain the most current version of all Juniper Networks

®

technical documentation,

see the product documentation page on the Juniper Networks website at

http://www.juniper.net/techpubs/.

If the information in the latest release notes differs from the information in the

documentation, follow the product Release Notes.

Juniper Networks Books publishes books by Juniper Networks engineers and subject

matter experts. These books go beyond the technical documentation to explore the

nuances of network architecture, deployment, and administration. The current list can

be viewed at http://www.juniper.net/books .

Supported Platforms

For the features described in this document, the following platforms are supported:

•

SA6500 FIPS

•

SA4500 FIPS

•

SA6500

•

SA4500

Documentation Conventions

Table 1 on page viii defines notice icons used in this guide.

Table 1: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Table 2 on page viii defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

ExamplesDescriptionConvention

To enter configuration mode, type

theconfigure command:

user@host> configure

Represents text that you type.Bold text like this

user@host> show chassis alarms

No alarms currently active

Represents output that appears on the

terminal screen.

Fixed-width text like this

•

A policy term is a named structure

that defines match conditions and

actions.

•

Junos OS System Basics Configuration

Guide

•

RFC 1997, BGP Communities Attribute

•

Introduces or emphasizes important

new terms.

•

Identifies book names.

•

Identifies RFC and Internet draft titles.

Italic text like this

Configure the machine’s domain name:

[edit]

root@# set system domain-name

domain-name

Represents variables (options for which

you substitute a value) in commands or

configuration statements.

Italic text like this

•

To configure a stub area, include the

stub statement at the[edit protocols

ospf area area-id] hierarchy level.

•

The console port is labeled

CONSOLE.

Represents names of configuration

statements, commands, files, and

directories; configuration hierarchy levels;

or labels on routing platform

components.

Text like this

stub <default-metric metric>;Enclose optional keywords or variables.< > (angle brackets)

SA Series 4500, 6500, and FIPS Appliances

Table 2: Text and Syntax Conventions (continued)

ExamplesDescriptionConvention

broadcast | multicast

(string1 | string2 | string3)

Indicates a choice between the mutually

exclusive keywords or variables on either

side of the symbol. The set of choices is

often enclosed in parentheses for clarity.

| (pipe symbol)

rsvp { # Required for dynamic MPLS

only

Indicates a comment specified on the

same line as the configuration statement

to which it applies.

# (pound sign)

community name members [

community-ids ]

Enclose a variable for which you can

substitute one or more values.

[ ] (square brackets)

[edit]

routing-options {

static {

route default {

nexthop address;

retain;

}

Identify a level in the configuration

hierarchy.

Indention and braces ( { } )

Identifies a leaf statement at a

configuration hierarchy level.

; (semicolon)

J-Web GUI Conventions

•

In the Logical Interfaces box, select

All Interfaces.

•

To cancel the configuration, click

Cancel.

Represents J-Web graphical user

interface (GUI) items you click or select.

Bold text like this

In the configuration editor hierarchy,

select Protocols>Ospf.

Separates levels in a hierarchy of J-Web

selections.

> (bold right angle bracket)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can send your comments to

techpubs-comments@juniper.net, or fill out the documentation feedback form at

https://www.juniper.net/cgi-bin/docbugreport/ . If you are using e-mail, be sure to include

the following information with your comments:

•

Document or topic name

•

URL or page number

•

Software release version (if applicable)

Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance

Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,

About the Documentation

or are covered under warranty, and need post-sales technical support, you can access

our tools and resources online or open a case with JTAC.

•

JTAC policies—For a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf .

•

Product warranties—For product warranty information, visit

http://www.juniper.net/support/warranty/ .

•

JTAC hours of operation—The JTAC centers have resources available 24 hours a day,

7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online

self-service portal called the Customer Support Center (CSC) that provides you with the

following features:

•

Find CSC offerings: http://www.juniper.net/customers/support/

•

Search for known bugs: http://www2.juniper.net/kb/

•

Find product documentation: http://www.juniper.net/techpubs/

•

Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

•

Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

•

Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/

•

Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

•

Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

To verify service entitlement by product serial number, use our Serial Number Entitlement

(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

•

Use the Case Management tool in the CSC at http://www.juniper.net/cm/ .

•

Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html .

SA Series 4500, 6500, and FIPS Appliances

PART 1

Overview

•

Appliances on page 3

•

FIPS on page 7

SA Series 4500, 6500, and FIPS Appliances

CHAPTER 1

Appliances

•

SA4500 and SA6500 on page 3

SA4500 and SA6500

The SA4500 and SA6500 (SA 4500/6500) are next-generation appliances featuring

a number of notable hardware features.

Standard Hardware

The SA 4500/6500 chassis features the following hardware components:

•

Console port—You use the console port to initially set up the SA 4500/6500 before

you fully integrate it as the secure gateway to your internal network. You can also use

the console port to perform certain configuration and clustering tasks after the Secure

Access Service begins operating as the secure gateway.

•

Bonding ports—By default, on the SA6500 only, the Secure Access Service uses bonding

of the multiple ports to provide failover protection. Bonding two ports on the Secure

Access Service automatically shifts traffic to the secondary port when the primary port

fails.

The SA6500 appliance bonds ports as follows:

•

Internal port = Port 0+Port 1

•

External port = Port 2+Port 3

The Secure Access Service indicates in a message on the System > Network > Overview

page of the administrator admin console whether or not the failover functionality is

enabled.

Bonding ports cannot span separate networks (multi-homed).

•

Management port—The SA6500’s management port:

•

Enables seamless integration into a dedicated Management Network.

•

Provides continuously available management access to the Secure Access Service.

•

Enables you to perform management activities without impacting user traffic.

•

Allows you to separate administrative access from user access between the Secure

Access Service and Enterprise devices on the internal network.

You can configure the Management port information and advanced settings via the

admin console, just as you would configure the internal port.

•

SFP ports—4-port Small Form-factor Pluggable (SFP) ports are available as an optional

feature for link redundancy to internal switches.

•

Status LEDs—Three device status LEDs are located on the left-side of the front panel

to display power, hard disk access and fault status.

•

Ethernet Port LEDs—The Ethernet port LEDs show the status of each Ethernet port.

The appliance supports up to four node active/active clusters or 2 node active/passive.

SA Series 6500 Field-Replaceable Units

The SA 6500 chassis features three types of field-replaceable units (FRUs) that you can

add or replace. The FRUs are “hot-swappable,” meaning you do not have to first shut

down the SA 6500 before adding or replacing any of the FRUs. The SA4500 has a

“cold-swappable” power supply.

For safety information, refer to the Juniper Networks Products Safety Guide available on

the Juniper Networks Support site.

•

Hard disks—The SA6500 ships with one hard disk, however, you can add an optional

second hard disk to the SA6500 chassis to offer component redundancy and help

minimize the Secure Access Service down time. When a second (redundant) hard disk

is installed, it maintains an exact copy of the software image and configuration

information on the working hard disk. Therefore, if the working hard disk fails, the

redundant hard disk immediately assumes responsibility for all Secure Access Service

operations. This function is referred to as the Redundant Array of Independent Disks

(RAID) mirroring process.

NOTE: The SA6500 hard disk modules are hot-swappable. You must make

sure that the Secure Access Service finishes booting and is operating

correctly before removing, replacing, or upgrading a hard disk module. After

you insert a new hard disk module, you must wait until the RAID mirroring

process is completely finished—which takes approximately 40

minutes—before rebooting or turning off the Secure Access Service.

SA Series 4500, 6500, and FIPS Appliances

•

Power supplies—The SA6500 ships with one AC power supply installed in the back

of the chassis. You can add an optional second power supply to support redundancy

and load-sharing features. In addition, if you need to replace one of the power supplies,

you can “swap” the faulty power supply for a replacement while the optional second

power supply assumes responsibility for the entire power load, thus avoiding a situation

where you have to power off the Secure Access Service before replacing the removable

unit.

•

Cooling fans—The SA6500 ships with two cooling fans installed in the back of the

chassis. If you need to replace one of the cooling fans, you can “swap” the faulty fan

for a replacement during operation in a matter of moments. You can purchase additional

cooling fans from your vendor when you order your SA6500, or you can purchase them

in the future to replace faulty or failed cooling fans, as necessary, in the future.

• Device Status LED Behavior on page 49

• Ethernet Port LED Behavior on page 50

• Replacing the Cooling Fans on page 43

• Replacing a Hard Drive on page 44

• Replacing IOC Modules on page 44

• Replacing a Power Supply on page 46

Chapter 1: Appliances

SA Series 4500, 6500, and FIPS Appliances

CHAPTER 2

FIPS

•

SA FIPS on page 7

•

SA FIPS Execution on page 8

•

FIPS Overview on page 9

SA FIPS

FIPS, or Federal Information Processing Standards, are National Institute of Standards

and Technology regulations for handling keys and encrypting data. Juniper Networks SA

FIPS is a standard SA4000 or SA6000 NetScreen Instant Virtual Extranet equipped with

a FIPS-certified cryptographic module. The tamper-proof hardware security module

installed on an SA FIPS Series Appliance is certified to meet the FIPS 140-2 level 3 security

benchmark. The module handles private cryptographic key management and SSL

handshakes, simultaneously, ensuring FIPS compliance and off-loading CPU-intensive

public key infrastructure (PKI) tasks from the Secure Access Service to a dedicated

module.

The configuration process for SA FIPS administrators is almost exactly the same as for

the non-SA FIPS administrators, requiring only minor configuration changes during the

initialization, clustering, and certificate generation processes. In the few cases where

administration tasks are different, this guide includes the appropriate instructions for

both SA and SA FIPS administrators. For end-users, SA FIPS is exactly the same as a

standard Secure Access Service system.

SA FIPS is a hardware feature that is built into selected Secure Access Services. It is not

available on SA700 Series Appliances.

SA FIPS Execution on page 8•

• Creating Administrator Cards on page 57

• Creating a New Security World on page 17

• Recovering an Archived Security World on page 20

• SA FIPS Execution on page 8

SA FIPS Execution

When you first install a FIPS system, the Secure Access Service serial console walks you

through the process of creating a security world through the serial console. A security

world is a key management system used by SA FIPS consisting of the following elements:

•

Cryptographic module—The cryptographic module (also sometimes called the hardware

security module, or HSM) included with SA FIPS Appliance includes hardware and

firmware installed directly on the appliance. A security world may contain a single

cryptographic module (standard environment) or multiple modules (clustered

environment). However, a single Secure Access FIPS appliance is always equipped

with a single cryptographic module.

•

Security world key—A security world key is a unique Triple DES encrypted key that

protects all other application keys within a security world. As required by the Federal

Information Processing Standards, you cannot import this key into a security world—you

must directly create it from a cryptographic module. In a clustered environment, all of

the modules within the security world share the same security world key.

•

Smart cards—A smart card is a removable key device that looks like a credit card. A

smart card authenticates users, allowing them access to various data and processes

controlled by the cryptographic hardware module. During the initialization process,

you must insert one of your smart cards into the reader (built-in or external, depending

upon which device model you own). As part of the initialization process, the smart card

is transformed into an administrator card that allows the card holder access to the

security world.

•

Encrypted data—Encrypted host data in a Secure Access FIPS environment includes

keys and other data required to share information in a secure manner.

These elements interlock to create a comprehensive security world. When you start the

appliance, it confirms that the security world is valid and that the cryptographic module

is in operational mode before starting normal operations.

You can set the cryptographic module into operational mode using a hardware switch

on the outside of the module. The switch’s settings include:

•

I—Initialization mode. Use this setting when initializing the cryptographic module with

a new security world or when adding a module to an existing security world in a Secure

Access cluster. Note that once you set the switch to I and begin initialization, you must

complete the process. Otherwise, your security world is only partially initialized, making

it unusable.

•

O—Operational mode. Use this setting to place the cryptographic module into

operational mode after initialization. Note that you must set the switch to O before

the module powers up in order to alert the unit that you want to begin day-to-day

processing. Otherwise, the module prompts you through the serial console to join the

existing security world or initialize a new one.

•

M—Maintenance mode. In future releases, this setting will be used to upgrade the

firmware on the cryptographic module. (Not yet supported.)

SA Series 4500, 6500, and FIPS Appliances

SA FIPS on page 7•

• Creating Administrator Cards on page 57

• Creating a New Security World on page 17

• Recovering an Archived Security World on page 20

FIPS Overview

The Juniper Networks SA 4500 and 6500 FIPS is a standard SA4500 or SA6500

appliance equipped with a FIPS-compliant crypto card. The tamper-proof hardware

security module installed on a Secure Access FIPS system is certified to meet the FIPS

140-2 level 3 security benchmark.

The configuration process for Secure Access FIPS administrators is almost exactly the

same as for the non-FIPS Secure Access administrators, requiring only minor configuration

changes during the initialization, clustering, and certificate generation processes. In the

few cases where administration tasks are different, this guide includes the appropriate

instructions for both Secure Access and Secure Access FIPS administrators. For end-users,

Secure Access FIPS is exactly the same as a standard Secure Access system.

The FIPS-compliant crypto card is a host bus adapter card that combines IPsec and SSL

cryptographic acceleration with Hardware Security Module (HSM) features. This

combination of a dedicated HSM, advanced cryptographic security and secure key

management meet the security and performance needs for any service.

This card has two main roles: a security officer and a user role. The FIPS-compliant crypto

card replaces the need for administrator cards with the concept of a security officer who

is responsible for key and password management. The security officer credential protects

the keystore from being exported and imported onto another FIPS-compliant crypto

card.

User roles perform cryptographic operations such as accessing keying material within

the keystore as well as performing bulk encryption operations.

The security officer credentials, user credentials, and RSA private keys are stored in the

HSM encrypted keystore located on the Secure Access disk. You are prompted to provide

these credentials whenever any operation requires them. Credentials are not automatically

retrieved from the HSM keystore.

Keystores are stored on the disk and are encrypted with a master key. The master key is

stored in the cryto card firmware and can be backed up by a security officer using a restore

password. This restore password can then be used to restore the master key onto the

same or different FIPS-compliant crypto cards allowing the keystore to be shared across

a cluster, for example.

• Name and Password Restrictions on page 15

• Initializing a Keystore on page 31

• Reinitializing the Keystore on page 31

Chapter 2: FIPS

• Joining a Cluster on page 27

• Importing Device Certificates on page 35

• Changing the Security Officer Password on page 53

• Changing the Web User Password on page 54

• Resetting the HSM Card In Case Of An Error on page 61

• Upgrading the HSM Firmware on page 55

• Binary Importing and Exporting of the Keystore on page 32

SA Series 4500, 6500, and FIPS Appliances

Page is loading ...

Juniper SA6500 FIPS User guide

Juniper SA6500 FIPS User guide

Related papers

Other documents