Sascha Fahl

Sascha Fahl

Auto-generated profile, based on publicly available information

Sascha Fahl

CISPA Helmholtz Center for Information Security, Hannover, Germany

Research Focus & Metrics

Academic Career Length

8Years (2019-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
2 December 2024
Verified
Conference Paper
Open access
JKJan H. Klemmer
Jan H. Klemmer
SHStefan Albert Horstmann
Stefan Albert Horstmann
NPNikhil Patnaik
Nikhil Patnaik
CLCordelia Ludden
Cordelia Ludden
CBCordell Burton
Cordell Burton
SFSascha Fahl
Sascha Fahl
Following the recent release of AI assistants, such as OpenAI's ChatGPT and GitHub Copilot, the software industry quickly utilized these tools for software development tasks, e.g., generating code or consulting AI for advice. While recent research has demonstrated that AI-generated code can contain security issues, how software professionals balance AI assistant usage and security remains unclear. This paper investigates how software professionals use AI assistants in secure software development, what security implications and considerations arise, and what impact they foresee on security in software development. We conducted 27 semi-structured interviews with software professionals, including software engineers, team leads, and security testers. We also reviewed 190 relevant Reddit posts and comments to gain insights into the current discourse surrounding AI assistants for software development. Our analysis of the interviews and Reddit posts finds that, despite many security and quality concerns, participants widely use AI assistants for security-critical tasks, e.g., code generation, threat modeling, and vulnerability detection. Participants' overall mistrust leads to checking AI suggestions in similar ways to human code. However, they expect improvements and, therefore, a heavier use of AI for security tasks in the future. We conclude with recommendations for software professionals to critically check AI suggestions, for AI creators to improve suggestion security and capabilities for ethical security tasks, and for academic researchers to consider general-purpose AI in software development.

15 November 2023
Verified
Conference Paper
Open access
SKSabrina Klivan
Sabrina Klivan
SHSandra Höltervennhoff
Sandra Höltervennhoff
NHNicolas Huaman
Nicolas Huaman
AKAlexander Krause
Alexander Krause
LSLucy Simko
Lucy Simko
SASabrina Amft
Sabrina Amft
Multi-Factor Authentication is intended to strengthen the security of password-based authentication by adding another factor, such as hardware tokens or one-time passwords using mobile apps. However, this increased authentication security comes with potential drawbacks that can lead to account and asset loss. If users lose access to their additional authentication factors for any reason, they will be locked out of their accounts. Consequently, services that provide Multi-Factor Authentication should deploy procedures to allow their users to recover from losing access to their additional factor that are both secure and easy-to-use. In this work, we investigate the security and user experience of Multi-Factor Authentication recovery procedures, and compare their deployment to descriptions on help and support pages. We first evaluate the official help and support pages of 1,303 websites that provide Multi-Factor Authentication and collect documented information about their recovery procedures. Second, we select a subset of 71 websites, create accounts, set up Multi-Factor Authentication, and perform an in-depth investigation of their recovery procedure security and user experience. We find that many websites deploy insecure Multi-Factor Authentication recovery procedures and allowed us to circumvent and disable Multi-Factor Authentication when having access to the accounts' associated email addresses. Furthermore, we commonly observed discrepancies between our in-depth analysis and the official help and support pages, implying that information meant to aid users is often either incorrect or outdated. Based on our findings, we provide recommendations for best practices regarding Multi-Factor Authentication recovery.

15 November 2023
Verified
Conference Paper
Open access
JKJan H. Klemmer
Jan H. Klemmer
MGMarco Gutfleisch
Marco Gutfleisch
CSChristian Stransky
Christian Stransky
YAYasemin Acar
Yasemin Acar
MSM. Angela Sasse
M. Angela Sasse
SFSascha Fahl
Sascha Fahl
Usable and secure authentication on the web and beyond is mission-critical. While password-based authentication is still widespread, users have trouble dealing with potentially hundreds of online accounts and their passwords. Alternatives or extensions such as multi-factor authentication have their own challenges and find only limited adoption. Finding the right balance between security and usability is challenging for developers. Previous work found that developers use online resources to inform security decisions when writing code. Similar to other areas, lots of authentication advice for developers is available online, including blog posts, discussions on Stack Overflow, research papers, or guidelines by institutions like OWASP or NIST. We are the first to explore developer advice on authentication that affects usable security for end-users. Based on a survey with 18 professional web developers, we obtained 406 documents and qualitatively analyzed 272 contained pieces of advice in depth. We aim to understand the accessibility and quality of online advice and provide insights into how online advice might contribute to (in)secure and (un)usable authentication. We find that advice is scattered and that finding recommendable, consistent advice is a challenge for developers, among others. The most common advice is for password-based authentication, but little for more modern alternatives. Unfortunately, many pieces of advice are debatable (e.g., complex password policies), outdated (e.g., enforcing regular password changes), or contradicting and might lead to unusable or insecure authentication. Based on our findings, we make recommendations for developers, advice providers, official institutions, and academia on how to improve online advice for developers.

11 May 2024
Verified
Conference Paper
Open access
JSJuliane Schmüser
Juliane Schmüser
HRHarshini Sri Ramulu
Harshini Sri Ramulu
NWNoah Wöhler
Noah Wöhler
CSChristian Stransky
Christian Stransky
FBFelix Bensmann
Felix Bensmann
SFSascha Fahl
Sascha Fahl


13 November 2023 in IEEE Security & Privacy
Verified
Journal Article
Closed access
MFMarcel Fourné
Marcel Fourné
DWDominik Wermke
Dominik Wermke
SFSascha Fahl
Sascha Fahl
YAYasemin Acar
Yasemin Acar
While securing dependencies and build systems is necessary, recent attacks have shown that developers are a commonly successfully attacked link in the chain. Therefore, a comprehensive approach that considers the human factor is crucial for effective software supply chain security.