CyberKit

Web Access Logs

Also called HTTP Access Logs.

Server-side records of every HTTP request a web server handles.

What it is

Web access logs are written by web servers for each incoming HTTP request, recording the client address, timestamp, method and URL, response status and size, referrer, and user agent. The Common and Combined Log Formats are the most widespread layouts.

Why it matters

They are central to investigating web-facing compromises, exposing exploitation attempts, web-shell interactions, and unusual request patterns against an application. After a breach, they often hold the precise request that first delivered a payload or triggered a vulnerability.

In practice

Access-log lines showing repeated POSTs to an unexpected .aspx file, pinpointing the web shell an attacker planted and used.

What to look for

  • Requests for admin pages, web shells or traversal paths.
  • Status code spikes, such as many 404s then a 200.
  • POST requests to static files.

Common mistake

Ignoring successful requests. A 200 on a strange path matters more than a pile of 404s.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

  • Proxy Logs: Records of outbound web requests passing through a forward proxy.
  • Authentication Logs: Records of login attempts, successes, and failures across systems.
  • Log Normalization: Mapping diverse log formats onto a single common schema.

Sources