Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Houda Naji

dblp:380/2633 · DBLP profile ↗
← Back
3ranked-venue papers
2as first author
3since 2021 · last 2025
0009-0005-0280-5536ORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 2 · 1 first-author · 2 since 2021Software engineering, systems software and programming languages · 1 · 1 first-author · 1 since 2021

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Network and information security
3 papers
Usable security · 62% Blockchain and cryptocurrency security · 29% Systems and software security · 10%
Software engineering, system software, and programming languages
2 papers
Empirical software engineering · 67% Requirements engineering and software design · 33%

Topics — the 5 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
developer studies
1.722025
"It's not my responsibility to write them": An Empirical Study of Software Product Managers and Security Requirements · USENIX Security Symposium 2025
Relationship Status: "It's Complicated" Developer-Security Expert Dynamics in Scrum · ICSE 2025
Requirements engineering and software design › non-functional requirements
security requirements
0.912025
"It's not my responsibility to write them": An Empirical Study of Software Product Managers and Security Requirements · USENIX Security Symposium 2025
Usable security › developer-centered security
developer security practices
0.812024
Defying the Odds: Solana's Unexpected Resilience in Spite of the Security Challenges Faced by Developers · CCS 2024
Blockchain and cryptocurrency security
smart contract security
0.812024
Defying the Odds: Solana's Unexpected Resilience in Spite of the Security Challenges Faced by Developers · CCS 2024
Systems and software security
secure software development
0.312025
"It's not my responsibility to write them": An Empirical Study of Software Product Managers and Security Requirements · USENIX Security Symposium 2025

Methods — techniques the papers use, named apart from their topics

qualitative interview study · 1.7interview study · 1.7interviews · 0.8code review study · 0.8automated analysis · 0.8
YearPublicationVenuePosition
2025 Relationship Status: "It's Complicated" Developer-Security Expert Dynamics in Scrum
abstract
The high number of cyber threats poses significant challenges, with impactful software exploits ranging from data theft to ransomware deployment. Unfortunately, past research highlighted limited security expertise within development teams. Collaboration between developers and security experts, therefore, emerges as one of the few workable means to address this gap. In this paper, we explore the complex interplay between developers and security experts within Scrum, one of the most widely adopted frameworks which actively promotes collaboration, to shed light on their working relationship, challenges, and potential avenues for improvement. To this end, we conducted a qualitative interview study with 14 developers and 13 security experts. Our qualitative results reveal three communication patterns and five shared challenges between the groups affecting the develop-security expert collaboration. Top challenges include consistent interaction difficulties and the lack of workable means to balance business and security needs. As a result, we found that three core Scrum values (openness, respect, courage) are missing from this relationship. Based on our results, we propose recommendations for fostering a healthy collaboration between developers and security experts, both within and beyond Scrum.
Houda Naji, Marco Gutfleisch, Alena Naiakshina
ICSE1
2025 "It's not my responsibility to write them": An Empirical Study of Software Product Managers and Security Requirements
Houda Naji, Felix Reichmann, Tobias Bruns, M. Angela Sasse, Alena Naiakshina
USENIX Security Symposium1
2024 Defying the Odds: Solana's Unexpected Resilience in Spite of the Security Challenges Faced by Developers
abstract
Solana gained considerable attention as one of the most popular blockchain platforms for deploying decentralized applications. Compared to Ethereum, however, we observe a lack of research on how Solana smart contract developers handle security, what challenges they encounter, and how this affects the overall security of the ecosystem. To address this, we conducted the first comprehensive study on the Solana platform consisting of a 90-minute Solana smart contract code review task with 35 participants followed by interviews with a subset of seven participants. Our study shows, quite alarmingly, that none of the participants could detect all important security vulnerabilities in a code review task and that 83% of the participants are likely to release vulnerable smart contracts. Our study also sheds light on the root causes of developers' challenges with Solana smart contract development, suggesting the need for better security guidance and resources. In spite of these challenges, our automated analysis on currently deployed Solana smart contracts surprisingly suggests that the prevalence of vulnerabilities - especially those pointed out as the most challenging in our developer study - is below 0.3%. We explore the causes of this counter-intuitive resilience and show that frameworks, such as Anchor, are aiding Solana developers in deploying secure contracts.
Sébastien Andreina, Tobias Cloosters, Lucas Davi, Jens-Rene Giesen, Marco Gutfleisch, Ghassan Karame, Alena Naiakshina, Houda Naji
CCS8