Asli Yardim
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Asli Yardim has a total of 16 co-authors. Here are the top co-authors by number of shared publications:
- Alena Naiakshina
University of Cologne, Cologne, Germany
7 shared publications - Raphael Serafini
University of Cologne, Cologne, Germany
4 shared publications - Anna-Marie Ortloff
University of Bonn, Bonn, Germany
2 shared publications - Catherine Tony
Hamburg University of Technology, Hamburg, Germany
2 shared publications - Joshua Gabriel Speckels
University of Cologne, Cologne, Germany
2 shared publications - Kevin Hermann
Ruhr University Bochum
2 shared publications
Latest Publications
- Open Access
- 29 August 2026
- Published by Association for Computing Machinery (ACM)
- p. 88-112
"How do security threats affect my work?" - Software Developers’ Mental Models of IT Security Threats and Mitigation Strategies
- 29 August 2026
- Published by Association for Computing Machinery (ACM)
- p. 88-112
Open Access"How do security threats affect my work?" - Software Developers’ Mental Models of IT Security Threats and Mitigation Strategies
- Open Access
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 1-18
Robust Methods for Developer Screening in Rapidly Evolving AI Contexts
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 1-18
Open AccessRobust Methods for Developer Screening in Rapidly Evolving AI Contexts
- Open Access
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 1-33
"The AI tool can’t make it any worse." Investigating Developers’ Security Behavior with AI Assistants in a Password Storage Study
Past research showed that software developers often require explicit instructions to implement security measures. With the rapid rise of AI assistant tools such as ChatGPT, it remains unclear whether AI assistance supports or undermines secure practices, whether explicit security instructions are still essential, and how developers behave without guidance. To investigate these research questions, we conducted a qualitative lab study with 21 computer science students and a quantitative online study with 80 freelance developers. We focused on secure password storage and asked participants to implement registration logic under four conditions: without instructions, with AI assistance, with security instructions, or with both AI assistance and security instructions. Our study reveals a clear behavioral shift: In our task, many participants relied on AI-assisted code generation for security-related tasks, often prioritizing convenience over security. However, explicit security-focused instructions can redirect this behavior toward secure outcomes, demonstrating that AI tools alone are insufficient without targeted guidance.
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 1-33
Open Access"The AI tool can’t make it any worse." Investigating Developers’ Security Behavior with AI Assistants in a Password Storage Study
Past research showed that software developers often require explicit instructions to implement security measures. With the rapid rise of AI assistant tools such as ChatGPT, it remains unclear whether AI assistance supports or undermines secure practices, whether explicit security instructions are still essential, and how developers behave without guidance. To investigate these research questions, we conducted a qualitative lab study with 21 computer science students and a quantitative online study with 80 freelance developers. We focused on secure password storage and asked participants to implement registration logic under four conditions: without instructions, with AI assistance, with security instructions, or with both AI assistance and security instructions. Our study reveals a clear behavioral shift: In our task, many participants relied on AI-assisted code generation for security-related tasks, often prioritizing convenience over security. However, explicit security-focused instructions can redirect this behavior toward secure outcomes, demonstrating that AI tools alone are insufficient without targeted guidance.
- Open Access
- 28 May 2025
- Published by Springer Nature in Empirical Software Engineering
- Vol. 30 (5) , 1-57
A taxonomy of functional security features and how they can be located
Security must be considered in almost every software system. Unfortunately, selecting and implementing security features remains a challenge due to the wide variety of security threats and possible countermeasures. While security standards are intended to help developers, they are usually too abstract and vague to help implementing security features, or they merely help configuring such. A resource that describes security features at an abstraction level that lies between high-level (i.e., rather too general) and low-level (i.e., rather too specific) security standards could facilitate secure systems development. This resource should support the selection of appropriate security features to achieve high-level security goals, allow easy retrieval of relevant low-level details, and provide pointers to suitable ways to realize the security features. To realize security features, developers typically use external security libraries or frameworks, to minimize implementation mistakes. Even when using libraries, developers still make mistakes when writing code to integrate them, often resulting in security vulnerabilities. When security incidents occur or the system needs to be audited or maintained, it is essential to know what security features have been implemented and, more importantly, where they are located. This task, commonly referred to as feature location, is often tedious and error-prone. While dedicated feature location techniques exist, they require significant manual effort or adherence to strict development processes, preventing their use. Therefore, we have to support long-term tracking of implemented security features. We present a study of security features presented in the literature and their coverage in popular security frameworks. We contribute (1) a taxonomy of 68 functional implementation-level security features including a mapping to widely used security standards, (2) an examination of 21 popular security frameworks concerning which of these security features they provide, and (3) a discussion on the representation of security features in source code. Our taxonomy aims to aid developers in selecting appropriate security features and security frameworks, as well as relating them to security standards when they need to choose and implement security features for a software system.
- 28 May 2025
- Published by Springer Nature in Empirical Software Engineering
- Vol. 30 (5) , 1-57
Open AccessA taxonomy of functional security features and how they can be located
Security must be considered in almost every software system. Unfortunately, selecting and implementing security features remains a challenge due to the wide variety of security threats and possible countermeasures. While security standards are intended to help developers, they are usually too abstract and vague to help implementing security features, or they merely help configuring such. A resource that describes security features at an abstraction level that lies between high-level (i.e., rather too general) and low-level (i.e., rather too specific) security standards could facilitate secure systems development. This resource should support the selection of appropriate security features to achieve high-level security goals, allow easy retrieval of relevant low-level details, and provide pointers to suitable ways to realize the security features. To realize security features, developers typically use external security libraries or frameworks, to minimize implementation mistakes. Even when using libraries, developers still make mistakes when writing code to integrate them, often resulting in security vulnerabilities. When security incidents occur or the system needs to be audited or maintained, it is essential to know what security features have been implemented and, more importantly, where they are located. This task, commonly referred to as feature location, is often tedious and error-prone. While dedicated feature location techniques exist, they require significant manual effort or adherence to strict development processes, preventing their use. Therefore, we have to support long-term tracking of implemented security features. We present a study of security features presented in the literature and their coverage in popular security frameworks. We contribute (1) a taxonomy of 68 functional implementation-level security features including a mapping to widely used security standards, (2) an examination of 21 popular security frameworks concerning which of these security features they provide, and (3) a discussion on the representation of security features in source code. Our taxonomy aims to aid developers in selecting appropriate security features and security frameworks, as well as relating them to security standards when they need to choose and implement security features for a software system.
- Open Access
- 25 April 2025
- Published by Association for Computing Machinery (ACM)
- p. 1-27
Women Security Experts Are Not The Enemy: A Qualitative Study on Gender-Related Communication Challenges
- 25 April 2025
- Published by Association for Computing Machinery (ACM)
- p. 1-27
Open AccessWomen Security Experts Are Not The Enemy: A Qualitative Study on Gender-Related Communication Challenges
- Open Access
- 25 April 2025
- Published by Association for Computing Machinery (ACM)
- p. 1-26
Exploring the Impact of Intervention Methods on Developers’ Security Behavior in a Manipulated ChatGPT Study
- 25 April 2025
- Published by Association for Computing Machinery (ACM)
- p. 1-26
Open AccessExploring the Impact of Intervention Methods on Developers’ Security Behavior in a Manipulated ChatGPT Study
- Open Access
A Taxonomy of Functional Security Features and How They Can Be Located
Security must be considered in almost every software system. Unfortunately, selecting and implementing security features remains challenging due to the variety of security threats and possible countermeasures. While security standards are intended to help developers, they are usually too abstract and vague to help implement security features, or they merely help configure such. A resource that describes security features at an abstraction level between high-level (i.e., rather too general) and low-level (i.e., rather too specific) security standards could facilitate secure systems development. To realize security features, developers typically use external security frameworks, to minimize implementation mistakes. Even then, developers still make mistakes, often resulting in security vulnerabilities. When security incidents occur or the system needs to be audited or maintained, it is essential to know the implemented security features and, more importantly, where they are located. This task, commonly referred to as feature location, is often tedious and error-prone. Therefore, we have to support long-term tracking of implemented security features. We present a study of security features in the literature and their coverage in popular security frameworks. We contribute (1) a taxonomy of 68 functional implementation-level security features including a mapping to widely used security standards, (2) an examination of 21 popular security frameworks concerning which of these security features they provide, and (3) a discussion on the representation of security features in source code. Our taxonomy aims to aid developers in selecting appropriate security features and frameworks and relating them to security standards when they need to choose and implement security features for a software system.
Open AccessA Taxonomy of Functional Security Features and How They Can Be Located
Security must be considered in almost every software system. Unfortunately, selecting and implementing security features remains challenging due to the variety of security threats and possible countermeasures. While security standards are intended to help developers, they are usually too abstract and vague to help implement security features, or they merely help configure such. A resource that describes security features at an abstraction level between high-level (i.e., rather too general) and low-level (i.e., rather too specific) security standards could facilitate secure systems development. To realize security features, developers typically use external security frameworks, to minimize implementation mistakes. Even then, developers still make mistakes, often resulting in security vulnerabilities. When security incidents occur or the system needs to be audited or maintained, it is essential to know the implemented security features and, more importantly, where they are located. This task, commonly referred to as feature location, is often tedious and error-prone. Therefore, we have to support long-term tracking of implemented security features. We present a study of security features in the literature and their coverage in popular security frameworks. We contribute (1) a taxonomy of 68 functional implementation-level security features including a mapping to widely used security standards, (2) an examination of 21 popular security frameworks concerning which of these security features they provide, and (3) a discussion on the representation of security features in source code. Our taxonomy aims to aid developers in selecting appropriate security features and frameworks and relating them to security standards when they need to choose and implement security features for a software system.