conn.log
Zeek's log of network connections, with one line per connection showing who talked to whom, on which ports, for how long and how many bytes each way.
In more detail
By default it is tab-separated text whose column names appear in a #fields header line, and a dash marks a field with no value, so parsers should read the header rather than assume column positions. Useful fields include id.orig_h and id.resp_h for the two addresses, orig_bytes and resp_bytes for the data each side sent, and local_orig and local_resp for whether each end is inside the local network. Adding up bytes per source and destination is a simple way to spot bulk data leaving the site.
Examples
#fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p proto service duration orig_bytes resp_bytes conn_state local_orig local_resp ...def count(value): return 0 if value == "-" else int(value) # Zeek writes - for an unset fieldRelated terms
- Zeek — An open-source network monitor that passively watches traffic and writes detailed logs of connections and protocols for security analysis.
- orig_bytes — The conn.log field counting the payload bytes sent by the side that opened a connection; resp_bytes counts what the other side sent back.
- egress monitoring — Watching traffic that leaves the network, especially how much goes where and when, to spot data being taken out.
Taught in
- Data Loss Prevention & Egress Monitoring — Cybersecurity Fundamentals, GRC & Cryptography