Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Proxy logs record every web request leaving an organisation, with the user, the destination, and the volume. Analysed properly they expose command and control, exfiltration, and phishing clicks.

What Is Proxy Log Analysis?
A web proxy sits between your users and the internet, and writes a line for every request it handles. That line names the user, the destination, the method, the result, the number of bytes in each direction, the user agent, and the category the vendor assigned to the site. Proxy log analysis is the practice of mining those lines for evidence of intrusion, and in most organisations it is the richest outbound-traffic source available.
The reason is coverage. Attackers have to communicate outward, and in a corporate network almost everything outbound on ports 80 and 443 passes through the proxy. Whether the organisation runs Squid, Zscaler, Netskope, a Secure Web Gateway appliance, or a cloud access broker, the fields and the reasoning are substantially the same.
python-requests, curl, Go-http-client, WinHTTP, and empty user agent strings from user workstations deserve explanation. Legitimate ones exist and should be allowlisted explicitly rather than ignored in bulk.POST requests to uncategorised hosts, all of which are common ways of smuggling data out through what looks like ordinary web traffic.Detection is only half the value. When a phishing campaign is reported, the proxy logs answer the two questions that determine the scope of the incident: who clicked, and what happened next. A search for the campaign URL across the estate produces the list of users who visited; the response code and byte counts tell you whether the page loaded or the connection was blocked; and a follow-up search for the hosts that were contacted afterwards shows whether anything was downloaded. That reconstruction takes minutes and would be impossible from email records alone, which is why suspicious email investigations almost always pass through the proxy.
Three gaps matter more than the rest.
Encrypted sessions without inspection. Where TLS is not intercepted, the proxy records a CONNECT to a hostname and a byte count, and nothing about the URL path, the content, or the response. That is still enough for beaconing and volume analysis, but not for identifying a specific malicious URL.
Traffic that avoids the proxy entirely. QUIC and HTTP/3 run over UDP port 443 and bypass many proxy deployments completely, which is why organisations that rely on proxy logs usually block outbound UDP 443 at the firewall and force traffic back to TCP. Direct connections from servers, VPN split tunnels, and personal devices on a guest network are the other common escape routes.
Identity. Logs without an authenticated username force every investigation to start with an IP-to-user lookup against DHCP and directory records, which may no longer exist. Integrated authentication turns a two-hour reconstruction into a single query.
Proxy logs are a near-complete record of what identifiable employees read online, including material revealing health, religion, trade union membership, or political opinion. That makes them personal data under UK GDPR and, in places, special category data. Monitoring for security purposes is normally defensible under legitimate interests, but the ICO’s guidance on monitoring workers expects transparency about what is collected, a documented assessment of necessity and proportionality, and in most cases a data protection impact assessment before TLS interception is switched on.
Practically, that means telling staff what is logged, excluding categories such as banking and health sites from interception, restricting who can run free-text searches across browsing history, retaining only as long as the security purpose requires, and logging the searches analysts perform. None of this reduces detection capability, and all of it is easier to arrange before deployment than after a subject access request arrives.
Proxy data works best alongside DNS records and flow analysis, which cover the traffic the proxy never sees. At Privia Security, we help organisations build and tune this kind of monitoring through our SOC maturation services.
No. Without interception you still see the destination hostname, timing, byte volumes, and the client identity, which supports beaconing detection, rare-destination hunting, exfiltration volume analysis, and phishing scope reconstruction. Interception adds URL paths and content inspection, at a meaningful privacy and engineering cost. Many organisations deploy it selectively rather than everywhere.
Long enough to investigate an intrusion discovered months later, which in practice means six to twelve months for most organisations. Because volume is high and cost scales with it, a common pattern is thirty to ninety days searchable in the SIEM with the remainder in cheaper storage. Set the period against the security purpose and document it, since indefinite retention is hard to justify.
DNS logs record name resolution, including lookups for destinations that are never contacted and traffic from devices that do not use the proxy. Proxy logs record the actual web request, with user identity, volume, and outcome. DNS gives earlier and broader visibility; the proxy gives richer detail on what followed. Teams that collect both detect noticeably more.
Routinely. Command and control over content delivery networks, cloud storage, collaboration platforms, and code repositories all appear as traffic to reputable, business-critical domains that cannot simply be blocked. Detection then depends on behaviour rather than reputation: an unusual client contacting that service, at machine-like intervals, with an upload ratio that does not match how colleagues use it.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.