Book Image

Check Point Firewall Administration R81.10+

By : Vladimir Yakovlev
Book Image

Check Point Firewall Administration R81.10+

By: Vladimir Yakovlev

Overview of this book

Check Point firewalls are the premiere firewalls, access control, and threat prevention appliances for physical and virtual infrastructures. With Check Point’s superior security, administrators can help maintain confidentiality, integrity, and the availability of their resources protected by firewalls and threat prevention devices. This hands-on guide covers everything you need to be fluent in using Check Point firewalls for your operations. This book familiarizes you with Check Point firewalls and their most common implementation scenarios, showing you how to deploy them from scratch. You will begin by following the deployment and configuration of Check Point products and advance to their administration for an organization. Once you’ve learned how to plan, prepare, and implement Check Point infrastructure components and grasped the fundamental principles of their operation, you’ll be guided through the creation and modification of access control policies of increasing complexity, as well as the inclusion of additional features. To run your routine operations infallibly, you’ll also learn how to monitor security logs and dashboards. Generating reports detailing current or historical traffic patterns and security incidents is also covered. By the end of this book, you'll have gained the knowledge necessary to implement and comfortably operate Check Point firewalls.
Table of Contents (21 chapters)
1
Part 1: Introduction to Check Point, Network Topology, and Firewalls in Your Infrastructure and Lab
6
Part 2: Introduction to Gaia, Check Point Management Interfaces, Objects, and NAT
13
Part 3: Introduction to Practical Administration for Achieving Common Objectives

Postmortems and lessons learned

After concluding the troubleshooting process, a postmortem (short for retrospective analysis) should be performed. Typically, this consists of several questions and short but informative answers to each of them. These questions are as follows:

  • What happened?

We may be able to answer this question better now than when we started the troubleshooting process since, initially, we may have been looking at a subset of effects.

  • Why did it happen?

This is the chain of relevant events that have been backtracked to the root causes of the issue. These may be both technical and procedural. All of them must be addressed. As a technical troubleshooter, you may only be able to cover the technical aspects of this question.

  • How did you respond and recover?

Provide a brief and factual outline of the steps taken to troubleshoot the issue. It may be useful to present this as a timeline.

  • What can be done to prevent similar...