Security OperationsLiveFrom Pro ($199/mo)

Log Inspector

Your logs record the attack attempts against your application. Paste a server log or drop a log file, and Log Inspector detects brute force, SQL injection attempts, path traversal and scanner activity, then points you to the fix.

Detection Coverage

What Log Inspector detects

Brute Force & Credential Stuffing

Repeated login failures from one IP address and high login failure rates.

SQL Injection Attempts

SQL injection payloads in request URLs and parameters.

XSS and Path Traversal

Script payloads in query strings and attempts to escape the web root.

Scanner Activity

Requests from known scanner and bot user agents.

Directory Enumeration

Bursts of 4xx responses to a single IP address.

Known Exploit Patterns

Log4Shell strings, HTTP request smuggling indicators and unusual request methods.

How it works

Paste a log, get findings

  1. 1

    Paste or upload

    Paste log lines or drop a log file. The format is detected automatically: Apache and Nginx access logs, JSON, syslog, Kubernetes and Docker output, and key=value logs.

  2. 2

    Pattern detection

    The log is checked against security signatures. IP addresses and other indicators are extracted, and anomalies such as failure bursts are summarised.

  3. 3

    Triage

    Each detection has a severity, the matching lines, a MITRE ATT&CK technique, a CWE reference where one applies and a recommended fix.

  4. 4

    Save as findings

    Save a detection as a finding to track it with the results from your scan engines.

access.logLog
203.0.113.42 - - [15/Apr/2025:14:22:33 +0000] "POST /api/auth/login HTTP/1.1" 401 52
203.0.113.42 - - [15/Apr/2025:14:22:34 +0000] "POST /api/auth/login HTTP/1.1" 401 52
203.0.113.42 - - [15/Apr/2025:14:22:35 +0000] "POST /api/auth/login HTTP/1.1" 401 52
203.0.113.42 - - [15/Apr/2025:14:22:36 +0000] "POST /api/auth/login HTTP/1.1" 401 52
FindingExample: repeated login failures from one IP address are reported as brute force (MITRE ATT&CK T1110, CWE-307).

Spoorder Log Inspector vs reading logs by hand

CriterionSpoorderreading logs by hand
SetupPaste or upload a log, nothing to installSearch by hand
DetectionBuilt-in security signaturesWhatever you think to search for
ContextMITRE ATT&CK and CWE references with a fixRaw log lines
Follow-upSave detections as tracked findingsNotes elsewhere
Do I need to install an agent or stream my logs?

No. Log Inspector analyses the log content you paste or upload. It does not connect to your servers or ingest a live log stream.

Which log formats are supported?

Apache and Nginx combined access logs, JSON structured logs, syslog, Kubernetes and Docker output, GitHub Actions runner logs and generic key=value logs. The format is detected automatically.

Is this a SIEM?

No. It is an on-demand analysis of a log you provide. It does not monitor continuously or send real-time alerts.

How does this help with compliance?

Detections you save become findings, which Spoorder maps to the controls of the frameworks on your plan. Log review is one input; it does not on its own satisfy a logging and monitoring control.

What plan does it need?

Log Inspector is included from the Pro plan ($199/mo).

Start scanning

Start with a free health check. Log Inspector is included from Pro ($199/mo).