Demo Data from EDBT 2026 / reviewers in the wild / expert
Paschal C. Amusuo
dblp:329/3995
· DBLP profile ↗
4ranked-venue papers
3as first author
4since 2021 · last 2025
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 3 · 3 first-author · 3 since 2021Security and privacy · 1 · 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
2 papers |
Authentication and access control · 42% Systems and software security · 37% Network security · 21% | |
| Software engineering, system software, and programming languages
4 papers |
Software testing · 53% Debugging and program repair · 23% Software maintenance and evolution · 16% |
Topics — the 12 heaviest of 16, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Authentication and access control
access control |
0.9 | 1 | 2025 | $ZTD_{\text{JAVA}}$: Mitigating Software Supply Chain Vulnerabilities via Zero-Trust Dependencies · ICSE 2025 |
Authentication and access control › access control
least privilege |
0.9 | 1 | 2025 | $ZTD_{\text{JAVA}}$: Mitigating Software Supply Chain Vulnerabilities via Zero-Trust Dependencies · ICSE 2025 |
Systems and software security
software supply chain security |
0.9 | 1 | 2025 | $ZTD_{\text{JAVA}}$: Mitigating Software Supply Chain Vulnerabilities via Zero-Trust Dependencies · ICSE 2025 |
Network security › network security architecture
zero trust architecture |
0.9 | 1 | 2025 | $ZTD_{\text{JAVA}}$: Mitigating Software Supply Chain Vulnerabilities via Zero-Trust Dependencies · ICSE 2025 |
Systems and software security
vulnerability discovery |
0.7 | 1 | 2023 | Systematically Detecting Packet Validation Vulnerabilities in Embedded Network Stacks · ASE 2023 |
Software testing
systematic testing |
0.7 | 1 | 2023 | Systematically Detecting Packet Validation Vulnerabilities in Embedded Network Stacks · ASE 2023 |
Debugging and program repair › software debugging
software failure analysis |
0.6 | 1 | 2022 | Reflections on software failure analysis · ESEC/SIGSOFT FSE 2022 |
Software maintenance and evolution › software ecosystems
dependency management |
0.3 | 1 | 2025 | $ZTD_{\text{JAVA}}$: Mitigating Software Supply Chain Vulnerabilities via Zero-Trust Dependencies · ICSE 2025 |
Operating systems › operating system family
linux |
0.3 | 1 | 2025 | LEMIX: Enabling Testing of Embedded Applications as Linux Applications · USENIX Security Symposium 2025 |
Software maintenance and evolution
software ecosystems |
0.3 | 1 | 2025 | $ZTD_{\text{JAVA}}$: Mitigating Software Supply Chain Vulnerabilities via Zero-Trust Dependencies · ICSE 2025 |
Software testing
fault detection |
0.2 | 1 | 2022 | Reflections on software failure analysis · ESEC/SIGSOFT FSE 2022 |
Debugging and program repair
program repair |
0.2 | 1 | 2022 | Reflections on software failure analysis · ESEC/SIGSOFT FSE 2022 |
Methods — techniques the papers use, named apart from their topics
systematic testing · 2.0fuzzing · 2.0dynamic analysis · 2.0zero-trust architecture · 1.7runtime monitoring · 1.7failure study · 0.6
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | $ZTD_{\text{JAVA}}$: Mitigating Software Supply Chain Vulnerabilities via Zero-Trust DependenciesabstractThird-party libraries like Log4j accelerate software application development but introduce substantial risk. Vulnerabilities in these libraries have led to Software Supply Chain (SSC) attacks that compromised resources within the host system. These attacks benefit from current application permissions approaches: third-party libraries are implicitly trusted in the application runtime. An application runtime designed with ZeroTrust Architecture (ZTA) principles - secure access to resources, continuous monitoring, and least-privilege enforcement - could mitigate SSC attacks, as it would give zero implicit trust to these libraries. However, no individual security defense incorporates these principles at a low runtime cost. This paper proposes Zero-Trust Dependencies to mitigate SSC vulnerabilities: we apply the NIST ZTA to software applications. First, we assess the expected effectiveness and configuration cost of Zero-Trust Dependencies using a study of third-party software libraries and their vulnerabilities. Then, we present a system design,$\text{ZTD}_{\text{Sys}}$, that enables the application of Zero-Trust Dependencies to software applications and a prototype,$\text{ZTD}_{\text{JAVA}}$, for Java applications. Finally, with evaluations on recreated vulnerabilities and realistic applications, we show that$\text{ZTD}_{\text{JAVA}}$can defend against prevalent vulnerability classes, introduces negligible cost, and is easy to configure and use. Paschal C. Amusuo, Kyle A. Robinson, Tanmay Singla, Huiyun Peng, Aravind Machiry, Santiago Torres-Arias, James C. Davis 0001 |
ICSE | 1 |
| 2025 | LEMIX: Enabling Testing of Embedded Applications as Linux Applications
Sai Ritvik Tanksalkar, Siddharth Muralee, Srihari Danduri, Paschal C. Amusuo, Antonio Bianchi, James C. Davis 0001, Aravind Machiry |
USENIX Security Symposium | 4 |
| 2023 | Systematically Detecting Packet Validation Vulnerabilities in Embedded Network StacksabstractEmbedded Network Stacks (ENS) enable low-resource devices to communicate with the outside world, facilitating the development of Internet of Things and Cyber-Physical Systems. Some defects in ENS are thus high-severity cybersecurity vulnerabilities: they are remotely triggerable and can impact the physical world. While prior research has shed light on the characteristics of defects in many classes of software systems, no study has described the properties of ENS defects nor identified a systematic technique to expose them. The most common automated approach to detecting ENS defects is feedback-driven randomized dynamic analysis (“fuzzing”), a costly and unpredictable technique. This paper provides the first systematic characterization of cybersecurity vulnerabilities in ENS. We analyzed 61 vulnerabilities across 6 open-source ENS. Most of these ENS defects are concentrated in the transport and network layers of the network stack, require reaching different states in the network protocol, and can be triggered by only 1–2 modifications to a single packet. We therefore propose a novel systematic testing framework that focuses on the transport and network layers, uses seeds that cover a network protocol's states, and systematically modifies packet fields. We evaluate this framework on 4 ENS and replicated 12 of the 14 reported IP/TCP/UDP vulnerabilities. On recent versions of these ENSs, it discovered 7 novel defects (6 assigned CVES) during a bounded systematic test that covered all protocol states and made up to 3 modifications per packet. We found defects in 3 of the 4 ENS we tested that had not been found by prior fuzzing research. Our results suggest that fuzzing should be deferred until after systematic testing is employed. Paschal C. Amusuo, Ricardo Andrés Calvo Méndez, Aravind Machiry, James C. Davis 0001 |
ASE | 1 |
| 2022 | Reflections on software failure analysisabstractFailure studies are important in revealing the root causes, behaviors, and life cycle of defects in software systems. These studies either focus on understanding the characteristics of defects in specific classes of systems, or the characteristics of a specific type of defect in the systems it manifests in. Failure studies have influenced various software engineering research directions, especially in the area of software evolution, defect detection, and program repair. Paschal C. Amusuo, Aishwarya Sharma, Siddharth R. Rao, Abbey Vincent, James C. Davis 0001 |
ESEC/SIGSOFT FSE | 1 |