Running a production incident is a skill. Most of the skill isn't technical. Here's what nobody told me when I started running incidents. Skill 1: Calling the cadence During an incident, time warps. Everyone is heads-down in…

Sichere Programmierung dev.to 03.06.2026, 22:24 Uhr 3 Min. Lesezeit

↗ Quelle (dev.to)

Reagiere als Erste:r — dein Feedback zählt!

Running a production incident is a skill. Most of the skill isn't technical. Here's what nobody told me when I started running incidents.

Skill 1: Calling the cadence

During an incident, time warps. Everyone is heads-down in logs. Nobody remembers when they last updated the status channel.

The incident commander's job is to force a cadence: 'Update in 5 minutes. What do we know? What do we need?' Without this, the incident drags on because no one is aggregating context.

Skill 2: Saying 'I don't know, and here's what we're doing to find out'

Stakeholders want certainty. You can't give it. The temptation is to guess.

Don't guess. Say 'We don't know the cause yet. We're investigating X and Y. I'll update in 10 minutes.' Trust builds on honesty, not performance.

Skill 3: Interrupting your engineers

Your engineers are investigating. They don't want to stop and explain. But if you don't interrupt, you can't make decisions.

Do it anyway. Say 'I know you're busy. 30 seconds — what have you learned?' Most engineers will appreciate the structure, even if they complain.

Skill 4: Knowing when to stop investigating and start mitigating

The temptation in an incident is to find the root cause. The right action is usually to mitigate first and investigate second.

'We don't know why, but rolling back stops it' is a win. Don't feel bad. The post-mortem can figure out why.

Skill 5: Managing morale

Long incidents grind people down. Notice when your team is flagging. Bring in a relief shift. Say 'good job, let's take 10.' Acknowledge that it's hard.

The worst incidents I've been in were the ones where the team ran out of emotional energy before the problem was fixed. That's on the commander.

Skill 6: Declaring the incident over

Incidents often drag on past actual resolution because nobody wants to declare victory. Declare it. 'Issue resolved at 15:47. We'll keep monitoring for 30 minutes but the incident is closed.' People need permission to exhale.

The real job

Incident command is emotional labor disguised as technical work. The best commanders I know are calm, honest, and generous with credit. The worst are the ones who try to be the smartest technical person in the room — that's not the job.

You can't learn this from a book. You learn it by running incidents badly and asking for feedback afterward. The feedback is usually uncomfortable. It's also how you get good.

Written by Dr. Samson Tanimawo

BSc · MSc · MBA · PhD

Founder & CEO, Nova AI Ops. https://novaaiops.com

IR-PLAYBOOK-RCEHIGH

Schritte anzeigen

SOC Incident Playbook: Remote Code Execution (RCE) Defense

WAF MitigationSofort

Virtuelles Patchen am Reverse Proxy / WAF für gefährdete URL-Pfade und Payloads aktivieren.

SecRule REQUEST_URI "@rx ..." "id:1001,phase:1,deny,status:403"

Web Shell ScanSofort

Web-Root auf neu angelegte Scripts, anomal modifizierte Dateien und Persistence scannen.

find /var/www -type f -name "*.php" -mmin -120

Outbound FilteringSofort

Ausgehenden Datenverkehr (Reverse Shells zu unbekannten IPs/Ports) blockieren.

ss -tunp | grep -E ":(4444|1337|8080|9001)"

Vendor Patching

Hersteller-Update in Staging validieren und schnellstmöglich in Produktion ausrollen.

apt update && apt --only-upgrade install <pkg>

1-Click Detection Engineering: Multi-Dialect SIEM Rules5 Formate

Regeln anzeigen

1 Warnungen

title: Detect Exploitation - Incident Command: The Skills They Don't Teach You
id: 2aa57599-7765-4795-9fab-88e5707bf2d2
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-24
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

Syntax validiert (0 Fehler)

rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-24"
        description = "YARA Signature for "
    strings:
        $str = "Incident Command: The Skills T" ascii wide
    condition:
        any of them
}

Syntax validiert (0 Fehler)

index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Incident Command The Skills They Dont Te")
| 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: "*Incident Command The Skills They Dont Te*"

Syntax validiert (0 Fehler)

CommonSecurityLog
| where Message has "Incident Command The Skills They Dont Te"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

🎯

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

💡 Tipp: Klicken Sie auf eine TTP, um Gegenmaßnahmen und SIEM-Erkennungsregeln anzuzeigen.Enterprise Matrix v14.1

🚀 Auf tsecurity.de entdecken

◀ VORHERIGER BEITRAG 1 Min

EU Digital Identity Wallet Faces Scrutiny Over Reliance on Apple and Google Technology

IT Security Nachrichten

NÄCHSTER BEITRAG 1 Min

Google ordered to put clearer links in AI search and let UK publishers opt out

AI & KI NachrichtenWeiterlesen ▶

Blättern: Pfeiltasten [ ← ] [ → ] · Tasten j / k · mobil: Wischen

Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Incident Command: The Skills They Don't .... 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

Schnell-Prompts für Analysten

⚠️ DEFANGED SANDBOX VIEW (tsecurity.de): Alle Netzwerkindikatoren und URLs wurden neutralisiert (2 Indikatoren entschärft). Nur zur defensiven Analyse!

Format: python

#!/usr/bin/env python3
# Exploit Title: PoC for Target
import socket, sys
target = '192[.]168[.]1[.]10'
url = 'hxxp://target[.]local/vuln'
s = socket.socket()
s.connect((target, 80))
s.send(b'GET / HTTP/1.1\r\nHost: target.local\r\n\r\n')