[PaloAlto] Firewall Traffic Monitor Filtering/Syntax - 트래픽 필터링, 구문 검색 방법

Basics of Traffic Monitor Filtering

 

1. Environment

- Supported PAN-OS.
- Palo Alto Firewall.

 

2. Resolution

When Trying to search for a log with a source IP, destination IP or any other flags, Filters can be used.

The filters need to be put in the search section under GUI: Monitor > Logs > Traffic (or other logs).

 

This document demonstrates several methods of filtering and looking for specific types of traffic on Palo Alto Networks firewalls. Categories of filters include host, zone, port, or date/time.

 

At the end of the list, we include a few examples that combine various filters for more comprehensive searching.

 

Traffic Monitor Filtering

3. Examples

 

Host Traffic Filter Examples

1) From Host a.a.a.a

(addr.src in a.a.a.a)
example: (addr.src in 1.1.1.1)
Explanation: shows all traffic from host ip address that matches 1.1.1.1 (addr.src in a.a.a.a)

 

2) To Host b.b.b.b

(addr.dst in b.b.b.b)
example: (addr.dst in 2.2.2.2)
Explanation: shows all traffic with a destination address of a host that matches 2.2.2.2

 

3) From Host a.a.a.a to Host b.b.b.b

(addr.src in a.a.a.a) and (addr.dst in b.b.b.b)
example: (addr.src in 1.1.1.1) and (addr.dst in 2.2.2.2)
Explanation: shows all traffic coming from a host with an IP address of 1.1.1.1 and going to a host destination address of 2.2.2.2

 

4) To Host Range

Note that you cannot specify an actual range but can use CIDR notation to specify a network range of addresses
(addr.src in a.a.a.a/CIDR)
example: (addr.src in 10.10.10.2/30)
Explanation: shows all traffic coming from addresses ranging from 10.10.10.1 - 10.10.10.3.

 

5) To or From Host a.a.a.a

(addr in a.a.a.a)
example: (addr in 1.1.1.1)
Explanation: shows all traffic with a source OR destination address of a host that matches 1.1.1.1

 

6) To display all traffic except to and from Host a.a.a.a

!(addr in a.a.a.a)
example: !(addr in 1.1.1.1)
Explanation: The "!" symbol is "not" opeator.

This means show all traffic with a source OR destination address not matching 1.1.1.1

 

Zone Traffic Filter Examples:

1) From Zone zone_a

(zone.src eq zone_a)
example: (zone.src eq PROTECT)
Explanation: shows all traffic coming from the PROTECT zone

 

2) To Zone zone_b

(zone.dst eq zone_b)
example: (zone.dst eq OUTSIDE)
Explanation: shows all traffic going out the OUTSIDE zone

 

3) From Zone zone_a to Zone zone_b

(zone.src eq zone_a) and (zone.dst eq zone_b)
example: (zone.src eq PROTECT) and (zone.dst eq OUTSIDE)
Explanation: shows all traffic traveling from the PROTECT zone and going out the OUTSIDE zone

 

 

Port Traffic Filter Examples:

1) From Port aa

(port.src eq aa)
example: (port.src eq 22)
Explanation: shows all traffic traveling from source port 22

 

2) To Port aa

(port.dst eq bb)
example: (port.dst eq 25)
Explanation: shows all traffic traveling to destination port 25

 

3) From Port aa TO Port bb

(port.src eq aa) and (port.dst eq bb)
example: (port.src eq 23459) and (port.dst eq 22)
Explanation: shows all traffic traveling from source port 23459 and traveling to destination port 22

 

4) From All Ports Less Than or Equal To Port aa

(port.src leq aa)
example: (port.src leq 22)
Explanation: shows all traffic traveling from source ports 1-22

 

5) From All Ports Greater Than Or Equal To Port aa

(port.src geq aa)
example: (port.src geq 1024)
Explanation: shows all traffic traveling from source ports 1024 - 65535

 

6) To All Ports Less Than Or Equal To Port aa

(port.dst leq aa)
example: (port.dst leq 1024)
Explanation: shows all traffic traveling to destination ports 1-1024

 

7) To All Ports Greater Than Or Equal To Port aa

(port.dst geq aa)
example: (port.dst geq 1024)
Explanation: shows all traffic traveling to destination ports 1024-65535

 

8) From Port Range aa Through bb

(port.src geq aa) and (port.src leq bb)
example: (port.src geq 20) and (port.src leq 53)
Explanation: shows all traffic traveling from source port range 20-53

 

9) To Port Range aa Through bb

(port.dst geq aa) and (port.dst leq bb)
example: (port.dst geq 1024) and (port.dst leq 13002)
Explanation: shows all traffic traveling to destination ports 1024 - 13002

 

 

Date/Time Traffic Filter Examples:

1) All Traffic for a Specific Date yyyy/mm/dd And Time hh:mm:ss

(receive_time eq 'yyyy/mm/dd hh:mm:ss')
example: (receive_time eq '2015/08/31 08:30:00')
Explanation: shows all traffic that was received on August 31, 2015 at 8:30am

 

2) All Traffic Received On Or Before The Date yyyy/mm/dd And Time hh:mm:ss

(receive_time leq 'yyyy/mm/dd hh:mm:ss')
example: (receive_time leq '2015/08/31 08:30:00')
Explanation: shows all traffic that was received on or before August 31, 2015 at 8:30am

 

3) All Traffic Received On Or After The Date yyyy/mm/dd And Time hh:mm:ss

(receive_time geq 'yyyy/mm/dd hh:mm:ss')
example: (receive_time geq '2015/08/31 08:30:00')
Explanation: shows all traffic that was received on or after August 31, 2015 at 8:30am

 

4) All Traffic Received Between The Date-Time Range Of yyyy/mm/dd hh:mm:ss and YYYY/MM/DD HH:MM:SS

(receive_time geq 'yyyy/mm/dd hh:mm:ss') and (receive_time leq 'YYYY/MM/DD HH:MM:SS')
example: (receive_time geq '2015/08/30 08:30:00') and (receive_time leq '2015/08/31 01:25:00')
Explanation: shows all traffic that was received between August 30, 2015 8:30am and August 31, 2015 01:25 am

 

 

Interface Traffic Filter Examples:

1) All Traffic Inbound On Interface ethernet1/x

(interface.src eq 'ethernet1/x')
example: (interface.src eq 'ethernet1/2')
Explanation: shows all traffic that was received on the PA Firewall interface Ethernet 1/2

 

2) All Traffic Outbound On Interface ethernet1/x

(interface.dst eq 'ethernet1/x')
example: (interface.dst eq 'ethernet1/5')
Explanation: shows all traffic that was sent out on the PA Firewall interface Ethernet 1/5

 

 

Allowed/Denied Traffic Filter Examples:

1) All Traffic That Has Been Allowed By The Firewall Rules

(action eq allow)
OR
(action neq deny)
example: (action eq allow)
Explanation: shows all traffic allowed by the firewall rules. Placing the letter 'n' in front of 'eq' means 'not equal to,' so anything not equal to 'deny' is displayed, which is any allowed traffic.

 

2) All Traffic Denied By The FireWall Rules.

(action eq deny)
OR
(action neq allow)

example: (action eq deny)
Explanation: shows all traffic denied by the firewall rules. Placing the letter 'n' in front of 'eq' means 'not equal to,' so anything not equal to 'allow' is displayed, which is any denied traffic.

 

Combining Traffic Filter Examples:

1) All Traffic From Zone Outside And Network 10.10.10.0/24 TO Host Address 20.20.20.21 In The Protect Zone:

(zone.src eq OUTSIDE) and (addr.src in 10.10.10.0/24) and (addr.dst in 20.20.20.21) and (zone.dst eq PROTECT)

 

2) All Traffic From Host 1.2.3.4 to Host 5.6.7.8 For The Time Range 8/30/2015 -08/31/2015

(addr.src in 1.2.3.4) and (addr.dst in 5.6.7.8) and (receive_time geq '2015/08/30 00:00:00') and (receive_time leq '2015/08/31 23:59:59')

 

 

 

4. Additional Information

- A good practice when drilling down into the traffic log when the search starts off with little to no information, is to start from least specific and add filters to more specific.

- When troubleshooting, instead of directly filtering for a specific app, try filtering for all apps except the ones you know you don't need, for example '(app neq dns) and (app neq ssh)'

- You can also throw in protocols you don't need (proto neq udp) or IP ranges ( addr.src notin 192.168.0.0/24 )

- This practice helps you drill down to the traffic of interest without losing an overview by searching too narrowly from the start.

 

- 검색이 거의 또는 전혀 정보 없이 시작될 때 트래픽 로그를 자세히 살펴볼 때 좋은 방법은 가장 구체적이지 않은 것부터 시작하여 더 구체적인 것에 필터를 추가하는 것입니다.

- 문제를 해결할 때 특정 앱을 직접 필터링하는 대신, 필요하지 않은 앱을 제외한 모든 앱을 필터링해 보세요(예: '(앱 neq dns) 및 (앱 neq ssh)').

- 필요하지 않은 프로토콜(proto neq udp)이나 IP 범위(addr.src notin 192.168.0.0/24)를 추가할 수도 있습니다.

- 이 연습은 처음부터 너무 좁은 범위로 검색하여 전반적인 개요를 놓치지 않으면서도 관심 있는 트래픽을 자세히 파악하는 데 도움이 됩니다.

 

 

 

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSlCAK

Basics of Traffic Monitor Filtering

 

 

---

[PaloAlto] Firewall Cloud Identity Engine에 대한 SCIM 커넥터 구성 - Azure Active Directory, PingFederate, Okta Directory

[PaloAlto] Firewall Cloud Identity Engine에 대한 SCIM 커넥터 구성 - Azure Active Directory, PingFederate, Okta Directory

[PaloAlto] Firewall Packet Capture (패킷 캡쳐) 종류 및 12단계 순서 - pcap, 커스텀 패킷, 위협 패킷, 애플리케이션 패킷, 관리 인터페이스 패킷

[PaloAlto] Firewall Packet Capture (패킷 캡쳐) 종류 및 12단계 순서 - pcap, 커스텀 패킷, 위협 패킷, 애플리