Skip to main navigation Skip to search Skip to main content

Speculative execution atacks and cloud security

  • Ohio State University

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

2 Scopus citations

Abstract

Speculative execution attacks, such as Meltdown, Spectre, and Foreshadow, exploit performance optimization features in modern processors and micro-architectural side channels to breach the confi-dentiality of computer systems. Although few incidences have been reported in the wild, their very existence imperils the promise of strong security isolation of cloud computing. This panel will invite experts from both academia and industry to discuss the impacts of speculative execution attacks on the cloud industry. The aim of the panel is to understand the state of the art of academic research and industry practice, and to explore future academic research directions and industry best practices.

Original languageEnglish
Title of host publicationCCSW 2019 - Proceedings of the 2019 ACM SIGSAC Conference on Cloud Computing Security Workshop
PublisherAssociation for Computing Machinery
Pages201
Number of pages1
ISBN (Electronic)9781450368261
DOIs
StatePublished - Nov 11 2019
Event10th ACM SIGSAC Conference on Cloud Computing Security Workshop, CCSW 2019, co-located with the 26th ACM Conference on Computer and Communications Security, CCS 2019 - London, United Kingdom
Duration: Nov 11 2019 → …

Publication series

NameProceedings of the ACM Conference on Computer and Communications Security
ISSN (Print)1543-7221

Conference

Conference10th ACM SIGSAC Conference on Cloud Computing Security Workshop, CCSW 2019, co-located with the 26th ACM Conference on Computer and Communications Security, CCS 2019
Country/TerritoryUnited Kingdom
CityLondon
Period11/11/19 → …

Keywords

  • Cloud security
  • Side channels
  • Speculative execution attacks

Fingerprint

Dive into the research topics of 'Speculative execution atacks and cloud security'. Together they form a unique fingerprint.

Cite this