2013 International Conference on Social Computing 2013
DOI: 10.1109/socialcom.2013.87
|View full text |Cite
|
Sign up to set email alerts
|

In Guards We Trust: Security and Privacy in Operating Systems Revisited

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
3
2

Relationship

2
3

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 24 publications
0
3
0
Order By: Relevance
“…In particular, we state some preliminary definitions of risk and security needed to form a collaboration system for risk mitigation, which is expected to rely on several security aspects [9], such as accountability or authentication and access control mechanisms [10]. For systems in which unknown users may enter, the concept of trust is usually used to monitor users behavior along time [11].…”
Section: Framing Data Structuresmentioning
confidence: 99%
“…In particular, we state some preliminary definitions of risk and security needed to form a collaboration system for risk mitigation, which is expected to rely on several security aspects [9], such as accountability or authentication and access control mechanisms [10]. For systems in which unknown users may enter, the concept of trust is usually used to monitor users behavior along time [11].…”
Section: Framing Data Structuresmentioning
confidence: 99%
“…To ensure that audio filtering is always-invoked in audio input and output, the access control policy of the component-based operating system needs to enforce that audio input and output devices can only be accessed via the audio guard. More details on the concept of an audio filtering guard are provided by Hanspach and Keller [17].…”
Section: Countermeasures Against Information Leaks From Covert Nementioning
confidence: 99%
“…Finally, exploiting illegitimate access to components would be a special case of a flawed system policy, where a policy circumvents an operating system guard g k that protects access to a component c k , managing a shared resource, and allows pi and pi to exchange messages via c k . The use of operating system guards to handle shared resources to protect applications from untrusted components has been described by Payne et al [29], Robinson et al [31,32], Heckman et al [15], and Hanspach and Keller [13].…”
Section: Related Workmentioning
confidence: 99%