Demo – made-up data. Northline, the sites and the numbers are invented. Notices 3.5 – work in progress
VANTAGENorthline
Collected✕7 sites need attention

Policy compare

Policies against each other · built Sun Nov 22 2026 04:16 PM

Each FortiGate's firewall policies checked against the ones above them, in table order: a policy that can never match, one whose action is never applied, two that do the same, and two that could be one. Then the same policy name doing different things at different sites. Fold by site; start collapsed. Does not colour a site.

0 conflict15 shadowed0 duplicate1 partly overlapped0 could merge
How policies are compared

From show firewall policy, show firewall addrgrp and show firewall service group, already collected. Only enabled policies count. Address and service groups are opened up; all, ALL, any and always cover everything. Objects are compared by name: two address objects for overlapping subnets are not seen as the same, so a real shadow through overlapping subnets is not found here. Before removing a policy, check its hit count (Pulse, with the API reads on) and the change window. Nothing is sent to the FortiGate.

Across sites: the same name, different rules14
Policy nameWhere and what
Block-Malicious-InAtlanta policy 1: deny – srcintf wan1,wan2; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Azure East policy 1: deny – srcintf wan1,wan2; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Azure West policy 1: deny – srcintf wan1,wan2; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Boston policy 1: deny – srcintf wan1,wan2; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Charlotte OT policy 1: deny – srcintf to-charlotte; dstintf iot; srcaddr ; dstaddr ; service ; schedule always
Charlotte policy 1: deny – srcintf wan1,wan2; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Chicago policy 1: deny – srcintf wan1,wan2,wan3,wan4; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Dallas policy 1: deny – srcintf wan1,wan2; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Denver policy 1: deny – srcintf wan1,wan2; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Detroit OT policy 1: deny – srcintf to-detroit; dstintf iot; srcaddr ; dstaddr ; service ; schedule always
Detroit policy 1: deny – srcintf wan1,wan2; dstintf any; srcaddr ; dstaddr ; service ; schedule always
Houston OT policy 1: deny – srcintf to-houston; dstintf iot; srcaddr ; dstaddr ; service ; schedule always
Block-Malicious-OutAtlanta policy 2: deny – srcintf iot,servers,users; dstintf wan1,wan2; srcaddr LAN-IoT,LAN-Servers,LAN-Users; dstaddr ; service ; schedule always
Azure East policy 2: deny – srcintf port2; dstintf wan1,wan2; srcaddr Azure-VNet; dstaddr ; service ; schedule always
Azure West policy 2: deny – srcintf port2; dstintf wan1,wan2; srcaddr Azure-VNet; dstaddr ; service ; schedule always
Boston policy 2: deny – srcintf iot,servers,users; dstintf wan1,wan2; srcaddr LAN-IoT,LAN-Servers,LAN-Users; dstaddr ; service ; schedule always
Charlotte OT policy 2: deny – srcintf iot,servers; dstintf to-charlotte; srcaddr LAN-IoT,LAN-Servers; dstaddr ; service ; schedule always
Charlotte policy 2: deny – srcintf iot,servers,users; dstintf wan1,wan2; srcaddr LAN-IoT,LAN-Servers,LAN-Users; dstaddr ; service ; schedule always
Chicago policy 2: deny – srcintf iot,servers,users; dstintf wan1,wan2,wan3,wan4; srcaddr LAN-IoT,LAN-Servers,LAN-Users; dstaddr ; service ; schedule always
Dallas policy 2: deny – srcintf iot,servers,users; dstintf wan1,wan2; srcaddr LAN-IoT,LAN-Servers,LAN-Users; dstaddr ; service ; schedule always
Denver policy 2: deny – srcintf iot,servers,users; dstintf wan1,wan2; srcaddr LAN-IoT,LAN-Servers,LAN-Users; dstaddr ; service ; schedule always
Detroit OT policy 2: deny – srcintf iot,servers; dstintf to-detroit; srcaddr LAN-IoT,LAN-Servers; dstaddr ; service ; schedule always
Detroit policy 2: deny – srcintf iot,servers,users; dstintf wan1,wan2; srcaddr LAN-IoT,LAN-Servers,LAN-Users; dstaddr ; service ; schedule always
Houston OT policy 2: deny – srcintf iot,servers; dstintf to-houston; srcaddr LAN-IoT,LAN-Servers; dstaddr ; service ; schedule always
Branch-to-HQAtlanta policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Boston policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Charlotte policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Dallas policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Denver policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Detroit policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Houston policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Los Angeles policy 8: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,SIP-Trunk,SMB; schedule always
Miami policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Minneapolis policy 7: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
New York policy 7: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
Philadelphia policy 9: accept – srcintf users,voice; dstintf to-chicago,to-chicago-b; srcaddr LAN-Users,LAN-Voice; dstaddr HQ-Servers; service HQ-ERP,HTTPS,MS-SQL,RTP-Voice,SIP-Trunk,SMB; schedule always
HQ-to-BranchAtlanta policy 10: accept – srcintf to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,SSH; schedu
Boston policy 10: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Charlotte policy 10: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Dallas policy 10: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Denver policy 10: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Detroit policy 10: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Houston policy 10: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Los Angeles policy 9: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Miami policy 10: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Minneapolis policy 8: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
New York policy 8: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
Philadelphia policy 10: accept – srcintf to-chicago,to-chicago-b; dstintf cameras,printers,servers,users,voice; srcaddr HQ-Mgmt; dstaddr LAN-Cameras,LAN-Printers,LAN-Servers,LAN-Users,LAN-Voice; service Collector-API,HTTPS,PING,SNMP,
IoT-CloudAtlanta policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Boston policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Charlotte policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Chicago policy 7: accept – srcintf iot; dstintf wan1,wan2,wan3,wan4; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Dallas policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Denver policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Detroit policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Houston policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Los Angeles policy 6: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Miami policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
New York policy 5: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
Philadelphia policy 7: accept – srcintf iot; dstintf wan1,wan2; srcaddr LAN-IoT; dstaddr IoT-Cloud; service HTTPS; schedule always
OT-Cameras-to-Plant-NVRCharlotte OT policy 7: accept – srcintf cameras; dstintf to-charlotte; srcaddr LAN-Cameras; dstaddr Plant-NVR; service Axis-Video; schedule always
Detroit OT policy 7: accept – srcintf cameras; dstintf to-detroit; srcaddr LAN-Cameras; dstaddr Plant-NVR; service Axis-Video; schedule always
Houston OT policy 7: accept – srcintf cameras; dstintf to-houston; srcaddr LAN-Cameras; dstaddr Plant-NVR; service Axis-Video; schedule always
OT-Servers-BackupCharlotte OT policy 8: accept – srcintf servers; dstintf to-charlotte; srcaddr LAN-Servers; dstaddr Plant-Backup; service Backup-Veeam; schedule backup-window
Detroit OT policy 8: accept – srcintf servers; dstintf to-detroit; srcaddr LAN-Servers; dstaddr Plant-Backup; service Backup-Veeam; schedule backup-window
Houston OT policy 8: accept – srcintf servers; dstintf to-houston; srcaddr LAN-Servers; dstaddr Plant-Backup; service Backup-Veeam; schedule backup-window
OT-to-Plant-HistorianCharlotte OT policy 4: accept – srcintf iot; dstintf to-charlotte; srcaddr OT-PLCs; dstaddr Plant-Historian; service EtherNet-IP,Modbus-TCP; schedule always
Detroit OT policy 4: accept – srcintf iot; dstintf to-detroit; srcaddr OT-PLCs; dstaddr Plant-Historian; service EtherNet-IP,Modbus-TCP; schedule always
Houston OT policy 4: accept – srcintf iot; dstintf to-houston; srcaddr OT-PLCs; dstaddr Plant-Historian; service EtherNet-IP,Modbus-TCP; schedule always
Plant-to-OT-HMICharlotte OT policy 5: accept – srcintf to-charlotte; dstintf iot; srcaddr Plant-Engineering; dstaddr OT-HMIs; service HTTPS,VNC-HMI; schedule always
Detroit OT policy 5: accept – srcintf to-detroit; dstintf iot; srcaddr Plant-Engineering; dstaddr OT-HMIs; service HTTPS,VNC-HMI; schedule always
Houston OT policy 5: accept – srcintf to-houston; dstintf iot; srcaddr Plant-Engineering; dstaddr OT-HMIs; service HTTPS,VNC-HMI; schedule always
Scanners-WMSAtlanta policy 13: accept – srcintf users; dstintf servers; srcaddr Scan-Guns; dstaddr Local-WMS; service FTP-Scanner,HTTPS; schedule always
Dallas policy 13: accept – srcintf users; dstintf servers; srcaddr Scan-Guns; dstaddr Local-WMS; service FTP-Scanner,HTTPS; schedule always
Denver policy 13: accept – srcintf users; dstintf servers; srcaddr Scan-Guns; dstaddr Local-WMS; service FTP-Scanner,HTTPS; schedule night-shift
Seattle policy 13: accept – srcintf users; dstintf servers; srcaddr Scan-Guns; dstaddr Local-WMS; service FTP-Scanner,HTTPS; schedule always
Teams-MediaAtlanta policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Boston policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Charlotte policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Chicago policy 6: accept – srcintf users,voice; dstintf wan1,wan2,wan3,wan4; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Dallas policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Denver policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Detroit policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Houston policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Miami policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
New York policy 4: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Philadelphia policy 6: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Phoenix policy 5: accept – srcintf users,voice; dstintf wan1,wan2; srcaddr LAN-Users,LAN-Voice; dstaddr MS365-Teams-Optimize-1,MS365-Teams-Optimize-2; service HTTPS,MS-Teams-Media; schedule always
Users-Finance-SaaSAtlanta policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Boston policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Charlotte policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Chicago policy 4: accept – srcintf users; dstintf wan1,wan2,wan3,wan4; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Dallas policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Denver policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Detroit policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Houston policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Los Angeles policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Miami policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Minneapolis policy 4: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
New York policy 2: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr Bank-Portal,Payroll-Provider; service HTTPS; schedule always
Users-InternetAtlanta policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Boston policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Charlotte policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Chicago policy 3: accept – srcintf users; dstintf wan1,wan2,wan3,wan4; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Dallas policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Denver policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Detroit policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Houston policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Los Angeles policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service ALL; schedule always
Miami policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Minneapolis policy 3: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
New York policy 1: accept – srcintf users; dstintf wan1,wan2; srcaddr LAN-Users; dstaddr all; service DNS,HTTP,HTTPS,NTP,PING; schedule always
Voice-SIPAtlanta policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Boston policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Charlotte policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Chicago policy 5: accept – srcintf voice; dstintf wan1,wan2,wan3,wan4; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Dallas policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Denver policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Detroit policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Houston policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Los Angeles policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service SIP-Trunk; schedule always
Miami policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
Minneapolis policy 5: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always
New York policy 3: accept – srcintf voice; dstintf wan1,wan2; srcaddr LAN-Voice; dstaddr SIP-Provider; service RTP-Voice,SIP-Trunk; schedule always

The name says these are the same rule; the configuration says they differ. Either one site has drifted, or the name should be different. Golden drift compares against a baseline.

Atlanta1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Azure Eastclean

5 enabled policies: none shadows, duplicates or conflicts with another.

Rebuild · Object hygiene

Azure Westclean

5 enabled policies: none shadows, duplicates or conflicts with another.

Rebuild · Object hygiene

Boston1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Charlotte1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Charlotte OTclean

8 enabled policies: none shadows, duplicates or conflicts with another.

Rebuild · Object hygiene

Chicago1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Dallas1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Denver1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Detroit1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Detroit OTclean

9 enabled policies: none shadows, duplicates or conflicts with another.

Rebuild · Object hygiene

Houston1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Houston OTclean

8 enabled policies: none shadows, duplicates or conflicts with another.

Rebuild · Object hygiene

Los Angeles1 shadowed · 1 partly overlapped
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic
Partly overlapped3Users-Internet2Block-Malicious-Outpolicy 2 above it denys part of the same traffic

Rebuild · Object hygiene

Miami1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Minneapolis1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

New York1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed2Users-Finance-SaaS1Users-Internetpolicy 1 above it matches all of this one's traffic

Rebuild · Object hygiene

Philadelphia1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Phoenix1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed3Users-Finance-SaaS2Users-Internetpolicy 2 above it matches all of this one's traffic

Rebuild · Object hygiene

Seattle1 shadowed
FindingPolicyNameAgainstIts nameWhy
Shadowed4Users-Finance-SaaS3Users-Internetpolicy 3 above it matches all of this one's traffic

Rebuild · Object hygiene

Backups

philadelphia: no backup for 2 days – the FortiGate did not answer (site unreachable). See Change → Backups.