Scared? Prepared? Towards a Ransomware Incident Response Scenario

Maximilian Greiner (Author and Speaker), Judith Strußenberg, Andreas Seiler, Stefan Hofbauer, Michael Schuster, Damian Stano, Günter Fahrnberger, Stefan Schauer, Ulrike Lechner

Research output: Chapter in Book or Conference ProceedingsConference Proceedings with Oral Presentationpeer-review

Abstract

Individuals, organizations, and supply chains must increase the level of preparedness in response to a cyber incident. This article is part of a larger research initiative that designs a process framework, playbooks, serious games, and simulations to prepare for a ransomware incident with the scenario being common ground. Drawing on a Design Science Research approach, we use 11 interviews, short cases, four real-world cases, and cross-case analysis to design a logistics domain scenario highlighting the business, actor, infrastructure, and threat view. A discussion of the design rationale and the next steps concludes the article.
Original languageEnglish
Title of host publicationInnovations for Community Services
Subtitle of host publication24th International Conference, I4CS 2024 Maastricht, The Netherlands, June 12–14, 2024 Proceedings
PublisherSpringer
Pages289-320
Number of pages31
Volume2109
Edition1
ISBN (Electronic)978-3-031-60433-1
ISBN (Print)978-3-031-60432-4
DOIs
Publication statusPublished - 13 Jun 2024
Event24th International Conference on Innovations for Community Services (I4CS) - School of Business and Economics (SBE), Maastricht, Netherlands
Duration: 12 Jun 202414 Jun 2024
https://www.eah-jena.de/i4cs-conference/archiv/2024

Conference

Conference24th International Conference on Innovations for Community Services (I4CS)
Abbreviated titleI4CS 2024
Country/TerritoryNetherlands
CityMaastricht
Period12/06/2414/06/24
Internet address

Research Field

  • Dependable Systems Engineering

Fingerprint

Dive into the research topics of 'Scared? Prepared? Towards a Ransomware Incident Response Scenario'. Together they form a unique fingerprint.

Cite this