A comparison study on Flush + Reload and Prime + Probe attacks on AES using machine learning approaches

Zirak Allaf, Mo Adda, Alexander Gegov

Research output: Chapter in Book/Report/Conference proceedingConference contribution

329 Downloads (Pure)

Abstract

AES, ElGamal are two examples of algorithms that have been developed in cryptography to protect data in a variety of domains including native and cloud systems, and mobile applications. There has been a good deal of research into the use of side channel attacks on these algorithms. This work has conducted an experiment to detect malicious loops inside Flush+Reload and Prime+Prob attack programs against AES through the exploitation of Hardware Performance Counters (HPC). This paper examines the accuracy and eciency of three machine learning algorithms: Neural Network (NN); Decision Tree C4.5; and K Nearest Neighbours (KNN). The study also shows how Standard Performance Evaluation Corporation (SPEC) CPU2006 benchmarks impact predictions.
Original languageEnglish
Title of host publicationAdvances in Intelligent Systems and Computing
EditorsFei Chao, Steven Schockaert, Qingfu Zhang
PublisherSpringer
Pages203-213
Number of pages11
ISBN (Electronic)978-319669397
ISBN (Print)978-3319669380
DOIs
Publication statusPublished - Sep 2017
EventThe 17th UK Workshop on Computational Intelligence - Cardiff University, Cardiff, United Kingdom
Duration: 6 Sep 20178 Sep 2017

Publication series

NameAdvances in Intelligent Systems and Computing (AISC)
PublisherSpringer, Cham
Volume650
ISSN (Print)2194-5357
ISSN (Electronic)2194-5365

Conference

ConferenceThe 17th UK Workshop on Computational Intelligence
Abbreviated titleUKCI 2017
Country/TerritoryUnited Kingdom
CityCardiff
Period6/09/178/09/17

Keywords

  • side-channel attack
  • machine learning
  • Flush Reload
  • Prime Probe
  • AES

Fingerprint

Dive into the research topics of 'A comparison study on Flush + Reload and Prime + Probe attacks on AES using machine learning approaches'. Together they form a unique fingerprint.

Cite this