<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Research and analysis of issues and challenges in ensuring cyber security in cloud computing ⋆</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Olha</forename><surname>Mykhaylova</surname></persName>
							<email>o.mykhailova@lpnu.ua</email>
							<affiliation key="aff0">
								<orgName type="institution">Lviv Polytechnic National University</orgName>
								<address>
									<addrLine>12 Stepana Bandery str</addrLine>
									<postCode>79013</postCode>
									<settlement>Lviv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Marta</forename><surname>Korol</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Lviv Polytechnic National University</orgName>
								<address>
									<addrLine>12 Stepana Bandery str</addrLine>
									<postCode>79013</postCode>
									<settlement>Lviv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Roman</forename><surname>Kyrychok</surname></persName>
							<email>r.kyrychok@kubg.edu.ua</email>
							<affiliation key="aff1">
								<orgName type="institution">Borys Grinchenko Kyiv Metropolitan University</orgName>
								<address>
									<addrLine>18/2 Bulvarno-Kudriavska str</addrLine>
									<postCode>04053</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Research and analysis of issues and challenges in ensuring cyber security in cloud computing ⋆</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">684F2F8EA3DD73B5309F4E73D68A4B5D</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:50+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Cloud services provide information tools in a virtual environment with the opportunity to expand the software and hardware resources of the user's computer device. Information is permanently stored on servers on the Internet and temporarily cached on client devices, such as personal computers, game consoles, laptops, smartphones, etc. To gain constant access to remote Internet resources, users use cloud services. They are a key element of rapidly evolving modern technologies, and cloud services are a strategic issue for many companies. Although the innovative capabilities of cloud services attract users, they can also create new threats to their information security. This is why research into cloud computing is important to understand its potential and effectiveness. This study will look at the security aspect of cloud services and compare several different platforms because the lack of sufficient protection can lead to the theft of personal data and other confidential information. The study will also look at the most common threats faced by cloud services, such as DDoS attacks, data leaks, data abuse, etc. In particular, the security measures provided by leading cloud platforms such as AWS, GCP, and Azure will be analyzed to determine their effectiveness and reliability. Our analysis will be useful for companies considering moving to the cloud and everyday users trying to keep their data safe online. The results of the study will provide a clear understanding of the benefits and limitations of using various cloud platforms from a security perspective. Keywords cloud computing security, cybersecurity in cloud services, cloud platform comparison, data protection, threats to cloud services, DDoS attack, data leakage prevention, security measures in AWS, GCP, Azure, cloud migration considerations 1  Amazon Web Services (AWS) [2] (established in March 2006) is a division of Amazon.com that offers a cloud computing platform for rent to individuals, businesses, and governments via subscription.  Microsoft Azure (created February 1, 2010) [3] is a Microsoft Corporation infrastructure that provides a cloud platform for application developers to facilitate the process of creating programs.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>In today's digital world, large amounts of data are stored and processed in cloud services. Cloud services are known to provide many benefits, including increased availability, flexibility, and cost-effectiveness. However, with these benefits come several challenges, such as increased security threats, potential vulnerabilities, and potential risks to data privacy <ref type="bibr" target="#b0">[1]</ref>.</p><p>In the modern world, the cloud computing market is experiencing increased competition among cloud service providers. In recent years, there has been a constant increase in the number of companies offering cloud services. The most popular of them are: Microsoft Azure allows you to deploy applications not only using Microsoft .NET and Visual Studio but also using various tools.  Google Cloud Platform (founded <ref type="bibr">April 7, 2008)</ref>  <ref type="bibr" target="#b3">[4]</ref>a set of cloud services developed by Google, running on the same infrastructure that Google uses for its end-user products. The service provides a range of modular cloud services such as computing, data storage, data analytics, and machine learning. With increasing popularity, developers are forced to constantly improve their platforms, including improving automatic threat detection and response mechanisms, expanding data encryption capabilities, improving user identification and authentication, and improving monitoring and vulnerability analysis tools <ref type="bibr" target="#b5">[6]</ref>. Collaborate with information security experts, conduct independent security audits, and improve incident response processes.</p><p>The topic of cloud computing has attracted the attention of various researchers. Many scholars and experts are actively engaged in research and analysis of the problems and challenges associated with cybersecurity in cloud computing. Using an example, work <ref type="bibr" target="#b6">[7]</ref> examines security in the AWS computing service; it demonstrates the importance and relevance of research in the field of cybersecurity, in particular in the context of the use of AWS cloud services. Also, in <ref type="bibr" target="#b7">[8]</ref>, the authors compared AWS and Azure Cloud Platforms services for 2021, where they recognize the differences between AWS and Azure in database management systems, architectures, resource management patterns, and complexity, which can affect scalability, performance, and pricing.</p><p>The method of this research is to analyze and identify the key issues and challenges that are used in cybersecurity inactivity processes in external computing to further align Amazon Web Services, Microsoft Azure, and Google Cloud Platform. To do this you will also need to use:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Updated downloads and resources without additional services  Identify non-response criteria in general descriptions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Test AWS, AZURE, and GCP in the context of selected cybersecurity blocking criteria.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Evaluate each platform on 10 balloon systems  Focus on the platform that is effective and relevant.</p><p>Thus, reviewing and analyzing the issues and challenges associated with cybersecurity in general terms remains extremely important for developing effective data preservation strategies.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Analysis of threats and security risks of cloud services</head><p>Small and medium-sized enterprises, like global companies, are increasingly relying on cloud computing security services to support day-to-day business functions and software development, and even to provide the technology infrastructure needed to operate. In this regard, cloud services often face many cyber-attacks. A cloud attack <ref type="bibr" target="#b8">[9]</ref> is a cyber-attack that targets cloud service platforms, such as computing services, storage services, or hosted applications in a platform as a service (PaaS) or software as a service (SaaS) model.</p><p>According to <ref type="bibr" target="#b9">[10]</ref>, in recent years the number of attacks on cloud services has increased rapidly. Cloud cyberattacks accounted for 20% of all cyberattacks in 2020, making cloud computing platforms the third most targeted cyber environment. Therefore, we will look at the different types of attacks and their characteristics, as well as the possible consequences of these attacks for users and organizations using cloud technologies. Below is an overview of types of cloud computing attacks to help you better understand these threats and take steps to prevent them.</p><p>These threats pose serious risks to cloud computing security. Denial-of-service attacks can disrupt access to cloud services, misconfiguration of security can open the door to attackers, and cloud malware attacks threaten data privacy and integrity. This may allow an attacker to use the associated resources for their purposes or to steal or manipulate data stored in the cloud. All these threats require important monitoring and the provision of appropriate security measures to protect cloud services and user data.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1.">Denial of service in cloud computing</head><p>DoS attacks attempt to make a service unavailable to its users. The attack consumes a large amount of system resources such as computing power, memory, and bandwidth. This consumption will make the service unavailable to users or unbearably slow. DoS attacks and their variant distributed denial of service (DDoS) attract a lot of media attention mainly because of their magnitude. In 1988, reports show only six DDoS attacks. DDoS attacks targeted major websites such as CNN, Yahoo, and Amazon in 2000 with an attack rate of approximately 1 GB/s. DDoS attacks achieved a speed of 70 GB/s in 2007. In 2013, there was a large-scale attack on a service. Over the past decade, DDoS attacks on cloud services have become increasingly sophisticated and dangerous, affecting various industries and operations related to cloud resources <ref type="bibr" target="#b10">[11]</ref>.</p><p>The attack on Spamhaus in 2013 stands out for its scale, using a traffic volume of 300 Gbps, which led to disruptions not only to Spamhaus itself but also to global Internet traffic.</p><p>A politically motivated attack on GitHub in 2015 showed the use of compromised devices to flood the website with traffic and disrupt its operations.</p><p>A 2016 Dyn attack that used compromised IoT devices to create a botnet overwhelmed Dyn's infrastructure, causing major sites like Netflix and PayPal to become unavailable.</p><p>Attacks on Google and AWS in 2020, using amplification techniques, resulted in extremely high traffic speeds (2.5 Tbsp. for Google and 2.3 Tbsp. for AWS), which posed a major threat to their infrastructure <ref type="bibr" target="#b11">[12]</ref>.</p><p>In 2022, Microsoft discovered protection against extremely high-throughput attacks, registering the largest attack at the time at 3.47 Tbit/s. Also noted is the shift to multi-vector attack strategies, where attackers combine different methods to maximize disruption.</p><p>Look closer at DoS attacks, which occur when security is compromised. This prevents legitimate clients from accessing its target cloud systems, devices, or other cloud resources.</p><p>A network of zombies controlled remotely by wellstructured and widely distributed nodes perform DDoS attacks. The attacker initiates the attack with the help of zombies called secondary victims. DDoS attacks are divided into 3 categories <ref type="bibr" target="#b11">[12]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>1.</head><p>Volume/Bandwidth-Based Attacks: This attack tries to overwhelm the user with a lot of garbage data, using network bandwidth and resources in the process.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.</head><p>Protocol attacks: The attack tries to overload the target's resources using the disadvantage associated with several network protocols.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.</head><p>Application Layer Attacks: These attacks target specific online applications and send HTTP requests that exceed program capacity.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.">Account Hijacking</head><p>In this type of security breach, hackers attempt to hijack an account by stealing security credentials and then eavesdropping on user actions and transactions.</p><p>Hackers can also manipulate data, insert false information, and redirect customers to illegitimate sites. This type of vulnerability is particularly scary because hackers know how to use the reputation and trust of users to manipulate customers.</p><p>In 2010, Amazon faced an attack <ref type="bibr" target="#b11">[12]</ref><ref type="bibr" target="#b12">[13]</ref><ref type="bibr" target="#b13">[14]</ref> that allowed hackers to steal the session IDs that give users access to their accounts after entering passwords. This left the customer's credentials open to hackers. The bug was removed 12 hours after it was discovered, but many Amazon users were unwittingly exposed to the attack during that time <ref type="bibr" target="#b14">[15]</ref>.</p><p>Account hijacking is done using the stolen credentials of the real user. By using credentials a hacker can access sensitive data and manipulate the data to suit his likeness. The traffic hijacking service involves hacker eavesdropping, data manipulation, data access, and return of falsified information. There are three states in which a security breach can occur.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>1.</head><p>Transfer of confidential data to a cloud server.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.</head><p>Transfer of confidential data from the cloud server to the client's computer.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.</head><p>Storage of confidential client data in the cloud servers that are remote and not owned by the client <ref type="bibr" target="#b15">[16]</ref>.</p><p>In account hijacking, a hacker uses a compromised email account to impersonate the account owner. Typically, account hijacking is done through phishing <ref type="bibr" target="#b16">[17]</ref>, sending fake emails to the user, picking a password, or several other hacking tactics. In many cases, a user's email account is linked to various online services, such as social networks and financial accounts.</p><p>A hacker can use an account to obtain a person's account personal information, conduct financial transactions, create new accounts, and request the account owner's contacts for money or assistance in illegitimate activities. Cloud account hijacking is a common tactic for identity theft schemes. The attacker uses the stolen account information for malicious or unauthorized activity. When a cloud account is hijacked, the attacker usually uses a compromised email account or other credentials to impersonate the account owner.</p><p>Hijacking an enterprise-level cloud account can be particularly devastating, depending on what the attackers do with the information. A company's integrity and reputation can be destroyed, and confidential data can be destroyed by leakage or falsification, causing significant costs for businesses. There are also possible legal consequences for companies and organizations with strict regulation industries, such as healthcare, if sensitive customer or patient data is exposed when a cloud account is compromised <ref type="bibr" target="#b13">[14]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3.">Malware injection in cloud computing</head><p>Malware injection in cloud computing is when an attacker tries to step in and inject malicious code or a fake service that masquerades as an existing service running in the cloud. This type of attack is also known as a download or metadata spoofing attack. Attacks of this type allow attackers to steal information from the Internet by causing automatic downloads of malicious software without prior consent from users. This undermines the reliability of the service and may lead to unwanted behavior. This may be the first serious attack attempt to introduce a malicious service or virtual machine in a cloud environment <ref type="bibr" target="#b10">[11]</ref>.</p><p>The goal of a cloud-based malware attack is to harm anything of interest, which may include data modification, functionality/behavior modification, or blocking. In such an attack, an attacker creates his implementation of a malicious service or module (for example, SaaS or PaaS) or a virtual machine instance (for example, IaaS) and adds it to a cloud system. The attacker then pretends to the cloud system that it is a new service or implementation instance among the valid instances for the service being attacked. If this action is successful, the cloud automatically redirects the valid user's requests to the implementation of the malicious service and the malicious code is executed. The basic cloud ware Injection attack scenario is that an attacker transfers a manipulated/incorrect copy of a service instance to the victim so that the malicious instance can access the victim's service requests. To achieve this goal, the attacker must gain control over the victim's data in the cloud <ref type="bibr" target="#b10">[11]</ref>.</p><p>An SQL injection attack is aimed at a database that is outside the client's input fields in the application. A malicious SQL command is inserted as part of an information field, which, when changed to a query, turns it into a meaningful, but unsafe, query.</p><p>A Cross-Site Scripting (XSS) attack is where an attacker gains access to sensitive information on the server by injecting code into the context of the document data used on the client-side HTML. This method allows the attacker to execute his script in the victim's web browser. XSS attacks are classified as stored and displayed according to OWASP. According to WHID (2011), about 12.6% of all attacks on the Internet are related to XSS. There is virtually no limit to the various XSS-based attacks.</p><p>A command injection attack is a form of command injection in which commands entered by vulnerable programs are executed. These entered commands can be executed at the root level or in a separate runtime environment, depending on the conditions. The commands entered, such as ls, ps, cat, etc., are executed in the context of the running environment with similar privileges as the application being used. One of the most important consequences of this attack is increased latency for alternate clients using applications running on the same virtual machine as the vulnerable application <ref type="bibr" target="#b10">[11]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.4.">Insecure APIs</head><p>The API plays a crucial role in the communication of the cloud computing infrastructure because it allows different users and cloud components to interact and share data. Thus, an attacker can exploit weaknesses in cloud management software such as Open Stack and its API implementation for malicious intent <ref type="bibr" target="#b17">[18,</ref><ref type="bibr" target="#b18">19]</ref>.</p><p>The first type of attack is an attack on API authentication services. This type of attack can be initiated by exploiting weaknesses in the cloud API that provides authentication services in the cloud infrastructure. Cloud management software such as OpenStack or CloudStack has provided an API to interact with authentication services. The relationship between hosts and authentication is sensitive because credentials such as passwords and session tokens are usually exchanged during the session.</p><p>Most APIs in cloud management software are based on REST or SOAP, which are web standards <ref type="bibr" target="#b19">[20]</ref>. Thus, it is vulnerable to Internet-based attacks such as eavesdropping, session hijacking, malicious code execution, XSS, and denial-of-service attacks <ref type="bibr" target="#b19">[20]</ref>. One important OpenStack service is the API that handles authentication, a module known as Keystone. Work <ref type="bibr" target="#b20">[21]</ref> revealed that the Keystone API is also susceptible to eavesdropping attacks because, during the authentication procedure, credential data is transmitted to users in clear text. Additionally, Keystone's token exchange-based authentication mechanism is also flawed. This is because hackers will be able to gain user privileges and access the services of other cloud components if they can get the password contained in the authentication token <ref type="bibr" target="#b17">[18,</ref><ref type="bibr" target="#b18">19]</ref>.</p><p>The second type of attack is the API Exhaustion Attack. This is a type of DOS attack on cloud API services. A denial of service (DOS) occurs when an attacker disrupts services by intentionally sending a large volume of traffic to overload the system. This prevents the system from processing the request of legitimate users and thus denying them access to the service. In the context of cloud computing, a DOS attack can target applications running in the cloud or the infrastructure of the cloud platform <ref type="bibr" target="#b21">[22,</ref><ref type="bibr" target="#b22">23]</ref>.</p><p>When a DOS attack targets a cloud platform API, it can cause an API exhaustion attack. Most cloud management software offers a web API for interoperability and simplicity. For example, CloudStack and OpenStack APIs are built on REST, and during a communication session, data is formatted as JSON <ref type="bibr" target="#b23">[24,</ref><ref type="bibr" target="#b24">25]</ref>. Work <ref type="bibr" target="#b20">[21]</ref> found that the OpenStack Keystone API, which uses web protocols to provide identity and authentication services, is vulnerable to information disclosure, DOS, and replay attacks.</p><p>An API exhaustion attack is when attackers maliciously exploit a cloud platform's API by sending many malicious API requests to overload the system. Cloud components will not be able to respond to legitimate API requests from other components and users while it is full. This is because web protocols (HTTP) use TCP as the transport protocol, thus, when the server receives API requests using HTTP; it will allocate additional resources for a new TCP session. The physical hosts of the cloud management system components will eventually wear out if this continues for a long period. Therefore, it cannot handle a legitimate API request, resulting in a DOS attack and violation of its availability. Cloud management software is vulnerable to this type of attack because it uses web technology in API services and many cloud administrators have drawn attention to this problem bug tracking portal and vulnerability database <ref type="bibr" target="#b14">[15,</ref><ref type="bibr" target="#b19">20]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.5.">Security misconfiguration</head><p>The latest report highlights that 75% of medium and large companies have switched to cloud computing. However, misconfiguration errors remain a major security concern in cloud computing. These errors are often the result of human errors that can occur when configuring cloud instances such as compute resources and storage, which can increase the system's vulnerability to data security breaches <ref type="bibr" target="#b25">[26]</ref>.</p><p>For example, improper configuration of an Amazon S3 instance can lead to improper access to protected documents via a web browser. This problem extends to insecure data stores on the Internet without any form of authentication, allowing all users of the platform to access the data. These errors impact the ability of cloud administrators to adequately control and secure complex hybrid and multi-cloud deployments <ref type="bibr" target="#b17">[18]</ref>.</p><p>Various factors can lead to misconfiguration errors. For example, a lack of understanding of cloud security policies, congestion, and misuse of APIs can complicate this situation. Ensuring that software components have proper default security settings is also an important reason, which facilitates the attempts of attackers to gain access to data. All this shows that misconfiguration errors can have serious consequences for data security in cloud environments <ref type="bibr" target="#b24">[25]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Cybersecurity assessment criteria in cloud computing</head><p>Given that cyberattacks are becoming more sophisticated and cybersecurity threats are constantly growing, the importance of developing a comprehensive security strategy for cloud services becomes imperative. For effective protection against cyberattacks in cloud services, it is recommended to use a variety of measures and protection methods that allow to guarantee a higher level of security for users.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Security misconfiguration</head><p>While AWS, Azure, and Google Cloud are the leading cloud service providers, they each have specific mechanisms in place to ensure cybersecurity. One of the key mechanisms is access demarcation and security management in the cloud computing environment.</p><p>Identity and Access Management (IAM) allows you to create and manage permissions for resources. IAM combines access control to services into a single system and is a consistent set of operations. IAM policies contain a role, user, or user group. Each role contains a list of permissions.</p><p>Identity and access management is based on such principles as:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Multi-factor authentication adds an extra layer of security. This means that a user will need to verify their identity using two or more authentication methods, such as a and an SMS code, to access your account.  Centralized management, with which users can create and manage access policies for users, groups, and roles from one place, which simplifies the administration process.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Role-based Access Control (RBAC) allows you to define access rights for users based on their responsibilities and needs. This allows you to finetune access to resources based on the specific needs of your organization.  IAM provides auditing and reporting capabilities that allow you to log access events, analyze resource usage, and track changes to access policies to meet regulatory requirements. This allows you to maintain control over your data and ensure compliance with security standards.</p><p>The main conclusions of our research include: Algorithm Development: A new algorithm based on the Taylor series has been proposed that provides the generation of pseudorandom sequences. This approach is based on the numerical properties of the natural logarithm of number 2 (ln2), which is mathematically stable and accurate. Using ln2 to initialize the generator allows achieving a high degree of randomness in the created sequences.</p><p>Algorithm Analysis: A detailed analysis of the developed algorithm was conducted, which includes checking its statistical characteristics and testing for compliance with NIST requirements. Testing showed that the algorithm could not initially provide a uniform distribution of pseudorandom numbers, leading to its improvement.</p><p>Algorithm Improvement: The basic algorithm has been improved, which provides better performance and improved statistical characteristics of the generated sequences. Optimization of the algorithm allows for significantly reducing the computational complexity, making it effective for use in real-world applications where computation time is a critical parameter.</p><p>The results of this research are an important step towards improving the reliability and quality of pseudorandom number generators. The proposed approach may find wide application in various fields such as cryptography, numerical modeling, simulations, and other numerical methods that require high-quality randomness and computational efficiency.</p><p>Furthermore, the improved algorithm proposed in this paper can be used to create new generators or to enhance existing solutions, for example through optimization of calculations or application of new generation methods. Future research may focus on expanding the algorithm to other mathematical constants, which may further improve the quality of pseudorandom numbers. It is also possible to create an algorithm based on formula (5) using intervals (for example, as in Hamming matrices) or using other Taylor series for generating new pseudorandom sequences. Using such methods opens new horizons for the development of number theory and computational mathematics, providing powerful tools for solving a wide range of tasks in various fields of science and technology, especially for information protection.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Protection against DDoS attacks and other network threats</head><p>One of the most common and most threatening forms is a DDoS (Distributed Denial of Service) attack, which can cause significant disruption to work networks, lead to the loss of availability of services and important data, and even cause significant financial losses. Protection against a DDoS attack is based on the following points <ref type="bibr" target="#b25">[26]</ref><ref type="bibr" target="#b26">[27]</ref><ref type="bibr" target="#b27">[28]</ref>:</p><p> Scalability and elasticity of the infrastructure</p><formula xml:id="formula_0"> Distribution  Network filters  Traffic optimization </formula><p>Monitoring and analytics services.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3.">Measures to prevent unauthorized data changes</head><p>In the world of cloud services, where data security is important, preventing unauthorized changes to information becomes an important task. Ensuring data privacy requires the implementation of effective security measures. In this context, it is important to note the measures to prevent data changes without permission, which becomes the main component of information reliability and security.</p><p>In cloud services, several functions and mechanisms help avoid data changes without permission: </p><formula xml:id="formula_1"></formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.4.">The shared responsibility model</head><p>The shared responsibility model is a concept that defines the level of responsibility for security and data protection between a cloud service and its customers. This model chooses who is responsible for various aspects of infrastructure and data in a cloud environment. Also, choose 1 of 3 types of platform services: infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS).</p><p>SaaS <ref type="bibr" target="#b28">[29]</ref> is a model that puts the most responsibility on the cloud service provider and the least on the user. In a SaaS environment, you are responsible for the data you add the systems, the devices you allow to connect to the systems, and the users who have access. Almost everything else belongs to the cloud provider. The cloud provider is responsible for the physical security of the data centers, power, network connectivity, and application development and updates <ref type="bibr" target="#b29">[30]</ref>.</p><p>PaaS <ref type="bibr" target="#b30">[31]</ref> divides the responsibility between you and the cloud provider. The cloud provider is responsible for maintaining the physical infrastructure and its access to the Internet, just like in IaaS. In the PaaS model, the cloud provider also supports operating systems, databases, and development tools. Think of PaaS as using a domain-joined computer: IT staff maintain the device with regular updates, patches, and upgrades.</p><p>IaaS places the greatest responsibility on the user. The cloud provider is responsible for maintaining the physical infrastructure and its access to the Internet. You are responsible for installation and configuration, patches and updates, and security.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.5.">The shared responsibility model</head><p>The availability and effectiveness of security policies is one of the most critical aspects. Well-designed security policies can protect against a wide range of threats, from cyber attacks to unauthorized access and data loss. They define the rules, procedures, and controls that govern access to information and resources, and establish security standards that must be followed by all users and system administrators. In this context, it is important to investigate both the presence and effectiveness of security policies in cloud services to ensure a high level of data and infrastructure protection.</p><p>Criteria for determining its effectiveness and adaptability to security requirements include:</p><p>The assessment of the security policy in cloud services includes several criteria that allow for determining its effectiveness and adaptability to security requirements. Some of the key evaluation criteria include:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Certainty and consistency.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Compliance The security policy must meet the requirements of legislation, standards, and regulatory requirements that apply to a specific industry or region.  Monitoring and analysis.  Sustainability and renewal.  Support and involvement of employees.</p><p>Evaluating a security policy against these criteria helps ensure that it meets the needs and requirements of security in cloud services.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Conducting testing of each platform according to defined criteria</head><p>Taking into account the criteria of the Criteria for evaluating cyber security in cloud computing, which were compiled in the previous points, we will compare 3 cloud services: AZURE, AWS, and GCP. Evaluating access separation for each of the platforms (Azure, AWS, GCP) on a scale from 1 to 10, where 10 is the best, you can make the following rating:</p><p>1. Azure (Microsoft Azure): 8. The service has a powerful and easy-to-use access control mechanism through Azure Active Directory (AAD). It provides the ability to manage many built-in roles, but some functionality can be difficult to configure with other platforms. 2.</p><p>AWS (Amazon Web Services): 9. IAM in AWS is a powerful and flexible tool for delimiting access. It provides extensive configuration options for roles, policies, and API access. Many built-in roles and categories refused to fine-tune access to resources.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.</head><p>GCP (Google Cloud Platform): 7. IAM in GCP is also a powerful access management tool, but it can be less flexible in some aspects together with AWS and Azure. However, it provides advanced functionality for managing projects and resources.</p><p>Then we compare platforms with points of protection against DDoS attacks and other network threats: The evaluation schedule can be justified as follows:</p><p>1. AWS (Amazon Web Services): Score 9. AWS has several powerful tools such as IAM for access management, AWS KMS for data encryption, CloudTrail for auditing and monitoring, and Amazon S3 for backup. These tools provide extensive opportunities for data protection and a high level of security.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.</head><p>Azure (Microsoft Azure): Score 8. Azure also has a similar set of data protection tools, such as Azure Active Directory, Azure Key Vault, Azure Audit Logs, and Azure Backup. However, some users may find Azure a bit more difficult to configure and use, which may result in a slight loss of points compared to AWS.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.</head><p>GCP (Google Cloud Platform): Score 7. GCP also has some effective data protection tools but may be less flexible in some aspects compared to AWS and Azure. While tools like Cloud IAM, Key Management Service, and Cloud Audit Logs offer a high level of security, GCP's interface and documentation may be less intuitive for some users, which lowers the overall score. Next, the aspect of the joint responsibility model will be considered. The evaluation schedule can be justified as follows:</p><p>1.</p><p>Azure (Microsoft Azure): 9. Azure provides a welldefined shared responsibility model that chooses which parts of the infrastructure are the responsibility of the cloud provider and which are the responsibility of the user. This will avoid confusion and understand the responsibilities of all parties for data and infrastructure security.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.</head><p>GCP (Google Cloud Platform) 8. GCP also provides a shared responsibility reporting model, but some users feel that some aspects may be less obvious or difficult to understand with Azure or AWS.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.</head><p>AWS (Amazon Web Services): 9. AWS has a welldefined and reported shared responsibility model that allows users to clearly understand their responsibility for the security and protection of data in the cloud environment. GCP (Google Cloud Platform) 8. GCP also has an extensive set of tools for configuring security policies, including Cloud Security Command Center and Google Cloud IAM. However, some users may find GCP's user interface and documentation to be less intuitive compared to Azure or AWS, which can make it difficult to set up and debug security policies.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.</head><p>AWS (Amazon Web Services): 9. AWS offers a wide range of tools for creating and managing security policies, including AWS Identity and Access Management (IAM), AWS Config, AWS CloudTrail, and many others. These services allow administrators to effectively control and monitor the security of resources in the AWS cloud environment.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 6</head><p>Comparison of platforms in the context of shared responsibility models</p><p>From the ratings provided, it can be noted that Amazon Web Services (AWS) received the highest overall rating, which is 45 points. This is a subjective opinion that was built on the fact that AWS stands out in terms of technical aspects with its broad set of services, deep level of customization, and high geographical spread. The biggest advantage of AWS is a powerful and selective toolkit for delimiting access, as well as a wide range of tools to protect against DDoS attacks and other network threats. Considering this, it can be concluded that AWS is the best choice for organizations that want optimal security in cloud computing. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusions</head><p>Based the research and analysis of the issues and challenges associated with ensuring cyber security in cloud computing, several key conclusions can be drawn. First of all, it is determined that protection against cyber threats in cloud computing requires a comprehensive and in-depth approach, the latter areas provide a wide range of services and capabilities that require constant monitoring and management. Key challenges in this context include ensuring data security and protection, detecting and responding to cyber threats, and managing access and user identity.</p><p>Another aspect of security is the continuous updating and improvement of security measures since cyber threats are constantly evolving and remain increasingly complex. This means that cloud computing providers such as AWS, Azure, and GCP must constantly improve their tools and services to ensure the highest level of security for their customers.</p><p>In addition, it is found that the choice of cloud computing platform can affect the level of cyber security, the second provider has its unique features and capabilities. The decisive factor when choosing a platform should be its ability to provide reliable and effective protection against cyber threats to the needs and requirements of a specific organization.</p><p>Therefore, based on these findings, it can be argued that ensuring cyber security in cloud computing is a challenging task, but at the same time, there are ample opportunities for innovation and development. With an understanding and timely response to the problems and challenges in this area, organizations can maximize the security of their data.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Popularity of cloud service providers [5].</figDesc><graphic coords="1,304.56,558.00,218.40,105.60" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 1</head><label>1</label><figDesc>Platform comparison in the context of access demarcation</figDesc><table><row><cell cols="2">Criterion/Platform AWS</cell><cell>AZURE</cell><cell>GCP</cell></row><row><cell>Multi-factor</cell><cell>Yes, supported through IAM</cell><cell>Yes, including Azure AD and</cell><cell>Yes, available to users and services</cell></row><row><cell>Authentication</cell><cell>and other services</cell><cell>other mechanisms</cell><cell>through the Identity Platform</cell></row><row><cell>Centralized</cell><cell>Yes, through Identity and</cell><cell>Yes, via Azure Active Directory</cell><cell>Yes, with Cloud Identity and Access</cell></row><row><cell>Management</cell><cell>Access Management (IAM)</cell><cell>(AAD) and other tools</cell><cell>Management (IAM)</cell></row><row><cell>Role-based Access</cell><cell>Yes, roles and access rights can</cell><cell>Yes, through Azure RBAC and</cell><cell>Yes, available for configuring access</cell></row><row><cell>Control</cell><cell>be defined through IAM</cell><cell>other mechanisms</cell><cell>rights for users and services</cell></row><row><cell>Audit and</cell><cell>Yes, provides capabilities for</cell><cell>Yes, provides audit and reporting</cell><cell>Yes, provides capabilities for logging</cell></row><row><cell>Reporting</cell><cell>logging events and resource</cell><cell>capabilities through Azure</cell><cell>events and analyzing resource access</cell></row><row><cell></cell><cell>usage analysis</cell><cell>Monitor and other tools</cell><cell></cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 2</head><label>2</label><figDesc>Comparison platforms in the context of protection against DDoS attacks and other network threats</figDesc><table><row><cell></cell><cell>Criterion/Platform</cell><cell>AWS</cell><cell></cell><cell>Azure</cell><cell>GCP</cell></row><row><cell cols="2">Free Basic Level of DDoS Protection</cell><cell cols="2">Yes, available to all users</cell><cell>Yes, through Azure DDoS</cell><cell>No</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>Protection</cell></row><row><cell cols="2">Enhanced Protection for an Additional Fee</cell><cell>Yes, available through</cell><cell></cell><cell>No, enhanced protection is</cell><cell>Yes, available through</cell></row><row><cell></cell><cell></cell><cell cols="2">AWS Shield Advanced</cell><cell>not available for an</cell><cell>Google Cloud Armor and</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>additional fee</cell><cell>other mechanisms</cell></row><row><cell></cell><cell>Web Application Firewall (WAF)</cell><cell>Yes, AWS WAF</cell><cell></cell><cell>No, but Azure Firewall and</cell><cell>Yes, Google Cloud Armor</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>Azure Security Center are</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>available</cell></row><row><cell></cell><cell>Event Logs and Security Analysis</cell><cell cols="2">Yes, available through</cell><cell>Yes, available through the</cell><cell>Yes, available through the</cell></row><row><cell></cell><cell></cell><cell cols="2">AWS CloudTrail and AWS</cell><cell>Azure Security Center</cell><cell>Google Cloud Security</cell></row><row><cell></cell><cell></cell><cell>Config</cell><cell></cell><cell>Command Center</cell></row><row><cell cols="3">Having familiarized ourselves with the platforms in terms</cell><cell></cell><cell>Security Center, and many others. Azure has a</cell></row><row><cell cols="3">of protection against DDoS attacks and other network</cell><cell></cell><cell>well-developed threat monitoring and detection</cell></row><row><cell cols="3">threats, we can give them the following ratings:</cell><cell></cell><cell>system that allows you to quickly respond to any</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>attacks.</cell></row><row><cell>1.</cell><cell cols="2">AWS (Amazon Web Services): 9. AWS provides a</cell><cell>3.</cell><cell>GCP (Google Cloud Platform): 7. Google Cloud</cell></row><row><cell></cell><cell cols="2">high level of protection against DDoS attacks and</cell><cell></cell><cell>Platform provides a significant level of protection</cell></row><row><cell></cell><cell cols="2">other network threats, including services such as</cell><cell></cell><cell>against DDoS attacks and other network threats</cell></row><row><cell></cell><cell cols="2">AWS Shield, AWS WAF, AWS Firewall Manager,</cell><cell></cell><cell>with services such as Google Cloud Armor, Google</cell></row><row><cell></cell><cell cols="2">Amazon GuardDuty, and others. These services</cell><cell></cell><cell>Cloud DDoS Protection, VPC Service Controls, and</cell></row><row><cell></cell><cell cols="2">provide different levels of protection, both basic</cell><cell></cell><cell>others. However, according to some experts,</cell></row><row><cell></cell><cell cols="2">and advanced, allowing you to adapt protection</cell><cell></cell><cell>GCP's security tools may be less integrated and</cell></row><row><cell></cell><cell cols="2">measures to the needs of users. Multi-factor</cell><cell></cell><cell>less easy to use with AWS and Azure, which may</cell></row><row><cell></cell><cell cols="2">authentication, protection of network resources,</cell><cell></cell><cell>pose some risk to users with less expertise in</cell></row><row><cell></cell><cell cols="2">and tracking of unusual activity are also</cell><cell></cell><cell>network security.</cell></row><row><cell></cell><cell cols="2">components of AWS security systems.</cell><cell></cell></row><row><cell>2.</cell><cell cols="2">Azure (Microsoft Azure): 8. Microsoft Azure also</cell><cell cols="2">Below is a table that compares measures to prevent</cell></row><row><cell></cell><cell cols="2">offers a wide range of tools to protect against</cell><cell cols="2">unauthorized data changes across AWS, Azure, and GCP</cell></row><row><cell></cell><cell cols="2">DDoS attacks and other network threats, including</cell><cell cols="2">based on criteria such as auditing and monitoring, data</cell></row><row><cell></cell><cell cols="2">services such as Azure DDoS Protection, Azure</cell><cell cols="2">encryption, change tracking, and backup:</cell></row><row><cell></cell><cell cols="2">Firewall, Azure Application Gateway, Azure</cell><cell></cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head>Table 3</head><label>3</label><figDesc>Comparison of platforms in the context of measures to prevent unauthorized data changes</figDesc><table><row><cell>Criterion/Platform</cell><cell>AWS</cell><cell>Azure</cell><cell>GCP</cell></row><row><cell>Tools and services</cell><cell>IAM, AWS Shield, AWS WAF,</cell><cell>Azure Active Directory</cell><cell>GC IAM, GC Armor, Google</cell></row><row><cell></cell><cell>and other</cell><cell>(AAD), Azure DDoS</cell><cell>Cloud Security Command</cell></row><row><cell></cell><cell></cell><cell>Protection, and other</cell><cell>Center, and other</cell></row><row><cell>Service Models</cell><cell>IaaS, PaaS, SaaS</cell><cell>IaaS, PaaS, SaaS</cell><cell>IaaS, PaaS, SaaS</cell></row><row><cell cols="2">Security Policies and Standards Uses own security policies and</cell><cell>Uses own security policies</cell><cell>Uses own security policies and</cell></row><row><cell></cell><cell>standards, such as PCI DSS,</cell><cell>and standards, such as PCI</cell><cell>standards, such as PCI DSS,</cell></row><row><cell></cell><cell>HIPAA, SOC, ISO</cell><cell>DSS, HIPAA, SOC, ISO</cell><cell>HIPAA, SOC, ISO, and others</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_4"><head>Table</head><label></label><figDesc>Comparison of platforms in the context of shared responsibility models</figDesc><table><row><cell cols="2">Criterion/Platform AWS</cell><cell>Azure</cell><cell>GCP</cell></row><row><cell>Audit and</cell><cell>AWS CloudTrail, Amazon</cell><cell>Azure Monitor, Azure</cell><cell>Cloud Audit Logs,</cell></row><row><cell>Monitoring</cell><cell>CloudWatch</cell><cell>Security Center</cell><cell>Cloud Monitoring</cell></row><row><cell>Data Encryption</cell><cell>AWS Key Management Service (KMS), Amazon S3 Encryption</cell><cell>Azure Key Vault, Data Encryption at Rest</cell><cell>Key Management Service, Data Encryption at Rest</cell></row><row><cell>Change Tracking</cell><cell>AWS CloudTrail</cell><cell>Azure Audit Logs</cell><cell>Cloud Audit Logs</cell></row><row><cell>Backup</cell><cell>Amazon S3, Amazon Glacier</cell><cell>Azure Backup</cell><cell>Google Cloud Storage, Cloud Storage Nearline</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_5"><head>Table 5</head><label>5</label><figDesc>Comparison of platforms in the context of shared responsibility models</figDesc><table><row><cell cols="2">Criterion/Platform</cell><cell>AWS</cell><cell>Azure</cell><cell>GCP</cell></row><row><cell cols="2">Availability of Certifications</cell><cell>SOC 1, SOC 2, ISO 27001, HIPAA, PCI DSS, FedRAMP</cell><cell>SOC 1, SOC 2, ISO 27001, HIPAA, PCI DSS, FedRAMP</cell><cell>SOC 1, SOC 2, ISO 27001, HIPAA, PCI DSS, FedRAMP</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>Google Cloud Security</cell></row><row><cell cols="2">Virtualization Support</cell><cell>AWS Config, AWS Inspector, AWS Trusted Advisor</cell><cell>Azure Security Center, Azure Policy, Azure Firewall</cell><cell>Command Center, Google Cloud IAM, Google Cloud</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>Armor</cell></row><row><cell cols="3">The evaluation of the effectiveness of security policies in</cell><cell></cell></row><row><cell cols="3">different cloud platforms can be as follows:</cell><cell></cell></row><row><cell>1.</cell><cell cols="2">Azure (Microsoft Azure) 9. Azure provides</cell><cell></cell></row><row><cell></cell><cell cols="2">extensive capabilities for creating and configuring</cell><cell></cell></row><row><cell></cell><cell cols="2">security policies through Azure Security Center</cell><cell></cell></row><row><cell></cell><cell cols="2">and Azure Policy. Thanks to these services,</cell><cell></cell></row><row><cell></cell><cell cols="2">administrators can effectively control and monitor</cell><cell></cell></row><row><cell></cell><cell cols="2">the state of security of resources in the Azure</cell><cell></cell></row><row><cell></cell><cell cols="2">cloud environment. Azure also provides</cell><cell></cell></row><row><cell></cell><cell cols="2">opportunities for integration with other security</cell><cell></cell></row><row><cell></cell><cell cols="2">monitoring and management systems, which</cell><cell></cell></row><row><cell></cell><cell cols="2">increases its effectiveness.</cell><cell></cell></row><row><cell>2.</cell><cell></cell><cell></cell><cell></cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Application of Game Theory, Fuzzy Logic and Neural Networks for Assessing Risks and Forecasting Rates of Digital Currency</title>
		<author>
			<persName><forename type="first">B</forename><surname>Bebeshko</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. Theor. Appl. Inf. Technol</title>
		<imprint>
			<biblScope unit="volume">100</biblScope>
			<biblScope unit="issue">24</biblScope>
			<biblScope unit="page" from="7390" to="7404" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A Survey on Cloud Computing Security: Challenges and Opportunities</title>
		<author>
			<persName><forename type="first">F</forename><surname>Sabahi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Movaghar</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACCESS.2023.3258591</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Access</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="page" from="34501" to="34519" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Cloud Computing Services and Platforms: A Detailed Review and Future Perspectives</title>
		<author>
			<persName><forename type="first">P</forename><surname>Kumar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Singh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Rathore</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.future.2023.07.003</idno>
	</analytic>
	<monogr>
		<title level="j">Future Generation Computer Systems</title>
		<imprint>
			<biblScope unit="volume">143</biblScope>
			<biblScope unit="page" from="1023" to="1038" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Shah</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Khan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ahmed</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-031-25711-2</idno>
		<title level="m">Cloud Computing: Principles, Systems and Applications</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">F</forename><surname>Richter</surname></persName>
		</author>
		<ptr target="https://www.statista.com/chart/18819/worldwide-market-share-of-leading-cloud-infrastructure-service-providers/" />
		<title level="m">Worldwide Market Share of Leading Cloud Infrastructure Service Providers</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">Practical Aspects of Using Fully Homomorphic Encryption Systems to Protect Cloud Computing</title>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">Assessment of the Security of the Use of Cloud Technologies and the Development of Methods of Protection Against Cyber Attacks on Cloud Services</title>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">M</forename><surname>Mazur</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2023">2023</date>
			<publisher>TNTU</publisher>
			<pubPlace>Ternopil</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Cybersecurity Analysis: Investigating the Data Integrity and Privacy in AWS and Azure Cloud Platforms, Artificial Intelligence and Blockchain for Future Cybersecurity Applications</title>
		<author>
			<persName><forename type="first">S</forename><surname>Galiveeti</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-74575-2_17</idno>
	</analytic>
	<monogr>
		<title level="j">Studies in Big Data</title>
		<imprint>
			<biblScope unit="volume">90</biblScope>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Sheps</surname></persName>
		</author>
		<ptr target="https://www.aquasec.com/cloud-native-academy/cloud-attacks/cloud-attacks/" />
		<title level="m">Top 10 Cloud Attacks and What You Can Do About Them</title>
				<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<ptr target="https://www.triskelelabs.com/blog/cloud-cyber-attacks-the-latest-cloud-computing-security-issues" />
		<title level="m">Cloud Cyber Attacks: The Latest Cloud Computing Security Issues</title>
				<imprint/>
		<respStmt>
			<orgName>Triskele Labs</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Cloud Computing: Threats, Attacks and Solutions</title>
		<author>
			<persName><forename type="first">P</forename><surname>Kumar</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Int. J. Emerging Technol. Eng. Res. (IJETER)</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">8</biblScope>
			<biblScope unit="page" from="24" to="28" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">A Review of DDoS Attacks and its Countermeasures in Cloud Computing</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">V</forename><surname>Songa</surname></persName>
		</author>
		<idno type="DOI">10.1109/ISCON52037.2021</idno>
	</analytic>
	<monogr>
		<title level="m">International Conference on Information Systems and Computer Networks</title>
				<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Proactive Measures on Account Hijacking in Cloud Computing Network</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">A</forename><surname>Christina</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Asian J. Comput. Sci. Technol</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="31" to="34" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Ambiguity in Cloud Security with Malware-Injection Attack</title>
		<author>
			<persName><forename type="first">I</forename><surname>Ranjan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Bhushan</surname></persName>
		</author>
		<idno type="DOI">10.1109/ICECA.2019.8821844</idno>
	</analytic>
	<monogr>
		<title level="m">3 rd International Conference on Electronics, Communication and Aerospace Technology (ICECA)</title>
				<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="1" to="5" />
		</imprint>
	</monogr>
	<note>CClo</note>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Designing Secured Services for Authentication, Authorization, and Accounting of Users</title>
		<author>
			<persName><forename type="first">D</forename><surname>Shevchuk</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Cybersecurity Providing in Information and Telecommunication Systems II</title>
		<imprint>
			<biblScope unit="volume">3550</biblScope>
			<biblScope unit="page" from="217" to="225" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Automated Conformity Verification Concept for Cloud Security</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Martseniuk</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Cybersecurity Providing in Information and Telecommunication Systems</title>
		<imprint>
			<biblScope unit="volume">3654</biblScope>
			<biblScope unit="page" from="25" to="37" />
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Designing Data Classification and Secure Store Policy According to SOC 2 Type II</title>
		<author>
			<persName><forename type="first">O</forename><surname>Deineka</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Cybersecurity Providing in Information and Telecommunication Systems</title>
		<imprint>
			<biblScope unit="volume">3654</biblScope>
			<biblScope unit="page" from="398" to="409" />
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Research on Security Challenges in Cloud Environments and Solutions based on the security-as-Code Approach</title>
		<author>
			<persName><forename type="first">O</forename><surname>Vakhula</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Opirskyy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Mykhaylova</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Cybersecurity Providing in Information and Telecommunication Systems II</title>
		<imprint>
			<biblScope unit="volume">3550</biblScope>
			<biblScope unit="page" from="55" to="69" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<title level="m" type="main">Improper Neutralization of Special Elements used in a command</title>
		<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="209" to="217" />
		</imprint>
	</monogr>
	<note>CWE: Individual Dictionary Definition</note>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">Application Programming Interface (API) Security in Cloud Applications</title>
		<author>
			<persName><forename type="first">F</forename><surname>Qazi</surname></persName>
		</author>
		<idno type="DOI">10.4108/eetcs.v7i23.3011</idno>
	</analytic>
	<monogr>
		<title level="j">EAI Endorsed Transactions on Cloud Systems</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="issue">23</biblScope>
			<biblScope unit="page">e1</biblScope>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Critical Review of Openstack Security: Issues and Weaknesses</title>
		<author>
			<persName><forename type="first">H</forename><surname>Albaroodi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Manickam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Singh</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. Comput. Sci</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="23" to="33" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Mobile Cloud Computing with SOAP and REST Web Services</title>
		<author>
			<persName><surname>Ali</surname></persName>
		</author>
		<idno type="DOI">10.1088/1742-6596/1018/1/012005</idno>
	</analytic>
	<monogr>
		<title level="j">Journal of Physics: Conference Series</title>
		<imprint>
			<biblScope unit="page">12005</biblScope>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">All Your Clouds Are Belong to Us</title>
		<author>
			<persName><forename type="first">J</forename><surname>Somorovsky</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">3 rd ACM workshop on Cloud computing security workshop -CCSW&apos;11</title>
				<imprint>
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">Security Analysis of Openstack Keystone</title>
		<author>
			<persName><forename type="first">B</forename><surname>Cui</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Xi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">9 th International Conference on Innovative Mobile and Internet Services in Ubiquitous Computing</title>
				<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<analytic>
		<title level="a" type="main">Mobile Application as a Critical Infrastructure Cyberattack Surface</title>
		<author>
			<persName><forename type="first">O</forename><surname>Mykhaylova</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Cybersecurity Providing in Information and Telecommunication Systems II</title>
		<imprint>
			<biblScope unit="volume">3550</biblScope>
			<biblScope unit="page" from="29" to="43" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">Investigating Cloud Computing Misconfiguration Errors using the Human Factors Analysis and Classification System</title>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">N</forename><surname>Nobles</surname></persName>
		</author>
		<idno type="DOI">10.2478/bsaft-2022-0007</idno>
	</analytic>
	<monogr>
		<title level="j">Scientific Bulletin</title>
		<imprint>
			<biblScope unit="volume">27</biblScope>
			<biblScope unit="issue">1</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<monogr>
		<ptr target="http://developer.openstack.org/api-guide/quick-start/api-quick-start.html#openstack-api-quick-guide" />
		<title level="m">OpenStack Docs: OpenStack APIs</title>
				<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b27">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Goasguen</surname></persName>
		</author>
		<ptr target="http://www.slideshare.net/sebastiengoasguen/intro-to-cloudstack-api" />
		<title level="m">Intro to CloudStack API</title>
				<imprint>
			<publisher>Slideshare</publisher>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b28">
	<analytic>
		<title level="a" type="main">A Comprehensive Survey on Cloud Computing Service Models</title>
		<author>
			<persName><forename type="first">A</forename><surname>Alkahtani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Khan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Hariri</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACCESS.2023.3262599</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Access</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="page" from="34792" to="34810" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b29">
	<analytic>
		<title level="a" type="main">Protecting Objects of Critical Information Infrastructure from Wartime Cyber Attacks by Decentralizing the Telecommunications Network</title>
		<author>
			<persName><forename type="first">P</forename><surname>Anakhov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Workshop on Cybersecurity Providing in Information and Telecommunication Systems</title>
				<imprint>
			<date type="published" when="2023">2023</date>
			<biblScope unit="volume">3050</biblScope>
			<biblScope unit="page" from="240" to="245" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b30">
	<analytic>
		<title level="a" type="main">A Comparative Study of PaaS and SaaS Cloud Models: Current Trends and Future Directions</title>
		<author>
			<persName><forename type="first">M</forename><surname>Silic</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Back</surname></persName>
		</author>
		<idno type="DOI">10.1186/s13677-023-00211-8</idno>
	</analytic>
	<monogr>
		<title level="j">J. Cloud Comput. Adv. Syst. Appl</title>
		<imprint>
			<biblScope unit="volume">12</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="14" to="28" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
