SecurCheckCyber Center
Need help
Back to analysis tools
All cyber threats
Infrastructure

Cloud account takeover

Cloud account takeover, cloud identity compromise

An attacker takes over an AWS, Microsoft Azure, Google Cloud or SaaS account and abuses its access to data, identities and cloud resources.

Fiche de sensibilisationPrête à diffuser à vos équipes ou clients

MIGHT YOU BE AFFECTED?

Turn knowledge into action.

How does this work?

A phished password, stolen session token, compromised API credential or weak multi-factor authentication may let an attacker operate as a legitimate cloud user. The impact depends on the account's permissions: privileged identities can create persistent access keys, alter policies, copy data or provision costly workloads.

REAL-WORLD EXAMPLE

« An administrator follows a convincing fake sign-in page. The attacker reuses the captured session, creates an access key and exports a storage snapshot to an account outside the organisation. »

Typical sequence

  1. 1The attacker obtains an account password, session token, API credential or recovery access.
  2. 2They sign in to the cloud or SaaS control plane, often from a new location or device.
  3. 3They enumerate permissions and establish persistence using new keys, roles, applications or sessions.
  4. 4They access, export or modify data and resources, or launch unauthorised workloads.

Warning signs

  • Unfamiliar successful sign-ins, impossible travel or unexplained MFA prompts.
  • New access keys, OAuth grants, privileged roles or administrator accounts.
  • Unexpected resource creation, billing changes, exports or large outbound transfers.
  • Cloud audit logs showing actions from unfamiliar devices, regions or applications.

How to protect yourself

  • Use phishing-resistant MFA such as FIDO2 security keys or passkeys for privileged cloud identities.
  • Enforce conditional access, minimal privileges and separate administrator accounts.
  • Restrict and rotate long-lived keys; prefer short-lived workload credentials.
  • Review cloud audit logs and alerts for new tokens, roles, sessions and resource changes.
  • Protect break-glass access and test incident response and recovery procedures.

If you think you are affected

Immediately contain the identity by suspending risky sessions and revoking exposed tokens and keys. Preserve cloud audit evidence, investigate all changes made since the first suspicious sign-in, remove persistent credentials and review possible data exposure. Restore access using trusted administrators and follow relevant incident-notification requirements.

Get help

Last updated: 8 October 2026