2018
DOI: 10.1007/978-3-030-02450-5_3
|View full text |Cite
|
Sign up to set email alerts
|

The Foul Adversary: Formal Models

Abstract: In classical notions of privacy in computer security, users attempt to keep their data private. A user that is bribed, extorted or blackmailed (i.e., coerced ) may not do so. To get a general model of coercion, we strengthen the Dolev-Yao adversary with the ability to coerce others, to the foul adversary. We show that, depending on the setting, subtly di↵erent abilities should be assigned to the adversary -whereas existing approaches are one-size-fits-all. The variations of the foul adversary are formalised an… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2020
2020
2020
2020

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(1 citation statement)
references
References 31 publications
0
1
0
Order By: Relevance
“…In addition, the attacker behaviour in the current model is limited. Advanced attacker models can be defined for not only security but also privacy properties, following the style of (Dong and Muller, 2018), and the automatic verification algorithms need to be developed with respect to the attacks, for example using logic reasoning of attacks such as (Li et al ., 2017). In addition, the formal verification in this work only focuses on the application design; the implementation may introduce vulnerabilities; therefore, formal verification on the implementation is needed.…”
Section: Discussionmentioning
confidence: 99%
“…In addition, the attacker behaviour in the current model is limited. Advanced attacker models can be defined for not only security but also privacy properties, following the style of (Dong and Muller, 2018), and the automatic verification algorithms need to be developed with respect to the attacks, for example using logic reasoning of attacks such as (Li et al ., 2017). In addition, the formal verification in this work only focuses on the application design; the implementation may introduce vulnerabilities; therefore, formal verification on the implementation is needed.…”
Section: Discussionmentioning
confidence: 99%