RE: [FW1] Keeping SecureClient PC's Safe.

[Larry Pingree]

Title: Keeping SecureClient PC's Safe.

Currently with secureclient you can deny incoming connections to your network. The new NG secureclient will allow you to configure rules that are outbound from the secureclient box as well. 

 

 

 

 

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Larry Pingree

Sr. Security Engineer/Check Point Instructor

CCSA, CCSE, CCSI, ICE, ICI, NSA

 

Website: http://www.SiegeWorks.com

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Hanke, Christian (DC)
Sent: Monday, August 20, 2001 2:38 PM
To: '[EMAIL PROTECTED]'
Subject: [FW1] Keeping SecureClient PC's Safe.

I am interested in what, if any, precautions others are taking to insure that the PC's using SecureClient to connect to their networks via VPN are not themselves compromised. My concern is that someone at home will be virus laden, compromised by a trojan, or who knows what else and then in turn compromise our network security by tunneling in to our cooperate network. Is this a valid concern? I am playing with the idea of requiring either a NAT box or one of the new Home Internet Gateways which include firewall functionality for users who wish to take advantage of the high speed VPN connection to our network. Of course, there would be no way to make sure their settings and configurations were optimal. What's everyone else doing about this? Your feedback would be greatly appreciated. Thanks all,

Christian