CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3.
2. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 And Related Products > Miscellaneous
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2006-12-12
Junior Member
 
Join Date: 2005-12-02
Posts: 13
Rep Power: 0
ligmania has an average reputation (10+)
Default standard firewall configuration baseline

Does anyone have a document that shows best practices in configuring and
deploying checkpoint firewalls ?
Reply With Quote
  #2 (permalink)  
Old 2006-12-18
Senior Member
 
Join Date: 2006-06-08
Location: UK
Posts: 149
Rep Power: 3
Joncon has an average reputation (10+)
Default Re: standard firewall configuration baseline

There is no such thing as a 'standard' firewall configuration as all firewalls differ dependant on their purpose. One FW may need ftp and therefore have it enabled another may not require it and therefore have it disabled. The security options chosen will also be dependant on the O/S Checkpoint sits on (IPSO / SOLARIS / SPLAT / WINDOWS). For example, you will need to do a hell of a lot more work to harden a windows host than you will to secure IPSO / SPLAT. I used to work for a security / audit consultancy looking at the security of FWs and used to upset the managers when I told them I couldn't give them a 'one size fits all' baseline doc for non technical auditors to follow as all firewalls are different.

Some common weaknesses I used to come across a lot:-
1. No stealth rule or stealth rule too low.
2. No logging.
3. Telnet enabled (rather than using something like SSH).
4. FTP enabled (rather than using something like SCP).
5. Backups not being taken / Test restores not been tested.
6. FW software missing critical patches.
7. O/S missing critical patches.
8. No documentation.
9. Rules allowing services no longer required.
10. Rules allowing services but no one knows why they exist.
11. 'Unknown' Admin GUIs defined.

There are plenty more. If you take the approach of least priviledge with all your configurations you will not go far wrong. Simple rule to follow is if something isn't needed disable it.

tht,

Joncon
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -7. The time now is 21:07.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0