Policy compare
Policies against each other · built Sun Nov 22 2026 04:16 PMEach 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.
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 name | Where and what |
|---|---|
| Block-Malicious-In | Atlanta 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-Out | Atlanta 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-HQ | Atlanta 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-Branch | Atlanta 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-Cloud | Atlanta 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-NVR | Charlotte 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-Backup | Charlotte 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-Historian | Charlotte 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-HMI | Charlotte 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-WMS | Atlanta 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-Media | Atlanta 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-SaaS | Atlanta 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-Internet | Atlanta 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-SIP | Atlanta 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
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Azure Eastclean
5 enabled policies: none shadows, duplicates or conflicts with another.
Azure Westclean
5 enabled policies: none shadows, duplicates or conflicts with another.
Boston1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Charlotte1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Charlotte OTclean
8 enabled policies: none shadows, duplicates or conflicts with another.
Chicago1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Dallas1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Denver1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Detroit1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Detroit OTclean
9 enabled policies: none shadows, duplicates or conflicts with another.
Houston1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Houston OTclean
8 enabled policies: none shadows, duplicates or conflicts with another.
Los Angeles1 shadowed · 1 partly overlapped
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
| Partly overlapped | 3 | Users-Internet | 2 | Block-Malicious-Out | policy 2 above it denys part of the same traffic |
Miami1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Minneapolis1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
New York1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 2 | Users-Finance-SaaS | 1 | Users-Internet | policy 1 above it matches all of this one's traffic |
Philadelphia1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |
Phoenix1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 3 | Users-Finance-SaaS | 2 | Users-Internet | policy 2 above it matches all of this one's traffic |
Seattle1 shadowed
| Finding | Policy | Name | Against | Its name | Why |
|---|---|---|---|---|---|
| Shadowed | 4 | Users-Finance-SaaS | 3 | Users-Internet | policy 3 above it matches all of this one's traffic |