Cloud computing security

Part of a series on
Computer hacking
History Phreaking Cryptovirology Hacking of consumer electronics List of hackers
Hacker culture and ethic Hackathon Hacker Manifesto Hackerspace Hacktivism Maker culture Types of hackers Black hat Grey hat White hat
Conferences Black Hat Briefings Chaos Communication Congress DEF CON Hackers on Planet Earth Security BSides ShmooCon Summercon
Computer crime Crimeware List of computer criminals Script kiddie
Hacking tools Exploit forensics-focused operating systems Payload Social engineering Vulnerability
Practice sites HackThisSite Zone-H
Malware Rootkit Backdoor Trojan horse Virus Worm Spyware Ransomware Logic bomb Botnet Keystroke logging HIDS Web shell RCE Infostealer
Computer security Application security Cloud computing security Network security
Groups Anonymous Chaos Computer Club Homebrew Computer Club (defunct) Legion of Doom (defunct) LulzSec (defunct) Masters of Deception (defunct) Red team / Blue team
Publications 2600: The Hacker Quarterly Hacker News Nuts and Volts Phrack
v t e

Cloud computing security or cloud security refers to a broad set of policies, technologies, applications, and controls used to protect virtualized IP, data, applications, services, and the associated infrastructure of cloud computing. It is a sub-domain of computer security, network security and, more broadly, information security.

Cloud computing and storage provide users with the capability to store and process their data in third-party data centers.^[1] Organizations use the cloud in a variety of service models (e.g., SaaS, PaaS, IaaS) and deployment models (private, public, hybrid, and community).^[2]

Security concerns associated with cloud computing are typically divided into issues faced by cloud providers and those faced by their customers.^[3] The responsibility is shared and is often described in a vendor’s "shared responsibility model".^[4][5][6] The provider must secure its infrastructure, while customers must secure their applications, identities, and configuration settings.^[5][6]

Analyses of large-scale cloud incidents indicate that many breaches result from misconfigurations and long-unremediated exposures rather than solely from zero-day vulnerabilities.^[7]

When an organization stores data or hosts applications on the public cloud, it loses physical access to the hardware. As a result, potentially sensitive data may be at risk from insider attacks. According to a 2010 Cloud Security Alliance report, insider attacks rank among the top threats in cloud computing.^[8] Cloud service providers must ensure that thorough background checks are conducted for employees with physical access to data centers.

To conserve resources and reduce cost, cloud providers often store multiple customers’ data on the same server. As a result, one user’s private data might be viewable by another without proper isolation.^[2] Providers implement data isolation and logical segregation to mitigate these risks.

The extensive use of virtualization in cloud infrastructure brings unique security concerns.^[9] Virtualization introduces an additional layer—the hypervisor—that must be secured and correctly configured.^[10] A compromise of the hypervisor management system can impact an entire data center.^[11]

Cloud security architecture is effective only if the correct defensive implementations are in place. An efficient cloud security architecture should recognize the issues that will arise with security management and follow all the best practices, procedures, and guidelines to ensure a secure cloud environment. Security management addresses these issues with security controls. These controls protect cloud environments and are put in place to safeguard any weaknesses in the system and reduce the effect of an attack.

Deterrent controls

Administrative mechanisms intended to reduce attacks by informing attackers of consequences.^[12]

Preventive controls

Controls designed to reduce vulnerabilities and prevent unauthorized access.^[13]

Detective controls

Controls that detect and respond to security events. Includes monitoring, SIEM, IDS/IPS, malware detection.^[14]

Corrective controls

Controls that reduce the impact of an incident and restore systems.^[15]

Cloud security engineering is characterized by the security layers, plan, design, programming, and best practices that exist inside a cloud security arrangement. Cloud security engineering requires the composed and visual model (design and UI) to be characterized by the tasks inside the Cloud. This cloud security engineering process includes such things as access to the executives, techniques, and controls to ensure applications and information. It also includes ways to deal with and keep up with permeability, consistency, danger stance, and by and large security. Processes for imparting security standards into cloud administrations and activities assume an approach that fulfills consistent guidelines and essential foundation security parts.^[16]

Though the idea of cloud computing is not new, organizations are increasingly adopting it because of its flexible scalability, relative trustability, and cost-effectiveness of services. However, despite its rapid adoption in some sectors and disciplines, research and statistics indicate that security-related pitfalls remain a major barrier to its full adoption.^[17]

It is generally recommended that information security controls be selected and implemented in proportion to the risks, typically by assessing the threats, vulnerabilities and impacts. Cloud security concerns can be grouped in various ways; Gartner identified seven, while the Cloud Security Alliance identified twelve areas of concern.^[18][19] Cloud access security brokers (CASBs) are software that sits between cloud users and cloud applications to provide visibility into cloud application usage, data protection and governance to monitor all activity and enforce security policies.^[20]

When someone breaches a third party's systems via one of its external partners or services, it's known as a supply chain attack. Rather than going straight after the primary system, the attacker enters through a reliable source, like an open-source tool, cloud provider, or software vendor. The attack may remain undetected for a considerable amount of time because these tools are already trusted. As more businesses rely on external technology and cloud services, supply chain attacks have grown more damaging and difficult to identify. Before code written in widely used languages, such as JavaScript, reaches end users, it is frequently altered in contemporary attacks. What is a supply chain attack highlights the attacks that take place and states, “In a supply chain attack, an attacker might target a cybersecurity vendor and add malicious code (or ‘malware’) to their software, which is then sent out in a system update to that vendor’s clients. ...When the clients download the update, believing it to be from a trusted source, the malware grants attackers access to those clients’ systems and information”(Cloudflare, 2020). This emphasizes the dangers of depending on outside software or vendors. It demonstrates how hackers can covertly enter a company's systems through legitimate channels, such as system updates.^[21]

Software dependencies

Software dependencies are the external tools or components a program relies on, like third-party libraries, frameworks, or pre-built modules. While these can speed up development, they can also pose risks. Security issues in the libraries, attacks targeting the supply chain, or outdated and poorly maintained code can all create vulnerabilities. Keeping dependencies up to date and carefully managing them is key to maintaining software secure and reliable.^[22]

The specific software dependencies include:

Cover third-party libraries

The third-party libraries and tools that a program depends on are known as software dependencies. These external packages may lead to supply chain assaults, coding defects, or difficulties resulting from the use of out-of-date or poorly maintained software. Maintaining the security and functionality of systems requires managing these dependencies.^[23]

What are the benefits and risks?

Software dependencies have a number of benefits. By offering reusable code, which eliminates the need for developers to create each feature from scratch, they expedite development. Additionally, they facilitate the addition of sophisticated or complicated features, such as analytics or interface elements, which would require a lot more time to develop independently. Utilizing reputable and well-maintained libraries can also raise the general caliber and dependability of your code. ^[24]Using third-party tools and libraries increases the risks associated with software dependencies. These pieces can be challenging to maintain and update because they are derived from external sources. Additionally, they could lead to dependency chains, where a single update impacts numerous system components, security flaws, and attack opportunities.^[25]

CI/CD

Continuous delivery (CD) and continuous integration (CI) are terms used in software development. While CD ensures that those updates can be released swiftly and smoothly, CI focuses on routinely merging and testing code changes.^[26]

Now let's get specific:

The practice of developers routinely merging their code into a shared repository is known as Continuous Integration (CI). An automated build and several tests, including unit and integration tests, are triggered by every merge. CI's primary goal is to identify bugs early on and correct mistakes that could result in security flaws. ^[27]The process of automatically preparing code changes so they can be released to production at any time is known as continuous delivery, or CD. By ensuring that every test runs properly and that the code passes every check, it expands on continuous integration. The update can be delivered without the need for manual steps once everything has been confirmed.^[28]

CI/CD pipelines

The processes used to build, test, and deliver software through continuous integration and continuous delivery platforms. The structure of a pipeline can change depending on what the project needs. According to articleWhat Is CI/CD? Continuous Integration & Continuous Delivery Explained states, “Properly setting up a CI/CD pipeline is the key to benefiting from all the advantages offered by CI/CD. One pipeline might have a multi-stage deployment strategy that delivers software as containers to a multi-cloud Kubernetes cluster, and another may be a simple pipeline that builds, tests, and deploys the application as a serverless function”(Raza & Wickramasinghe, 2021). This shows how pipelines can look very different depending on the development goals. ^[29]

Any service without a “hardened” environment is considered a “soft” target. Virtual servers should be protected just like a physical server against data leakage, malware, and exploited vulnerabilities. “Data loss or leakage represents 24.6 % and cloud-related malware 3.4 % of threats causing cloud outages”.^[30]

Every enterprise will have its own identity management system to control access to information and computing resources. Cloud providers either integrate the customer’s identity management system into their own infrastructure, using federation or SSO technology or a biometric-based identification system,^[1] or provide an identity management system of their own.

Cloud service providers physically secure the IT hardware (servers, routers, cables etc.) against unauthorized access, interference, theft, fire, flood etc., and ensure that essential supplies (such as electricity) are sufficiently robust to minimise the possibility of disruption.

Various information security concerns relating to personnel involved in cloud services are typically handled through screening, security-awareness training, and role-based access controls.

Providers ensure that all critical data (credit-card numbers, for example) are masked or encrypted and that only authorised users have access to data in its entirety. Moreover, digital identities and credentials must be protected as must any data that the provider collects or produces about customer activity in the cloud.

Penetration testing is the process of performing offensive security tests on a system, service, or computer network to find security weaknesses in it. Since the cloud is a shared environment with other customers or tenants, following penetration-testing rules of engagement step-by-step is a mandatory requirement. Scanning and penetration-testing from inside or outside the cloud should be authorised by the cloud provider.^[31]

Scanning the cloud from outside and inside using free or commercial tools is crucial. Without a hardened environment, your service is considered a soft target. Virtual servers should be hardened just like a physical server against data leakage, malware, and exploited vulnerabilities. “Data loss or leakage represents 24.6 % and cloud-related malware 3.4 % of threats causing cloud outages”.

Privacy legislation often varies by country. By having information stored via the cloud it is difficult to determine under which jurisdiction the data falls. Trans-border clouds are popular given that the largest companies transcend several countries. Legal dilemmas from the ambiguity of the cloud refer to how there is a difference in data-sharing law between and inside organisations.^[32]

Due to the autonomous nature of the cloud, consumers are often given management interfaces to monitor their databases. By having controls in one central location and by having the interface be easily accessible for user convenience, there is a possibility that a single actor could gain access to the cloud's management interface; giving them control over much of the system.^[33]

The cloud’s use of resource pooling means memory or storage resources may be recycled to another user. It is possible for current users to access information left by previous ones.^[33]

Cloud services require internet connectivity and use internet protocols, making them subject to attacks such as man-in-the-middle attacks. Furthermore, heavy reliance on internet connectivity means service disruptions or outages can cut off users entirely.^[33]

As encryption algorithms age, vulnerabilities arise. Cloud providers must stay current with encryption standards and transition older systems before they become compromised.^[34]

Cloud environments are extremely vulnerable, particularly when it comes to hackers and attackers, due to cloud misconfigurations, which are one of the most prevalent and dangerous security flaws. Cloud platforms are complicated; even a minor configuration error, like excessively permissive access or inappropriate storage, can provide attackers with entry points. Cloud breaches are frequently caused by misconfigurations because attackers can obtain unauthorized access by taking advantage of incorrectly configured settings. ^[35]

Security misconfigurations occur when security settings are not fully implemented or are set up incorrectly. Weak passwords, misconfigured databases, unprotected cloud storage, incorrectly configured firewalls or network settings, and out-of-date software or firmware are just a few of the many possible causes. These errors frequently result from system design flaws, human error, or gaps in knowledge regarding security procedures. As the article Security Misconfiguration Vulnerabilities: Risks, Impacts, and Prevention explains, “Security misconfigurations are errors that occur when security settings are not configured or implemented properly. Misconfigurations can arise from a range of sources, including weak passwords, improperly configured databases, unsecured cloud storage, misconfigured firewalls or network settings, and outdated software or firmware. They can happen due to various reasons, including poor design, lack of understanding of security concepts, and human error”(Kiteworks, 2025). ^[36]This quote highlights the variety of ways misconfigurations can occur and emphasizes why organizations must identify and correct them to protect against potential security breaches.

Most common misconfigurations include unrestricted outbound access, disabled logging, missing alerts, exposed access keys, excessive account permissions, ineffective identity architecture, inadequate network segmentation, improper public access, public snapshots and images, open databases or storage buckets, and neglected cloud infrastructure. The article The Common Cloud Misconfigurations That Lead to Cloud Data Breaches explains: “Cloud misconfigurations — the gaps, errors and vulnerabilities that occur when security settings are poorly chosen or neglected entirely — provide adversaries with an easy path to infiltrate the cloud. Multi-cloud environments are complex, and it can be difficult to tell when excessive account permissions are granted, improper public access is configured or other mistakes are made”(Ashwood, 2024).^[37]  The article also emphasizes that “cloud security posture management should be a key component of your security strategy if you want to avoid becoming the next victim of a cloud data breach”(Ashwood, 2024). ^[38], showing why strong security measures and backups are essential.

Additionally, another article, 8 Common Cloud Misconfiguration Types (and How to Avoid Them), offers practical solutions: “Access to storage buckets should be granted only within the organization… Security teams should enable strong encryption by default for crucial data in storage buckets, monitor all storage nodes labeled as public, and eliminate unnecessary permissions or exposed access”(Lee, 2025c). ^[39] This highlights how businesses can lower the risk of misconfiguration by implementing simple, doable measures like restricting access, encrypting private information, keeping an eye on public resources, and eliminating superfluous permissions. To safeguard data and stop breaches, cloud settings must be actively managed.^[40]

Some advanced encryption algorithms applied to cloud computing increase the protection of privacy. In a practice called crypto-shredding, encryption keys can be deleted when data is no longer used.

Attribute-based encryption is a form of public-key encryption in which the user’s secret key and the ciphertext depend on attributes (e.g., the country the user lives in, or their subscription type). In such systems, access to decryption depends not simply on identity but on attributes.

Some of the strengths of ABE are that it bypasses the need for explicit key sharing (as in traditional PKI) and identity-based encryption (IBE). However, ABE suffers from key-redistribution complexity: since decryption keys depend on attributes rather than identities, malicious users might leak attribute information, enabling unauthorized access.^[41]

In CP-ABE, the encryptor controls the access policy for the ciphertext. The process includes Setup, Encrypt, KeyGen, and Decrypt algorithms; the encryptor defines an access structure that must match a user’s attributes before decryption is allowed.^[42]

In KP-ABE, the sender encrypts under a set of attributes, and the user’s private key is issued to match a policy describing which ciphertexts they may decrypt. KP-ABE shifts access-control responsibility partially to the key-issuer rather than the encryptor. While it provides flexibility, the policy disclosure may weaken privacy guarantees.^[43]

Fully Homomorphic Encryption allows arbitrary computation on ciphertext without decryption. It is emerging as a high-security option for cloud environments, including voting systems. While promising, it remains largely experimental.^[44]

Searchable encryption enables secure search on encrypted data. It has symmetric and public-key variants. While it supports functionality over encrypted data, it introduces extra attack surfaces, especially when attribute indexing is involved.^[45]

Similar to a computer's motherboard or heart, Data is the foundation of life and operation. Basic memory holds extremely important data to enable the user and computer to pick up where they left off.^[46]

When delving into the details of the data lifecycle and security, it's critical to strengthen security protocols and make sure that security strategies are strong enough to reduce the likelihood of access or decryption. The Harvard University data lifecycle essay made it apparent that "the best time to secure information in your project is before you even collect it." This statement reinforces the notion that data should be stored and safeguarded before a user or computer even acts.^[47]

Numerous factors influence data security and data life-cycle security, beginning with:^[48]

Data creation

It is the initial output that the user provides in these forms, such as software or hardware, and it creates a space where information is found and finally kept. From there, it can be altered and safeguarded once both the user and the software have validated it. The creation of new data is beneficial because it enhances performance over time on various security alternatives and allows for innovation to You can continue to add to it once it has been stored and secured, etc. We have a better framework for how it is carried out, thanks to Why Accurate Data is Important for Business Operations. Let's utilize the safe data business lens of security as an example, which lowers risk and facilitates consistent outcomes. The knowledge is currently available and preserved; you can simply return to it and continue working on it, which increases engagement and boosts productivity. In any format where an audience may review it, the quality of the data simply improves over time. This is true not just when data is imported but also when new sources of information are created to enhance certain regions. It reduces risk, increases worker productivity, and promotes more consistent results. Accurate and well-managed data improves business operations. Properly saved and updated data makes it easier to review, expand upon, and enhance, improving performance and creating more space for fresh concepts and superior solutions.^[49]

Data Storage

Data storage is the output that the computer produces from the input that the user provides. Depending on the model of the computer, this will determine how the information is presented. If the RAM is full, it means that the data is being disseminated because the computer is overheated or overloaded with data, which requires a lot of power from the computer, particularly from its hardware. The requirements for data storage are broken down in the IBM article What is Data Storage? Examining the benefits and drawbacks of data storage and its significance. ^[50]

Data Storage's Importance

keeps information accessible and well-organized when needed. enables consumers or businesses to monitor progress and make more informed decisions. prevents the loss or damage of crucial data. facilitates long-term initiatives by centralizing records.^[51]

Pros of Data Storage:

Facilitate the access and reuse of information Since everything is kept in one system, productivity can be increased. Enables data backup for security. Supports updates, expansion, and new ideas over time. ^[52]

Cons of Data Storage:

Requires extra storage as data quantities grow, can take up space, and requires security measures to prevent unauthorized access. Maintaining accuracy and organization requires regular updating. Misunderstandings or outdated information could be the outcome of poor management. ^[53]

The users' directory contains files and folders that store data. Alternatively, if you're using a personal computer, you can locate storage or extra storage on the hard drive as a stand-in if your computer isn't big enough. ^[54]Another type of object storage that divides data into metadata and particular identifiers. It's fantastic because it can be this type of storage and used in public cloud servers, which gives some of these providers, like AWS (Amazon Web Services), emails, social media content, etc., scalability and flexibility. It also works well with APIs (application programming interfaces).^[55]

Data transmission

Due to its connection to the communication component of syncing devices, this has a significant impact on data lifecycle security. Cables, wireless, wifi, and channels can all be used to transfer these types of communication. Some excellent illustrations of how digital data transmissions operate are message commands. Both synchronous and asynchronous use are possible. Additionally, bandwidth and latency are important aspects of these data transmission methods, which offer effective accuracy in terms of speed and overall accuracy.^[56]

HTTPS (Hypertext Transfer Protocol Secure) is a security protocol that is used during data transmission. This works by encrypting the data being transferred between websites, which makes it an excellent example. As a sign that it is being watched over or managed by a human, it will transmit the TLS version and a cipher of random values behind the scenes to guarantee authenticity from the recipient's end. Because the data is actively shielded from vulnerable attacks, this is beneficial. ^[57]

Data processing

It serves as the fundamental basis for data collection and is essentially a substantial amount of analysis that, if the device has enough storage, may be processed all at once; otherwise, it must be divided, which is where hard drives come into play. Additionally, it offers a range of sources that offer feedback, which is the analytical component. ^[58]

However, how is the cycle's operation protected? According to the article How to Ensure Secure Data Processing, utilizing a data virtualization platform reduces risk and data breaches even with multiple collaborators by providing a data architecture, basically a template that doesn't change the user's data storage option, and then creating a layout or an analytics report in custom datasets.^[59]

Archival & deletion (secure deletion is often overlooked)^[60]

In essence, archival data is information that is not regularly used but is kept in file storage so that it can be found and used at a later time if necessary. Deletion is when the data is no longer needed, so it's permanently deleted from the server/ storage. ^[61]This is critical because it not only creates space due to the removal of data. However, it's important to know that when deleting, it's good to make sure that it's securely deleted because it can still be traceable and recoverable. How to properly ensure that your deletion is properly secured by using cryptographic measures or physically destroying the storage media, the best one is erasing, which basically wipes out which make the data completely unrecoverable/no longer traceable.^[60]

Numerous laws and regulations govern the storage and use of data. In the US these include privacy and data-protection laws, the Payment Card Industry Data Security Standard (PCI DSS), the Health Insurance Portability and Accountability Act (HIPAA), the Sarbanes-Oxley Act, the Federal Information Security Management Act of 2002 (FISMA), and the Children’s Online Privacy Protection Act of 1998. Similar standards exist in other jurisdictions (e.g., Singapore’s Multi-Tier Cloud Security Standard).

Similar laws may apply in different legal jurisdictions and may differ markedly from those in the US. Cloud service users must often understand the legal and regulatory differences between the jurisdictions. For example, data stored by a cloud service provider (CSP) may be located in, say, Singapore and mirrored in the US.^[62]

Business continuity and data recovery

Cloud providers have business continuity and data recovery plans in place to ensure service continuity and data protection.^[63]

Log and audit trail

In addition to producing logs and audit trails, cloud providers work with their customers to secure these logs and ensure they’re accessible for forensic investigation (e.g., eDiscovery).

Unique compliance requirements

In addition to the requirements on customers, data centers used by cloud providers may be subject to additional compliance obligations. Using a cloud service provider (CSP) can lead to extra security concerns around data jurisdiction since customer or tenant data may not remain in the same location or provider’s cloud.^[64]

Aside from the security and compliance issues already discussed, cloud providers and their customers negotiate terms around liability (stipulating how incidents involving data loss or compromise will be resolved, for example), intellectual property, and end-of-service (when data and applications are ultimately returned to the customer). These issues are typically addressed in service-level agreements (SLAs).^[65]

Legal issues may also include records-keeping requirements in the public sector, where agencies must retain and make available electronic records in a specific fashion.

• Computer security
• Common Vulnerabilities and Exposures

• Mowbray, Miranda (15 April 2009). "The Fog over the Grimpen Mire: Cloud Computing and the Law". SCRIPT-ed. 6 (1): 132–146. doi:10.2966/scrip.060109.132.
• Mather, Tim; Kumaraswamy, Subra; Latif, Shahed (2009). Cloud Security and Privacy: An Enterprise Perspective on Risks and Compliance. O’Reilly Media, Inc. ISBN 978-0-596-80276-9.
• Winkler, Vic (2011). Securing the Cloud: Cloud Computer Security Techniques and Tactics. Elsevier. ISBN 978-1-59749-592-9.
• Ottenheimer, Davi (2012). Securing the Virtual Environment: How to Defend the Enterprise Against Attack. Wiley. ISBN 978-1-118-15548-6.
• BS ISO/IEC 27017: "Information technology. Security techniques. Code of practice for information security controls based on ISO/IEC 27002 for cloud services." (2015)
• BS ISO/IEC 27018: "Information technology. Security techniques. Code of practice for protection of personally identifiable information (PII) in public clouds acting as PII processors." (2014)
• BS ISO/IEC 27036-4: "Information technology. Security techniques. Information security for supplier relationships. Guidelines for security of cloud services" (2016)

• DoD Cloud Computing Security Requirements Guide (CC SRG)

• Archived 2018-10-21 at the Wayback Machine