# Software-as-a-Service Security Challenges and Best Practices: A Multivocal Literature Review
## 3 Literature Review  
Before moving forward with the MVLR, it is essential to include a review of the existing studies to understand the current state of research. This section provides a quick random of some current research on SaaS security issues and mitigation strategies. [PERSON] performed a systematic literature review (SLR) to gather SaaS security issues and solution. This SLR identified CC security requirements from scientific publications between January 2011 and March 2013. The identified requirements were categorized into a framework to assess their frequency. This research study also identified challenges in requirement assessment and proposed a solution for it [24]. [PERSON] et al. presented the security issues of three cloud service models, IaaS, PaaS, and SaaS. The main security issues in CC, as stated in this article, are storage, virtualization, and networks. This paper also makes a distinction between vulnerabilities and threats, emphasizing the importance of comprehending these problems and establishing a connection between threats and vulnerabilities to determine which vulnerabilities lead to the implementation of these threats to render the framework more resilient. To mitigate these risks, several existing solutions were also identified. According to the findings of this paper, traditional protection systems may not function well in cloud environments because they constitute a dynamic architecture made up of a variety of technologies [25]. A systematic mapping study (SMPS) was performed by [PERSON] and [PERSON] in [26] to find the security issues of mobile computing. Based on the interpretation and assessment of 83 primary studies, this mapping study breaks down the security sub-characteristics from the ISO/IEC 25010 and compares them to the details contained in this study. The findings of the study indicate that there are sufficient studies to address the issue of confidentiality and integrity. However, accountability and non-repudiation need more attention. A SMPS was performed by [PERSON] et al. to identify the security threats in CC. The aim of this study was to compile a list of the most recent publications in the literature that addressed security threats in CC. Centered on the Cloud Protection Alliance's \"Top Threats to CC guide\", this analysis presents metrics regarding existing research publications that deal with some of the seven security threats in CC. Furthermore, this research identified the most researched challenges, spreading the findings through 15 security domains, and identified the types of threats and solutions suggested. In view of these findings, the research focuses on publications that deal with meeting a regulatory requirement [27]. According to [PERSON] et al., users' use of CC technologies and applications is hampered by security and privacy concerns. The security and privacy issues raised by several CC system providers were investigated in this study. According to the results of the study, these considerations are insufficient. To meet the five goals (confidentiality, data integrity, availability, monitoring, and audit), more security techniques should be deployed in the cloud world, and privacy acts should be updated to adapt a new partnership between CSPs and CT in the cloud literature. According to the study, the CC literature needs to flourish until the protection and privacy problems are addressed [28]. [PERSON] and [PERSON] conduct a study of security and privacy problems as well as potential remedies. They discuss the benefits and disadvantages of the current methods to fully resolve the protection and privacy issues in the cloud world, as well as the advantages and drawbacks of existing methods to completely resolve the security and privacy issues [29]. According to [PERSON] and [PERSON], security is still a major concern in the CC paradigm. User confidential data loss, data leakage, and the disclosure of confidential data are a few of the major security concerns.