Hi guys ,so i started this year really confident and full of hope, i planned that the year was going to be my year of productivity and i was going to get the job done, looking back i did use this to make myself feel better , get the job done, the ai trend really did a number on me lol, i didnt take it quite well, i started this year as a decent developer, but i had a problem , i did'nt want to be mediocre ive always been liike that , the problem of wanting to learn everything and ending up learning nothing, wanting to become everything and becoming nothing , that was basically what i have been doing , i wanted to learn everything , be able to build everything , understand everything, be able to answer every question, well i did get really good at ai prompting for what its worth ? i started out with vibe coding then literilly using ai for everything , people would ask me questions and i would paste it on ai to reply and feel like a mentor ,i mean i have 5 experience in programming i cant start all over i would just get really better with ai till i become invincible , well that , that was a bad idea, but i guess its better late than never , restarting my tech journey as of today , starting from scratch , html,how does the internet work, the real basics , learning to use ai as a copilot and not the implementor, learning to think for myself , might have taken me 5 years and 11 months to learn this lesson but i guess its never too late to restart ? it isnt right ? i know i am aing the right decision but i just cant get that disappointed feeling off my chest from wasting soo much time ,of wanting to become everything ,i guess the point of this is to - well who am i kidding this is more of a self-reflection and a breath of fresh air to write out what i am felling less than an advice or to make someone learn from me.we have two months left so hopefully i make something with the rest of it , i am going to be posting my daily progress on here and what i'm learning , hopefully i dont quit and i actuallly achieve alot with the rest to recover for the wasted time
Intelligence View
my tech restart
Hi guys ,so i started this year really confident and full of hope, i planned that the year was going to be my year of productivity and i was going to get the job done, looking back i did use this to make myself feel better , get the job…
1. Sofort-Triage & Abwehrmaßnahmen
SOC Incident Playbook: Vulnerability Remediation & Verification
title: Detect Exploitation - my tech restart
id: 4f7319e7-3136-4b51-9421-331a44e36ddb
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
- https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-25
logsource:
category: network_connection
product: any
detection:
selection:
CommandLine|contains:
- 'exploit'
condition: selection
falsepositives:
- Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
- attack.initial_accessrule CTI_Threat_Indicator {
meta:
author = "iShareStuff CTI Automated Detection Engine"
date = "2026-09-25"
description = "YARA Signature for "
strings:
$str = "my tech restart" ascii wide
condition:
any of them
}index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("my tech restart")
| 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 - countmessage: "*my tech restart*"CommonSecurityLog
| where Message has "my tech restart"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc2. Cyber Threat Intelligence & Forensik
MITRE ATT&CK Matrix Navigator 14 Taktiken
tsecurity.de Cognitive Threat RAG
Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich my tech restart.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.
Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.
- 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.
SOCIAL SHARE CARD GENERATOR