Proxy Logs
Also called Web Proxy Logs.
Records of outbound web requests passing through a forward proxy.
What it is
Proxy logs are produced by forward web proxies that broker users' outbound HTTP and HTTPS traffic, recording requested URLs, hosts, methods, status codes, user agents, bytes transferred, and frequently the associated user. They sit at the boundary between internal clients and the internet.
Why it matters
They give a per-request view of web activity that is ideal for spotting C2 over HTTP, suspicious downloads, and exfiltration to unusual destinations, while tying activity back to specific users. Where TLS is intercepted, proxies expose full URLs and content that flow logs alone cannot.
In practice
Proxy logs revealing repeated POSTs of small, identically sized payloads to a newly registered domain: the fingerprint of an HTTP beacon.
What to look for
- Requests to newly registered or uncategorized domains.
- Uploads to file sharing or paste sites.
- User agents that do not match installed browsers.
Common mistake
Assuming all traffic goes through the proxy. Check for direct outbound connections that skip it.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Event Log Reader
Read a binary .evtx file or pasted event XML, with logon types, NTSTATUS codes and the Keywords mask decoded.
- Linux Case
A server making outbound connections nobody can explain: read its audit log, journal and scheduled jobs, and say who did what.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Wireshark Open source
Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.
-
Zeek Open source
Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.
-
Suricata Open source
An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.
-
Arkime Open source
Indexes full packet capture at scale so you can search and pull sessions later. Our notes.
Read next
- Web Access Logs: Server-side records of every HTTP request a web server handles.
- DNS Logging: Recording the domain-name lookups that hosts request and resolve.
- Firewall Logs: Records of network connections a firewall allowed or denied.