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.

Arjun Narayan

dblp:28/10322 · DBLP profile ↗
← Back
8ranked-venue papers
2as 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 · 4 · 1 first-authorSystems, architecture and hardware · 2 · 1 first-authorSecurity and privacy · 2

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
7 papers
Privacy and data protection · 59% Cryptographic protocols and secure computation · 21% Systems and software security · 8%
Software engineering, system software, and programming languages
2 papers
Program verification · 54% Programming languages and type systems · 46%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 50% Electronic design automation · 50%

Topics — the 12 heaviest of 15, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Privacy and data protection
differential privacy
0.842017
DStress: Efficient Differentially Private Computations on Distributed Data · EuroSys 2017
Verifiable differential privacy · EuroSys 2015
Linear dependent types for differential privacy · POPL 2013
Privacy and data protection
privacy-preserving data analysis
0.422015
Verifiable differential privacy · EuroSys 2015
DJoin: Differentially Private Join Queries over Distributed Databases · OSDI 2012
Cryptographic protocols and secure computation
verifiable computation
0.212015
Verifiable differential privacy · EuroSys 2015
Privacy and data protection › differential privacy › privacy auditing
verification of differential privacy
0.212015
Verifiable differential privacy · EuroSys 2015
Systems and software security
operating system security
0.212014
Ironclad Apps: End-to-End Security via Automated Full-System Verification · OSDI 2014
Program verification › system verification
end-to-end verification
0.212014
Ironclad Apps: End-to-End Security via Automated Full-System Verification · OSDI 2014
Security and privacy of machine learning
adversarial attack
0.112011
Differential Privacy Under Fire · USENIX Security Symposium 2011
Digital forensics and information hiding › digital forensics
network forensics
0.112011
Secure network provenance · SOSP 2011
Electronic design automation › hardware verification and test
fault diagnosis
0.112011
Secure network provenance · SOSP 2011
Distributed systems
fault tolerance
0.112011
Secure network provenance · SOSP 2011
Graph data management
distributed graph
0.112017
DStress: Efficient Differentially Private Computations on Distributed Data · EuroSys 2017
Privacy and data protection › privacy evaluation
privacy-utility tradeoff
0.112015
Verifiable differential privacy · EuroSys 2015

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

differential privacy · 1.1automated full-system verification · 0.4type theory · 0.3linear types · 0.3dependent types · 0.3tamper-evident logging · 0.2verification · 0.2adversarial analysis · 0.1
YearPublicationVenuePosition
2017 DStress: Efficient Differentially Private Computations on Distributed Data
abstract
In this paper, we present DStress, a system that can efficiently perform computations on graphs that contain confidential data. DStress assumes that the graph is physically distributed across many participants, and that each participant only knows a small subgraph; it protects privacy by enforcing tight, provable limits on how much each participant can learn about the rest of the graph.
Antonis Papadimitriou, Arjun Narayan, Andreas Haeberlen
EuroSys2
2015 Verifiable differential privacy
abstract
Working with sensitive data is often a balancing act between privacy and integrity concerns. Consider, for instance, a medical researcher who has analyzed a patient database to judge the effectiveness of a new treatment and would now like to publish her findings. On the one hand, the patients may be concerned that the researcher's results contain too much information and accidentally leak some private fact about themselves; on the other hand, the readers of the published study may be concerned that the results contain too little information, limiting their ability to detect errors in the calculations or flaws in the methodology.
Arjun Narayan, Ariel Feldman, Antonis Papadimitriou, Andreas Haeberlen
EuroSys1
2014 Differential Privacy: An Economic Method for Choosing Epsilon
abstract
Differential privacy is becoming a gold standard notion of privacy; it offers a guaranteed bound on loss of privacy due to release of query results, even under worst-case assumptions. The theory of differential privacy is an active research area, and there are now differentially private algorithms for a wide range of problems. However, the question of when differential privacy works in practice has received relatively little attention. In particular, there is still no rigorous method for choosing the key parameter ε, which controls the crucial tradeoff between the strength of the privacy guarantee and the accuracy of the published results. In this paper, we examine the role of these parameters in concrete applications, identifying the key considerations that must be addressed when choosing specific values. This choice requires balancing the interests of two parties with conflicting objectives: the data analyst, who wishes to learn something abou the data, and the prospective participant, who must decide whether to allow their data to be included in the analysis. We propose a simple model that expresses this balance as formulas over a handful of parameters, and we use our model to choose ε on a series of simple statistical studies. We also explore a surprising insight: in some circumstances, a differentially private study can be more accurate than a non-private study for the same cost, under our model. Finally, we discuss the simplifying assumptions in our model and outline a research agenda for possible refinements.
Justin Hsu, Marco Gaboardi, Andreas Haeberlen, Sanjeev Khanna, Arjun Narayan, Benjamin C. Pierce, Aaron Roth 0001
CSF5
2014 Ironclad Apps: End-to-End Security via Automated Full-System Verification
Chris Hawblitzel, Jon Howell, Jacob R. Lorch, Arjun Narayan, Bryan Parno, Danfeng Zhang, Brian Zill
OSDI4
2013 Linear dependent types for differential privacy
abstract
Differential privacy offers a way to answer queries about sensitive information while providing strong, provable privacy guarantees, ensuring that the presence or absence of a single individual in the database has a negligible statistical effect on the query's result. Proving that a given query has this property involves establishing a bound on the query's sensitivity---how much its result can change when a single record is added or removed.
Marco Gaboardi, Andreas Haeberlen, Justin Hsu, Arjun Narayan, Benjamin C. Pierce
POPL4
2012 DJoin: Differentially Private Join Queries over Distributed Databases
Arjun Narayan, Andreas Haeberlen
OSDI1
2011 Secure network provenance
abstract
This paper introduces secure network provenance (SNP), a novel technique that enables networked systems to explain to their operators why they are in a certain state -- e.g., why a suspicious routing table entry is present on a certain router, or where a given cache entry originated. SNP provides network forensics capabilities by permitting operators to track down faulty or misbehaving nodes, and to assess the damage such nodes may have caused to the rest of the system. SNP is designed for adversarial settings and is robust to manipulation; its tamper-evident properties ensure that operators can detect when compromised nodes lie or falsely implicate correct nodes.
Wenchao Zhou, Qiong Fei, Arjun Narayan, Andreas Haeberlen, Boon Thau Loo, Micah Sherr
SOSP3
2011 Differential Privacy Under Fire
Andreas Haeberlen, Benjamin C. Pierce, Arjun Narayan
USENIX Security Symposium3