┌─
─┐
└─
─┘
[ SYSTEM INITIALIZED · LOG SENTINEL v1.0 ]

LOG SENTINEL

Log Analysis Dashboard with Anomaly Detection
── Brute Force  ·  Dir Scanning  ·  Error Spikes  ·  Off-Hours Traffic ──
> PROTOCOL

HOW IT WORKS

─────────────────────────────────
[ 01/03 ]
01
UPLOAD

Drop your Apache or Nginx access log file into the analyzer.

> accepted: .log .txt
> max size: 16MB
[ 02/03 ]
02
ANALYZE

Four detection algorithms run simultaneously against your log data.

> brute_force.detect()
> scanner.detect()
> error_spike.detect()
> off_hours.detect()
[ 03/03 ]
03
REVIEW

Every threat scored, ranked, and explained in plain English.

> risk_score: CRITICAL
> explanation: generated
> INPUT

UPLOAD LOG FILE

─────────────────────────────────
sentinel@localhost: ~/log-analysis
> sentinel --version 1.0.0
✓ all modules loaded
> awaiting log file input...
DRAG & DROP LOG FILE
or click to browse · .log .txt · max 16MB
> DOCUMENTATION

UNDERSTANDING THREATS

─────────────────────────────────

Log Sentinel detects four categories of suspicious behavior. Here's what each one means and why it matters.

BRUTE FORCE ATTACK
authentication · high severity

A brute force attack happens when someone repeatedly tries to guess a password by sending hundreds or thousands of login attempts in a short time. They're usually automated bots cycling through common password lists.

> flagged when: same IP makes 10+ failed logins
WHAT TO DO:
> Block the IP at your firewall
> Enable account lockout after 5 failed attempts
> Consider adding CAPTCHA to your login page
DIRECTORY SCANNING
reconnaissance · medium severity

Directory scanning is when an attacker probes your server for hidden or sensitive files — things like admin panels, configuration files, or database backups. They use automated tools that try thousands of common paths looking for anything exposed.

> flagged when: same IP generates 10+ 404 errors
WHAT TO DO:
> Block the IP at your firewall
> Ensure sensitive files aren't publicly accessible
> Remove or relocate admin panels from default paths
SERVER ERROR SPIKE
exploitation · medium severity

When the same IP repeatedly causes 500 internal server errors, it often means they're sending malformed or malicious requests designed to break your application. This can be a sign of injection attacks or attempts to find exploitable bugs.

> flagged when: same IP triggers 5+ server errors
WHAT TO DO:
> Inspect your application error logs immediately
> Check for SQL injection or XSS patterns in requests
> Review and harden your input validation
OFF-HOURS TRAFFIC
behavioral · low severity

Traffic between midnight and 6am is inherently suspicious for most applications. Legitimate users are rarely active at 3am, but automated bots and attackers often operate at night to avoid detection and reduce competition for server resources.

> flagged when: any activity detected between 00:00–06:00
WHAT TO DO:
> Cross-reference with other anomaly flags on the same IP
> Check if the traffic matches known legitimate use patterns
> Consider rate limiting during off-hours windows
> RISK SCORING SYSTEM

Every flagged event is assigned a risk score based on its threat level. Scores stack when a single IP triggers multiple anomaly types.

80
brute force
60
error spike
40
dir scanning
30
off-hours
CRITICAL ≥100  ·  HIGH ≥70  ·  MEDIUM ≥40  ·  LOW <40
> IP DETAIL