Apache HTTP Server common access log
Apache HTTP Server common access log. HTTP requests serialized using the Common Log Format.
Source and collection
Configured service log destination; commonly under /var/log or the service data directory.
Record the exact log format directive, rotation policy, time zone and service version.
Native example and provenance
upstream test fixture. Published example; no independent capture provenance claimed.
Original publisher / pinned upstream fixture — line 1
One complete record selected; values unchanged.
Pinned source commit: 9ae756f00f82786ac3496ce99c2dd288c5a5c031
Download the exact sample · Offline research kit
SHA-256: b6d2fc79528540c5a42ac69a58a1ff09764bdba067b279f2b72898bd0b98caf8
::1 - - [26/Dec/2016:16:16:29 +0200] "GET /favicon.ico HTTP/1.1" 404 209
Structure and field interpretation
| Field/path | Serialized type |
|---|---|
raw record | text |
- Timestamp
- May omit year or time zone depending on configuration.
- Message
- Parse according to the exact service format, preserving quoted request fields.
Investigation uses
- Review client, request, response status and bytes.
- Preserve quoting, escaping and complete multiline records when applicable.
Validation boundaries
Custom LogFormat directives change the schema; status does not establish application security outcome.
This text sample passed byte-integrity and record-framing checks. Its field interpretation follows the cited format; a vendor-specific semantic parser has not been certified.
For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.
Related sources
Ecosystem connections
- Telemetry Library — ATT&CK data components
- Detection Rules — candidate detection content
- Threat hunting — from intelligence to validated defense
- Practical security learning paths
- AdversaryGraph — evidence-led investigation
References
Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.