This document is under active development and has not been finalized.
Skip to content

Incident Response Process

5-Phase Model

The incident response process of the BAUER GROUP follows the established NIST SP 800-61 framework, adapted to the requirements of §30(2) No. 2 BSIG.

Phase 1: Preparation

MeasureDescription
Incident response teamDefined roles: CISO (lead), IT Ops, Development, Communications
ToolingLog aggregation, monitoring dashboards, ticketing system
DocumentationResponse playbooks for the most common scenarios
CommunicationPredefined contact lists, escalation paths, templates
ExercisesAt least annually tabletop exercise or simulation

Phase 2: Detection and Analysis

Detection MethodDescriptionResponse Time
Automated monitoringLog-based anomaly detection, threshold alertsReal-time
Vulnerability alertsCVE feeds, dependency monitoring, vendor advisories< 4 hours
Employee reportsPhishing suspicion, unusual behaviorImmediately upon detection
External reportsCustomers, partners, security researchers, BSIImmediately upon receipt

Analysis steps:

  1. Initial assessment: Is the incident real? (Triage)
  2. Classification by severity (Critical / High / Medium / Low)
  3. Impact analysis: Which systems, data and customers are affected?
  4. Reporting obligation check: Does the incident constitute a significant incident per §32 BSIG?
  5. Initial forensic assessment: Attack vector, timeframe, indicators of compromise (IoC)

Phase 3: Containment

StrategyApplicationExample
Short-termImmediate damage limitationIsolate network segment, lock account
Long-termSustained containmentTake affected system offline, firewall rule
Evidence preservationBefore any remediationMemory dump, log export, disk image

EVIDENCE PRESERVATION

Always secure forensic evidence before initiating any cleanup or remediation measures. Evidence is critical for root cause analysis, regulatory reporting and potential law enforcement involvement.

Phase 4: Eradication and Recovery

StepDescription
Eliminate root causeRemove malware, deactivate compromised accounts, patch vulnerability
Clean systemsReinstall or verified restore from clean backup
Rotate credentialsAll potentially compromised passwords, API keys, certificates
Verify integrityConfirm system integrity before returning to production
Enhance monitoringIncreased surveillance for 30 days after recovery

Phase 5: Post-Incident

ActivityDeadlineResponsible
Post-mortem meetingWithin 5 business daysCISO
Root cause analysisWithin 10 business daysCISO + IT
Lessons learned documentWithin 15 business daysCISO
Action planWithin 20 business daysCISO + Executive Management
Risk analysis updateWithin 30 daysCISO

Playbooks

Predefined response playbooks exist for the most common scenarios:

ScenarioImmediate ActionsEscalation
RansomwareNetwork isolation, verify backup integrity, DO NOT pay ransomImmediately: CISO + Exec. Management + law enforcement if applicable
Data leakClose access path, determine scope, assess GDPR reportingImmediately: CISO + Exec. Management + DPO
Phishing (successful)Lock account, reset password, verify MFA< 1h: CISO
DDoSActivate CDN/WAF, contact upstream providerImmediately: IT Ops + CISO
Supply chain compromiseIsolate affected component, review SBOMImmediately: CISO + Development

Documentation licensed under CC BY-NC 4.0 · Code licensed under MIT