Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

I built a log analyzer, and it found real attacks on my own machine

I am documenting every day of my cybersecurity learning journey publicly. This post covers Days 8 through 12 — the first half of Week 2. The log analyzer and what it found The most significant thing I built this week is a P…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

I am documenting every day of my cybersecurity learning journey publicly. This post covers Days 8 through 12 — the first half of Week 2.






The log analyzer and what it found



The most significant thing I built this week is a Python log analyzer. It reads Linux auth.log files, finds every failed SSH login attempt, extracts the source IP from each one, and counts how many times each IP tried.



Here is the core logic:




from collections import Counter

failed_ips = []
with open("/var/log/auth.log", "r") as f:
for line in f:
if "Failed password" in line:
parts = line.split()
for i, part in enumerate(parts):
if part == "from":
failed_ips.append(parts[i + 1])

ip_counts = Counter(failed_ips)
for ip, count in ip_counts.most_common(10):
print(ip + " — " + str(count) + " attempts")






I ran this against my actual Kali machine's auth.log. My system has been running for less than two weeks. The output showed real external IP addresses that had attempted SSH brute force attacks — automated scanners crawling the internet looking for systems with weak SSH credentials.



That is what SOC analysts see at enterprise scale — except they are watching thousands of servers simultaneously using SIEM tools. My script does the same thing for a single log file. Writing it at the code level makes the enterprise workflow more intuitive.



Security+ — 5 days of study



Started CompTIA Security+ SY0-701 on Day 8 using Professor Messer's free course. Here is what the first five days covered.



Malware types — the most tested area of Domain 2



The distinction that appears most on practice tests: virus vs worm.



A virus requires human action to spread. It attaches to files and moves when those files are shared.



A worm spreads automatically. It exploits vulnerabilities to move across networks without anyone clicking anything. WannaCry was a worm — it used the EternalBlue exploit on SMB port 445 and infected 230,000 systems across 150 countries in a single day without requiring any user interaction.



Understanding this distinction at the mechanism level, not just the definition level, is what makes it stick on exam day.



Social engineering — most breaches start here



Eight attack types: phishing, spear phishing, whaling, vishing, smishing, pretexting, baiting, tailgating.



The one I had not thought carefully about: pretexting. An attacker creates a convincing scenario — "I am the new IT admin, I need your credentials to migrate your account" — and relies on the target's willingness to be helpful. No exploit. No malware. Just a believable story.



Technical defenses cannot stop pretexting. Training is the defense.



Zero Trust — replacing perimeter security



The old model: build a wall around the network, trust everything inside. This failed when remote work and cloud services dissolved the perimeter.



Zero Trust: never trust, always verify. Every access request is authenticated and authorized regardless of source. A device already inside the network is treated as untrusted until it proves otherwise.



Base64 — not encryption



Bandit level 10 reinforced something worth writing about explicitly.



Base64 looks like encrypted data. It is not. It is encoding — converting binary data to ASCII text. Anyone can decode it instantly with one command: base64 --decode.



Attackers use it to make payloads look mysterious in logs and scripts. It is one layer of obfuscation. Once you recognize base64 (padding with = at the end, characters from A-Z a-z 0-9 + /), decoding it takes seconds.



The same is true for ROT13 — rotating letters 13 positions. Not encryption. Not security. Appears in CTF challenges constantly.



Port scanner version 2



Updated the port scanner from Week 1 to display service names alongside port numbers. Changed one output line using a Python dictionary lookup:




common_services = {21: "FTP", 22: "SSH", 80: "HTTP", 443: "HTTPS"}
service = common_services.get(port, "Unknown")
print("[OPEN] Port " + str(port) + " — " + service)






Now instead of "[OPEN] Port 22" it shows "[OPEN] Port 22 — SSH". Small change, meaningfully more useful.



Three tools on GitHub now



Port scanner (v2 with service names), password generator, and log analyzer. All with documentation explaining how they work and what I learned building them. Link on my profile.

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Remote Code Execution (RCE) Defense
Syntax validiert (0 Fehler)
title: Detect Exploitation - I built a log analyzer, and it found real attacks on my own machine
id: 3d73dbf5-6cd5-4365-b33c-f6d2a6f4cf78
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-26
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
  - attack.t1566
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-26"
        description = "YARA Signature for "
    strings:
        $str = "I built a log analyzer, and it" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("I built a log analyzer and it found real")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*I built a log analyzer and it found real*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "I built a log analyzer and it found real"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

CTI Threat Relationship Graph4 Knoten / 3 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich I built a log analyzer, and it found rea.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten I built a log analyzer, and it found real attacks on my own machine

Thematisch verwandte Begriffe: built, analyzer, found, real · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-86066 | Horilla is an HR and CRM software. Prior to 2.0.0, approve_validate_atte…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag