defense-log-analysis
Hunt for attacker activity in logs — auth, web, cloud, endpoint — with concrete queries and what to look for. Load for blue-team log/SIEM hunting, "analyze these logs", "find the attack", triage of auth/web/cloud logs, or building hunts. Signals: log files/SIEM, "what happened", IOC hunting.
v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/defense-log-analysisScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto42c0768e…f92ec661
42c0768ee9a4…f05bf92ec6611 file · 1.5 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-log-analysis@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
You have logs (or a SIEM) and need to find attacker activity — during triage, IR, or proactive hunting. Pairs with each offensive skill: know the attack, hunt its footprint.
Why it works
Attacks leave patterns across log sources. Hunting hypothesis-first (pick a technique → query its signature → pivot on hits) beats scrolling. The same ATT&CK technique shows up in auth, web, cloud, and endpoint logs in characteristic ways.
Method — by source, what to look for
- Authentication: spikes of 4625/failed logins then a 4624 success (brute force →
web-rate-limit-bypass); logins from new geos/ASNs/impossible travel; new/again-enabled accounts; MFA fatigue (many prompts). - Web/proxy: bursts of 401/403/500 on one param (fuzzing), suspicious user-agents, long/encoded
query strings (SQLi/LFI/SSTI payloads), spikes to
/admin,/api,.git, requests to metadata IPs (SSRF). - Cloud (CloudTrail/Audit):
ConsoleLogin/AssumeRoleanomalies, IAM changes (CreateAccessKey,AttachUserPolicy,setIamPolicy),GetSecretValuebursts, unusual regions,iam:PassRole+ deploy (→cloud-iam-privesc). - Endpoint/process: suspicious parents (
w3wp→cmd),certutil/curldownloads, encoded PowerShell, new services/scheduled tasks (→defense-dfir-triage). - Pivot & timeline: on a hit, pivot by user/IP/host and build a timeline; correlate across sources.
Gotchas
- Baseline first — "anomalous" only means something against normal; know what normal looks like.
- Watch timezones/clock skew when correlating sources.
- Turn confirmed patterns into durable detections (→
defense-detection-sigma), don't just eyeball once.
Verify success
A concrete finding: an attacker action identified with the query that found it, pivoted to scope (accounts/hosts/timeline), and IOCs extracted for detection/containment.
References
Splunk/Elastic search docs; MITRE ATT&CK; SANS hunting; Sigma for portable detections.
File di questa versione
- SKILL.md2.5 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 42c0768e | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in DFIR e threat hunting
Vai alla categoria- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login