Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Request logs and the security log

For administrators of public sites - what Exponential writes to 404.log and security.log (probes, traversal, injection, scanners, 404 bursts), how addresses and query values are masked, how long the logs are kept, and…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/security/request-logs-and-the-security-log.md

On this page

Request logs and the security log

This page is for administrators and hosting teams. Exponential separates real faults from noise: not-found answers go to 404.log, requests the classifier takes for a probe or an attack go to security.log, and error.log keeps the real faults (Request logs). For a public site this gives you a quiet error log and a separate, readable record of attacks.

Contents

  1. The logs
  2. Reading a security.log line
  3. Privacy built in
  4. Retention
  5. Acting on what you see
  6. Related pages

The logs

LogHoldsLog viewer label
error.logreal faults onlyerror
404.log404 and 410 answers with the reason the kernel found"Not found requests (404)"
notice.log401 and 403 answersnotice
security.logprobes, traversal, injection, attack tools, 404 bursts, with any status"Security (request classifier)"

Every request is classified once and ends up in one log only. Nothing is blocked: the classifier only classifies. Blocking is the job of request-shield, the web server, or a listener in requestclassifier.ini [ClassifierSettings] Listeners[].

Reading a security.log line

[ Oct 17 2026 09:00:00 ] [203.0.x.x] probe/wp-login confidence=high 404 GET /wp-login.php siteaccess=site namespace=/wp-login.php ua=3f2a9c1b "curl/8.5.0"
PartMeans
probe/wp-logincategory and rule: probe, traversal, injection, scanner, threshold
confidence=highlow, medium or high
404the final status; a 200 on an injection attempt deserves a closer look
GET /wp-login.phpmethod and URI; query values kept as evidence, secrets and addresses in them masked
siteaccess=, namespace=where it arrived
ua=8 hex digits of the user agent's hash and its first 60 characters

Privacy built in

  • Client addresses masked (203.0.x.x) with site.ini [RequestLogSettings] MaskIP=enabled (the default); the raw address is never written to a file.
  • In 404.log every query value is replaced by ***.
  • The log viewer masks e-mail addresses, IP addresses and secrets by default; Show unmasked needs setup/unmasklogs and is itself recorded (Log viewer: Privacy).

Retention

404.log and security.log keep 5 compressed archives of up to 10 MB, pruned after 30 days (404) and 90 days (security) (Log rotation). Change them per log in settings/override/logviewer.ini.append.php, [RotationSettings] MaxAgeDays[security]=<days>. Pruning by age runs with ./console exp:logs --apply --prune or the cronjob part logs (php runcronjobs.php logs).

Acting on what you see

  • A steady flow of probe/* with 404 is normal internet noise; watch for changes in volume.
  • injection/* or traversal/* with status 200 or 500: check the URL, the module and any custom extension that handles it.
  • Many threshold/404-rate from one network: consider a rule in request-shield or the web server.
  • Read the weekly routine in "Log review routine" in this section.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x