Proceedings of the 11th International Conference on Ubiquitous Information Management and Communication 2017
DOI: 10.1145/3022227.3022277
|View full text |Cite
|
Sign up to set email alerts
|

A study on authentication mechanism in SEaaS for SDN

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2017
2017
2023
2023

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(2 citation statements)
references
References 11 publications
0
2
0
Order By: Relevance
“…In [49], an approach named the application authentication system and deployed outside the controller is proposed, allowing authentication, log history of unauthorized operations, and the management of access permissions, resources, application certificates, authorization elements, authentication and encryption, among others. Similarly, in [50], a security-as-a-service (SEaaS) solution is defined. One of its features is the authorization mechanism between the controller and the applications, taking the Floodlight controller architecture as a reference.…”
Section: A Northbound Interface and Application Planementioning
confidence: 99%
See 1 more Smart Citation
“…In [49], an approach named the application authentication system and deployed outside the controller is proposed, allowing authentication, log history of unauthorized operations, and the management of access permissions, resources, application certificates, authorization elements, authentication and encryption, among others. Similarly, in [50], a security-as-a-service (SEaaS) solution is defined. One of its features is the authorization mechanism between the controller and the applications, taking the Floodlight controller architecture as a reference.…”
Section: A Northbound Interface and Application Planementioning
confidence: 99%
“…Behavior-based access control method + IDS [48] API abuse, DoS, Malicious apps Publish/Subscribe model [49] Lack of authentication mechanisms between the app and the Controller Independent mechanism [50] Lack of authentication mechanisms between the app and the Controller Floodlight-based mechanism [51] [52] Nonencrypted communication between app and controller Lack of management over reliability Lack of access control Use of REST-like functions [53] Lack of third-party app authentication NTRU encryption algorithm and NSS digital signatures [54] Malicious apps NTRU encryption algorithm S=spoofing, T=tampering, R=repudiation, I= information disclosure, D=denial of service, E=elevation of privilege…”
Section: B East/westbound Interface and Control Planementioning
confidence: 99%