Skip to main content

Python – Orphaned Object Finder

My next Python project can help you find non-used objects in your ASA configuration. I saw it’s very common to update ASA’s configuration, add network objects, modify ACLs but no one remember about objects which are not used anymore. The only one time when people review the config is migration from one vendor to another one. My script can help you in keeping config clean from non-used objects.

This is a config I will work with:

[hzw@zeus oof]$ cat acl2.txt
object network 172.16.0.0_16
 subnet 172.16.0.0 255.255.0.0
object network 192.168.1.0_24
 subnet 192.168.1.0 255.255.254.0
object network 192.168.1.0_23
 subnet 192.168.1.0 255.255.254.0
object network 172.16.250.5
 host 172.16.250.5
object network 172.16.250.0_24
 subnet 172.16.250.0 255.255.255.0
object network 172.16.250.5_
 host 172.16.250.5
object network 172.16.250.110
 host 172.16.250.110
object network 10.10.0.100_h
 host 10.10.0.100
object-group network TEST1
 network-object object 172.16.250.5
 network-object object 172.16.250.0_24
 network-object object 172.16.250.5_
 network-object object 172.16.250.110
 network-object 172.16.250.0 255.255.255.0
object-group network TEST2
 network-object host 10.10.0.100
 network-object host 10.10.0.20
 network-object host 172.16.250.5
 network-object 192.168.1.0 255.255.255.0
 network-object object 192.168.1.0_24
 network-object object 192.168.1.0_23
[hzw@zeus oof]$
 
 
and two object networks are not used by any ‘network-object object’. You can review Python source code here: https://github.com/hzw7/oof
As usual the script has two modes: normal one with final output only and debug one with all steps the script takes.

This is an output from a normal mode:

[hzw@zeus oof]$ python oof-0.01.py acl2.txt

Orphan objects:
[1, '172.16.0.0_16']
[15, '10.10.0.100_h']
[hzw@zeus oof]$
 
 
and from a debug mode:
 
 
[hzw@zeus oof]$ python oof-0.01.py acl2.txt -d
object network -> OBJECT NAME: 172.16.0.0_16
object network -> OBJECT NAME: 192.168.1.0_24
object network -> OBJECT NAME: 192.168.1.0_23
object network -> OBJECT NAME: 172.16.250.5
object network -> OBJECT NAME: 172.16.250.0_24
object network -> OBJECT NAME: 172.16.250.5_
object network -> OBJECT NAME: 172.16.250.110
object network -> OBJECT NAME: 10.10.0.100_h
|-network-object object -> NETWORK-OBJECT OBJECT NAME: 172.16.250.5
|-network-object object -> NETWORK-OBJECT OBJECT NAME: 172.16.250.0_24
|-network-object object -> NETWORK-OBJECT OBJECT NAME: 172.16.250.5_
|-network-object object -> NETWORK-OBJECT OBJECT NAME: 172.16.250.110
|-network-object object -> NETWORK-OBJECT OBJECT NAME: 192.168.1.0_24
|-network-object object -> NETWORK-OBJECT OBJECT NAME: 192.168.1.0_23




Network-object table:
[18, '172.16.250.5']
[19, '172.16.250.0_24']
[20, '172.16.250.5_']
[21, '172.16.250.110']
[28, '192.168.1.0_24']
[29, '192.168.1.0_23']







Object network table:
[1, '172.16.0.0_16']
[3, '192.168.1.0_24']
[5, '192.168.1.0_23']
[7, '172.16.250.5']
[9, '172.16.250.0_24']
[11, '172.16.250.5_']
[13, '172.16.250.110']
[15, '10.10.0.100_h']
togn i
172.16.250.5
ton j
172.16.0.0_16
ton j
192.168.1.0_24
ton j
192.168.1.0_23
ton j
172.16.250.5
removed

ton j
172.16.250.5_
ton j
172.16.250.110
ton j
10.10.0.100_h
togn i
172.16.250.0_24
ton j
172.16.0.0_16
ton j
192.168.1.0_24
ton j
192.168.1.0_23
ton j
172.16.250.0_24
removed

ton j
172.16.250.110
ton j
10.10.0.100_h
togn i
172.16.250.5_
ton j
172.16.0.0_16
ton j
192.168.1.0_24
ton j
192.168.1.0_23
ton j
172.16.250.5_
removed

ton j
10.10.0.100_h
togn i
172.16.250.110
ton j
172.16.0.0_16
ton j
192.168.1.0_24
ton j
192.168.1.0_23
ton j
172.16.250.110
removed

togn i
192.168.1.0_24
ton j
172.16.0.0_16
ton j
192.168.1.0_24
removed

ton j
10.10.0.100_h
togn i
192.168.1.0_23
ton j
172.16.0.0_16
ton j
192.168.1.0_23
removed

Orphan objects:
[1, '172.16.0.0_16']
[15, '10.10.0.100_h']
[hzw@zeus oof]$ 
 
 
Final result “Orphaned objects:” is the same but you have many additional steps where you see how the script run.
https://github.com/hzw7/oof


 


 

Labels:

Comments

Post a Comment

Popular posts from this blog

What should you know about HA 'override enabled' setting on Fortigate?

High availability is mandatory in most of today's network designs. Only very small companies or branches can run their business without redundancy. When you have Fortigate firewall in your network you have many options to increase network availability. You can use Fortigate Clustering Protocol ( FGCP ) or Virtual Router Redundancy Protocol ( VRRP ). FGCP has two modes: 'override' disabled (default) and 'override' enabled . I'm not going to explain how to set up HA as you can find many resources on Fortinet websites: https://cookbook.fortinet.com/high-availability-two-fortigates-56/ https://cookbook.fortinet.com/high-availability-with-fgcp-56/ Let's recap what is the main difference between them. The default HA setting is 'override' disabled and this is an order of selection an active unit: 1) number of monitored interfaces - when both units have the same number of working (up) interfaces check next parameter 2) HA uptime - an ...
8 comments
Read more

FortiGate and GRE tunnel

Recently I worked on one project where a client requested to re-route web traffic to the GRE tunnel to perform traffic inspection. I would like to share with you what is required if you configure it on FortiGate. We need a new GRE interface and policy base routing (PBR) to change the route for specific source IPs. Of course you need firewall policies to permit the traffic. Let's start with GRE interface. Unfortunately you can't configure it using the GUI, only CLI is the option: config system gre-tunnel edit "gre1" set interface "port1" set local-gw 55.55.55.55 set remote-gw 44.44.44.44 next end When the end peer is Cisco router, you need to set the IP for the GRE interface: config system interface edit gre1 set ip 192.168.10.10 255.255.255.255 set remote-ip192.168.10.20 end In next step we need to fix routing. We need the alternate path via GRE but to keep the route in the active routing table you need to set the same AD (adminis...
Post a Comment
Read more

Inpection of asymmetric sessions on FortiGate

There is one feature available on FortiGate, and I think you should know it, as it modifies a bit what we know about stateful firewalls. In past every packet was treated individually and you had to create policies in both directions. With stateful firewalls we can track connections, and by checking couple of attributes, we can treat them as part of the same session. For example when you initiate connection from a host1 to host2, the returning connection from host2 to host1 will be treated as part of the same connection (session). They have to have the same source/destination and destination/source IPs, port numbers and interfaces.There is an exception from this rule and FortiGate in some specific cases can accept connections on port which was not used in the initial connection. Let me explain how it works on the below example:      The host1 has a default gateway on R1 (10.0.1.2), but you may notice that it is not the optimal path to host2 subnet. When we analyze ...
1 comment
Read more