Security for Vertical Industries

Mehrnoosh Monshizadeh, Vikramajeet Khatri, Iris Adam

Research output: Chapter in Book/Report/Conference proceedingChapterScientificpeer-review

Abstract

Abstract Having a changing ecosystem in 5G requires coordinating and adapting new security capabilities for Mobile Virtual Network Operators (MVNOs) that can cover several verticals, their new business models, and mode of operation. In such an ecosystem, cloud service providers should offer corresponding security services to MNVOs, regarding the deployment, layer, and configuration of security functions. Furthermore, 5G network slicing requires automated security and orchestration functionality, especially in complex network environments comprising multiple providers and multiple tenants. MNVOs must not only define security-related Service Level Agreements (SLAs) for new business models but also offer automated security management capabilities to tenants like verticals. To utilize such benefits and toward a secure and flexible 5G architecture, this article investigates MVNOs' security challenges and mitigation mechanisms for cloud layers as well cloud deployments. In addition, in this article the challenges for MVNOs to correlate security events in 5G scenarios are analyzed and a framework for automated security event management is proposed to offer security monitoring and correlation capabilities to mobile network operators, infrastructure service providers, and tenants like verticals.
Original languageEnglish
Title of host publicationWiley 5G Ref: The Essential 5G reference Online
PublisherJOHN WILEY & SONS
Pages1-14
Number of pages14
ISBN (Print)9781119471509
DOIs
Publication statusPublished - 2019
MoE publication typeA3 Part of a book or another research book

Keywords

  • cloud computing
  • IaaS
  • MVNO
  • NFV
  • OPNFV
  • PaaS
  • service level agreement
  • security framework
  • SaaS
  • SDN
  • TaaS

Fingerprint

Dive into the research topics of 'Security for Vertical Industries'. Together they form a unique fingerprint.

Cite this