2022 IEEE Symposium on Security and Privacy (SP) 2022
DOI: 10.1109/sp46214.2022.9833611
|View full text |Cite
|
Sign up to set email alerts
|

Waldo: A Private Time-Series Database from Function Secret Sharing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 26 publications
(7 citation statements)
references
References 58 publications
0
7
0
Order By: Relevance
“…More recently, Liu et al [76] employed secure multi-party computation (SMC) techniques for privacypreserving collaborative medical time-series analysis, based on dynamic time warping. Dauterman et al [31] use function secret sharing (FSS) to support various functionalities, e.g., multi-predicate filtering, on private time-series databases. All these authors focus on simple collaborative time-series tasks and not on the privacy-preserving training of machine learning models on time-series data, which is the main focus of this work.…”
Section: A Privacy-preserving Time-seriesmentioning
confidence: 99%
“…More recently, Liu et al [76] employed secure multi-party computation (SMC) techniques for privacypreserving collaborative medical time-series analysis, based on dynamic time warping. Dauterman et al [31] use function secret sharing (FSS) to support various functionalities, e.g., multi-predicate filtering, on private time-series databases. All these authors focus on simple collaborative time-series tasks and not on the privacy-preserving training of machine learning models on time-series data, which is the main focus of this work.…”
Section: A Privacy-preserving Time-seriesmentioning
confidence: 99%
“…It is recalled that in the attributed graph encryption phase, each value demanding protection is encoded into a one-hot vector. The adoption of such encoding strategy, inspired by [39], [42], is actually useful in providing an alternative way to avoid fresh FSS keys in OblivGM for evaluating the same predicate on different attribute values. At a high level, the idea is that with such encoding, FSS keys can be evaluated against the public locations of entries in one-hot vectors.…”
Section: Secure Query Token Generationmentioning
confidence: 99%
“…On another hand, as the one-hot vectors are protected under the RSS technique in OblivGM, the above idea has to be instantiated over the RSS-protected one-hot vectors. Inspired by [42], OblivGM leverages the replication property of RSS and constructs three pairs of FSS keys for each private predicate so as to bridge FSS and RSS. How this can actually work out will become more clear in the subsequent phase of secure attributed subgraph matching, which will be introduced shortly in Section V-D.…”
Section: Secure Query Token Generationmentioning
confidence: 99%
“…In the past few years, we've seen an explosion of academic and industrial cryptographic systems built on distributed trust; some applications are based on secure multi-party computation [9,34,86] (e.g. private search [23,24,64,82], private analytics [7,11,19,27,42] private media delivery [38], private blocklist lookups [46], private DNS [72], anonymous messaging [17,20,28,48,49,84], and cryptocurrency wallets [30,31,45,63,67,70,75]), while others are based on Byzantine fault-tolerant consensus and blockchains [6,8,15,25,36,37,47,50,56,88].…”
Section: Introductionmentioning
confidence: 99%
“…Distributed-trust systems only provide strong security guarantees insofar as there is no central point of attack that allows an attacker to compromise more than an application-specific threshold of parties. Many academic works simply assume the existence of multiple non-colluding servers [20,23,24,28,38,38,46,82], but an application developer that wants to deploy a distributed-trust system faces difficult questions: who should have administrative control over the different trust domains, and how do you convince another party that you do not control to run your system? We study the difficulties developers have faced when deploying distributed-trust systems in §2.…”
Section: Introductionmentioning
confidence: 99%