- Products
- Learn
- Local User Groups
- Partners
- More
The Great Exposure Reset
24 February 2026 @ 5pm CET / 11am EST
CheckMates Fest 2026
Watch Now!AI Security Masters
Hacking with AI: The Dark Side of Innovation
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 |
|---|---|
| 56 | |
| 44 | |
| 16 | |
| 14 | |
| 14 | |
| 11 | |
| 10 | |
| 10 | |
| 9 | |
| 8 |
Thu 12 Feb 2026 @ 05:00 PM (CET)
AI Security Masters Session 3: AI-Generated Malware - From Experimentation to Operational RealityFri 13 Feb 2026 @ 10:00 AM (CET)
CheckMates Live Netherlands - Sessie 43: Terugblik op de Check Point Sales Kick Off 2026Thu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesThu 12 Feb 2026 @ 05:00 PM (CET)
AI Security Masters Session 3: AI-Generated Malware - From Experimentation to Operational RealityFri 13 Feb 2026 @ 10:00 AM (CET)
CheckMates Live Netherlands - Sessie 43: Terugblik op de Check Point Sales Kick Off 2026Thu 19 Feb 2026 @ 03:00 PM (EST)
Americas Deep Dive: Check Point Management API Best PracticesAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY