Demo Data from EDBT 2026 / reviewers in the wild / expert
Naveen Sastry
dblp:14/2724
· DBLP profile ↗
7ranked-venue papers
1as first author
0since 2021 · last 2008
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 6 · 1 first-authorComputer networks · 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
7 papers |
Cryptographic protocols and secure computation · 38% Systems and software security · 24% Authentication and access control · 18% | |
| Software engineering, system software, and programming languages
1 paper |
Program verification · 77% Programming languages and type systems · 23% |
Topics — the 11 heaviest of 15, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Cryptographic protocols and secure computation
electronic voting |
0.1 | 2 | 2006 | Designing Voting Machines for Verification · USENIX Security Symposium 2006 Tamper-Evident, History-Independent, Subliminal-Free Data Structures on PROM Storage-or-How to Store Ballots on a Voting Machine (Extended Abstract) · S&P 2006 |
Authentication and access control
authentication |
0.0 | 1 | 2004 | Distillation Codes and Applications to DoS Resistant Multicast Authentication · NDSS 2004 |
Network security › attack strategy
denial-of-service attack |
0.0 | 1 | 2004 | Distillation Codes and Applications to DoS Resistant Multicast Authentication · NDSS 2004 |
Authentication and access control › authentication
multicast authentication |
0.0 | 1 | 2004 | Distillation Codes and Applications to DoS Resistant Multicast Authentication · NDSS 2004 |
Cyber-physical and IoT security
wireless sensor network security |
0.0 | 1 | 2004 | TinySec: a link layer security architecture for wireless sensor networks · SenSys 2004 |
Systems and software security
crash reporting |
0.0 | 1 | 2003 | Scrash: A System for Generating Secure Crash Information · USENIX Security Symposium 2003 |
Systems and software security
vulnerability discovery |
0.0 | 1 | 2003 | Scrash: A System for Generating Secure Crash Information · USENIX Security Symposium 2003 |
Systems and software security › isolation
isolation of untrusted code |
0.0 | 1 | 2008 | Verifiable functional purity in java · CCS 2008 |
Cryptographic protocols and secure computation › electronic voting
electronic voting security |
0.0 | 1 | 2006 | Designing Voting Machines for Verification · USENIX Security Symposium 2006 |
Electronic design automation › circuit simulation › reduced-order modeling
passive reduced-order modeling |
0.0 | 1 | 2006 | Tamper-Evident, History-Independent, Subliminal-Free Data Structures on PROM Storage-or-How to Store Ballots on a Voting Machine (Extended Abstract) · S&P 2006 |
Cryptographic primitives and cryptanalysis › symmetric cryptography
lightweight cryptography |
0.0 | 1 | 2004 | TinySec: a link layer security architecture for wireless sensor networks · SenSys 2004 |
Methods — techniques the papers use, named apart from their topics
static verification · 0.2cryptographic data structures · 0.1verification design · 0.1protocol analysis · 0.1tinysec · 0.0link layer protocol design · 0.0distillation codes · 0.0secure crash information generation · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2008 | Verifiable functional purity in javaabstractProving that particular methods within a code base are functionally pure--deterministic and side-effect free--would aid verification of security properties including function invertibility, reproducibility of computation, and safety of untrusted code execution. Until now it has not been possible to automatically prove a method is functionally pure within a high-level imperative language in wide use, such as Java. We discuss a technique to prove that methods are functionally pure by writing programs in a subset of Java called Joe-E; a static verifier ensures that programs fall within the subset. In Joe-E, pure methods can be trivially recognized from their method signature. To demonstrate the practicality of our approach, we refactor an AES library, an experimental voting machine implementation, and an HTML parser to use our techniques. We prove that their top-level methods are verifiably pure and show how this provides high-level security guarantees about these routines. Our approach to verifiable purity is an attractive way to permit functional-style reasoning about security properties while leveraging the familiarity, convenience, and legacy code of imperative languages. Matthew Finifter, Adrian Mettler, Naveen Sastry, David A. Wagner 0001 |
CCS | 3 |
| 2006 | Tamper-Evident, History-Independent, Subliminal-Free Data Structures on PROM Storage-or-How to Store Ballots on a Voting Machine (Extended Abstract)abstractWe enumerate requirements and give constructions for the vote storage unit of an electronic voting machine. In this application, the record of votes must survive even an unexpected failure of the machine; hence the data structure should be durable. At the same time, the order in which votes are cast must be hidden to protect the privacy of voters, so the data structure should be history-independent. Adversaries may try to surreptitiously add or delete votes from the storage unit after the election has concluded, so the storage should be tamper-evident. Finally, we must guard against an adversarial voting machine's attempts to mark ballots through the representation of the data structure, so we desire a subliminal-free representation. We leverage the properties of Programmable Read Only Memory (PROM), a special kind of write-once storage medium, to meet these requirements. We give constructions for data structures on PROM storage that simultaneously satisfy all our desired properties. Our techniques can significantly reduce the need to verify code running on a voting machine. David Molnar, Tadayoshi Kohno, Naveen Sastry, David A. Wagner 0001 |
S&P | 3 |
| 2006 | Designing Voting Machines for Verification
Naveen Sastry |
USENIX Security Symposium | 1 |
| 2005 | Cryptographic Voting Protocols: A Systems Perspective
Chris Karlof, Naveen Sastry, David A. Wagner 0001 |
USENIX Security Symposium | 2 |
| 2004 | Distillation Codes and Applications to DoS Resistant Multicast Authentication
Chris Karlof, Naveen Sastry, Adrian Perrig, J. D. Tygar |
NDSS | 2 |
| 2004 | TinySec: a link layer security architecture for wireless sensor networksabstractWe introduce TinySec, the first fully-implemented link layer security architecture for wireless sensor networks. In our design, we leverage recent lessons learned from design vulnerabilities in security protocols for other wireless networks such as 802.11b and GSM. Conventional security protocols tend to be conservative in their security guarantees, typically adding 16--32 bytes of overhead. With small memories, weak processors, limited energy, and 30 byte packets, sensor networks cannot afford this luxury. TinySec addresses these extreme resource constraints with careful design; we explore the tradeoffs among different cryptographic primitives and use the inherent sensor network limitations to our advantage when choosing parameters to find a sweet spot for security, packet overhead, and resource requirements. TinySec is portable to a variety of hardware and radio platforms. Our experimental results on a 36 node distributed sensor network application clearly demonstrate that software based link layer protocols are feasible and efficient, adding less than 10% energy, latency, and bandwidth overhead. Chris Karlof, Naveen Sastry, David A. Wagner 0001 |
SenSys | 2 |
| 2003 | Scrash: A System for Generating Secure Crash Information
Peter Broadwell, Matthew Harren, Naveen Sastry |
USENIX Security Symposium | 3 |