Cloud security is protecting systems and data that run on rented infrastructure. The provider secures the underlying hardware and services; you secure what you configure and store. Most cloud breaches are not exotic: they are exposed storage, over-broad permissions and leaked keys, which makes careful configuration the heart of the field.
Key concepts
- Shared responsibility: know exactly which controls the provider handles and which are yours.
- Identity first: roles, policies and short-lived credentials are the new perimeter.
- Least privilege and separation: separate accounts or projects for environments, and permissions narrowed to what each workload needs.
- Configuration as code: define infrastructure in versioned files, review it and scan it for misconfigurations.
- Logging and detection: audit logs of every API call, kept safely and watched.
Vocabulary
- IAM: identity and access management.
- Misconfiguration: a setting, such as a public storage bucket, that exposes more than intended.
- KMS: a managed service for creating and using encryption keys.
- CSPM: tooling that continuously checks cloud settings against good practice.
What to study, in order
- Core cloud services: compute, storage, networking and identity, in a small account you pay for and control.
- Write an access policy by hand, then narrow it until it allows only what a task needs.
- Define a small environment as code and run a configuration scanner over it.
- Turn on audit logging and find your own actions in it.
- Handle secrets properly: a secrets manager, rotation and no keys in source control.