
Version 5.2
Sourcefire 3D System Installation Guide
42
Understanding Deployment
Deployment Options
Chapter 2
A gateway VPN can be used in a point-to-point, star, or mesh deployment:
•
Point-to-point deployments connect two endpoints with each other in a
direct one-to-one relationship. Both endpoints are configured as peer
devices, and either device can initiate the secured connection. At least one
device must be a VPN-enabled managed device.
Use a point-to-point deployment to maintain your network security when a
host at a remote location uses public networks to connect to a host in your
network.
•
Star deployments establish a secure connection between a hub and
multiple remote endpoints (leaf nodes). Each connection between the hub
node and an individual leaf node is a separate VPN tunnel. Typically, the hub
node is the VPN-enabled managed device, located at the main office. Leaf
nodes are located at branch offices and initiate most of the traffic.
Use a star deployment to connect an organization’s main and branch office
locations using secure connections over the Internet or other third-party
network to provide all employees with controlled access to the
organization’s network.
•
Mesh deployments connect all endpoints together by means of VPN
tunnels. This offers redundancy in that when one endpoint fails, the
remaining endpoints can still communicate with each other.
Use a mesh deployment to connect a group of decentralized branch office
locations to ensure that traffic can travel even if one or more VPN tunnels
fails. The number of VPN-enabled managed devices you deploy in this
configuration controls the level of redundancy.
For more information on gateway VPN configuration and deployments, see
Gateway VPN in the
Sourcefire 3D System User Guide
.
Deploying with Policy-Based NAT
L
ICENSE
:
Control
S
UPPORTED
D
EVICES
:
Any
You can use
policy-based network address translation
(NAT) to define policies that
specify how you want to perform NAT. You can target your policies to a single
interface, one or more devices, or entire networks.
You can configure static (one-to-one) or dynamic (one-to-many) translation. Note
that dynamic translations are order-dependent where rules are searched in order
until the first matching rule applies.
Policy-based NAT typically operates in the following deployments:
•
Hide your private network address.
When you access a public network from your private network, NAT
translates your private network address to your public network address.
Your specific private network address is hidden from the public network.