| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| (CheckPoint NG with Application Intelligence R55 Build 127) Hi, Is possible to restrict remote vpn users so that they can't access the whole network once authenticated? I guess you can but i can't seem to get it to work. I've created a group called lockdown and added the required users (I only want them to be able to access 1 server on RDP). Then i've created a rule: lockdown@svr1 svr1 any traffic RemoteDesktop ClientAuth Log But once i've authenticated i can still get to other servers? I have missed something? Thanks for any help / informartion. Cheers, Slash. |
| |||
| There are several ways to accomplish this. You should of course first check SmartView Tracker for the rules that allow your RemoteUsers unwanted access. In your case I'd simply create a second rule below your Accept rule: lockdown@svr1 any any traffic any Drop Log Make sure no other rule above these two grants permission to your RemoteUsers. What else could be done? - you could define the allowed locations for your RemoteUsers within their User Properties - you could use Accept instead of ClientAuth and define the RemoteAccess Community within the VPN tab of the related rule (see examples in demo mode) Example: lockdown@svr1 svr1 RemoteAccess RemoteDesktop Accept Log Best regards, Danny Trommer CCSA/CCSE/CCSE+ |
| |||
| Why using Client Auth with a Remote Access VPN, surely should be Client Encrypt action if traditional mode, or specify the Remote Access VPN and Accept if Simplified Mode. Is the user a member of another user group that would have access to the whole network still. |
| |||
| Hi, When i try the above the policy fails to install with error: User Groups are allowed only on Authentication Rules Any ideas? I've got this in the rulebase: 10: lockdown@svr1 svr1 RemoteAccess RemoteDesktop Accept Log 11: lockdown@svr1 any any traffic any drop log Thanks for any help Slash. |
| |||
| You could try using IP pools and try and restrict access that way. But i could be wrong on that as I've never tested it. But from what I can see your rules it looks fine other than the ClientAuth this should be Cleint Encrypt as mcnallym says. Last edited by Danielpb; 2007-08-02 at 05:13. |
![]() |
| Thread Tools | |
| Display Modes | |
| |