Firewall Support Center

How to Read Firewall Traffic Logs: Action, Bytes, NAT, and Session End Reason

Read firewall traffic logs as a connection story using timestamps, addresses, NAT, rule actions, byte counters, and session endings.

Who and whereTime, client, destination, and device context
Firewall handlingRule, action, interfaces, and NAT
Connection outcomePackets, bytes, duration, and ending
Illustrative troubleshooting view · Firewall Support Center

Read a connection as a sequence

A traffic log is a structured observation of a connection or packet event. Start by identifying the device and time, then the participants, then the handling decision and outcome. Product field names and logging behavior differ. The same workflow helps you read FortiGate, Palo Alto, and Check Point records without assuming that every field means exactly the same thing.

First identify the correct attempt

Match a user report to the timestamp, time zone, source address, destination, protocol, and port. Include the firewall or cluster member and virtual context. Shared public addresses, proxies, and VPN address pools can make the source look different from the user’s local interface. Correlate identity information with the connection time.

Use this reading order

Field groupQuestion to answer
Time and deviceIs this the correct attempt and firewall context?
Original addresses and portsWhich endpoint initiated which service?
Translated addresses and portsWhat addresses did the next segment see?
Rule, action, and zonesHow did the firewall classify and handle it?
Bytes, packets, and durationWas meaningful traffic observed in both directions?
End reason and related logsHow did this recorded session finish?

A synthetic example

Client: 10.10.10.25:51514
Destination: 10.40.20.50:443
Protocol: TCP
Rule action: allow
Client packets: several SYN attempts
Server packets observed: 0
Recorded ending: timeout

Interpret the example cautiously

This is an invented teaching record, not copied output from a device. It supports investigating an incomplete TCP connection. It does not prove that the server was offline or that the firewall dropped its response. Check whether the request left the firewall and whether any response returned on the expected path.

Understand NAT and counters

A source NAT field can identify the address visible to an internet service. A destination NAT field can identify the internal server behind a public service. Counter direction can be client/server or sent/received depending on the product and record. Consult the field definition before treating a zero counter as evidence about a specific interface.

Separate policy from the final result

Allow means the recorded traffic met the relevant handling decision. It does not establish a successful login, file transfer, or HTTP response. A reset, timeout, or security inspection event supplies additional context. Palo Alto’s end-reason field describes session termination and can select one reason when several apply. Read related threat, URL, decryption, or authentication logs when the transaction requires them.

Check logging coverage

A start record can appear before the session ends. An end record can arrive later. Some rules may not log the event you expect, and a collector can have ingestion delay. Confirm logging settings and device-local evidence before concluding that an absent search result means no packet arrived.

Build a repeatable incident note

Store the original record, the precise test, your interpretation, and one confirming packet or server observation. Redact user identifiers and internal details before public sharing. Compare the successful record after the repair with the original failure so the operational outcome is explicit.

Official references

Palo Alto traffic log field definitions

Palo Alto log types