Skip to the content ForoHackers
Log inJoin

Cloud security: start here

Cloud security
#3313 · · Quote · Report

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

  1. Core cloud services: compute, storage, networking and identity, in a small account you pay for and control.
  2. Write an access policy by hand, then narrow it until it allows only what a task needs.
  3. Define a small environment as code and run a configuration scanner over it.
  4. Turn on audit logging and find your own actions in it.
  5. Handle secrets properly: a secrets manager, rotation and no keys in source control.

Related tags

#cloud #identity #containers #devops #supply-chain-security

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply