---
title: "What is cloud computing security? A beginner's guide"
description: "It is a shared responsibility: providers protect the underlying services, while customers secure the accounts, information, and settings they control."
published: "2026-11-06T13:00:00.000Z"
updated: "2026-11-06T13:00:00.000Z"
url: "https://getdosya.com/what-is-cloud-computing-security-a-beginner-s-guide"
canonical: "https://getdosya.com/what-is-cloud-computing-security-a-beginner-s-guide"
site: "Get dosya"
---

# What is cloud computing security? A beginner's guide

It is a shared responsibility: providers protect the underlying services, while customers secure the accounts, information, and settings they control.

## Key takeaways

- Under the shared responsibility model providers protect the underlying infrastructure, while customers secure their accounts, data and settings, so document who owns each task.
- Main threats include compromised accounts with excessive permissions, accidental sharing, vulnerable applications, and ransomware that targets backups, so CISA recommends encrypted, immutable backups.
- Core practices include phishing-resistant multifactor authentication, least-privilege access, encryption in transit and at rest, protected keys, and logs with alerts that someone reviews.
- Begin with an inventory of services and owners, then reduce access risks, then prove detection and recovery by restoring a sample file.

Cloud computing security is the combination of tools, policies, and everyday practices used to protect data, applications, and infrastructure hosted in the cloud. It is a shared responsibility: providers protect the underlying services, while customers secure the accounts, information, and settings they control. This guide explains the main risks, how protection works, and which practical steps to take first. ([cisco.com](https://www.cisco.com/site/us/en/learn/topics/security/what-is-cloud-security.html))

## What does cloud computing security protect?

Cloud computing security protects information and systems that use cloud services, including online files, business applications, databases, and virtual servers. Its scope includes controlling access, protecting information from exposure or unauthorized changes, detecting suspicious activity, and maintaining access to important services. It is not one product or a setting you switch on once. ([cisco.com](https://www.cisco.com/site/us/en/learn/topics/security/what-is-cloud-security.html))

For a beginner, three questions make the subject easier to understand:

- **Who can access it?** Only approved people and applications should reach sensitive information.
- **Who can change it?** Permissions should prevent unauthorized edits, deletions, and configuration changes.
- **Can you recover it?** Important information should remain recoverable after accidental deletion, an attack, or another disruption. ([cyber.gov.au](https://www.cyber.gov.au/publication/cloud-shared-responsibility-model-guidance-for-individuals-and-small-and-medium-businesses))

Consider a shared folder containing customer contracts. Protecting it involves more than choosing a reputable storage provider. You also need to decide who can open the folder, whether recipients can share it further, and how to revoke access when collaboration ends. Those decisions turn security features into meaningful protection. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-saas-securely))

## Understand the cloud services you use

Cloud computing provides on-demand access to computing resources over a network. Instead of owning and maintaining every server yourself, you use resources supplied as a service. NIST groups these offerings into three main service models, which provide different levels of customer control. ([nist.gov](https://www.nist.gov/publications/nist-definition-cloud-computing))

| Service model | What you use | Typical customer security focus |
| --- | --- | --- |
| Software as a service, or SaaS | A ready-made application, such as hosted email | Accounts, sharing, data, and application settings |
| Platform as a service, or PaaS | A managed platform for running applications | Application code, identities, data, and service configuration |
| Infrastructure as a service, or IaaS | Virtual machines, storage, and networking | Operating systems, applications, network rules, identities, and data |

The table is a starting point, not a substitute for service documentation. For example, running your own virtual machine generally leaves you responsible for its operating-system updates, while a managed application transfers more maintenance work to the provider. More management by the provider does not remove your responsibility for access and information. ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility/))

## Who is responsible for security in the cloud?

The cloud provider and customer divide security duties under a shared responsibility model. Providers generally protect the physical facilities and infrastructure supporting their services. Customers protect what they control, with the exact division changing according to the service they use. ([aws.amazon.com](https://aws.amazon.com/compliance/shared-responsibility-model/?trk=public_post_comment-text))

A useful distinction is security **of the cloud** versus security **in the cloud**. The first concerns the provider's underlying infrastructure; the second concerns your use of it. For an IaaS virtual server, customer responsibilities can include software patches, firewall configuration, and application security. For a managed service, the provider handles more of that stack. ([aws.amazon.com](https://aws.amazon.com/compliance/shared-responsibility-model/?trk=public_post_comment-text))

Before using any service, document the division rather than relying on assumptions. Your responsibility checklist should identify:

- Who creates, approves, and removes user access.
- Who configures protection for stored information and manages encryption choices.
- Who enables logs and investigates security alerts.
- Who creates backups and tests restoration.
- Who contacts the provider during an incident. ([media.defense.gov](https://media.defense.gov/2024/Mar/07/2003407863/0/0/0/CSI-CloudTop10-Shared-Responsibility-Model.PDF))

Assign an internal owner to each customer task. “The provider handles security” is too broad to guide action, especially when something goes wrong. If documentation leaves a responsibility unclear, ask the provider to explain it before putting important information into the service. ([media.defense.gov](https://media.defense.gov/2024/Mar/07/2003407863/0/0/0/CSI-CloudTop10-Shared-Responsibility-Model.PDF))

## Common cloud security threats

Cloud security threats include weaknesses in account access, unsafe configurations, vulnerable software, and destructive activity. Understanding the path an attacker—or an accidental mistake—could take helps you choose useful defenses instead of collecting tools without a purpose. Start with the risks affecting the services you actually use. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-a-cloud-platform-securely))

### Compromised accounts and excessive permissions

An account with weak authentication can give an attacker a route into cloud resources. The impact becomes greater when that account has broad administrative permissions or access it no longer needs. Strong authentication and restricted privileges address different parts of this problem: one makes impersonation harder, while the other limits what an authenticated account can do. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-10-identity-and-authentication))

### Misconfiguration and accidental sharing

A legitimate user can expose information by choosing an overly broad sharing option. A folder intended for one contractor, for example, might become available to anyone holding its link. Confidential defaults, clear sharing controls, and the ability to revoke access help reduce this risk without preventing necessary collaboration. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-saas-securely))

### Vulnerable applications and integrations

Cloud hosting does not eliminate software vulnerabilities. Applications and their dependencies still require secure development, testing, and maintenance by whichever party controls them. Third-party suppliers also matter because their products and access can affect the security of the service you depend on. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-7-secure-development))

### Ransomware, deletion, and damaged backups

An attacker who gains sufficient access may damage working data and attempt to destroy recovery copies. Backups therefore need protection from unauthorized changes and deletion, not just a successful backup notification. CISA recommends encrypted, immutable backups alongside recovery planning and restoration testing. ([cisa.gov](https://www.cisa.gov/sites/default/files/2025-04/aa23-319a-stopransomware-rhysida-ransomware_2.pdf))

These examples suggest a practical way to prioritize: identify the easiest route to your most important information, then examine how much damage that access could cause. Avoid treating every alert or technical weakness as equally urgent. Use the sensitivity of the data and the potential operational impact to guide your decisions. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/choosing-a-cloud-provider))

## Cloud security best practices that build a strong foundation

Effective cloud security best practices combine prevention, detection, and recovery. Each control should address a recognizable risk and have someone responsible for maintaining it. The following layers provide a useful starting framework, whether you manage one business application or a broader cloud environment. ([nsa.gov](https://www.nsa.gov/Press-Room/Press-Releases-Statements/Press-Release-View/Article/3699169/nsa-releases-top-ten-cloud-security-mitigation-strategies/))

### Strengthen authentication

Require multifactor authentication, or MFA, wherever the service supports it. Prefer phishing-resistant options, such as supported security keys or passkeys, rather than assuming every MFA method provides equivalent protection. Give administrative accounts particular attention because they can control access and security settings across the environment. ([media.defense.gov](https://media.defense.gov/2024/Mar/07/2003407863/0/0/0/CSI-CloudTop10-Shared-Responsibility-Model.PDF))

Keep individual accounts separate rather than sharing one login among several people. Where appropriate, use single sign-on to manage access centrally and connect account removal to your employee departure process. Also plan how authorized administrators can regain access during an emergency without using powerful emergency accounts for routine work. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-a-cloud-platform-securely))

### Grant only the access each role needs

Least privilege means giving a person or application only the permissions necessary for its task. Someone reviewing invoices may need read access, but not permission to delete records or change security settings. Define roles around actual work rather than granting administrator access simply because it is convenient. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-9-secure-user-management))

Review permissions when people change roles and when temporary projects end. Include external collaborators and applications in that review, not just employees. A useful test is to ask whether each permission has a current business reason and an identifiable owner who can approve it. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-9-secure-user-management))

### Protect information in transit and at rest

Encryption in transit protects information moving between systems, while encryption at rest protects stored information. Check both rather than accepting an unexplained claim that a service is “encrypted.” Protection should cover relevant connections between users, applications, internal components, and external services—not only the browser connection you can see. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-1-data-in-transit-protection))

Encryption also depends on protecting the keys used to unlock information. A cloud key management service can help generate, store, use, and retire those keys securely. Choose an approach your team can operate reliably; additional control over keys brings responsibilities that need to be understood before implementation. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/understanding-cloud-services/choosing-and-configuring-a-kms-for-secure-key-management-in-the-cloud))

### Maintain software and secure configurations

Identify which operating systems, applications, and dependencies your team must maintain. Establish a process to assess vulnerabilities, prioritize fixes, and verify that changes have been applied. Obtain corresponding information about the provider's maintenance responsibilities rather than assuming all hosted software is automatically updated. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-5-operational-security))

For applications you build, include security checks during development instead of waiting until deployment. Review how the application handles authentication, sensitive information, and dependencies. Treat a new integration or significant code change as a reason to reassess protection, not merely as a feature release. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-7-secure-development))

### Enable useful logs and alerts

Logs record activity; alerts call attention to activity that may require action. Confirm that important events are recorded, including sign-ins, permission changes, configuration changes, and relevant data access. Check retention periods and protect audit records from alteration or deletion so they remain useful during an investigation. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-13-audit-information-and-alerting-for-customers))

Assign someone to review and respond to alerts. A notification that nobody owns is not an effective response process. Decide which events need immediate investigation, how the provider supplies supporting information, and whether your team can access that information when needed. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-13-audit-information-and-alerting-for-customers))

## Make cloud data protection practical

Cloud data protection starts with knowing what you hold and why it matters. A public brochure and a confidential personnel file should not have identical sharing rules. Classifying information helps you decide which services, access restrictions, and handling practices are appropriate for each category. ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility/))

For secure cloud storage, assess the whole workflow rather than storage capacity alone:

- **Before upload:** Identify the information's sensitivity and approved location.
- **During collaboration:** Use authenticated recipients and permissions suited to their work.
- **When access changes:** Remove permissions that no longer serve a purpose.
- **During recovery:** Confirm who can restore information and which versions are available.
- **At the end of use:** Understand how deletion and any remaining copies are handled. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-2-asset-protection-and-resilience))

For example, when sharing a confidential proposal with a contractor, specify the intended recipient, give only the required access, and decide when that access should end. Check that the recipient cannot broaden access in ways your policy forbids. This is more useful than telling employees simply to “be careful with files.” ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-saas-securely))

Recovery deserves separate attention. Define how much recent work you could afford to lose and how quickly you need important information back. Then check whether backup frequency, retention, restoration options, and protection from deletion can support those needs; test recovery rather than relying on the presence of a backup feature. ([cyber.gov.au](https://www.cyber.gov.au/publication/cloud-shared-responsibility-model-guidance-for-individuals-and-small-and-medium-businesses))

Also review where data is stored, processed, and accessed by support personnel. Those locations may differ. If the information is sensitive or subject to contractual requirements, obtain appropriate advice rather than assuming a regional storage setting answers every governance question. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-2-asset-protection-and-resilience))

## How do you choose cloud security solutions?

Choose cloud security solutions by matching their capabilities to your risks, responsibilities, and ability to operate them. Start with the controls your existing service provides, identify a specific gap, and evaluate additional tools against that gap. The right choice is the one that meets your protection needs—not necessarily the one with the longest feature list. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/choosing-a-cloud-provider))

For a small team using hosted email and file sharing, the immediate need may be stronger account access and better sharing policies. A team running custom applications may need additional configuration checks, vulnerability management, and monitoring. These are different operating problems, so they should not automatically lead to the same purchase. ([learn.microsoft.com](https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility/))

One category you may encounter is **cloud security posture management**, or CSPM. These tools help identify configuration weaknesses in cloud environments. They can improve visibility, but findings still need context, prioritization, and remediation; purchasing a scanning tool does not by itself establish a secure operating process. ([ncsc.gov.uk](https://www.ncsc.gov.uk/blog-post/cspm-silver-bullet-or-another-piece-in-the-cloud-puzzle))

Use a short evaluation checklist:

1. **Coverage:** Does it support the services and accounts you actually use?
2. **Actionability:** Does a finding explain the risk and give your team a workable response?
3. **Ownership:** Who investigates findings and approves changes?
4. **Integration:** Can it fit your existing access and monitoring processes?
5. **Evidence:** What documentation or independent assurance supports the provider's claims?
6. **Ongoing work:** Can your team maintain the configuration and respond consistently? ([ncsc.gov.uk](https://www.ncsc.gov.uk/blog-post/cspm-silver-bullet-or-another-piece-in-the-cloud-puzzle))

During a trial, test a concrete scenario rather than watching only a sales demonstration. For instance, ask the evaluator to show how a misconfiguration is detected, assigned, corrected, and verified. That turns an abstract feature comparison into a test of whether the solution fits your workflow.

## Prepare for a cloud security incident

An incident plan should explain who acts, how they obtain evidence, and how they coordinate with the provider. Write it before an emergency and keep contact details accessible. Include a way to communicate if your normal cloud email or collaboration service becomes unavailable. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-a-cloud-platform-securely))

A practical response sequence is to validate the alert, identify affected accounts and resources, contain unauthorized access, preserve relevant evidence, and coordinate recovery. The exact containment action depends on the situation, so avoid assuming every incident calls for deleting resources or shutting down the entire service. Your plan should distinguish customer actions from support you must request from the provider. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-5-operational-security))

Practice with a realistic scenario, such as a compromised administrator account or an accidentally shared confidential folder. Walk through who receives the alert, who can revoke access, and where investigators obtain logs. Record unanswered questions and resolve them before treating the plan as ready. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-a-cloud-platform-securely))

After an incident, investigate the underlying cause rather than stopping when access is restored. Update affected controls and procedures, and verify that the change addresses the weakness. Recovery should leave you with a better-understood environment, not merely a working one. ([ncsc.gov.uk](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-5-operational-security))

## A beginner's implementation plan

The following is a suggested order for applying these cloud security tips, not a universal timetable. Move faster on known exposures or compromised accounts, and adjust the sequence around your most important information. For each phase, record an owner, the intended result, and evidence that the work is complete.

### First, establish visibility and ownership

List your cloud applications, storage locations, administrators, external collaborators, and important integrations. Record what each service contains and who is responsible for managing it. Then review the shared responsibility documentation so your inventory identifies security duties as well as products. ([media.defense.gov](https://media.defense.gov/2024/Mar/07/2003407863/0/0/0/CSI-CloudTop10-Shared-Responsibility-Model.PDF))

Use a simple completion test: someone unfamiliar with the setup should be able to find the service owner and understand where to raise a security concern. If the inventory cannot answer that, it needs more work before it becomes a reliable operational reference.

### Next, reduce immediate access risks

Review administrative accounts, enable strong authentication, and remove access that is no longer needed. Check whether confidential resources have unnecessarily broad sharing permissions. Prioritize places where sensitive information and powerful access overlap, rather than changing every low-impact setting first. ([ignet.gov](https://www.ignet.gov/sites/default/files/files/CIGIE-OIG%20Best%20Practices%20for%20Cloud%20Computing.pdf))

Keep a short change record showing what was adjusted, who approved it, and how you checked that legitimate work still functions. This makes the exercise easier to review and gives future administrators useful context instead of leaving them to guess why a restriction exists.

### Then, prove detection and recovery

Confirm that important security events generate usable records and reach someone responsible for reviewing them. Restore a representative file or dataset and check whether the result is usable. Finally, run a short incident exercise that connects detection, decision-making, provider support, and recovery. ([cisa.gov](https://www.cisa.gov/sites/default/files/2025-04/aa23-319a-stopransomware-rhysida-ransomware_2.pdf))

Treat success as demonstrated behavior, not a completed purchase or a checked settings page. A useful review can show who has access, how a suspicious change would be noticed, and whether important information can be restored. Repeat that review when your services, staff, or business needs change.

## Build habits, not just a tool collection

You do not need to master every cloud security product before making progress. Begin with a clear picture of what you use, who controls it, and what matters most. Then choose manageable improvements and verify their results. The goal is a repeatable way to make sound security decisions—not a one-time project that nobody revisits.

## Related guides

- [Sending documents securely: 5 methods compared](/sending-documents-securely-5-methods-compared)
- Data center location: why it matters for compliance

## Sources

1. [cisco.com: What is cloud security](https://www.cisco.com/site/us/en/learn/topics/security/what-is-cloud-security.html)
2. [Cloud shared responsibility model: Guidance for individuals and small and medium businesses | CGA](https://www.cyber.gov.au/publication/cloud-shared-responsibility-model-guidance-for-individuals-and-small-and-medium-businesses)
3. [Cloud security guidance | Using cloud services securely | Using Software as a Service (SaaS) securely | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-saas-securely)
4. [The NIST Definition of Cloud Computing | NIST](https://www.nist.gov/publications/nist-definition-cloud-computing)
5. [Shared responsibility in the cloud - Microsoft Azure | Microsoft Learn](https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility/)
6. [Shared Responsibility Model - Amazon Web Services (AWS)](https://aws.amazon.com/compliance/shared-responsibility-model/?trk=public_post_comment-text)
7. [media.defense.gov: CSI CloudTop10 Shared Responsibility Model.PDF](https://media.defense.gov/2024/Mar/07/2003407863/0/0/0/CSI-CloudTop10-Shared-Responsibility-Model.PDF)
8. [Cloud security guidance | Using cloud services securely | Using a cloud platform securely | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-a-cloud-platform-securely)
9. [Cloud security guidance | The cloud security principles | Principle 10: Identity and authentication | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-10-identity-and-authentication)
10. [Cloud security guidance | The cloud security principles | Principle 7: Secure development | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-7-secure-development)
11. [cisa.gov: Aa23 319a stopransomware rhysida ransomware 2](https://www.cisa.gov/sites/default/files/2025-04/aa23-319a-stopransomware-rhysida-ransomware_2.pdf)
12. [Cloud security guidance | Choosing a cloud provider | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/choosing-a-cloud-provider)
13. [nsa.gov: Nsa releases top ten cloud security mitigation strategies](https://www.nsa.gov/Press-Room/Press-Releases-Statements/Press-Release-View/Article/3699169/nsa-releases-top-ten-cloud-security-mitigation-strategies/)
14. [Cloud security guidance | The cloud security principles | Principle 9: Secure user management | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-9-secure-user-management)
15. [Cloud security guidance | The cloud security principles | Principle 1: Data in transit protection | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-1-data-in-transit-protection)
16. [Cloud security guidance | Understanding cloud services | Choosing and configuring a KMS for secure key management in the cloud | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/understanding-cloud-services/choosing-and-configuring-a-kms-for-secure-key-management-in-the-cloud)
17. [Cloud security guidance | The cloud security principles | Principle 5: Operational security | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-5-operational-security)
18. [Cloud security guidance | The cloud security principles | Principle 13: Audit information and alerting for customers | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-13-audit-information-and-alerting-for-customers)
19. [Cloud security guidance | The cloud security principles | Principle 2: Asset protection and resilience | National Cyber Security Centre](https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-2-asset-protection-and-resilience)
20. [Cloud Security Posture Management: silver bullet or another piece in the cloud puzzle? | National Cyber Security Centre](https://www.ncsc.gov.uk/blog-post/cspm-silver-bullet-or-another-piece-in-the-cloud-puzzle)
21. [ignet.gov: CIGIE OIG%20Best%20Practices%20for%20Cloud%20Computing](https://www.ignet.gov/sites/default/files/files/CIGIE-OIG%20Best%20Practices%20for%20Cloud%20Computing.pdf)
