Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Adam Batori

dblp:385/6388 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
1since 2021 · last 2024
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 1 · 1 since 2021

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
1 paper
Hardware security and side channels · 83% Blockchain and cryptocurrency security · 8% Digital forensics and information hiding · 8%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Hardware security and side channels
microarchitectural side channel
0.812024
SoK: SGX.Fail: How Stuff Gets eXposed · SP 2024
Hardware security and side channels › trusted execution environments
SGX attacks
0.812024
SoK: SGX.Fail: How Stuff Gets eXposed · SP 2024
Hardware security and side channels
trusted execution environments
0.812024
SoK: SGX.Fail: How Stuff Gets eXposed · SP 2024
Digital forensics and information hiding
digital rights management
0.212024
SoK: SGX.Fail: How Stuff Gets eXposed · SP 2024
Blockchain and cryptocurrency security › smart contract
privacy-preserving smart contracts
0.212024
SoK: SGX.Fail: How Stuff Gets eXposed · SP 2024

Methods — techniques the papers use, named apart from their topics

systematization of knowledge · 0.8survey · 0.8
YearPublicationVenuePosition
2024 SoK: SGX.Fail: How Stuff Gets eXposed
abstract
Intel’s Software Guard Extensions (SGX) promises an isolated execution environment, protected from all software running on the machine. As such, numerous works have sought to leverage SGX to provide confidentiality and integrity guarantees for code running in adversarial environments. In the past few years however, SGX has come under heavy fire, threatened by numerous hardware attacks. With Intel repeatedly patching SGX to regain security while consistently launching new (micro)architectures, it is increasingly difficult to track the applicability of various attack techniques across the SGX design landscape.Thus, in this paper we set out to survey and categorize various SGX attacks, their applicability to different SGX architectures, as well as the information leaked by them. We then set out to explore the effectiveness of SGX’s update mechanisms in preventing attacks on real-world deployments. Here, we study two commercial SGX applications. First, we investigate the SECRET network, an SGX-backed blockchain aiming to provide privacy-preserving smart contracts. Next, we also consider PowerDVD, a UHD Blu-Ray Digital Rights Management (DRM) software licensed to play discs on PCs. We show that in both cases vendors are unable to meet security goals originally envisioned for their products, presumably due to SGX’s long update timelines and the complexities of a manual update process. This in turn forces vendors to make difficult security/usability trade offs, resulting in security compromises.
Stephan van Schaik, Alexander Seto, Thomas Yurek, Adam Batori, Bader AlBassam, Daniel Genkin, Andrew Miller 0001, Eyal Ronen, Yuval Yarom, Christina Garman
SP4