Demo Data from SIGIR 2026 / reviewers in the wild / expert
Ashish Bijlani
dblp:21/7434
· DBLP profile ↗
4ranked-venue papers
1as first author
0since 2021 · last 2019
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 2Systems, architecture and hardware · 1 · 1 first-authorSoftware engineering, systems software and programming languages · 1
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.
| Software engineering, system software, and programming languages
4 papers |
Software maintenance and evolution · 74% Operating systems · 26% | |
| Network and information security
3 papers |
Systems and software security · 86% Web and mobile security · 14% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Storage systems · 100% |
Topics — the 11 heaviest of 11, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Systems and software security › vulnerability patching
automated patching |
0.4 | 1 | 2019 | Automating Patching of Vulnerable Open-Source Software Versions in Application Binaries · NDSS 2019 |
Systems and software security
vulnerability patching |
0.4 | 1 | 2019 | Automating Patching of Vulnerable Open-Source Software Versions in Application Binaries · NDSS 2019 |
Software maintenance and evolution › software dependencies
software dependency management |
0.4 | 1 | 2019 | Automating Patching of Vulnerable Open-Source Software Versions in Application Binaries · NDSS 2019 |
Storage systems
file systems |
0.4 | 1 | 2019 | Extension Framework for File Systems in User space · USENIX ATC 2019 |
Storage systems › file systems › file system design
user space file system |
0.4 | 1 | 2019 | Extension Framework for File Systems in User space · USENIX ATC 2019 |
Software maintenance and evolution
software ecosystems |
0.3 | 1 | 2017 | Identifying Open-Source License Violation and 1-day Security Risk at Large Scale · CCS 2017 |
Web and mobile security
mobile security |
0.1 | 1 | 2012 | CleanOS: Limiting Mobile Data Exposure with Idle Eviction · OSDI 2012 |
Operating systems › mobile systems
mobile operating systems |
0.1 | 1 | 2012 | CleanOS: Limiting Mobile Data Exposure with Idle Eviction · OSDI 2012 |
Operating systems › extensible operating systems
kernel extensibility |
0.1 | 1 | 2019 | Extension Framework for File Systems in User space · USENIX ATC 2019 |
Systems and software security
vulnerability discovery |
0.1 | 1 | 2017 | Identifying Open-Source License Violation and 1-day Security Risk at Large Scale · CCS 2017 |
Software maintenance and evolution › software dependencies
third-party library detection |
0.1 | 1 | 2017 | Identifying Open-Source License Violation and 1-day Security Risk at Large Scale · CCS 2017 |
Methods — techniques the papers use, named apart from their topics
provenance tracking · 0.6large-scale code analysis · 0.6
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2019 | Automating Patching of Vulnerable Open-Source Software Versions in Application Binaries
Ruian Duan, Ashish Bijlani, Yang Ji 0002, Omar Alrawi, Yiyuan Xiong, Moses Ike, Brendan Saltaformaggio, Wenke Lee |
NDSS | 2 |
| 2019 | Extension Framework for File Systems in User space
Ashish Bijlani, Umakishore Ramachandran |
USENIX ATC | 1 |
| 2017 | Identifying Open-Source License Violation and 1-day Security Risk at Large ScaleabstractWith millions of apps available to users, the mobile app market is rapidly becoming very crowded. Given the intense competition, the time to market is a critical factor for the success and profitability of an app. In order to shorten the development cycle, developers often focus their efforts on the unique features and workflows of their apps and rely on third-party Open Source Software (OSS) for the common features. Unfortunately, despite their benefits, careless use of OSS can introduce significant legal and security risks, which if ignored can not only jeopardize security and privacy of end users, but can also cause app developers high financial loss. However, tracking OSS components, their versions, and interdependencies can be very tedious and error-prone, particularly if an OSS is imported with little to no knowledge of its provenance. Ruian Duan, Ashish Bijlani, Meng Xu 0001, Taesoo Kim, Wenke Lee |
CCS | 2 |
| 2012 | CleanOS: Limiting Mobile Data Exposure with Idle Eviction
Phillip Ames, Sravan Bhamidipati, Ashish Bijlani, Roxana Geambasu, Nikhil Sarda |
OSDI | 4 |