Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Chapter 14: Configuring Virtual Private Networks
Example VPN Scenarios
456
b On the Authentication tab:
• Authentication method = Single Certificate
• Firewall Certificate = Select the certificate you created in step 1A
• Remote Certificate = Select the certificate you created in step 1C for
this client
c On the Crypto tab: Order the algorithms to match that of the client
d On the Advanced tab: No changes needed
e Click Add to save the new VPN association.
f Click the Save icon to save your changes.
4 Repeat step 3 for each client, changing the name in step 3A and the remote
certificate in step 3B as appropriate.
Summary
Each individual VPN connection can be used as soon as the remote clients are
configured. Each client will need the client-specific certificate and private key
information you saved in steps 1B and 1C in order to configure their end of the
VPN connection. If you saved this information to diskette you can either hand it
to them in person, mail it to them, or perform the imports while the machine is
within a trusted network. It is not safe to distribute certificate and private key
information via e-mail.
Note: The configuration described above restricts VPN traffic by terminating it in a
virtual burb. Proxies and rule entries must be configured to specify what access the
VPN clients have to the trusted network.
Scenario 3: Large scale deployment of clients
This scenario is similar to Scenario 2 except that instead of a small number of
remote clients it assumes you have hundreds or even thousands of remote
clients. Because it is unreasonable to create a unique VPN association for
each client, a Certificate Authority (CA) will be used. The CA, in conjunction
with the remote identities you define, allows you to create one VPN that is
accessible by all of the clients.
The following figure provides the sample configuration information used in this
scenario.