This article updates a 2012 Concise Courses webcast on cloud security. The cloud has changed enormously since then, but the fundamentals discussed at the time matter more than ever.
Cloud computing lets organizations rent computing power, storage and software instead of running their own data centers. It brings speed and flexibility, but it also changes how security works. The perimeter is no longer a firewall around a building; it is every identity, configuration and API in an account that can be reached from anywhere.
1. The Shared Responsibility Model
Every cloud provider divides security duties with its customers. The split depends on the service:
| Service model | Provider secures | Customer secures |
|---|---|---|
| Infrastructure as a Service (IaaS) | Physical data centers, hardware, hypervisor | Operating systems, applications, data, identities, network configuration |
| Platform as a Service (PaaS) | Infrastructure plus the runtime platform | Applications, data, identities, configuration |
| Software as a Service (SaaS) | Almost everything technical | Data, user access and configuration settings |
Whatever the model, the customer is always responsible for who has access and how data is handled. Most cloud breaches happen on the customer’s side of the line.
2. Identity Is the New Perimeter
- Require multi-factor authentication for every user, especially administrators.
- Apply least privilege: grant only the permissions each person or service needs.
- Replace long-lived access keys with short-lived credentials and roles.
- Use single sign-on so access can be revoked in one place when people leave.
3. Protecting Data
- Classify data so you know what is sensitive and where it lives.
- Encrypt data at rest and in transit, and manage keys carefully.
- Block public access to storage by default, and review any exceptions.
- Back up critical data to a separate account or provider.
4. Configuration Management
Misconfiguration, such as a storage bucket left open or a security group allowing access from anywhere, is the most common cause of cloud incidents. Defining infrastructure as code, reviewing changes before they are deployed and scanning continuously with cloud security posture management tools keep configurations under control.
5. Visibility and Monitoring
- Turn on audit logging for every account and region.
- Send logs to a central place that attackers cannot easily tamper with.
- Alert on high-risk events, such as new administrator accounts or disabled logging.
6. Incident Response in the Cloud
Cloud incidents move quickly. Prepare playbooks for compromised credentials and exposed data, make sure responders have the access they need in advance and practice with tabletop exercises.
For an overview of the topic, return to our cloud security hub, or read about zero trust and BYOD.
Frequently Asked Questions
What is the most important first step in cloud security?
Enforce multi-factor authentication for every account, especially administrators. Compromised identities are behind a large share of cloud incidents.
What is least privilege?
Granting each user or service only the permissions it needs.
The Cloud’s Home Turf
Washington State is home to the two largest cloud providers, and the Seattle area has become a center of cloud security talent, with meetups and conferences where new cloud attack techniques and defenses are often first discussed. Browse security events in Washington State.