- Products
- Learn
- Local User Groups
- Partners
- More
Step Into the Future of
AI-Powered Cyber Security
The State of Ransomware Q1 2026
Key Trends and Their Impact
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
CheckMates Go:
CheckMates Fest
Hi team,
Can I know difference between get interface with topology and without topology meaning. And when we use this, tell me scenario.
One of the core security features of the product is Anti-Spoofing.
For anti-spoofing to work, topology must be defined.
The topology includes all the networks reachable from that interface.
This can either be done manually or as part of "Get Interfaces with Topology" though you should only use this option before the gateway goes into production.
This has been discussed here among other places: https://community.checkpoint.com/t5/General-Topics/Get-interface/m-p/246503
When you get interfaces with topology, Check Point will automatically generate objects for the anti-spoofing settings.
They will be linked to the interfaces, but may not be visible in the Object Tree. Check:
sk126872 - Some Network objects are not visible in the SmartConsole object list
Something to be aware of if you want to use these objects in a policy.
Since I encountered problems here and there a long time ago when importing with topology, I have never done it again since then, and the point mentioned that objects are automatically created that I create myself has prevented me from doing it again to this day. But for beginners, I would always recommend importing with topology first and learning how to use as feature correctly.
I personally never do get interface with topology, as that would reset it all to what fw "thinks" should be defined...its way safer (in my opinion) to do without topology and as long as you set it per routing option, you are good to go, since if something changes on that interface subnet, no need to do anything, it would update it for you.
Below is what Im referring to and its always good idea to assign the zone as well.
Also, in simple words, anti spoofing is there so say if interface subnet is on 10.10.10.0/24 and traffic comes from 192.x.x something, it would get dropped.
One of the core security features of the product is Anti-Spoofing.
For anti-spoofing to work, topology must be defined.
The topology includes all the networks reachable from that interface.
This can either be done manually or as part of "Get Interfaces with Topology" though you should only use this option before the gateway goes into production.
This has been discussed here among other places: https://community.checkpoint.com/t5/General-Topics/Get-interface/m-p/246503
When you get interfaces with topology, Check Point will automatically generate objects for the anti-spoofing settings.
They will be linked to the interfaces, but may not be visible in the Object Tree. Check:
sk126872 - Some Network objects are not visible in the SmartConsole object list
Something to be aware of if you want to use these objects in a policy.
Since I encountered problems here and there a long time ago when importing with topology, I have never done it again since then, and the point mentioned that objects are automatically created that I create myself has prevented me from doing it again to this day. But for beginners, I would always recommend importing with topology first and learning how to use as feature correctly.
I personally never do get interface with topology, as that would reset it all to what fw "thinks" should be defined...its way safer (in my opinion) to do without topology and as long as you set it per routing option, you are good to go, since if something changes on that interface subnet, no need to do anything, it would update it for you.
Below is what Im referring to and its always good idea to assign the zone as well.
Also, in simple words, anti spoofing is there so say if interface subnet is on 10.10.10.0/24 and traffic comes from 192.x.x something, it would get dropped.
With dynamic routes, better to either turn it off, not really recommended or as you have said use "Network defined by routes", but ultimately need to keep an eye on it, and would suggest not using prevent mode straight away if you have critical services.
100%
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 25 | |
| 11 | |
| 11 | |
| 7 | |
| 7 | |
| 6 | |
| 6 | |
| 6 | |
| 6 | |
| 5 |
Tue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceWed 13 May 2026 @ 11:00 AM (EDT)
TechTalk: The State of Ransomware Q1 2026: Key Trends and Their ImpactThu 14 May 2026 @ 07:00 PM (EEST)
Under the Hood: Presentando Check Point Cloud Firewall como ServicioTue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceTue 19 May 2026 @ 06:00 PM (IDT)
AI Security Masters E8 - Claude Mythos: New Era in Cyber SecurityAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY