CSV Format for Cleanup Instances

Overview

When you select a cleanup type in the cleanup browser and click Export, you are prompted to download a CSV file with the details of the instances of the selected cleanup for all of the selected devices. The filename includes cleanup type, and the date and time of the export. The first few lines of the file include commented text that you can set a parser to ignore.

CSV File Contents

To view the CSV file properly, open it with a text editor.

The file includes file header, device header and instance sections:

  • File header: The first three lines in the file that identify the following:
    • Version of the export engine: "# version <VERSION NUMBER>"
    • Cleanup type name: "# cleanup type:","<NAME>"
    • Cleanup type code: "# cleanup code:","<CODE>" where the code has one letter and two digits, such as C05
  • Device header: The three lines before the instances from each device that identify the following:
    • Device name: "# device:","<DEVICE NAME>"
    • Device vendor name: "# type:","<VENDOR NAME>"
    • Instance format: The format for the instances for the cleanup type and vendor (see below)
  • Instance: Each rule or object that matches the criteria for the cleanup

For each cleanup type and vendor, the instance format is:

Disabled Rules

Vendor

Instance Format

Check Point

"POLICY PACKAGE","RULE NUMBER","CHECK POINT UID","RULE NAME","RULE COMMENT"

Cisco

"ACL NAME","ACE COMMENT"

Fortinet

"ZONE2ZONE","RULE NUMBER","RULE UID","RULE NAME","RULE COMMENT"

Juniper

"ZONE2ZONE","POLICY ID","POLICY NAME","POLICY COMMENT"

Palo Alto

"ZONE2ZONE","RULE NUMBER","RULE UID","RULE NAME","RULE COMMENT"

Duplicate Network Objects

The two lines before each set of duplicates are:

Vendor

Instance Format

All vendors

Number of duplicates and their matched properties

"DUPLICATE_<OBJECT TYPE>:<NUMBER OF DUPLICATES>","IP:<IP_ADDRESS>","MASK:<NETMASK>","<COMMENT>"

For example: "DUPLICATE_NETWORKS:2","IP:1.1.1.0","MASK:255.255.255.0",""

* For Juniper devices, the object's zone is added to the end of the instance.

Instance format

"OBJECT TYPE","OBJECT NAME","IP","COMMENT"

Where "OBJECT TYPE" is either: Host, Network

For example: "Network","LAN","1.1.1.0/255.255.255.0",""

Duplicate Services

The two lines before each set of duplicates are:

Vendor

Instance Format

All vendors

Number of duplicates and their matched properties

"DUPLICATE_<OBJECT TYPE>:<NUMBER OF DUPLICATES>","PROTOCOL:<PROTOCOL NUMBER>","Port:<PORT NUMBER>","SrcPort:<PORT NUMBER>","Timeout:<TIMEOUT VALUE>"

For example: "DUPLICATE_SERVICES: 4","PROTOCOL: 6","Port: 5060","","Timeout: 0"

Instance format

"OBJECT TYPE","OBJECT NAME","IP","COMMENT"

Where "OBJECT TYPE" is: Service

For example: "Service","sip-tcp","6","5060","Session Initiation Protocol over TCP"

Empty Groups

Vendor

Instance Format

All vendors

"OBJECT TYPE","OBJECT NAME",,"COMMENT"

Where "OBJECT TYPE" is either: Network group, Service Group

For example: "Network group","Group1","","Internal Group"

Fully Shadowed and Redundant Rules

Vendor

Instance Format

Check Point

"POLICY PACKAGE","RULE NUMBER","CHECK POINT UID","RULE NAME","RULE COMMENT"

Cisco

"ACL NAME","ACE COMMENT"

Fortinet

"ZONE2ZONE","RULE NUMBER","RULE UID","RULE NAME","RULE COMMENT"

Juniper

"ZONE2ZONE","JUNIPER POLICY ID","RULE NAME","RULE COMMENT"

Palo Alto

"ZONE2ZONE","RULE NUMBER","RULE UID","RULE NAME","RULE COMMENT"

Unattached Objects

Vendor

Instance Format

All vendors

"OBJECT TYPE","OBJECT NAME","IP","COMMENT"

Where "OBJECT TYPE" is either: Host, Network, Network group

For example: "Network","Network_2_IPV6","2001:400:1:1::100/64",""

Unused Objects

Vendor

Instance Format

All vendors

"OBJECT TYPE","OBJECT NAME","IP","COMMENT"

Where "OBJECT TYPE" is either: Host, Network, Network group

For example: "Network","Network_2_IPV6","2001:400:1:1::100/64",""