|
|
Table Of Contents
Cisco VPN 3000 Concentrator Series Security Policy
Cisco VPN 3000 Series Concentrator
Admin (Crypto-Officer) Guidance
Non-FIPS Approved Cryptographic Algorithms
Cisco VPN 3000 Concentrator Series Security Policy
Introduction
This non-proprietary Cryptographic Module Security Policy describes how the VPN 3000 Series Concentrator meets the security requirements of FIPS 140-2, and how to operate a VPN 3000 Concentrator using IPSec encryption in secure FIPS 140-2 mode. This policy was prepared as part of the Level 2 FIPS 140-2 validation of the VPN 3000 Series Concentrator, referred to in this document as the VPN Concentrator.
Note
The VPN 3000 Series Concentrator comprises models 3005, 3015, 3030, 3060, and 3080.
This document may be copied in its entirety and without modification. All copies must include the copyright notice and statements on the last page.
FIPS 140-2 (Federal Information Processing Standards Publication 140-2—Security Requirements for Cryptographic Modules) details the U.S. Government requirements for cryptographic modules. More information about the FIPS 140-2 standard and validation program is available on the NIST website at:
http://csrc.nist.gov/cryptval/
This document contains the following sections:
"Document Organization" section
"Cisco VPN 3000 Series Concentrator" section
"Authentication Mechanisms" section
"Cryptographic Key Management" section
"Mitigation of Other Attacks" section
"Cryptographic Algorithms" section
"Security Relevant Data Items" section
"Non-FIPS Approved Cryptographic Algorithms" section
References
VPN 3000 Series Concentrator Getting Started, Release 3.6—explains how to unpack and install the VPN Concentrator and how to configure the minimal parameters.
VPN 3000 Series Concentrator Reference Volume I: Configuration, Release 3.6—explains how to start and use the VPN Concentrator Manager and how to configure your device beyond the minimal parameters you set during quick configuration.
VPN 3000 Series Concentrator Reference Volume II: Administration and Monitoring, Release 3.6—explains and defines all functions available in the Administration and Monitoring screens of the VPN Concentrator Manager.
Release Notes for Cisco VPN 3000 Series Concentrator, Release 3.6 through 3.6.7.F
Release Notes for Cisco VPN 3000 Series Concentrator, FIPS Release 3.6
You can find this documentation as well as information on the complete line of products from Cisco Systems at the website http://www.cisco.com.
The NIST Validated Modules website (http://csrc.nist.gov/cryptval/) contains contact information for answers to technical or sales-related questions for the modules.
Document Organization
The Security Policy document is one document in a complete FIPS-2 Submission Package. In addition to this document, the complete submission package contains:
•
•
•
With the exception of this Non-Proprietary Security Policy, the FIPS 140-2 Validation Documentation is proprietary to Cisco Systems and is releasable only under appropriate non-disclosure agreements. For access to these documents, contact Cisco Systems.
Cisco VPN 3000 Series Concentrator
This section presents an overview of the VPN Concentrator, its interfaces, roles and services, authentication mechanisms, cryptographic key management, design assurance, and mitigation of attacks.
Overview
Cisco VPN 3000 Series Concentrator comprises a family of hardware appliances that operate as concentrators in Virtual Private Networking (VPN) environments. They combine the best features of a software concentrator, including scalability and easy deployment, with the stability and independence of a hardware platform. The VPN Concentrator connects a remote user to a corporate network. The user connects to a local Internet service provider (ISP), then to the VPN device Internet IP address. The VPN Concentrator encrypts the data and encapsulates it into a routable IPSec packet, creating a secure tunnel between the remote user and the corporate network. The corporate server authenticates the user, decrypts and authenticates the IPSec packet, and translates the source address in the packets to an address recognized on the corporate network. This address is used for all traffic sent from the corporate network to the remote user for the duration of the connection. The VPN Concentrator distinguishes between tunneled and non-tunneled traffic and, depending on your server configuration, allows simultaneous access to the corporate network and to Internet resources. It supports RADIUS and TACACS+ for remote authentication.
Module Interfaces
The VPN Concentrator is a multi-chip stand-alone module and the cryptographic boundary of the module is defined by its metal enclosure. The module provides a number of physical and logical interfaces to the device.
The physical interfaces that the module provides are mapped to four FIPS 140-2 defined logical interfaces: data input, data output, control input, and status output. The logical interfaces and their module mapping are described in Table 1.
Roles and Services
The VPN Concentrator supports role-based authentication. To perform tasks on the VPN Concentrator, users must enter a password and authenticate to the system. Users can access the VPN Concentrator in one of the following ways:
•
•
•
•
•
•
In a FIPS approved mode of operation, only the interfaces through the serial port, HTTPS (using TLS) and SSH are enabled.
There are two main roles in the VPN Concentrator (as required by FIPS 140-2) that operators may assume: a crypto officer role and a user role. The VPN Concentrator also supports an administrator role and up to four additional administrative roles with the restricted privileges.
Table 2 shows how the VPN Concentrator roles map to the crypto officer and user roles.
:
Table 2 FIPS Mapping of Roles
Admin user
Crypto-Officer
Four administrative accounts (config, isp, mis, user)
Crypto-Officer
User
User
Admin Role
The admin user is responsible for configuring the VPN Concentrator properly. The admin can access all the services available via the management interfaces. This section lists these services.
The non-crypto services include show status commands and user establishment and authentication initialization. The various non-crypto services available to the administrator role include the following:
•
•
•
•
•
•
•
•
The crypto services include key generation, encryption/decryption, and the power-up self-tests. Some of the specific crypto services available to the admin role include the following:
•
•
•
•
•
•
•
•
•
Admin users may not configure static session keys for encrypted tunnels, nor are they allowed to enter static keys for certificate enrollment. These keys are all generated dynamically via the appropriate mechanism (IKE, RSA, DSA).
For information on the specific administrator commands, see the section "Administration | Access Rights | Access Settings" in the VPN 3000 Series Concentrator Reference Volume II: Administration and Monitoring user guide.
Other Administrator Roles
For FIPS, the administrator role is also the crypto officer delegated for specific tasks such as taking backups or managing users. The VPN Concentrator implements four roles called config, isp, mis, and user. These roles have limited rights on the system and are configured by the Admin user. These roles are disabled by default and the admin user has to enable them if needed. These roles are accessed through an Ethernet port using the Web-based administration tool or by connecting through the console port. All administrator roles are entered by supplying the correct username/password combination and passing the appropriate IP address checks. All administrators are responsible for ensuring that the VPN Concentrators are configured properly to meet all FIPS 140-2 requirements.
At some permission levels, an administrator can access only the configuration and monitoring functions that the administrator with the highest level of permissions selects. It is possible to give other administrators the highest level privileges. For more detailed information on the subset descriptions, see the section "Administration | Access Rights | Access Settings" in the VPN 3000 Series Concentrator Reference Volume II: Administration and Monitoring user guide.
User Role
Users are the people or entities that wish to send data or traffic through the VPN Concentrator. Users comprise devices, concentrators, and anyone passing data through the VPN Concentrators. All user roles are entered by supplying the correct authentication information. Users are authenticated to the VPN Concentrators based on the authentication protocol established by the administrator (for example, security association ID or IP address and preshared secret key combination).
Authentication Mechanisms
The VPN Concentrator supports the username-password combination or digital certificates for authenticating IPSec users. An operator must log on to the VPN Concentrator to connect to the module through one of the management interfaces (Serial Port, SSH, HTTPS over TLS in FIPS mode) and provide a username and password.
Physical Security
The VPN Concentrator is a multi-chip stand-alone cryptographic module.
Cryptographic Key Management
The module uses the following FIPS-approved algorithms.
•
DES (FIPS 46-3)
CBC
56 bits
Triple DES (FIPS 46-3)
CBC
168 bits
AES (FIPS 197)
CBC
128, 196, 256 bits
•
–
–
•
–
–
•
–
–
It also uses the SSL/TLS protocol, SSH protocol and HTTPS. It uses the PKCS 1.0 algorithm for encrypting and signing using the RSA public-key crypto system.
Cryptographic Keys Used by the VPN Concentrator
The VPN concentrator uses a variety of keys during its operation. Table 4 lists the keys used by various services and protocols.
Only the crypto officer (administrator) can log on to the box directly through the console or the web interface. Normal users of the module access it only through the services. So the CSPs are accessed directly only by the crypto officer. All other users access them through protocol.
Note
The VPN Concentrator uses PKCS10 format for certificate requests. It also supports the Simple Certificate Enrollment Protocol (SCEP).
Key Generation
The VPN Concentrator uses a FIPS-approved random number generator. The VPN Concentrator generates all keys using the pseudo random number generator defined in the ANSI X9.31 standard.
Key Entry and Output
All the keys are entered through the administrative interface. Keys are never output from the VPN module.
Key Storage
All cryptographic keys are stored in encrypted form using Key Encryption Keys (KEKs). The only keys stored in plain-text form are the KEKs and IPSec pre-shared keys. KEKs are accessible only to the crypto officer. Also a user thread cannot access shared keys of other users.The RAS/DSA keys are stored encrypted in the flash using a PKCS#5-based pass-phrase.
Key destruction
As required by FIPS 140-2, all keys can be destroyed and the VPN zeroizes all keys prior to their destruction. Also performing a hardware or software reboot zeroizes all the ephemeral session keys.
Self-Tests
The VPN Concentrator provides the following power-up self-tests automatically each time it starts:
•
•
•
•
•
•
•
•
All power-up self-tests must be passed before allowing any operator to perform any cryptographic services. The power-up self-tests are performed after the cryptographic systems are initialized, but prior to the initialization of the LANs. This prevents the module from passing any data during a power-up self-test failure. In the unlikely event a power-up self-test fails, an event is displayed indicating the error and then the module logs the error. In this state, the module does not a perform any operations. The only way the operator can try to clear the error is to check the logs and cycle the power.
In addition, the VPN Concentrator also provides the following conditional self-tests:
•
•
•
In the unlikely event a conditional self-test fails, an event is displayed indicating the error and then the VPN Concentrator logs the error. In this state, the module does not a perform any operations. The only way the operator can try to clear the error is to check the logs and cycle the power.
The module does not allow a bypass mode of operation.
Design Assurance
Cisco Systems uses the Perforce Configuration Management System. Perforce is used in software and document version control, code sharing and build management.
The configuration management system is used for Software Lifecycle Modeling. Software life-cycle modeling is the business of tracking source code as it goes through various stages throughout its life, from development, to testing, release, reuse, and retirement. Cisco Systems also uses Perforce Configuration Management to effectively perform the following processes:
•
•
•
•
•
Cisco Systems follows established software engineering principles to design, develop, track and document software and hardware modules.
Mitigation of Other Attacks
The VPN Concentrator does not claim to mitigate any attacks in a FIPS approved mode of operation.
Secure Operation
The Cisco VPN Concentrator meets Level 2 requirements for FIPS 140-2. The sections below describe how to place and keep the module in FIPS-approved mode of operation.
Admin (Crypto-Officer) Guidance
The following are instructions to the admin (crypto officer) to run the module in a FIPS approved mode of operation.
Initial Setup
The following list is a summary of the security rules that the administrator must configure and enforce on the VPN Concentrators:
•
•
•
•
•
•
•
Cryptographic Algorithms
VPN Concentrators support many different cryptographic algorithms. However, to properly use VPN Concentrators in FIPS mode, only the FIPS-approved algorithms may be used. The following cryptographic algorithms are to be used for encrypting traffic, hashing, or signing/verifying digital signatures:
•
Note
•
•
•
•
•
Administrators must configure VPN Concentrators to use only the cryptographic algorithms listed above for all services that they provide.
Security Relevant Data Items
VPN Concentrators store many security relevant data items, such as authentication keys (Pre-shared keys, DSA or RSA private keys, etc.) and traffic encryption keys. All security data items are stored and protected within the VPN Concentrator tamper evident enclosure (see section "Tamper Evidence" for details on applying tamper evident labels). In addition, most security data items are stored encrypted on VPN Concentrators.
Security Protocols
VPN Concentrators, by design, support many Internet security tunneling protocols for protecting data transfer. However, to ensure that the device operates in FIPS mode, the administrator must ensure that the VPN Concentrator is configured such that only the IPSec protocol is used to protect data transmission. All other tunneling protocols supported by a VPN Concentrator may not be used if compliance with the FIPS 140-2 standard is required.
Services
To operate in FIPS crypto officer mode, you must configure the VPN Concentrator as follows:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
User Guidance
The user has to choose passwords responsibly and should safeguard them properly without disclosing them.
Tamper Evidence
The VPN Concentrator protects all critical security parameters through the use of tamper evident labels. The administrator is responsible for properly placing all tamper evident labels. The security labels recommended for FIPS 140-2 compliance are provided in the FIPS Kit (CVPN3000FIPS/KIT), which you can order for any validated model. These security labels are very fragile and cannot be removed without clear signs of damage to the labels.
VPN Concentrator Model 3005
VPN Concentrator Model 3005 has a smaller and more compact encasing (1U) than that of the VPN Concentrator models 3015-3080. The main encasing of the VPN Concentrator Model 3005 may be removed like the encasing of a personal computer. The VPN Concentrator's encasing is attached with four screws at the rear of the device. In addition, the VPN Concentrator also has a removable front panel.
Both the main encasing and front panel of the VPN Concentrator must be protected through the use of tamper evident labels. Apply the serialized tamper-evidence labels as follows:
Step 1
Step 2
Step 3
Figure 1 Applying Tamper-evident Labels on VPN Concentrator 3005
Step 4
Figure 2 Applying Labels on Sides of VPN Concentrator 3005
Step 5
Step 6
VPN Concentrator Models 3015-3080
The encasing of the VPN Concentrator Models 3015-3080 is very similar to that of the VPN Concentrator Model 3005. The 3015-3080 models have a larger encasing (2U) and use Scalable Encryption Processing modules (SEPs). The main encasing of the VPN Concentrator models 3015-3080 may be removed like the encasing of a personal computer. The VPN Concentrator encasing is attached with four screws at the rear of the device. In addition, the VPN Concentrator also has a removable front panel.
The main encasing, front panel, and side panel of the VPN Concentrator must be protected through the use of tamper evident labels.
In addition, VPN Concentrator Models 3015-3080 employ SEPs to accelerate IPSec cryptographic operations. The SEPs are located at the back panel of the VPN Concentrators. The SEP devices are attached to the VPN Concentrator by two screws. Security labels must be applied across the SEPs to ensure that these devices are not tampered with. Apply tamper evident labels according to the instructions below.
Step 1
Step 2
Step 3
Figure 3 Applying Tamper-evident Labels on VPN Concentrator Models 3015—3080
.
Step 4
Figure 4 Applying Labels over SEP Modules
Step 5
Step 6
Non-FIPS Approved Cryptographic Algorithms
The following cryptographic algorithms are not FIPS-compliant algorithms.
Symmetric Key Algorithms
•
•
•
Hashing/Authentication Algorithms
•
•
Public Key Algorithms
•
•
Acronyms
Cisco VPN 3000 Concentrator Series Security Policy
Copyright © 2004, Cisco Systems, Inc.
All rights reserved.
Note
Posted: Fri Apr 30 10:38:58 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
