Cisco ASA 5505 - Manual (Page 1490)

67-64
Cisco ASA 5500 Series Configuration Guide using the CLI
Chapter 67 Configuring Connection Profiles, Group Policies, and Users
Supporting a Zone Labs Integrity Server
mechanism is called Are You There (AYT), because the VPN client monitors the firewall by sending it
periodic “are you there?” messages; if no reply comes, the VPN client knows the firewall is down and
terminates its connection to the ASA.) The network administrator might configure these PC firewalls
originally, but with this approach, each user can customize his or her own configuration.
In the second scenario, you might prefer to enforce a centralized firewall policy for personal firewalls
on VPN client PCs. A common example would be to block Internet traffic to remote PCs in a group using
split tunneling. This approach protects the PCs, and therefore the central site, from intrusions from the
Internet while tunnels are established. This firewall scenario is called push policy or Central Protection
Policy (CPP). On the ASA, you create a set of traffic management rules to enforce on the VPN client,
associate those rules with a filter, and designate that filter as the firewall policy. The ASA pushes this
policy down to the VPN client. The VPN client then in turn passes the policy to the local firewall, which
enforces it.
Supporting a Zone Labs Integrity Server
This section introduces the Zone Labs Integrity server, also called the Check Point Integrity server, and
presents an example procedure for configuring the ASA to support the Zone Labs Integrity server. The
Integrity server is a central management station for configuring and enforcing security policies on
remote PCs. If a remote PC does not conform to the security policy dictated by the Integrity server, it is
not granted access to the private network protected by the Integrity server and ASA.
This section includes the following topics:
• Overview of the Integrity Server and ASA Interaction, page 67-64
• Configuring Integrity Server Support, page 67-65
Overview of the Integrity Server and ASA Interaction
The VPN client software and the Integrity client software are co-resident on a remote PC. The following
steps summarize the actions of the remote PC, ASA, and Integrity server in the establishment of a session
between the PC and the enterprise private network:
1. The VPN client software (residing on the same remote PC as the Integrity client software) connects
to the ASA and tells the ASA what type of firewall client it is.
2. After the ASA approves the client firewall type, the ASA passes Integrity server address information
back to the Integrity client.
3. With the ASA acting as a proxy, the Integrity client establishes a restricted connection with the
Integrity server. A restricted connection is only between the Integrity client and the Integrity server.
4. The Integrity server determines if the Integrity client is in compliance with the mandated security
policies. If the Integrity client is in compliance with security policies, the Integrity server instructs
the ASA to open the connection and provide the Integrity client with connection details.
5. On the remote PC, the VPN client passes connection details to the Integrity client and signals that
policy enforcement should begin immediately and the Integrity client can enter the private network.
6. After the VPN connection is established, the Integrity server continues to monitor the state of the
Integrity client using client heartbeat messages.