Skip to main content

Block a list of URL address in your network with Checkpoint GAIA


Block a list of URL address in your network with Checkpoint GAIA

Block-a-list-of-URL-address-in-your-network-with-Checkpoint-GAIA
Block a list of URL address in your network with Checkpoint GAIA :-
Have you ever faced a situation of blocking particular URL or group of URL’s in your network ? If yes, then this tutorial is completely for you. :-)
Checkpoint comes with Application & URL filtering software blade for this job but today i am going to show you how to block a list of URL address in your network with IPS software blade.
You have to understand the basic DNS operations, When user is trying to open a Website then first it’s communicating with a Local DNS server for DNS query then Local DNS server is forwarding this request to particular webserver.
Block-a-list-of-URL-address-in-your-network-with-Checkpoint-GAIA
actually what actually we are going to do here is blocking DNS request on Local network.
To do so, Open Smart Dashboard on your console PC. Navigate to IPS > Protections > By Type > Application Control > in the right-pane search for Domain Black List and double click on it .
Block-a-list-of-URL-address-in-your-network-with-Checkpoint-GAIA
now select your protection profile, then click on the Edit option and in the main action select the preventoption. Now in the Additional Settings option, you have option to define your URL to drop DNS request.
Block-a-list-of-URL-address-in-your-network-with-Checkpoint-GAIA
Click on the Select option , Now click on the New > Domain
Block-a-list-of-URL-address-in-your-network-with-Checkpoint-GAIA
then enter your domain name here.
dnsoperations1
If you want to implement on all profiles. Click on the Change action tab and select prevent on all profileoption.
Block-a-list-of-URL-address-in-your-network-with-Checkpoint-GAIA
Hope you like my post.Block a list of URL address in your network with Checkpoint GAIA. Please Share with others.
Labels:

Comments

Post a Comment

Popular posts from this blog

CLI Commands for Troubleshooting FortiGate Firewalls

CLI Commands for Troubleshooting FortiGate Firewalls 2015-12-21 Fortinet , Memorandum , Network Cheat Sheet , CLI , FortiGate , Fortinet , Quick Reference , SCP , Troubleshooting Johannes Weber This blog post is a list of common troubleshooting commands I am using on the FortiGate CLI . It is not complete nor very detailled, but provides the basic commands for troubleshooting network related issues that are not resolvable via the GUI. I am not focused on too many memory, process, kernel, etc. details. These must only be used if there are really specific problems. I am more focused on the general troubleshooting stuff. I am using it personally as a cheat sheet / quick reference and will update it from time to time. Coming from Cisco, everything is “show”. With Fortinet you have the choice confusion between show | get | diagnose | execute . Not that easy to remember. It is “ get router info6 routing-table” to show the routing table but “ diagn...
Post a Comment
Read more

Check Throughput of Interfaces - Palo Alto Networks NGFW

Check Throughput of Interfaces - Palo Alto Networks NGFW Following command shows brief interface throughput. > show system statistics session To see the complete statistics, run the show system state browser command > show system state browser Press Shift+L and click on Ports To enable tracking and updates press Y and U To see additional ports, press space bar
Post a Comment
Read more

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking The way we do business is changing. As critical business applications migrate to the cloud, and the mobile workforce continues to grow, networking and security solutions need to evolve in order to meet the changing business needs. Gartner believes (and we agree) that the future of networking lies with  SASE (Secure Access Service Edge)  – the convergence of networking and security into one cloud service. Here’s why. 1990s – 2000s: MPLS and the Era of Clear Network Boundaries? Back in the day, networking models were hardware-centric and manually configured. Applications, data, and services lived within private datacenters and relied on remote access solutions to connect remote workers. Dedicated network connectivity, known as MPLS, was the preferred approach for connecting remote locations. MPLS provides predictable performance, low latency and packet loss, and central management. However, MPLS is ...
Post a Comment
Read more