Secure Computing, Sidewinder, Type Enforcement, and Strikeback are either registered trademarks or trademarks of
Secure Computing Corporation. All other trademarks, tradenames, service marks, service names, product names, and
images mentioned and/or used herein belong to their respective owners.
Secure Computing Corporation Software Licens e Agreement
CAREFULLY READ THE FOLLOWING TERMS AND CON DITIONS BEFORE LOADING THE SOFTWARE. BY LOADING
THE SOFTWARE, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, UNDERSTAND IT, AND AGREE
TO BE BOUND BY ITS TERMS AND CONDITIONS.
Secure Computing Corporation ("Secure Computing") provides its software and licenses its use either directly or through
authorized dealers. You assume responsibility for the selection of the programs to achieve your intended results, and for
the installation (unless installation is purchased from Secure Computing or an authorized dealer), use, and results
obtained from the programs.
1. Grant of License
Secure Computing grants to you, and you accept, a non-exclusive, and non-transferable license (without right to sublicense) to use the Software Products as defined herein on a single machine.
2. Software Products
"Software Products" mean (i) the machine-readable object-code versions of the Software of Secure Computing
contained in the media (the "Software"), (ii) the published user manuals and documentation that are made available for
the Software (the "Documentation"), and (iii) any updates or revisions of the Software or Documentation that you may
receive (the "Update"). Under no circumstances will you receive any source code of the Software. Software Products
provided for use as "backup" in the event of failure of a primary unit may be used only to replace the primary unit after
a failure in fact occurs. They may not be used to provide any capability in addition to the functioning primary system
that they b a c k u p .
3. Use
You may not transfer any Software Products to any third party. You may not copy, translate, modify, sub-license, adapt,
decompile, disassemble, or reverse engineer any Software Product in whole or in part except to make one copy of the
Software solely for back-up or archival purposes.
4. Limited Warranty and Remedies
Secure Computing warrants that the di sk(s) or tape(s) on which its Software is recorded is/are free from defects in
material and workmanship under normal use and service for a period of ninety (90) days from the date of shipment to
you.
Secure Computing does not warrant that the functions contained in the Software will meet your requirements or that
operation of the program will be uninterrupted or error-free. The Software is furnished "AS IS" and without warranty as
to the performanc e or resu lts Lice nsee may obtai n by usin g the So ftwar e. The ent ire ri sk as to the resu lts and
performance of the Software is assumed by Licensee. If Licensee does not receive media which is free from defects in
materials and workmanship during the 90-day warranty period, Licensee will receive a refund for the amount Licensee
paid for the Software Product returned.
5. Limitation of Warranty and Remedies
THE WARRANTIES STATED HEREIN ARE IN LIEU OF ALL OTHER WA RRANTIES, EXPRESS OR IMPLIED, INCLUDING
ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES AND
COUNTRIES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT
APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY HAVE OTHER RIGHTS WHICH
VA RY BY STATE OR COUNT RY.
i
Page 4
SECURE COMPUTING’S AND ITS LICENSORS ENTIRE LIABILITY UNDER, FOR BREACH OF, OR ARISING OUT OF
THIS AGREEMENT, IS LIMITED TO A REFUND OF THE PURCHASE PRICE OF THE PRODUCT OR SERVICE THAT
GAVE RISE TO THE CLAIM. IN NO EVENT SHALL SECURE COMPUTING OR ITS LICENSORS BE LIABLE FOR YOUR
COST OF PROCURING SUBSTITUTE GOODS. IN NO EVENT WILL SECURE COMPUTING OR ITS LICENSORS BE
LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL, EXEMPLARY, OR OTHER DAMAGES
WHETHER OR NOT SECURE COMPUTING HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
6. Term and Termination
This license is effective until terminated. If you are using this license with a limited term, it shall expire at the end of
the license term. You may terminate it at any time by destroying the Software Product, including all computer programs
and documentation, and erasing any copies residing on computer equipment. This Agreement also will automatically
terminate if you do not comply with any terms or conditions of this Agreement. Upon such termination, you agree to
destroy the Software Product and erase all copies residing on computer equipment.
7. Ownership
All intellectual property rights including trademarks, service marks, patents, copyrights, trade secrets, and other
proprietary rights in or related to the Software Products are, and will remain the property of Secure Computing or its
licensors, whether or not specifically recognized or protected under local law.
8. Export Restrictions
You agree to comply with all applicable United States export control laws and regulations, including without limitation,
the laws and regulations administered by the United States Department of Commerce and the United States Department
of State.
9. U.S. Government Rights
Software Products furnished to the U.S. Government are provided on these commercial terms and conditions as set
forth in DFARS 227.7202-1(a).
10. General
Any waiver of or modification to the terms of this Agreement will not be effective unless executed in writing and
signed by Secure Computing. If any provision of this Agreement is held to be unenforceable, in whole or in part, such
holding shall not affect the validity of the other provisions of this Agreement. In the event of any inconsistency
between this Agreement and any other related agreements between you and Secure Computing, the terms of this
Agreement shall prevail.
Technical Support Information
Secure Computing works closely with our Channel Partners to offer worldwide Technical Support services. If you
purchased this product through a Secure Computing Channel Partner, please contact your reseller directly for support
needs.
To contact Secure Computing directly or inquire about obtaining a support contract, refer to our “Contact Secure" Web
page for the latest contact informatio n at www.securecomputing.com. Or if you prefer, send us an email at
support@securecomputing.com.
Comments?
If you have comments or suggestions you would like to make regarding this document, please send an email to
techpubs@securecomputing.com.
Printing History
DatePart numberSoftware Release
March 200186-0935037-ASoft-PK 5.1.3 Build 4 and Sidewinder 5.1.0.02
This guide provides the information needed to set up connections
between remote systems running SafeNet/Soft-PK™ VPN client
software and systems on a network protected by Secure Computing’s
Sidewinder firewall. SafeNet/Soft-PK is a Windows-compatible
program that se cu res data communications sent from a desk top or
laptop computer across either a public network or an existing
corporate dial-up line.
Note: The SafeNet/Soft-PK product is referred to as simply "Soft-PK" throughout the
remainder of this document.
IMPORTANT: This guide describes administration of VPNs between Soft-PK Version 5.1.3
Build 4 and Sidewinder Version 5.1.0.02. If you are working with a later version of either
product, check our Web page at www.securecomputing.com for the latest
documentation (select Downloads & Activations -> Product Documentation).
This guide is w r i tten for the person as signed to administ er
Sidewinder- bas ed VPN connections involving a Soft-PK VPN client.
Setting up VPN connec tion s invo lve s pro cedures don e on Sidewi nde r
and procedur es done using Sof t-PK to pre-configure the VPN client
security policy for each remote user (road w a rri or, telecommuter,
etc.).
P
As a network administrator, you should read and understand all the
procedure s in this document. You will then be able to prov ide all
remote users with the information, files, and software they need to set
up Soft-PK software to commu nicate with your trusted network(s).
This guide assumes you are familiar with networks and network
terminology. Because Soft-PK will use a security association with a
Sidewinder firewall , you should be familiar with Sidewinder
administration. Kno w led ge of the Internet and of Windows operating
systems are also key requirements.
Preface: Abo u t th i s Gui dev
Page 8
How this guide is organized
P
How this guide is
organized
This guide contai ns the f ollowing chapters.
Chapter Titl eDescription
Chapter 1:
Getting Started
Chapter 2:
Planning your VPN
Configuration
Chapter 3:
Configuring Sidewinder
for Soft-PK Clients
Chapter 4:
Installing and Working
with Soft-PK
Presents an overview of the Soft-PK and the
Sidewinder Virtual Priv ate Ne twork (VPN)
environment and describes the requirements. It
includes a checklist to guide you through the
basic steps to setup and deploy a VPN.
Provides information to help you understand key
concepts and options that are involved in a VPN
connection.
Provides a summary of Sidewinder procedures
associated with setting up and configuring SoftPK connections in your network.
Note: Perform these procedures before you
configure your Soft-PK clients.
Includes Soft-PK installation notes and describes
the basic Soft-PK procedures for managin g
certificates and creating a customized Soft-PK
security policy for your remote clients.
Chapter 5:
Deploying Soft-PK to Your
End Users
Appendix A:
Troubleshooting
Finding informationThis guide is in Acrobat (softcopy) format only and does not contain
an index. However, you can use Acrobat’s
Summarizes the steps for preparing and
deploying the Soft-PK software, digital certificate
files, and security policy to your end users. It is
based on a worksheet (in MS Word format) that
you edit and send to each remote end user.
Provides a summary of troubleshooting
techniques available for resolving Soft-PK and
Sidewinder VPN connection problems.
Find feature to search for
every instance of any word or phrase that you want.
viPreface: About this Gui d e
Page 9
Where to find additional information
Viewing and printing this
document online
Where to find
When you view this document online in PDF format, you may find
that the screen images are blurry. If yo u n eed to see the image more
clearly, you can either enlarge it (which may not eliminate the
blurriness) or you can print it. (The images are very clear when
printed out.)
For the best results, print this PDF document using a PostScript printer
driver.
If your printer understands PostScript but does not have a
PostScript driver in st alled, you need to install a PostScript driver.
You can download one for your printer from
www.adobe.com.
If your printer is no t a PostScript printer and th is document does
not print as expecte d, try one of the follo wing:
— If your p rint er h as the opti on,
and then try printing.
— Print specific page(s) at a time rather than sending the entire
document to the printer.
Refer to the following for related information.
Print as Image, enable this option
additional
information
About Soft-PK
For additional information about configuring and troubleshooting
Soft-PK software, refer to the online help that is integrated into the
program’s user interface. Soft-PK online help provides detailed
step-by-step procedures for individual VPN client tasks.
About Sidew inder
For more information about setting up VPN connections on
Sidewinder, refer to Chapter 11 in the Sidewinder Administration
Guide. In addition, be sure to review documentation asso ciated
with patch releases.
About digital certificates
For information on digita l certificate s and Public Key In frastructure
(PKI) technology, see:
— Understanding Public-Key Infrastructure, by Carlisle Adams
and Steve Lloyd (1999)
— Internet X.509 Public Key Infrastructure, Certificate and CRL
Profile, RFC 2459, R. Housley, W. Ford, W. Polk, D. Solo
(January 1999)
Preface: Abo u t th i s Gui devii
Page 10
Where to find additional information
To contact Secure Computing directly or inquire about obtaining a
support contract, refer to our Web site at
and select “Contact Us." Or if you prefer, send us email at
support@securecomputing.com (be sure to include yo ur customer ID in
the email).
www.securecomputing.com,
viiiPreface: About this Guide
Page 11
1
C HAPTER 1
Getting Started
About this chapterThis chapter provides an overview of the Soft-PK™ and Sidewinder
Virtual Private Network (VPN) environment and describes the
requirements. It includes a checklist to guide you through the basic
steps to setup and deplo y a VP N.
This chapter addresses the following topics:
"About Soft-PK & Sidewinder VPNs" on page 1-2
"Requirement s" on page 1-3
"Roadmap to deploying your VPN s" on page 1-5
1
Getting Started1-1
Page 12
About Soft-PK & Sidewinder VPNs
1
About Soft-PK &
Sidewinder VPNs
Figure 1-1.
Sidewinder VPN
connection providing
secure data transmission
between a remote
system running Soft-PK
and your internal
network(s)
Soft-PK is security software for remote PC users. It is designed to
provide data pri vac y between remote users and a corporate network.
Industry-st andard encr yption and user veri fication rou tines pr otect th e
data sent over the connection. Soft-PK conforms to Internet
Engineering Task Force (IETF) stand a rd s for TCP/IP and IP Security
(IPSec) protocols.
Soft-PK works with the Secure Computing Sidewinder firewall to
establish secure VPNs over public and private networks. Information
passed across a VPN is encrypted, ensuring privacy and
confidentiality.
Protected Network
Note: In a VPN connection, keep in mind that the definition of "remote" depends on
perspective. From the Sidewinder’s point of view, the remote end is a system connecting
from the Internet. From the Soft-PK system’s point of view, the remote end is the Sidewinder
(VPN gateway) and the protected net work.
Sidewinder
VPN
Internet
= VPN tunnel
= Data
Soft-PK
Internet
1-2Getting Started
Using Soft-PK, a mobile employee or telecommuter can establish
authenticated and encrypted access with networks protected by
Secure Computing’s fully IKE (Internet Key Exchange) co mp li ant
Sidewinder firewall. Remote users can access secure corporate
resources using either public networks or corporate dial-up lines.
Page 13
Requirements
RequirementsTo configure VPN communication between Sidewinder and Soft-PK
clients, your Sidewinder must be configured with the proper VPN
parameter settings and access rules. In addition, depending on your
VPN connection set up, you may also need to define the proper
digital certificates.
To run the Soft-PK VPN client, each remote system must meet
minimum hardware and sof tware requirements. In addition, the
system must be able to make a connection with the Internet through
any of a number of means (for exampl e, a dial-up n etworkin g facilit y,
an Ethernet LAN interface, DSL, cable modem, etc.).
Before starting your VPN setup, ensure that your environment meets
the requirements listed in this section.
Sidewinder and other network requirements
The network over which Soft-PK and Sidewinder will be used must
meet the basic requirements listed in Ta ble 1-1.
Table 1-1. Network requirements for using Soft-PK with Sidewinder
CategoryRequirement
Network
Sidewinder
A network infrastructure with at least one installed and
operational Sidewinder.
Note: You can protect more than one LAN with a single
Sidewinder.
Sidewinder Version 5.1 or later
a
VPN feature license
Remote client
Internet
connection
If using digital
certificate
authentication
Connection to the Internet (via a dial-up line, DSL, cable
modem, etc.)
Digital certificates based on Sidew in de r self -signed
certificates,
or
Digital certificates from a public CA or y our own CA
server. (Registration over the network using SCEP is
recommended.)
a. This document is based on Sidewinder running Version 5.1.0.02.
Getting Started1-3
Page 14
Requirements
Soft-PK requirements
Each system on wh ich Soft-PK will be instal l ed must meet the
requirements listed in Table 1-2
IMPORTANT: A remote system must only run one VPN client. If a VPN client program
such as SecureClient was previously installed on the remote s ystem, ensure it is properly
uninstalled. See Chapter 4, "Installing and Working with Soft-PK" for details.
Table 1-2. System requirem en ts f o r running Soft-PK
CategoryRequirement
.
Hardware
Software
An IBM PC or compatible computer (portable or desktop)
with at least a 75 Mhz Pentium microprocessor (or
equivalent).
A non-encrypting modem (for use with dial-up
networking) or an Ethernet interface.
At least 10 MB of free hard disk space.
The reco mmended system RA M size:
Dial-up Networking component of Microsoft Windows
and/or Ethernet LAN interface.
If the remo te system uses a mod em, the end user mus t
have dial-up account with an Internet Service provider
(ISP) or a private corporate dial-up account.
TIP: Instruct Soft-PK users to follow the instructions
provided by Microsoft to install Dial-Up Networking
on their Windows machine. Also, create a dial-up
networking profile for the ISP used to gain access to the
Internet.
1-4Getting Started
Microsoft Internet Explorer 4.0 or later (for using help)
Page 15
Roadmap to deploying your VPNs
Roadmap to
deploying your
VPNs
Because Secure Computing produ c ts provide network se cu rity, we
recommend that, as the network administrator, you carefully oversee
the installation and configuration of the Soft-PK client(s). Setting up
VPN connectio ns u s i ng Soft-PK and Sidewinder involves performing
procedures on each remote system running Soft-PK AND on your
Sidewinder.
If done properl y, administ rators c an do most o f the VPN c onfiguratio n
for both Soft-PK and Sidewin der, with little required of the end us ers.
For example, you can set up the digital certificates and create a
security profile that you include with Soft-PK’s installation files. Users
then simply need to install Soft-PK and import a few files.
TIP: A separate Soft-PK User’s Guide is NOT provided for end users of Soft-PK. As an
administrator, you should use the worksheet provided on the SafeNet/Soft-PK CD-ROM (in
MS Word format) as the basis for providing the remote Soft-PK users with the appropriate
installation and setup instructions. This way, Soft-PK users are required to follow only the
instructions that have been customized for your firewall configuration. (Refer to Chapter 5,
"Deploying Soft-PK to Your End Users" for details about the worksheet.)
Figure 1-2 pro vides a graphical ov erview of the Sof t-PK and
Sidewinder VPN deployment process. Each of the tasks depicted in
Figure 1-2 are a lso reflected in the checklist st a rting on page 1-7.
Getting Started1-5
Page 16
Roadmap to deploying your VPNs
Admin tasks
performed on
Sidewinder system
Admin tasks
performed using
Soft-PK prior to
deploying to end
users
Figure 1-2. VPN
deployment
overview
1 — Satisfy Sidewinder, network, & system requirements
4a3— Convert key file/
certificate pair to pkcs12
format
If using CA-assigned
certificates:
4b1 — Request/export
the CA root certificate
4b2— Request a firewall
certificate
4b3— Determine the
identifying information
(DN) your clients use
4b4— Define remote
certificate identities
within Sidewinder
5 — Configure the VPN connections on the Sidewinder
6 — Configure the certificates and security policy(ies) for your
remote users
If using pre-shared
keys (passwords):
4c1 — Define remote
identities within
Sidewinder
Important: Be sure
specify Extended
Authentication when
configuring your VPN
connection in Step 5
7— Prepare and deploy your Soft-PK installation package to
remote users
8— Trouble shoot any connection problems
1-6Getting Started
Page 17
Roadmap to deploying your VPNs
Soft-PK deployment
checklist
The following checklist identifies each major step involved in the
setup and deployment of your Soft-PK software (as shown in Figure
1-2). You can use the checklist as a reference point and mark off each
item as you complete it to ens ur e a succ es sful VPN rollout.
TIP: Each step provides an overview of the task and points you to specific documentation
for more detailed inform ation.
1 — Satisfy Sidewinder, network, & system requirements
Sidewinder/network: Verify that your Sidewinder is at Version 5.1.0.02 or later,
❒
licensed for VPN, and that your network is fully operational.
End-user systems: Verify that each system on which Soft-PK will be installed meets
❒
the requirements as describe d on page 1-4 .
2 — Plan your VPN configuration
Review Chapter 2 to become familiar with key concepts and options that are
❒
available when setting up VPNs.
Review Chapter 11 in the Sidewinder Administration Guide for additional background
❒
on VPN configuration.
Review the readme.txt fi le located on the So ft-PK CD for addit i onal informat io n fr o m
Note: For details, see"Enabling the VPN servers" on page 3-2 and "Configuring ACL & proxies
entries for VPN connections" on page 3-3.
CMD server: The Certificate Management Daemon (CMD) server must be enabled
❒
before you can con figure the certificate ser v er.
EGD server: The Entropy Generating Daemon (EGD) server is used by ISAKMP. This
❒
server must be enabled before you can create VPN associations.
ISAKMP server: The ISAKMP server must be enabled and set to listen on the
❒
appropriate burb (typically, t h is w ill be the Internet burb).
More...
Getting Started1-7
Page 18
Roadmap to deploying your VPNs
❒
❒
❒
4 — Create/Request the digital certificates
If using Sidewinder self-signed certificates:
❒
❒
ISAKMP ACL entry: At a minimum, you must define and enable an ACL entry that
allows ISAKMP traffic from the Internet to the Internet burb on Sidewinder (external
IP address of Sidewinder).
Other ACL entries: Depending on where you terminate your VPN connections on
Sidewinder (e.g., in a virtual burb), you may need to cr e a te ACL entries to allow traffic
between burbs.
Proxies: Depending on where you terminate your VPN connections on Sidewinder
(e.g., in a virtual burb), you may need to enable proxies to allow traffic between burbs.
Use Cobra to create and export a firewall certificate. See "Creating & exporting a
firewall certificate" on page 3-4 for details.
Use Cobra to create and export remote certificates for each end user. See "Creating &
exporting remote ce rtificate(s)" on page 3-6 for details.
Use a command-line utility on Sidewinder to convert the key/file certificate pair to
❒
pkcs12 format. See "Con ve r t ing the certificate file/private key file pair t o pkc s 12
format" on page 3-8 for detai ls.
If using a CA -assigned certificates:
Use Cobra to define a CA and obtain the CA root certificate and export it for sending
❒
to client(s). See "Defining a CA to use and obtaining the CA root cert" on page 3-9 for
details.
Use Cobra to request a certificate for the firewall from the CA. See "Requesting a
❒
certificate for the firewall" on page 3-10 for details.
Determine t he identifying in fo r mation (e.g., Dis t i n g u is h ed Name settings ) your
❒
clients will use i n their person al ce rtifi cate s. See " De te rmini ng iden tify ing in for matio n
for client certific ates" on page 3-12.
Use Cobra to specify the client certific ate identity information to within Sidewinder.
❒
See "Defining remote client identities in Sidewinder" on page 3-13 for details.
If using pre-shared keys (passwords):
Use Cobra to specify the client identity information to within Sidewinder. See
❒
"Managing pre-shared keys (passwords)" on page 3-14 for deta ils.
1-8Getting Started
More...
Page 19
Roadmap to deploying your VPNs
TIP: Use the
UserWorksheet .doc
file on the Soft-PK CD
as a starting point to define
the information each end
user will need to install an d
quickly set up Soft-PK for
your network.
5 —Configure the VPN connections on the Sidewinder
Use Cobra to define the VPN security association configuration. See "Configuring the
❒
VPN on the Sidewinder" on page 3-15 for details.
Enable Extended Authentication.
❒
6 — Configure the cer tificates and security policy(ies) for your remote
users
Install your copy of Soft-PK. See "Soft-PK installation notes" on page 4-2 for details.
❒
Use Soft-PK to set up the certificates needed by each end users. See
❒
Use Soft-PK to create and save security policies that are customized for your end
❒
users. See "Configuring a security policy on the Soft-PK" on page 4-13 for details.
7 — Prepare and deploy your Soft-PK installation package to remote users
Prepare the files you will distribute to your end users. For details, see "Overview" on
❒
page 5-2.
Create Soft-PK installation and configuration instructions for your end users. For
❒
details, see "Customizing the user worksheet" on page 5-4.
— If necessary, define configuration steps for the Windows Dial-Up Networking
feature on each machine on which you are installing and using Soft-PK. For
details, see "Specifying di a l-up network ins tructions" on page 5-4.
— Specify the Soft-PK installatio n instructions . For detai ls, see "Sp ecifying install ation
instructions" on page 5-4.
— Specify the instructions for importing/requesting/setting up client cer tificates.
For details, see "Specifying certificate import/requ est in st r uct ion s " on page 5-5.
— Specify the instructions for establishing a security association. For details, see
"Specifying security policy instructions" on page 5-6.
Send the Soft-PK deployment software and files to your end users.
❒
More...
Getting Started1-9
Page 20
Roadmap to deploying your VPNs
8 —Troubleshoot any connection problems
❒
❒
❒
Use the Soft-PK Log Viewer. See "Soft-PK Log Viewer" on page A-1.
Use the Soft-PK Connection Monitor. See "Soft-PK Connection Monitor" on page A-2.
Use Sidewinder commands. See "Sidewinder troubleshoot ing com mands" on p age
A-4 and the Sidewinder Administration Guide for details.
1-10Getting Started
Page 21
2
C HAPTER 2
Planning Your VPN
Configuration
About this chapterThis chapter provides information to help you understand key
concepts and options that are involved in a VPN connection. It
addresses the fol l ow ing topics:
"Identifying basic VPN connection needs" on page 2-2
"Identifying authentication requirements" on page 2-3
"Determining where you will terminate your VPNs" on page 2-7
"Understandi ng Sidewinder client address pools" on pag e 2-9
2
Planning Your VPN Configuration2-1
Page 22
Identifying basic VPN connection needs
2
Identifying basic
VPN connection
needs
Figure 2-1.
Identify remote users
and the target internal
systems in a sample
diagram
Before you actually begin configuring your Sidewinder or work with
Soft-PK, ensure you have an understanding of the basic profile for
your VPN connec ti ons.
Begin by doing the following:
List the remote users that need a VPN connection
List the interna l/ tr u s ted systems to which users need access
Identify the important IP addresses
It may help to start a sketch that defines your basic requirements.
Depending on your organization and network, this could be
somewhat more complex th an the di agram shown in Figure 2-1.
Mike
(1)
abc server
172.16.17.2
Protected Network
Sidewinder
192.168.10.7
Internet
Sales
xyz server
- How many remote clients?
- Which internal networks?
- Sidewinder addresses?
(1)
Support group
(4) road warriors
Bryan
(4) road warriors
Larry
Moe
Curly
Shemp
Gary
Laz
Todd
Chuck
2-2Planning Your VPN Configuration
Page 23
Identifying authentication requirements
Identifying
authentication
requirements
Determine how you will id entify and au thenticat e the part ners in your
VPN. Sidewinder and Soft-PK both support using digital certificates
and pre-shared key VPN configurations. In addition, when you use
Sidewinder version 5.1.0.02 or later, you can set up Extended
Authentication to provide increased security to your VPN network.
The following summarizes VPN authen t i c a tion methods.
Using digital cer t ifi c at e au th e ntication
When using digital certificates (or "public key authentication"), each
system in the VPN requires a unique
corresponding public key
certificate file.
The private key file
A private key file is uniq ue to each system in the network and kept
secret by the holder (VPN client, firewall, etc.). It is used to create
digital signatures and, depending upon the algorithm, to decrypt
data encrypted with the corresponding public key.
The certificate file (with public key)
private key file anda
Certificates contain informational values such as the identity of the
public key’s owner, a copy of the public key itself (so others can
encrypt messages or verify digital signatures), an expiration date,
and the digital signature of creating entity (CA or firewall).
When using Si dewinder, the trusted source for authorizin g key/
certificate pairs can be Sidewinder itself through "self-signed"
certificates, or a publi c or private Ce rtificate Aut hority (CA) serve r (for
example; Ne tscape, Baltimo re, Entrust, etc. ) . Digital certifi ca te
implementations using Sidewinder/Soft-PK follow the X.509 standard.
IMPORTANT: You must configure the necessary certificates before you configure the VPN
connection parameters on Sidewinder or Soft-PK.
In addition, digital certificates have an "effective" date and an
"expiration date." Before certificates expire, they must be retrieved
and updated in the VPN gateway (i.e., Sidewinder firewall) to
continue using them in a VPN.
Planning Your VPN Configuration2-3
Page 24
Identifying authentication requirements
If not already done, decide if you will use self-signed certificates
generated by Sidewinder or a public/private CA server.
Table 2-1. Sidewinder self-signed cer t ific ates versus CA-based certific ates
ScenarioProfile
A closer look at self-signed
certificates
Figure 2-2. Sidewinder
self-signed certificate
summary
Using self-signed ce r t ificates
(for a small number of VPN
No CA needed
Requires one VPN association for each client
clients)
Using CA-based certific at es
(for a medium to large
number of VPN clients)
Uses a private or public CA
Single VPN association for all clients
Can make VPN deployment and management
more efficient
A VPN implement ed using Sidewi nder self -signed ce rtificates does not
require an external certificate authority and is relatively easy to
configure f or a small number of ( less than 10) clie nts. However, one
VPN associati on must be conf igured o n Sidewinde r for e ach cl ient. As
the number of configured clients grows, so does the administrative
time. Figure 2-2 shows the certificates involved in a VPN using
Sidewinder self-s igned certificates.
exports certificate files to PK12 object
Firewall certif icate imported to Soft-PK,
4
(private key remains on Sidewinder)
Client private key and certificate file
5
(PKCS12) imported into Soft-PK
2-4Planning Your VPN Configuration
Client
Cert.
2
*.pk1
*.pem
Client
Cert.
5
3
PK12 object for
import ing to
Soft-PK
Note: A self-si gned certif i c a te c re ate d
on Sidewinder remains valid for one
year beginning from the date it is
created.
Page 25
Identifying authentication requirements
A closer look at CA-based
certificates
Figure 2-3. CA-ba sed
digital certificate
summary
A VPN implemented using CA-based certificates requires access to a
private or public CA. Each end -point (c lient , firewall, etc.) in t he VPN
retains a private key file that is associated with a public certificate. In
addition, each end-point in the VPN needs the CA root certificate on
their system. Fi gure 2-3 shows the certificates involved in a VPN using
CA-based certificates.
Client
4
3
Cert.
Soft-PK
CA
Cert.
Protected Network
CA
Admin requests CA root certificate
1
Firewall
2
*.pk
Cert.
Sidewinder
CA
Cert.
1
Private CA server (could be a public CA
server not in the network)
*.pem
Internet
*.pem
2
Admin requests firewall certificate
Admin provides CA root certificate to
3
client (or instruction s to obtain it)
Admin provide s client key/certificate
4
to client (or instructions to obtain it)
Understanding pre-sh ared key authentication
A pre-shared key (referred to as shared password by Sidewinder) is
an alphanumeric string—from eight to 54 characters—that can replace
a digital certificate as the means of identifyi ng a communicating party
during a Phase 1 IKE negotiation. T his key/ pas s wor d is called "preshared" because you have to share it with another party before you
can communicate wi th them over a secure connection . Once you both
have this key/password, you would both have to enter it into your
respective IPSec-compliant devices (e.g., firewall and software client).
Using a pre-shared key/password for authentication is the easiest type
of VPN association to configur e.
IMPORTANT: You should only use this method along with Extended Authentication.
Planning Your VPN Configuration2-5
Page 26
Identifying authentication requirements
Extended authentication
In addition to the normal authentication checks inherent during the
negotiation process at the start of every VPN association, Extended
Authentication goes one step further by requiring the person
requesting the VP N connection to validate th eir identity.
Depending on the authent ica tio n meth od you s ele ct, t he per son mus t
provide a unique user name and password, a special passcode, or
one-time password before the VPN association is established. For
example, assume you configure a VPN association to use Extended
Authentication and th at you select the standard pas sw ord process as
the form of authentication. When a person attempts to establish a VPN
connection, Sidewinder will perform the standard VPN negotiations
but in addition will issue a request for the proper password. The
person initiating the VPN connection request must then enter the
proper password at their workstation before the connection will be
made.
The Extended Authentication option is most useful if you have
travelling emplo ye es that connect remotely to your network us ing
laptop computers. If a laptop computer is stolen, without Extended
Authentication it might be possible for an outsider to illegally access
your network. T his is be caus e the info rmation n eeded to esta blish th e
VPN connection (the self-signed certificate, etc.) is saved within the
VPN client software. When Extended Authentication is used, however,
the user is required to enter an additio nal piece of authentication
information that is not sav e d on the computer—either a password,
passcode, or PIN. This additional level of authentication renders the
VPN capabilities of the laptop useless when in the hands of a thief.
2-6Planning Your VPN Configuration
Page 27
Determining where you will terminate your VPNs
Determining
where you will
terminate your
VPNs
Figure 2-4. VPN tunnel
terminating on trusted
Figure 2-5. VPN tunnel
terminating on a
virtual burb
burb
You can configure a VPN security association on Si dewinder to
terminate in any burb. For exam p l e, Figure 2-4 shows a VPN security
association terminating in the tr usted burb. It allows all n etwork traffic
to flow betwee n the ho sts on the t r uste d netwo rk and the VP N cl ient .
Other than an external-to-ex t ernal ISA K MP A CL ent ry , you need no
special ACL entries or proxy control.
Internet
burb
Sidewinder
Internet
Soft-PK
VPN
= VPN tunnel
= Data
Protected Network
Trusted
burb
Figure 2-5 shows another opt ion that allows you to terminate VPN
traffic in a "virtual" burb. A virtu al burb is a burb that does not contain
a network interface card . The sole purpose of a virtual burb is to ser ve
as a logical endpoint for a VPN association.
Trusted
burb
Protected Network
Internet
burb
Proxies
Proxies
Virtual
burb
Sidewinder
Internet
Soft-PK
VPN
= VPN tunnel
= Data
Terminating a VPN association in a virtual burb accomplishes two
important goals:
Separation of VPN traffic f ro m no n-V PN tr affic
Enforce a security policy that applies strictly to y ou r VPN users
By terminating the VPN in a virtual burb you effectively isolate the
VPN traffic from non-VPN traffic. Plus, you are able to configure a
unique set of rules (via proxies and ACLs) for the virtual burb that
allow you to control pr ec isely what your VPN users can or canno t do.
Note: The VPN implementation depicted in Figure 2-5 represents a "proxied" VPN because
proxies must be used to move VPN data between burbs. The use of proxies enables you to
control the resources that a VPN client has access to on your internal network.
Planning Your VPN Configuration2-7
Page 28
Determining where you will terminate your VPNs
More about virtual burbs and VPNs
Consider a VPN association that is implemented without the use of a
virtual burb. Not only will VPN traffic mix with non-VPN traffic, but
there is no way to enfo rce a different set of rules for th e VPN traffic.
This is because proxies an d ACLs, the ag ents used t o enforce th e rules
on a Sidewinder, are applied on burb basis, not to specific traffic
within a burb.
Note: Do not terminate VPN connections in the Internet burb.
You can define up to nine ph y s ical and virtual burbs. For example, if
you have two distinct types of VPN associations and you want to
apply a different se t of rules to each type, simply create two virtual
burbs, then configure the required proxies and ACLs for each virtual
burb.
One question that might come to mind when using a virtual burb is:
"How does VPN traffic get to the virtual burb if it doesn’t have a
network card?" The answer is found in the way that a VPN security
association i s defined on the Sidew i nder. All VPN traffic origina ting
from the Internet initially arrives in the Internet burb. A VPN security
association, however, can terminate VPN traffic in any burb on the
Sidewinder. By terminating the VPN in a virtual burb, the VPN traffic
is automatically routed to that virtual burb within Sidewind er.
Defining a virtual burb
To create a virtual burb on the Sidewinder for terminating a VPN, do
the follow ing.
4.Assign DNS to listen for the virtual burb. Enter the following command:
cf dns add listen burb=burbname
where: burbname = the name you have assigned your virtual burb
5.Verify that DNS is listening on the virtual burb by typing the following
command:
cf dns query
2-8Planning Your VPN Configuration
Page 29
Understanding Sidewinder client address pools
Understanding
Sidewinder client
address pools
Figure 2-6. VPN
association
implemented using
client address pool
You may choose to implement you r VPN using Sidewinder client
address pools. Client address pools are reserved virtual IP addresses,
recognized as internal addresses of the trusted network. Addresses in
this pool are configur ed on Side wind er and as sign ed (or "p ushe d") to
a VPN client (per VPN configuration) when the VPN connection is
started. Client traffic within the protected network appears to come
from the virtual IP address pool. Only Sidewinder knows the client’s
real IP address.
Client address pool
10.1.1.1
10.1.1.2 (reserved for Client Y)
10.1.1.3
10.1.1.254
VPN
Client A
VPN
Client Y
VPN
Client Z
Internal
network
Sidewinder
Trusted
burb
Internet
burb
Proxies
Virtual
burb
N
P
V
Internet
VPN
V
P
N
Virtual IP address
mappings using this
client address pool.
VPN ClientVirtual IP Address
ANext available within the pool
Y
10.1.1.2
Next available within the pool Z
One of the reasons f o r using client address pools is t hat t hey simplify
the management of VPN clients. They allow the firewall to manage
certain configuration details on behalf of the client. This enables a
remote client to initiate a VPN connection even if the client has not
preconfigured itself for the connection.
When using client address pool, all the Soft-PK client needs to initiate
a VPN connectio n is :
Authentication information (e.g. a password or certificate)
Planning Your VPN Configuration2-9
Page 30
Understanding Sidewinder client address pools
Address of the firewall
Protected networks
The client does not need to define a virtual IP for use in the VPN
connection, nor do they need to conc ern themse lve s with DNS i ssues
on the truste d network.
In addition to simplifying the configuration process for your clients,
client address pools give you the ability to place additional controls
on VPN clients.
You ca n a ll ow or restrict access on a client address pool basis.
For example, assume you create two client address pools. Client
associations ini ti a t ed f rom pool A might be granted access to certain networks that are off limits to clients from pool B.
You can allow or restrict access on a client basis.
This is done by assigning a specific IP address within a client
address pool to a specific user. By creating a network object for
that IP address, you can then use the network object in an ACL
entry to allow or re strict the client’s access to additional services.
IMPORTANT: Client address pools are most useful when implemented in a VPN
association between Sidewinder and clients or gateways whose IP addresses are assigned
dynamically. Client address pools are not typically used in VPN associations between two
peers that contain sta t ic IP addresses.
For more detailed information on client address pools, see the
Sidewinder Administration Guide.
2-10Planning Your VPN Configuration
Page 31
3
C HAPTER 3
Configuring Sidewinder for
Soft-PK Clients
About this chapterThis chapter provid es a summary of Sidewinder procedur es associated
with setting up and configuring Soft-PK connections in your network.
IMPORTANT: Perform these pro cedures bef ore you configure your Soft-PK clients.
This chapter addresses the following topics:
"Enabling the VPN servers" on page 3-2
"Configuring ACL & proxies entries for VPN connections" on page
3-3
"Managing Sidewinder self-signed certs" on page 3-4
"Managing CA-based certificates" on page 3-9
"Managing pr e-shared keys ( pa s swords)" on page 3-14
"Configurin g th e VPN on the Sidewinder" on page 3-15
3
Configuring Sidewinder for Soft-PK Clients3-1
Page 32
Enabling the VPN servers
3
Enabling the VPN
servers
Figure 3-1. Services
Configuration -> Servers
-> Control
Before you co nfigure a VPN association o n your Sidewinde r , you must
first enable the Sidewinder’s EGD and CMD servers. In addition, you
must enable the ISAKMP server and set it to listen on the Internet
burb.
Do the follo w ing from the Sidewinder Cobra interface:
1.Enable the cmd, egd, and isakmp servers.
a. Select Services Configuration -> Servers -> Control.
Enable these servers (cmd ser ver is
enable by default)
To enable a server, select it from the Server Name lis t an d clic k
b.
Enable.
Figure 3-2. VPN
Configuration -> ISAKMP
Server
c. Click Apply.
2.Configure the ISAKMP server.
a. Select VPN Configuration -> ISAKMP Server.
In the Burbs to Listen on list column, click the burb name associated
b.
with the Internet burb.
c. In the Available Authentication Method fields, specify the method(s)
to use for Extended Authentication.
3-2Configuring Sidewinder for Soft-PK Clients
d. Click Apply.
Page 33
Configuring ACL & proxies entries for VPN connections
Configuring ACL &
proxies entries for
VPN connections
Depending on where you decide to terminate your VPN tunnel, you
must ensure that you have the appropriate ACL entries set up to allow
ISAKMP traffic and allow/deny the appropriate proxy traffic. At a
minimum, you must define and enable an ACL entry that allows
ISAKMP traffic from th e Internet to the external IP address of
Sidewinder.
1.Define (or ensure you have) an ACL entry that allows external-to-
external ISAKMP traffic . Select
Policy Configuration -> Access Control List.
Check for these attributes:
Agent = Server
Service = ISAKMP
Action = Allow
Enabled = Enable
Source burb = Internet (all source addresses, *)
Destinati o n b urb = In ternet burb (exte r na l IP of Sidewinder)
Note 1: Ensure you have defined appropriate network objects/groups. To view the
current network object configuration, select Shortcut to Network Obje cts from the
Source/Destination tab.
Note 2: For details about confi guring and managing network objects, see Chapter 4
in the Sidewinder Administration Guide.
2.[Configuration dependent] Define (or ensure you have) ACL entries that
allow access to and from any virtual burbs you may have. The virtual
burb should be specified as either the source or destination burb,
depending on the type of ACL entr y bein g defi ne d.
Note: For details about configuring and managing ACL entries, see Chapter 4 in the
Sidewinder Administration Guide.
3.[Configuration dependent] Enable the desired proxies in the
appropriate virtual burb(s). Select
Services Configuration -> Proxies.
Configuring Sidewinder for Soft-PK Clients3-3
Page 34
Managing Sidewinder self-signed certs
Managing
Sidewinder selfsigned certs
If you are using Sidewinder to generate certificates, use the following
procedure to create and exp ort self-sig ned certificates that identify the
firewall and each remote client.
TIP: Typically, a VPN configura tio n using Sidewinder self-signe d certificates is suitable if
the number of clients is small.
Note: A self-signed certificate created on Sidewinde r remains valid for one year
beginning from the date it is created.
Creating & exporting a firewall certificate
Use the following procedure on Sidewinder to create and export a
firewall self-signed certificate that identifies the firewall. The firewall
certificate file (with its em bedded public key) will reside on the
Sidewinder and must eventually be imported by each Soft-PK client
system.)
2.Select the Firewall Certificates tab. Click New.
Figure 3-3.
Sidewinder Certificate
Management: Crea te
New Firewall Certificate
window
3-4Configuring Sidewinder for Soft-PK Clients
Page 35
Managing Sidewinder self-signed certs
Specify the following Firewall Certificate settings.
3.
FieldSetting
Certificate NameSpecify a name for the firewall certificate.
Distinguished
Name
E-Mail Address,
Domain Name,
IP Address
Specify a set of data that identifies the firewall. Use the
following format:
cn=,ou=,o=,l=,st=,c=
where:
cn = common name
ou = organizational unit
o = organization
l = locality
st = state
c = country
IMPORTANT: The syntax for this fiel d is very
important. The above entries must be separated
by commas, and contain no spaces. In addition,
the order of the specified distinguished name fields
must match the desired order to be listed in the
certificate.
Optional fields to identify information (in addition to
DN).
Export th e firewall
certificate (for later transfer
to each client system)
Submit to CASelect Self Signed.
Signature TypeSelect RSA.
4.Click Add to add the certificate to the Certificates list.
5.Click Close to return to the F irewall Certificate window.
Click Export and save the firewall certificate (containing the public key)
6.
to a file. Add a
7.Click OK when done.
.pem extension (for example, "firewallcert.pem").
Once you have finished creati ng the firewall cert if icate, you will
typically copy it to an MS-f o rmatted diskette for di stribution to each
remote Soft-PK cl ient. You can do this u sing the
mcopy command. For
example:
% mcopy -t filename a:filename
Configuring Sidewinder for Soft-PK Clients3-5
Page 36
Managing Sidewinder self-signed certs
Creating & exporting remote certificate(s)
Use the follo w ing procedure on Si dewinder to cre a te a self-signed
certificate file (with its embedded public key) and a private key file
for each of your Soft-PK clie nt s. Once a pair of certificate/private key
files are created for a unique client, you must use Sidewinder’s
pkcs12_util command to combine each file pair into a PKCS12-
formatted object. Each PKCS12-formatted object must be distributed to
the respective Soft-PK client.
From the Sidewinder Cobra interface:
Note: Do this from the local Sidewinder console (not a remote Cobra interface).
Specify the following Remote Certificate settings.
3.
FieldSetting
Certificate NameSpecify a name for the remote certificate.
Distinguished
Name
E-Mail Address,
Domain Name,
IP Address
Specify a set of data that identifies the client. Use the
following format:
cn=,ou=,o=,l=,st=,c=
where:
cn = common name
ou = organizational unit
o = organization
l = locality
st = state
c = country
IMPORTANT: The syntax for this fiel d is very
important. The above entries must be separated
by commas, and contain no spaces. In addition,
the order of the specified distinguished name fields
must match the desired order to be listed in the
certificate.
Optional fields to identify information (in addition to
DN).
Submit to CASelect Self Signed.
Signature TypeSelect RSA.
Generated Privat e
Key File
Generated
Certificate File
4.Click Add to add the certificate to the Certificates list.
Click Browse and specify where you want to save the
private key associated with this certificate. You must use
a .pk1 extension (for example, "clientprivate.pk1").
IMPORTANT: The private key files must be
created as
used starting in Step 6 will not work with
objects.
Click Browse and specify where you want to save this
certificate. Use a .pem extension (for example,
"clientcert.pem").
.pk1 objects. The conversion utility
Configuring Sidewinder for Soft-PK Clients3-7
.pk8
Page 38
Managing Sidewinder self-signed certs
5.
Click Close to return to the previous window.
Converting the certi ficate
file/private key file pair to
pkcs12 format
T o start the PKCS12 utility on the Sidewinder, from the command line,
6.
enter the following command:
pkcs12_util
The utility will prompt you for the name and location of the private key
file, for the name and location of the associated certificate file, and for
the name and location in which to store the resulting PKCS12-formatted object.
The following message appears:
Please put file extensions on all file names.
Enter the name of the PKCS1 object (private key) file:
7.Type the full path name of the private key file.
The following message appears:
Enter the name of the PEM signed public key (certificate)
file:
8.Type the full path name of the associated certificate file.
The following message appears:
Enter the name of the output PKCS12 object (*.p12):
9.Type the full path name of th e object file th at will be created by the
utility. Be sure to use a
.p12 extension on the file name.
The following message appears:
pkcs12 encryption password for public key (it WILL be clear
screen text):
10. Type a password for this PKCS12 object.
You apply a password to the object because the object contains both
the public and private keys. The password will be needed when importing this object into a Soft-PK client. The password can consist of any
alpha-numeric characters.
Note: After typing the password, the utility creates the PKCS12 file in the directory
you specified in Step 9.
11. Return to Step 1 for each remo te cli e n t .
Copy the client key/
certificate object to a
diskette
3-8Configuring Sidewinder for Soft-PK Clients
Once you have finished creating the PKCS12 object(s ) , copy each
object to its ow n diskette for distribution to the appropriate Soft-PK
client. You can do this using the
% mcopy -t filename a:filename
mcopy command. For example:
Page 39
Managing CA-based certificates
Managing CAbased certificates
Figure 3-5.
Create New Certificate
Authority window
If you are using a CA to authorize certificates, use the following
procedures to de fine the CA, request the fir ew a ll and CA certificates,
and define the remote ident ities of each clie nt within Sidew in der
(needed later when setting up your VPN connections).
Defining a CA to use and obtaining the CA root cert
To request a CA certificate for Sidewinder, do the following from
Cobra.
1.Select Services Configuration -> Certificate Management and click the
Certificates Authorities tab. Click New.
2.In the New Certificate Authority window, specify the name, type, and
location of the CA.
3.Click Add, then click Close.
4.Click Get CA Cert to request the CA certificate and import it to the
firewall
5.Click Get CRL to manually retrieve a n ew Certificate Revocation L ist (CRL)
from the CA.
Configuring Sidewinder for Soft-PK Clients3-9
Page 40
Managing CA-based certificates
Figure 3-6.
Create New Firewall
Certificates window
Click Export to save the CA certificate to a file for later importation into
6.
client system(s). Each user must then use Soft-PK to import the CA
certificate you obta in ed fo r th em.
Note: You can have the user request the CA certificate from the CA using Soft-PK.
You must provide the necessary CA information/in structions to do so.
Requesting a certificate for the firewall
To request a firewa ll certificate f r om a CA, do the fo llowing.
1.Select Services Configuration -> Certificate Management and click the
Firewall Certificates tab. Cl ick New.
3-10Configuring Sidewinder for Soft-PK Clients
Page 41
Managing CA-based certificates
Specify the firewall certificate information.
2.
FieldSetting
Certificate NameSpecify a name for the firewall certificate.
Distinguished
Name
E-Mail Address,
Domain Name,
IP Address
Specify a set of data that identifies the firewall. Use the
following format:
cn=,ou=,o=,l=,st=,c=
where:
cn = common name
ou = organizational unit
o = organization
l = locality
st = state
c = country
IMPORTANT: The syntax for this fiel d is very
important. The above entries must be separated
by commas, and contain no spaces. In addition,
the order of the specified distinguished name fields
must match the desired order to be listed in the
certificate.
Optional fields to identify information (in addition to
DN).
Submit to CASelect the CA appropriate for your configuration.
Signature TypeSelect RSA.
SCEP PasswordSpecify a password for managing the certificate (e.g., to
retrieve the key, revoke, etc.)
3.Click Add to send the enrollment request.
IMPORTANT: After you send the enrollment request, the CA administrator must
issue the certificate before you can continue.
4.On the Firewall Certif ica tes tab, click Query to request the CA for a
signed copy of the certificate. (Certificates are automatically submitted
to its CA approximately every 15 minutes.)
5.Record all firewal l certificate info r ma t ion spec ified in Step 2. This
information must be entered into each Soft-PK client.
Configuring Sidewinder for Soft-PK Clients3-11
Page 42
Managing CA-based certificates
Determining identifying information for client
certificates
Define the identifying information that will be used for each remote
client certificate. Typically, these are the values entered in the
Distinguished Name (DN) fields when defining a certificate. This
information will be needed in either of the following scenarios:
If you plan to direct remote users to request a re mote certificate
from the CA.
or
If you plan to reques t remot e cert ificat es from the C A on beh alf of
the end-user.
Use Table 3-1 as a template for defining this information.
Table 3-1. Client Distinguis hed Name (DN) information
Distinguished Name fieldsSetting
cn (common name)
ou (organizational unit)
Note: Soft-PK lists this field as
"Department."
o (organization)
Note: Soft-PK lists this field as
"Company."
l (locality)
Note: Soft-PK lists this field as
"City."
st (state)
c (country)
3-12Configuring Sidewinder for Soft-PK Clients
Page 43
Figure 3-7.
Certificate Identities
defined on the firewall
Managing CA-based certificates
Defining remote client identities in Sidewinder
When using CA-based certificates, you must define an identity
"template" in Sidew i nder that matches all possible client identiti e s
used by the remote entities in your VPN.
To define remote certificate identities on Sidewinder, do the
following.
1.Select Services Configuration -> Certificate Management and click the
Certificate Identities tab. Click New.
Specify an identify name and the Distinguished Name fields.
2.
Note: An asterisk can be used as a wildcard when defining the fields on this window.
(Other special characters are not allowed.) F or example; *, O=ac me, C= us represents
all users at ACME.
3.Click Add.
Configuring Sidewinder for Soft-PK Clients3-13
Page 44
Managing pre-shared keys (passwords)
Managing preshared keys
(passwords)
When using pre-shared key s (passwords), yo u must define an ident ity
"template" in Sidew i nder that matches all possible client identiti e s
used by the remote entities in your VPN.
To define remote certificate identities on Sidewinder, use the same
procedure as defined in "Def ining remote client identities in
Sidewinder" on page 3-13.
IMPORTANT: Be sure to specify Extended Authentication, a s described in the next
section, when configuring the VPN on the Sidewinder.
3-14Configuring Sidewinder for Soft-PK Clients
Page 45
Configuring the VPN on the Sidew i n der
Configuring the
VPN on the
Sidewinder
Figure 3-8.
Sidewinder Security
Associations window
(defined VPNs)
Create a VPN security association for a Tunnel VPN using the newly
created certificates . Do the following from the Sidewinder Cobra
interface:
Select the General tab and specify the following primary VPN settings.
2.
FieldSetting
NameEnter the name of this VPN association.
EncapsulationSelect Tunnel. This is the more popular form of VPN
encapsulation. Both the data and the source and
destination IP addresses are encrypted within the
encapsulated payload.
ModeSelect either Dynamic IP Client or Dynamic IP
Restricted Client (the remote end is a device whose IP
address is not fixed). Example: A salesperson that gains
Internet access from a laptop.
Note: For Dynamic IP Restricted Client, the remote
end is assigned a virtual internal IP address using one of
two methods. You specify the range of IP addresses
available to the remote end by using either the Client
Address Pool field or the Dynamic Virtual Address Range
field.
More...
Configuring Sidewinder for Soft-PK Clients3-15
Page 46
Configuring the VPN on the Sidewinder
FieldSetting
Local Network/IPSpecify the network names or IP addresses to use as
the destination for the client(s) in the VPN. Click the
New button to specify the IP Address / Hostname
and Number of bits in Netmask. The value specified
identifies the network portion of the IP address. For
example, if you specify 24 with an IP address of
10.10.10.0, all IP addresses that begin with 10.10.10 are
accepted.
Note: If you are using Client Address Pools, the local
(destination for clients) is configured using different
windows.
EnabledSelect Yes.
BurbClick the dropdown list to assign this VPN to a burb.
Sidewinder terminates each VPN in a burb so that
access rules may or may not be applied to the VPN.
If you selected Dynami c I P R e stricted Clien t in the Mode field, you will
need to define one of the following mutually exclusive options.
Client Address
Pool
Dynamic Vir tual
Address Range
Determine if you want remote clients to be assigned
only the IP addresses contained within one of the
available client address pools. If so, use the dropdown
list to select the client address pool you want to use.
With this option, Sidewinder selects an IP address from
the available pool and assigns it to the client for use
during the VPN connection.
Note: For information on creating Client Address Pools,
see Chapter 11 in the Sidewinder Administration Guide.
Define the range of addresses a client can use when
initiating a VPN connection . The addr e sses specified
here do not represent a real network but are virtual
addresses. With this option the client assigns their own
IP address, although the address must be within the
approved address range.
3-16Configuring Sidewinder for Soft-PK Clients
Page 47
Figure 3-9.
Sidewinder Security
Associations Properties,
Authentication tab
Figure 3-10.
"Single Certificate"
options
Configuring the VPN on the Sidew i n der
Select the Authentication tab. Choose the authentication method
3.
appropriate for your configuration.
The "view" changes
depending upon the
Authentication Method
you select from the
dropdown list.
If you selected Single Ce rtificate (Figure 3-10), specify the following
self-signed certificate options.
Table 3-2. Single Certificate (self-signed) options
FieldSetting
Firewall
Certificate
Remote
Certificate
Firewall Identity
Type
Select the certificate used to authenticate the key
exchange.
Select the certificate used on the remote end of the
VPN from the list provided.
Select the type of identity to use when identifying the
firewall to the rem o t e c lient.
ValueContains the actual value used as the firewall identity.
This field cannot be edited.
Require Extended
Enable this checkbox.
Authentication
Configuring Sidewinder for Soft-PK Clients3-17
Page 48
Configuring the VPN on the Sidewinder
Figure 3-11. "Certificate
& Certificate Authority"
options
If you selected Ce rti f icate & Certificate Authority (Figure 3-11),
Select the certificate used to
authenticate the key exchange.
Select the type of identity to use when
identifying the firewall to the remote
client.
firewall identity. This field cannot be
edited.
Enable this checkbox.
Select the certificate authority used to
sign the digital certificates.
Select the certificate identity(ies) to
recognize in VPN connections.
3-18Configuring Sidewinder for Soft-PK Clients
Page 49
Figure 3-12. "Password"
options
Configuring the VPN on the Sidew i n der
If you selected Password (Figure 3-12), specify the following
password options.
Table 3-4. Password options
FieldSetting
Save your settings!4.
5.Click Close.
TIP: For typical Soft-PK configurations, you do not need to configu re settings in the
Crypto tab or Advanced tab windows. For details about those settings, refer to Chapter 11
in the Sidewinder Administration Guide.
Genera lEnter Pass wo rd/
Renter password
Require Extended
Authentication
IdentitiesFirewall IdentitySpecify the identity to use when
Remote IdentitySpecify the Certificate Identities and
Select the certificate used to
authenticate the key exchange.
Enable this checkbox.
identifying the firewall to the remote
client.
select the certificate identity(ies) to
recognize in VPN connections.
Click Add to save the settin gs.
Configuring Sidewinder for Soft-PK Clients3-19
Page 50
Configuring the VPN on the Sidewinder
3-20Configuring Sidewinder for Soft-PK Clients
Page 51
4
C HAPTER 4
Installing and Working with
Soft-PK
About this chapterThis chapter includes Soft-PK installation notes. It also describes the
basic Soft-PK procedures for managing certificates and creating a
customized Soft-PK security policy for your remote clients.
IMPORTANT: As network administrator, you need to install your own copy of Soft-PK
and become familiar with the software before you deploy setup instructions and the SoftPK software to each end user.
This chapter addresses the following to pi cs:
"Soft-PK installation notes" on page 4-2
"Starting Soft -PK" on page 4-3
"Managing certificates on Soft-PK" on page 4-6
"Configuring a security policy on the Soft-PK" on page 4-13
TIP: Chapter 5, "Deploying Soft-PK to Your End Users" describes how you should
customize the UserWorksheet.doc file contained on the Soft-PK CD to specify the correct
information your end user s should follow.
4
Installing and Working with Soft-PK4-1
Page 52
Soft-PK installation notes
4
Soft-PK
installation notes
Note the following about ins t alling, removing, or upgrading Soft-PK
software. You can customize the UserWorksheet.doc file located on the
product CD to sp ecify detailed installation instructions to you r end
users. (See Chapter 5 for details.)
Table 4-1. Soft- PK instal l/u ni nstall task summary
TaskNotes
Uninstall any
existing VPN
client programs
Installing
Soft-PK
Prior to installing Soft-PK on any system, uninstall/remove
any other VPN client programs that reside on the system.
Uninstall using the Control Pane l’s Add/Remove program
and reboot your computer before beginning the Soft-PK
installation or upgrade.
IMPORTANT: This applies to any previous copies of
SecureC l ient software.
To install Soft-PK, run the Autorun program from the Soft-PK
CD. (If Autorun is disabled, you can also run the
program in the SoftPK directory.)
For Windows NT or 2000, be sure to log in as Administrator
or equivalent.
setup.exe
Uninstalling
Soft-PK
Upgrading
Soft-PK
TIP: When setting up remote installations, you may
elect to provide the installation Autorun/setup.exe
program to your end users via other means (for
example, provide a zip distribution or network-based
installation).
Note: Soft-PK may warn of an error on install when PPTP is
already installed on th e client system. This is not a concern
when establishing Soft-PK to Sidewinder VPNs. Bypass the
warning (press OK) and continue the installation normally
(press next).
To remove Soft-PK, follow the standard Windows Uninstall
program.
IMPORTANT: When you remove this software and
its components, you have the option to keep your
security policy, digital cer tificates, and private keys.
This is recommended if you are uninstalling before an
upgrade.
Before upgrading or reinstal lin g Soft-PK, uninstall any
previous versions as noted above.
4-2Installing and Working with Soft-PK
Page 53
Starting Soft-PK
Starting Soft-PKSoft-PK starts automatically each time the computer on which it
resides is started. It runs transparently at all times behind all other
software applications including the Windows login. The Soft-PK icon
in the taskbar changes color and image to indicate the status of system
communications.
Figure 4-1. Soft-PK icon
in the Windows taskbar
Soft-PK icon in taskbar
Determining Soft-PK status f rom icon variations
The following table summarizes all icon variations and their meaning.
Table 4-2. Soft-P K taskbar icons
IconDescription
Grey — Indicates Windows did not start the Soft-PK service
properly.
Red — Indicates Soft-PK is installed correctly; no connection is
established.
Red box — I ndicates a non-s ecure connection established ;
transmitting non-secure communications.
Yellow key — Indicates at least one secure connection
established; no transmission.
Yellow key/green bo x— Indicates at least one secure
connection established; transmitting secure communications
only.
Yellow key/red bo x— Indicates at least one s ecure connection
established; transmitting non-secure communications only.
Yellow key/red and gr een box— Indicates at least one secure
connection established; transmitting secure and non-secure
communications.
In summary, green means the computer is transmitting securely; red
means it is transmitting unsecure communications. Both
red and green
means that the comput er is transmitting both secure and unsecure
data simultaneously, on different channels.
Installing and Working with Soft-PK4-3
Page 54
Starting Soft-PK
Activating/Deactivatin g Soft-PK
The Soft-PK user interface defines the security mode and the action
Soft-PK takes when it detects pac kets of vari ous protocol s and variou s
destinations. Once conf igu red, us ers need to acces s th e user interfac e
only to view or modify these settings.
As shown in Figure 4-2, you can right-click on the Soft-PK icon in the
taskbar to see all program options.
Figure 4-2. Soft-PK
taskbar icon options
Figure 4-3. Soft-PK Start
menu options
Right-click the Soft-PK tray ic on to
access menu
Means Soft-PK security policy is
currently a ctive!
IMPORTANT: To deactivate the Soft-PK se c urity policy, right-click on the Soft- P K ic o n in
the taskbar and toggle the Activate/Deactivate Security Policy menu option. (When
deactivated, the option shows Activate Security Policy.) If you deactivate the security
policy, you must toggle this setting to reactivate.
Figure 4-3 shows th e program options that are available when you
launch the Soft-PK user interface from the Start menu.
Soft-PK options after selecting Start ->
Programs -> SafeNet Soft-PK
TIP: Browse the Soft-PK online help system to become familiar with client procedures.
4-4Installing and Working with Soft-PK
Page 55
Starting Soft-PK
About the Soft-PK program options
This section pro vides a brief description of t he Sof t -PK main program
options. Use S oft-PK’s comprehensive online help for detailed
information.
Certificate Manager
The Certificate Manager allows you to request , import, and store
the digital certificates received from certificate authorities (CAs). To
communicate securely using digital certificates, users must have
two digital c ertif icate s: a CA (or s elf-s igne d fire wall) cert ifica te and
a personal certificate.
Security Policy Editor
The Security Policy Edi tor allows you to create connec tion polici es
and their associated proposals and list th em in a hierarc hical orde r
that defines an IP data communications security policy.
Log Viewer
The Log Viewer displays t he communi cations l og, a diagn ostic tool
that lists the IKE ne gotiations that occur dur in g th e authentication
phase.
Connection Monitor
The Connection Mon itor disp lays stati stical an d diagnos tic information for each active connection in the security policy. This utility is
designed to display the actual security policy settings configured in
the Security Polic y Editor and the security association (SA) information established during Phase 1 IKE negotiations and Phase 2
IPSec negotia tions.
Installing and Working with Soft-PK4-5
Page 56
Managing certificates on Soft-PK
Managing
certificates on
Soft-PK
If you are using digital certificate authentication in your VPN, you
should provide your end use rs with the information and fi les needed
to set up the ne cessary c ertif icates o n their So ft-PK clie nt. This secti on
provides a basic overview of what you need to do and includes (or
provides cross-r eference to) the appropriate procedures.
IMPORTANT: The firewall self-signed or CA root certificate should always be present on
the Soft-PK client before configuring the client certificate.
Setting up Sidewinder self-signed certificates
If you are using Sidewinder self-signed digital certificates, as
administrato r, do the follow in g.
1.If not already done, creat e and export a firewall certificate . See "Creat ing
& exporting a firewall certificate" on page 3-4 for details.
Note: You must have the firewall certificate configured in the Soft-PK system before you
import the persona l ce r tificate.
2.If not already done for each end user, create and export a remote
certificate and convert to PKCS12. See "Creating & exporting remote
certificate(s)" on page 3-6 for details.
3.Provide instructions for importing the self-signed firewall certificate. A
copy of this procedure is provided in this chapter, see "Importing a CA
root or self-signed firewall certificate into Soft-PK" on page 4-9 and
included in the UserWorksheet.doc file.
4.Prov ide instructions for importing the self-signed personal certificate. A
copy of this procedure is provided in this chapter, see "Importing a
personal cert ificate into Soft-PK" on page 4-11 and included in the
UserWorksheet.doc file.
4-6Installing and Working with Soft-PK
Page 57
Managing certificates on Soft-PK
Setting up CA-based certificates
If you are using CA-based di g ital certificat es, as administr a tor, do the
following.
1.If not already done, request and export the CA root certificate. See
"Defining a CA to use and obtaining the CA root cert" on page 3-9 for
details.
Note: You must have a CA certificate configured in the Soft-PK system before you can
request a personal certificate online.
2.If not already done for each end user, create and export a remote
certificate. See "Requesting a personal certificate from a CA on user’s
behalf" on page 4-8 for details.
3.Provide instructions for importing the CA root certificate. A copy of this
procedure is provided in this chapter, see "Importing a CA root or selfsigned firewall certificate into Soft-P K" on page 4-9 and included in the
UserWorksheet.doc file.
4.Prov ide instru ctions f or importing th e person al certifica te. A cop y of this
procedure is provided in this chapter, see "Importing a personal
certificate into Soft-PK" on page 4-11 and included in the
UserWorksheet.doc file.
Installing and Working with Soft-PK4-7
Page 58
Managing certificates on Soft-PK
Requesting a personal certificate fr om a CA on user’s
behalf
right click the SafeNet icon and select Certificate Manager).
2.Click the My Certificates tab.
3.Click Request Certific ate.... The Online Certificate Request dialog box
appears.
4.Select the Gen e rate Exportable Key check box.
Note: You will only be able to export the private key associated with the personal
certificate you are now requesting if you check th is option now. For security reasons,
no one can change it later. This is the only time the certificate can be exported.
5.Click Advanced to select a certificate service provider.
6.Under Enrollment method, click Online.
7.Under Subject Information, enter all r elevant personal information,
pressing the Tab key to move through the dialog box.
Note: If you press Enter, the request will generate before you are finished.
8.Under Online Request Information, enter or select these options:
a. In the Challenge Phrase box, enter any combination of numbers or
letters you choose. For security reasons, only asterisks appear here.
b. In the Confirm Challenge box, enter th e same phrase from the last
step.
c. From the Issuing CA list, select a CA certificate.
9.Click OK. Certificate Manager now generates a public/private key pair,
and then displays the
Online Certificate Request dialog box to indicate
that it is waiting for a response from the CA. When the CA accepts your
request, the
10. Optional: To view your request, click the Certificate Requests tab. Select
the request and click
11. Get your CA administrator to approve your request.
12. Once your request is approved, select it under the Certificate Requests
tab and click
13. Click Yes when the Certificate Manager dialog box asks if you want to
Certificate Manager dialog box appears. Click OK again.
View. Click inside the certificate window to close it.
Retrieve.
add this personal certificate. The request disappears, but the personal
certificate now appears under the My Certificates tab.
4-8Installing and Working with Soft-PK
Page 59
Managing certificates on Soft-PK
TIP: You should select the new certificate and click Verify to validate it.
Exporting a personal
certificate
Importing a CA root or selfsigned firewall certificate
into Soft-PK
14. In the My Certificates tab, select a personal certificate.
15. Click Export. The Export Certificate and Private Key dialog box appears.
16. In the Filename box, enter the drive, directory, and filename for the
personal certificate file. The default setting is C:\Temp\Cert.p12.
17. In the Password box, type any password you choose.
18. In the Confirm Password box, retype the password.
Note: The end user will need to know this password when import this file into their copy
of Soft-PK.
Importing cert ificate in Soft -PK
Use the following procedures to import certificates into the Soft-PK
system.
Note: These procedures are summarized on the UserWorksheet.doc file, customize as
needed for your end users.
Use the following proced ure to import a self -signed fire wall or CA
root certificate int o the Soft-PK system. This procedure is done at the
client system and assumes Soft-PK is already installed and you already
have a diskette containing an exported self-signed firewall or CA root
certificate.
right click the SafeNet icon and select Certificate Manager).
2.Click the CA Certificates tab.
3.Click Import Certificate.... The Import CA Certificate window appears.
Installing and Working with Soft-PK4-9
Page 60
Managing certificates on Soft-PK
Figure 4-4.
Soft-PK Certificate
Manager: CA Certif icates
tab, Import CA
Certificate
Insert the diskette containing the self-signed firewall or certificate file.
4.
5.From the Files of type: field, select All Files (*.*) and then navigate to
display the files located on the diskette.
6.Select the appropriate certname.pem file and click Open. The following
window appears prompting you to confirm you want to import the
selected certificate.
Figure 4-5.
Verification window
Figure 4-6.
Viewing the certificate
7.
Click Yes.
8.[Optional] From the CA Certificates tab, click View to see the informatio n
in the certificate.
4-10Installing and Working with Soft-PK
Page 61
Managing certificates on Soft-PK
Importing a personal
certificate into Soft-PK
Figure 4-7.
My Certificates tab:
Import Certificate (and
private Key) window
Use the follo wing procedure to import a person a l certificate into the
Soft-PK system. This procedure is done at the client system and
assumes Soft-PK is already in stal le d.
Note: This procedure is summarized on the UserWorksheet.doc file, customize tha t
procedure as needed for your end users.
right click the SafeNet icon and select Certificate Manager).
2.Click the My Certificates tab.
3.Click Import Certificate....
Figure 4-8. Import
Certificate Password
window
Insert the diskette containing the remote key/certificate object file.
4.
5.From the Files of type: field, select All Files (*.*) and then navigate to
display the files located on the diskette.
6.Select the appropriate filename.p12 file and click Open. The following
window appears.
Note: The file type must be a PKCS12 object. PKCS8 and PKCS1 objects cannot be
used.
Specify the password used when creating the p12 object (step 10 on
7.
page 3-8). You will not be allowed to import the certi fica te if th e
password is incorrect.
Installing and Working with Soft-PK4-11
Page 62
Managing certificates on Soft-PK
Figure 4-9.
Verification window
Figure 4-10.
Viewing the certificate
Note: You must provide this password to the end user so they can later import this
certificate file.
8.Click Import. A prompt appears to confirm you want to import the
selected Personal Certificate.
Click Yes.
9.
10. [Optional] From the My Certificates tab , click View to see the information
in the certificate.
4-12Installing and Working with Soft-PK
Page 63
Configuring a security policy on the Soft-PK
Configuring a
security policy on
As an administrator, you can configure end user security policies on
your Soft-PK system, save them to a diskette, and distribute them to
your users. Your end users then simply import the security policy
the Soft-PK
Basic connection optionsWhen you configur e a user policy o n Soft-PK, you can specify to send
you’ve set up.
all traffic over one VPN connect ion, or specify to send traffic over
separate connections (some or all of which can be secured) for
different traffic dest inations. This choice is made by select ing
> Secure
from the main menu.
Options -
All Connections— This allows you to configu re one, and only one
connection that secures all IP communications with the option to
direct all co nnections to a specif ic gateway.
Specified Connections— This option all ows you to configu re
multiple simultaneous connections. This option includes a default
connection co nfigu ratio n call ed " Other Conn ecti ons," that cont rols
traffic not covered by prior connection ru les.
Setting up an Other
Connections policy
The remainder of this section describes the setup of a single
connection policy under the
Specified Connections scenario. Th e
connection settings you configure must coincide with configured
settings/capabilities on the Sidewinder VPN Gateway.
Note: This procedure assumes your client system will not use this policy for every
connection. That is, the system may sometimes be used in a local network where a VPN
connection is not needed.
right click the SafeNet icon and select Security Policy Editor).
2.Select Options -> Secure Specified Connections.
3.Click on Other Connections. This is the catchall rule for all IP
communications that do not conform to the proposals you will defined
for individual connections. This policy will handle all traffic not defined
in another policy.
Note: Configure this according to your site/user requir em ents. You can allow all
traffic to pass through (Non-secure mode), configure a VPN policy (Secure mode), or
stop all other traffic (Block mode).
Installing and Working with Soft-PK4-13
Page 64
Configuring a security policy on the Soft-PK
Start def i ni ng a new policy. Select Edit -> Add -> Connection to create a
4.
new polic y.
Figure 4-11.
Soft-PK: Security Policy
Editor
New connection
named SecureVPN
Note: By default, the
"Other Connections"
policy handles all
traffic not d efined in
other policies
Specify a descriptive name for the connection. (The name "SecureVPN"
5.
is used in this example.)
6.Specify the connection type. In the Connec tion Security field, specify
Secure.
7.Specify the trusted network to which the client will be communicating.
Remote Party Identity and Addressing fields:
In the
Change the ID Type to IP Subnet.
Specify the Subnet and Mask of the trusted network.
8.Specify the Sidewinder connection information.
a. Enable the Connect using Secure Gateway Tunnel box.
b. Specify the interface information:
If using shared password: Specify set the ID Type to IP Address
and enter the IP Address of the Sidewinder’s internet interface.
If using digital certificates:
— Set the
— Enter the
the IP Address field.
ID Type to Distinguished Name.
IP Address of the Sidewinder’s internet interface in
4-14Installing and Working with Soft-PK
Page 65
Figure 4-12. Soft-PK: Edit
Distinguished Name
window to specify
Firewall public certificate
Figure 4-13.
Soft-PK: Security Policy
fields
Configuring a security policy on the Soft-PK
— Click on the Edit Name button, in the window that appears
(Figure 4-12, enter the
Distinguished Name information. Input
all fields from the Firewall Certificate and click
This is case sensitive,
make sure it matches
the certificate exactly.
Select Security Policy and select the Phase 1 Negotiation Mode.
9.
Use Main Mode for
certificate-based VPNs
OK.
Figure 4-14.
Soft-PK: My Identity
fields
Use Aggressive Mode
for pre-shared keys
Specify how the user will be identified to the Sidewinder. Select My
10.
Identify
.
Installing and Working with Soft-PK4-15
Page 66
Configuring a security policy on the Soft-PK
a.
b. In the Internet Interface selection drop-down box, specify which
11. Specify the Authentication settings. Sel ect Authentication (Phase 1) ->
Proposal 1
Figure 4-15.
Soft-PK: Authentication
(Phase 1) -> Proposal 1
fields
Select the authentication method for this connection.
If using shared password: Click Pre-Shared Key and enter the
shared password.
If using digital certificates: Select the personal certificate
previously imported from the drop-down list. Notice th e ID Type
automatically changes t o Distinguished Name.
interface to use when creating the VPN. For our example, the default
“Any” is adequ ate.
.
In Authentication Method field, specify the method appropriate for
a.
your configuration. (For example, use RSA Signatures if using only
digital certificate authentication, use RSA Signatures: Extended
Authentication if using digital certificate authe ntication and
extended authentication.)
b. In Encr yp tion and Data Integrity/Algorithms fields:
Encrypt Alg: Select DES or Triple-DES (highest).
Hash Alg: Select MD5 or SHA-1 (highest).
SA Life: Set this to 3500 seconds.The Phase 1 Lifetime on the Soft-
PK should NOT be left as Unspecified. It should be set to some
period of time slightly shorter than is configured on the
Sidewinder SA definition (Advanced tab on the Sidewinder COBRA
GUI).
c. In Key Group field, select at least Group 2. Group 5 (highest).
4-16Installing and Working with Soft-PK
Page 67
Figure 4-16.
Soft-PK: Key Exchange
(Phase 2) -> Proposal 1
fields
Configuring a security policy on the Soft-PK
Specify the Key Exchange setti ngs. Select Key Exchang e (Phase 2) ->
12.
Proposal 1
.
SA Life: Select Unspecified to default to Sidewinder settings.
Compression should not be used.
Encapsulation Protocol: Selec t the same settings in the Encryption
and Hash Algorithms fields as Phase I. Do
Encapsulation
.
not change Tunnel
Do not use the Authentication Protocol (AH). (This does not encrypt
traffic.)
13. [Optional] Click Save to save the policy on this system.
IMPORTANT: You can export a policy witho ut saving it, but the policy will then not
be saved on the system on which it was configured
14. Select File -> Export.
a. You will be prompted to prot ect your security policy. Your end users
will then not be able to chang e the settings or create new policies.
However, your end users will be able to change the
My Identity
fields.
b. Specify the location of the exported file.
15. Provide a copy of this file to the appropriate end users (see Chapter 5 for
details).
Installing and Working with Soft-PK4-17
Page 68
Configuring a security policy on the Soft-PK
4-18Installing and Working with Soft-PK
Page 69
5 7
C HAPTER 5
Deploying Soft-PK to Your
End Users
About this chapterThis chapter summarizes the final p reparati on ste ps for deployin g th e
Soft-PK software, digital certificate files, and security policy to your
end users. It is based on a worksheet that you edit and send to each
remote end user.
IMPORTANT: T h is chapter assumes you have obtained the required certificates and
have configured and saved a security policy.
This chapter addresses the following to pi cs:
"Overview" on page 5-2
"Customizing the user worksheet" on page 5-4
5
Deploying Soft-PK to Your End Users5-1
Page 70
Overview
OverviewY ou should de ploy the Soft-PK instal lation program with a cust omized
security policy and the necessary digital certificates. Custom
installations are designed to make it easy to manage corporat e
security policies for tens, hundreds, or thousands of end users.
5
Along with the necessary software and files, you should provide
specific Soft-PK installation and setup instructions for each end user.
This facilit ates managem ent of corpor ate securit y policies fo r your end
users and simplifies what the end user must do.
The Soft-PK product CD provided by Secure Computing includes a
file (userworksheet.doc) in MS Word format that you can customize
and send to users.
Figure 5-1. Sample
userworksheet.doc file
contained on Soft-PK
product CD
Word
format
5-2Deploying Soft-PK to Your End Users
This worksheet contains five main sections that you should edit and
save before di stri but in g to en d use rs. T he se se ctio ns are b ase d on the
information pre sented in earlier chapters in this manual.
Prior to customizing the worksheet, take a few minutes to organize
the files and information you need to deploy to your end users.
T able 5-1. Organize the files/software for each client (end user)
Deployment
item
Soft-PK software
program
Digital certificate
files
Notes
Soft-PK setup.exe file and supporting files.
If deploying Sidewinder self-signed ce rti fic at es :
firewall certificate (*.pem)
personal certificate, with private key (*.p12)
If deploying CA-based certificates:
CA root certificate (*.pem)
personal certificate, with private key (*.pk)
IMPORTANT: Personal certificates must be
unique to each individual; you cannot distribute
one personal certificate to all of your end users.
Security policyInclude a locked security policy file (*.spd) that end users
cannot modify.
Copy the Soft-PK software, cer tificate file, person al certif icate file , and
security policy fil e to an unzip pe d im age of SafeNet /Soft-PK software.
Deploying Soft-PK to Your End Users5-3
Page 72
Customizing the user worksheet
Customizing the
user worksheet
Figure 5-2. Sample text
for specifying dial-up
networking setup
This section provides summary information about each section in the
default UserWorksheet.doc file .
Specifying dial-up network instructions
Figure 5-2 shows the text in the initial UserWorksheet.doc file that
pertains to setti ng up dial-up netw orking. Delete or change this t ext as
needed for your end user’s particular env ironment.
Specifying installation instructions
Figure 5-3 shows the text in the initial UserWorksheet.doc file that
pertains to Soft-PK installation instructions. The default text covers
basic installat ion, one that installs only the Soft-PK. Change this text
according to how you want users to install Soft.PK
Figure 5-4 shows the text in the initial UserWorksheet.doc file that
pertains to digital certificates. The default text covers a basic
instructions for import ing cer t ific at e files from a disk you provide.
Change this text according to how you want users to set up
digital certificates (or delete if not using certificates).
Deploying Soft-PK to Your End Users5-5
Page 74
Customizing the user worksheet
Figure 5-5. Sample text
for importing the
security policy
Specifying security policy instructions
Figure 5-5 shows the text in the initial UserWorksheet.doc file that
pertains to the Soft-PK security policy. The default text covers a basic
instructions for importing a security policy from a disk you provide.
Change this text according to how you want users to set up the
security policy.
Specifying basic connection information
Figure 5-6. Sample text
for starting the VPN
Figure 5-6 shows the text in the initial UserWorksheet.doc file that
pertains to star ting the V PN. The defa ult text cov ers basi c activatio n of
a security po licy.
5-6Deploying Soft-PK to Your End Users
Page 75
A
A PPENDIX A
Troubleshooting
About this appendixThis appendix provi des a summary of troubleshooting tech niq ues
available for resolving Soft-PK and Sidewinder VPN connection
problems. This append ix addresses the followin g topics:
"Soft-PK Log Viewer" on page A-1
"Soft-PK Conne ction Monitor" on page A-2
"Sidewinder troubleshooting commands" on page A-4
Soft-PK Log
Viewer
The Log Viewer displays the communications log, a diagnostic tool
that lists the IKE ne gotiations that occur dur in g th e authentication
phase. This is a ver y useful tool w hen y ou canno t cor rectly es tablis h a
VPN connection. (However, a good log viewer does not replace a
carefully set up VPN security association.)
Note: The Log Viewer shows only ISAKMP and IKE messages, it does not show audit
messages for all traffic flow through the VPN.
A
Figure A-1. Log Viewer
window on Soft-PK
To start the Log Viewer, right-click the Soft-PK icon or select it from
the Start menu.
IMPORTANT: This information is not saved. Unless you freeze and save or print this
information, it will be cleared by ongoing negotiations.
TroubleshootingA-1
Page 76
A
Soft-PK Connection Monitor
The following summarizes the tasks you can perform.
ButtonSummary
ClearClears the communications log.
IMPORTANT: You cannot retrieve this information once you
clear it.
FreezeFreezes/Unfreezes the communications log. Because the
communications log scrolls thro ugh IKE negotiations as
they occur, you may need to freeze the log in order to save
or print specific messages.
Since this button acts as a toggle, it will now read UnFreeze
until you click it again to restart the log.
PrintPrint the current con t ent in the communications log.
TIP: You may want to freeze the log before you attem pt to
print it.
SavePrint the curr en t content in the communications log.
Soft-PK
Connection
Monitor
Figure A-2. Connection
Monitor window
TIP: You may want to freeze the log before you attem pt to
save it.
CloseCloses the log viewer.
The Connection Mon itor displays statis tical and diagnos tic information
for each active connection in the security policy. This utility is
designed to disp lay the actual security poli cy settings configured in
Security Policy Editor and the security association (SA) information
established during Phase 1 IKE negotiations and Phase 2 IPSec
negotiations.
To star t th e Connection Monitor, right-click the Soft-PK icon or select
it from the Start menu.
A-2Troubleshooting
Page 77
Soft-PK Connection Monitor
You will see an icon to the left of the connection name:
A key indicates that the connection has a Phase 2 IPSec SA, or both
a Phase 1 and Phase 2 SA. When there is a single Phase 1 SA to a
gateway that is protecting multiple Phase 2 SAs, there will be a
single Phase 1 connec tion with t he SA icon and indiv idual Pha se 2
connections with the key icon listed above that entry.
An SA indicates that the co nnection has only a Phase 1 IKE SA.
This occurs when conn ecting to a secure gateway tunnel or when
a Phase 2 IPSec SA fails to establish or has not been established
yet.
A black mark moving beneath the key icon indicates that the client
is processing sec ur e IP tr affic for that connection.
More about the Connection Monitor
Global Statistics are not real-time operations; they are updated every
five seconds.
Figure A-3. Connection
Monitor window
Dropped Packets includes packets from connections that are
configured as blocked.
Remote Modifier is either the remote party subnet mask or the end of
the address range when IP Address Range is selected for the Remote
Party Identity and Ad dressing ID Type.
To view the details
To see the details about a connection, click Details. The Security
Association Details window appears as shown below.
You will see a Phase 1 tab and/or a Phase 2 tab; these tabs indicate
TroubleshootingA-3
Page 78
Sidewinder troubleshooting commands
that the selected co nn ection has establish ed SAs.
To view Authentication (Phase 1) security associations negotiated
To view Key Exchange (Phase 2) security a ssociations negot iated
by IKE, click the Phase 1 tab.
by IPSec, cli c k the Phase 2 tab.
Sidewinder
troubleshooting
commands
In addition to standard log ging, the Sidewind er also performs auditing
of certain syst em ev ents whi ch al lows y ou to g enerat e info rmation on
VPN connectio ns. Table A-1 shows some useful c ommands you can
use to track VPN connections in real-time mode and check VPN
settings/configuration.
T able A-1. Basic Sidewinder VPN troubleshooting commands
Commands
tcpdum p -n pi ext_interface port 500 proto 50
To show IPSEC and ESP traffic arriving at the firewall