2018
DOI: 10.1007/978-3-319-98989-1_24
|View full text |Cite
|
Sign up to set email alerts
|

Trust Anchors in Software Defined Networks

Abstract: Advances in software virtualization and network processing lead to increasing network softwarization. Software network elements running on commodity platforms replace or complement hardware components in cloud and mobile network infrastructure. However, such commodity platforms have a large attack surface and often lack granular control and tight integration of the underlying hardware and software stack. Often, software network elements are either themselves vulnerable to software attacks or can be compromised… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
5
3

Relationship

2
6

Authors

Journals

citations
Cited by 10 publications
(8 citation statements)
references
References 43 publications
(44 reference statements)
0
8
0
Order By: Relevance
“…However, in the unlikely case that a layer does not fit in available TEEs, the network design needs to be adjusted with smaller, but more layer(s), or a smaller training batch size. We also assume that there is a secure way to bootstrap trust between the server TEE and each of the client device TEE (e.g., using a slightly modified version of the SIGMA key exchange protocol [32,77], or attested TLS [30]), and that key management mechanisms exist to update and revoke keys when needed [55]. Finally, we assume that the centralized server will forward data to/from its TEE.…”
Section: Threat Model and Assumptionsmentioning
confidence: 99%
“…However, in the unlikely case that a layer does not fit in available TEEs, the network design needs to be adjusted with smaller, but more layer(s), or a smaller training batch size. We also assume that there is a secure way to bootstrap trust between the server TEE and each of the client device TEE (e.g., using a slightly modified version of the SIGMA key exchange protocol [32,77], or attested TLS [30]), and that key management mechanisms exist to update and revoke keys when needed [55]. Finally, we assume that the centralized server will forward data to/from its TEE.…”
Section: Threat Model and Assumptionsmentioning
confidence: 99%
“…However, in the unlikely case that a layer does not fit in available TEEs, the network design needs to be adjusted with smaller, but more layer(s), or a smaller training batch size. We also assume that there is a secure way to bootstrap trust between the server TEE and each of the client device TEE (e.g., using a slightly modified version of the SIGMA key exchange protocol [32,77], or attested TLS [30]), and that key management mechanisms exist to update and revoke keys when needed [55]. Finally, we assume that the centralized server will forward data to/from its TEE.…”
Section: Threat Model and Assumptionsmentioning
confidence: 99%
“…TLSonSGX guarantees that OvS authorities retain communication with SDN controllers and the cryptographic material they use [24]. This methodology can be paired with OFTinSGX to provide broader security assurances for OpenFlow switches.…”
Section: Related Workmentioning
confidence: 99%