Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 38 ยท Getting Started

What Is Cloud Security?

Learn what cloud security is, why it differs from traditional IT security, which areas it covers, and how this course works, with a runnable inventory example.

Cloud security is the set of practices, tools and habits that keep data, applications and infrastructure safe when they run on rented computing services such as virtual machines, managed databases, object storage and serverless functions. The servers still exist, but somebody else owns the buildings and the hardware, and you control most things through an API and a web console instead of a screwdriver.

That shift changes who can do damage and how fast. A single wrong setting can expose a whole storage bucket to the internet in seconds, and a single leaked access key can let an attacker start hundreds of machines from the other side of the world. This course teaches you how to prevent those mistakes, notice them quickly, and respond well.

About the examples. We cannot connect to a real cloud account from a web page, and this course never asks you to attack anyone. Every runnable example is a small Python program that models a cloud idea (a policy, a log, a network rule) with made-up data. Command-line output from real providers is shown read-only and labelled as an example. Only ever test systems that you own or have written permission to test.

How cloud security differs from traditional security

In a classic data center you secure a perimeter: a firewall at the edge, a locked server room and a network you control end to end. In the cloud there are three big differences.

  • Everything is software-defined. Networks, firewalls, disks and permissions are created by API calls. That makes them easy to automate and easy to get wrong at scale.
  • The perimeter is blurry. Storage, databases and admin consoles are reachable over the internet by design. Identity (who is calling) becomes the new perimeter.
  • Responsibility is shared. The provider secures the facilities and the virtualization layer, you secure what you put on top. We study this in detail in the shared responsibility model.

The main areas of cloud security

Cloud security is usually split into a handful of domains. Each has its own chapter later in the course.

Six areas to know

Identity and access Who may do what
Network What can talk to what
Data Encrypt, classify, back up
Workloads VMs, containers, functions

Each area has its own chapter in this course.

1 / 2
  1. Identity and access management (IAM). Users, roles, keys and permissions. The most common root cause of cloud breaches.
  2. Network security. Virtual networks, subnets, security groups, firewalls and private connectivity.
  3. Data protection. Encryption, key management, classification, backups.
  4. Workload security. Hardening virtual machines, containers and serverless functions.
  5. Monitoring and detection. Collecting logs, finding suspicious behavior, responding.
  6. Governance and compliance. Policies, standards and proof that you follow them.
  7. DevSecOps. Building security checks into code, builds and infrastructure definitions.

What attackers actually go after

Most real cloud incidents are not exotic. They come from a short list of ordinary problems:

  • Storage or databases left open to the public internet.
  • Access keys committed to source code or pasted into chat.
  • Accounts without multi-factor authentication, or with far too many permissions.
  • Unpatched or default-configured workloads reachable from outside.
  • Missing logs, so nobody notices for weeks.

You can see the pattern: they are almost all configuration and identity mistakes, not clever hacking of the provider. That is good news, because configuration can be checked automatically.

A first runnable example: an inventory check

Security starts with knowing what you have. The program below models a tiny cloud inventory as a list of dictionaries and flags resources that break three simple rules. Real tools do the same thing with thousands of resources fetched from the provider's API.

Python Find risky resources in a toy inventory

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Change public for bucket-promo to False and run again. One finding disappears, but the missing encryption remains. Real cloud security is usually many small checks like these.

The cloud security mindset

Four ideas will carry you through the rest of the course.

  1. Assume breach. Design so that one stolen credential or one compromised server does not give an attacker everything.
  2. Least privilege. Give every person and program only the permissions it needs, for only as long as it needs them.
  3. Defense in depth. Layer controls (identity, network, encryption, monitoring) so one failure is not fatal.
  4. Automate and verify. If a rule matters, a program should check it continuously.
flowchart LR
    A["Prevent<br/>(secure defaults)"] --> B["Detect<br/>(logs, alerts)"]
    B --> C["Respond<br/>(contain, fix)"]
    C --> D["Improve<br/>(lessons learned)"]
    D --> A

Prevent, detect, respond, improve: the loop every cloud security team runs.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why is identity often called the new perimeter in the cloud?

    Cloud resources are managed and often accessed over the internet via APIs, so strong identity and permission control is what separates legitimate from illegitimate use.
  2. 2. Which of these is a typical cause of real cloud breaches?

    Most incidents come from ordinary mistakes such as public storage, exposed keys and excessive permissions.
  3. 3. What does least privilege mean?

    Limiting permissions limits the damage of any single stolen credential or mistake.
  4. 4. Which sentence best describes the examples in this course?

    Models run in your browser with made-up data, and testing real systems requires authorization.

Summary

  • Cloud security protects data, apps and infrastructure that run on rented, API-driven services.
  • Identity, network, data, workloads, monitoring, governance and DevSecOps are the main areas.
  • Most incidents come from misconfiguration and leaked or over-powerful credentials.
  • Prevent, detect, respond and improve: assume breach and apply least privilege and defense in depth.
  • Automated checks, like the inventory example, scale better than manual review.

Next: Cloud Service and Deployment Models