* Conoscenza del computer >> Software >  >> LinkedIn

Leggere e analizzare i log IIS: formati, campi, strumenti e sicurezza

Perché analizzare i log IIS

  • Troubleshooting: Errori 404, 500, 503, timeout, application pool crashes.
  • Sicurezza: Scansioni vulnerabilità (SQLi, XSS, path traversal), brute force login, bot malevoli, data exfiltration.
  • Performance: Pagine lente (time-taken alto), colli di bottiglia, risorse pesanti.
  • Business: Traffico per pagina, user agent, geolocalizzazione IP, conversioni.
  • Compliance: Audit accessi dati sensibili (GDPR, HIPAA, PCI-DSS).

Formati log IIS

Campi W3C più utili (selezionate in Logging → Select Fields)

#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken bytes-sent bytes-received
  • date time: UTC (non locale!) — convertite per analisi.
  • c-ip: Client IP (reale se no proxy/CDN; se dietro CDN/load balancer → guardate X-Forwarded-For in cs(X-Forwarded-For)).
  • cs-method: GET, POST, PUT, DELETE, HEAD, OPTIONS.
  • cs-uri-stem: Path risorsa (/api/users, /images/logo.png).
  • cs-uri-query: Query string (?id=123&token=abc).
  • sc-status: HTTP status code (200, 301, 404, 500...).
  • sc-substatus / sc-win32-status: Dettaglio errore IIS/Win32 (es. 500.19 = config error, 401.2 = auth failed).
  • time-taken: **Millisecondi** per elaborare richiesta — chiave per performance.
  • cs(User-Agent): Browser, bot, scanner, tool (curl, python-requests, sqlmap).
  • cs(Referer): Da dove arriva l'utente (spoofabile).

Dove trovare i file log

  • Default: %SystemDrive%\inetpub\logs\LogFiles\W3SVC\ (es. C:\inetpub\logs\LogFiles\W3SVC1\u_ex240115.log).

  • Nominazione: u_ex.log (UTC date). Nuovo file ogni giorno mezzanotte UTC.
  • In IIS Manager: Sito → Logging → "Directory" (modificabile).

Strumenti per analisi

FormatoEstensioneCampiNote
W3C Extended (default).logFino a 22 campi selezionabiliStandard, parsabile, supporta UTF-8
IIS (Microsoft).log15 campi fissiLegacy, meno flessibile
NCSA Common.log7 campi fissiApache-style, solo HTTP, no referrer/UA
ODBC / SQLDBSet predefinitoDisabilita kernel cache → performance ↓

Query Log Parser esempi (salvate come .sql, eseguite: logparser file:query.sql -i:W3C)

-- Top 20 errori 404
SELECT TOP 20 cs-uri-stem, COUNT(*) AS Hits
FROM 'C:\inetpub\logs\LogFiles\W3SVC1\u_ex*.log'
WHERE sc-status = 404
GROUP BY cs-uri-stem
ORDER BY Hits DESC;

-- Richieste più lente (top 50)
SELECT TOP 50 date, time, c-ip, cs-method, cs-uri-stem, time-taken, sc-status
FROM 'C:\inetpub\logs\LogFiles\W3SVC1\u_ex*.log'
WHERE time-taken > 5000
ORDER BY time-taken DESC;

-- IP con più errori 5xx
SELECT c-ip, COUNT(*) AS Errors
FROM 'C:\inetpub\logs\LogFiles\W3SVC1\u_ex*.log'
WHERE sc-status >= 500
GROUP BY c-ip
ORDER BY Errors DESC;

-- User Agent sospetti (scanner, bot)
SELECT cs(User-Agent), COUNT(*) AS Hits
FROM 'C:\inetpub\logs\LogFiles\W3SVC1\u_ex*.log'
WHERE cs(User-Agent) LIKE '%sqlmap%' OR cs(User-Agent) LIKE '%nikto%' OR cs(User-Agent) LIKE '%nmap%' OR cs(User-Agent) LIKE '%bot%' OR cs(User-Agent) LIKE '%crawler%' OR cs(User-Agent) LIKE '%scanner%'
GROUP BY cs(User-Agent)
ORDER BY Hits DESC;

Indicatori di compromissione (IOC) da cercare

  • Richieste con UNION SELECT, ' OR 1=1,

    LinkedIn

    • --热点software

    Software © www.354353.com

ToolTipoPunti di forza
Log Parser 2.2 (Microsoft, gratis)CLI / COMSQL-like query su file log, export CSV/SQL/XML, veloce, scriptabile
Log Parser Studio (GUI per Log Parser)GUIQuery predefinite (Top 404, Slow requests, IP analysis), grafici
GoAccess (open source, CLI/HTML)CLI/WebReport interattivo HTML real-time, geoip, molto veloce
AWStats (Perl, legacy)CLI/CGIReport statici, datato
ELK Stack (Elasticsearch, Logstash, Kibana)PlatformCentralizzato, scaling, dashboard, alerting, ML — enterprise
Graylog / Loki + GrafanaPlatformAlternative open source a ELK, più leggere
PowerShell / Python (pandas)ScriptFlessibilità totale, automazione, ML custom