Demo Data from SIGIR 2026 / reviewers in the wild / expert
Elad Ben-Yehuda
dblp:207/1859
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2017
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software 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.
| Network and information security
1 paper |
Systems and software security · 50% Authentication and access control · 50% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Cloud and datacenter computing · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Authentication and access control › access control
least privilege |
0.3 | 1 | 2017 | WatchIT: Who Watches Your IT Guy? · SOSP 2017 |
Systems and software security
operating system security |
0.3 | 1 | 2017 | WatchIT: Who Watches Your IT Guy? · SOSP 2017 |
Cloud and datacenter computing › workload isolation
container isolation |
0.1 | 1 | 2017 | WatchIT: Who Watches Your IT Guy? · SOSP 2017 |
Methods — techniques the papers use, named apart from their topics
resource prediction · 0.6container isolation · 0.6
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2017 | WatchIT: Who Watches Your IT Guy?abstractSystem administrators have unlimited access to system resources. As the Snowden case highlighted, these permissions can be exploited to steal valuable personal, classified, or commercial data. This problem is exacerbated when a third party administers the system. For example, a bank outsourcing its IT would not want to allow administrators access to the actual data. We propose WatchIT: a strategy that constrains IT personnel's view of the system and monitors their actions. To this end, we introduce the abstraction of perforated containers -- while regular Linux containers are too restrictive to be used by system administrators, by "punching holes" in them, we strike a balance between information security and required administrative needs. Following the principle of least privilege, our system predicts which system resources should be accessible for handling each IT issue, creates a perforated container with the corresponding isolation, and deploys it as needed for fixing the problem. Noam Shalev, Idit Keidar, Yaron Weinsberg, Yosef Moatti, Elad Ben-Yehuda |
SOSP | 5 |