Proceedings of the 2016 New Security Paradigms Workshop 2016
DOI: 10.1145/3011883.3011890
|View full text |Cite
|
Sign up to set email alerts
|

Content-based security for the web

Abstract: The World Wide Web has become the most common platform for building applications and delivering content. Yet despite years of research, the web continues to face severe security challenges related to data integrity and confidentiality. Rather than continuing the exploit-and-patch cycle, we propose addressing these challenges at an architectural level, by supplementing the web's existing connection-based and server-based security models with a new approach: contentbased security. With this approach, content is … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 38 publications
(36 reference statements)
0
6
0
Order By: Relevance
“…Our work highlights significant UI vulnerabilities in ShadowCrypt. Even though ShadowCrypt has not witnessed widespread deployment, we believe it is critical to understand the security of such mechanisms, which could influence the design of ongoing research systems [7,13,17,19,[28][29][30]36] and future technologies. Our work demonstrates that it is important for any system that aims to secure browser-based I/O (even beyond ShadowCrypt) to explicitly consider UI attacks in its threat model.…”
Section: Contributionsmentioning
confidence: 99%
See 1 more Smart Citation
“…Our work highlights significant UI vulnerabilities in ShadowCrypt. Even though ShadowCrypt has not witnessed widespread deployment, we believe it is critical to understand the security of such mechanisms, which could influence the design of ongoing research systems [7,13,17,19,[28][29][30]36] and future technologies. Our work demonstrates that it is important for any system that aims to secure browser-based I/O (even beyond ShadowCrypt) to explicitly consider UI attacks in its threat model.…”
Section: Contributionsmentioning
confidence: 99%
“….attachShadow({mode: 'open'}); 3 root.innerHTML = "<shadow></shadow>"; 4 shadow = root.querySelector("shadow"); 5 shadowCryptNodes = shadow.getDistributedNodes(); 6 plaintext = shadowCryptNodes [1].querySelector('.delegate') 7 .value;…”
Section: Shadow Dom Futurementioning
confidence: 99%
“…However, designing mechanisms that are efficient, scalable, and usable in order to meet the security requirements of integrity, authenticity, confidentiality and privacy are very much open problems that a few researchers have started to research on. [7,52,59]. A issue in meeting these requirements is to establish trust in the keys utilized for enforce the security mechanisms.…”
Section: Related Workmentioning
confidence: 99%
“…A more serious issue is that there is no provision for key revocation and reflecting key revocation in trust schemas. Afanasyev et al [7] [8] proposed a DNS like name service for NDN to identify the need to look up names. While the proposed system has features similar to DNSSEC [9] and to security extensions of DNS, they show that their design differs from the DNS design mainly due to how NDN operates and NDN caching mechanisms.…”
Section: Related Workmentioning
confidence: 99%
“…However, NDN suffers from new security issues such as interest flooding, cache poisoning, access control, and data authenticity, to name a few [ 11 ]. Existing solutions in the literature consider traditional security approaches adopted in the vanilla NDN for fixed or wired networks [ 12 , 13 ]. In the current solutions, the content is signed by the producer and then by the authority that issued the certificate to the producer.…”
Section: Introductionmentioning
confidence: 99%