Flow Table Security in SDN: Adversarial Reconnaissance and Intelligent Attacks

Mingli Yu, Ting He, Patrick McDaniel, Quinn K. Burke

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

Abstract

The performance-driven design of SDN architectures leaves many security vulnerabilities, a notable one being the communication bottleneck between the controller and the switches. Functioning as a cache between the controller and the switches, the flow table mitigates this bottleneck by caching flow rules received from the controller at each switch, but is very limited in size due to the high cost and power consumption of the underlying storage medium. It thus presents an easy target for attacks. Observing that many existing defenses are based on simplistic attack models, we develop a model of intelligent attacks that exploit specific cache-like behaviors of the flow table to infer its internal configuration and state, and then design attack parameters accordingly. Our evaluations show that such attacks can accurately expose the internal parameters of the target flow table and cause measurable damage with the minimum effort.

Original languageEnglish (US)
Title of host publicationINFOCOM 2020 - IEEE Conference on Computer Communications
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages1519-1528
Number of pages10
ISBN (Electronic)9781728164120
DOIs
StatePublished - Jul 2020
Event38th IEEE Conference on Computer Communications, INFOCOM 2020 - Toronto, Canada
Duration: Jul 6 2020Jul 9 2020

Publication series

NameProceedings - IEEE INFOCOM
Volume2020-July
ISSN (Print)0743-166X

Conference

Conference38th IEEE Conference on Computer Communications, INFOCOM 2020
CountryCanada
CityToronto
Period7/6/207/9/20

All Science Journal Classification (ASJC) codes

  • Computer Science(all)
  • Electrical and Electronic Engineering

Fingerprint Dive into the research topics of 'Flow Table Security in SDN: Adversarial Reconnaissance and Intelligent Attacks'. Together they form a unique fingerprint.

Cite this