CuraSec

tag: Cloud-Provider · 3 items

2026-10-31 · HN (security) · source ↗ #cloud-provider#vendor-breach#akamai
  • Engineer — Plan: If workloads run on Linode (now Akamai Cloud), review the incident disclosure at the status page to determine whether credentials, SSH keys, or customer data were exposed and rotate accordingly.
  • SOC/IR — Skip
  • Leader — Plan: Confirm whether Linode/Akamai Cloud appears in the vendor inventory; if so, request a formal incident scope statement and assess whether any customer or regulated data was co-hosted there.
2026-10-10 · BleepingComputer · source ↗ #ransomware#cloud-provider#vendor-risk
  • Engineer — Skip
  • SOC/IR — Skip
  • Leader — Learn: A ransomware attack taking down a national cloud provider serving government clients is a concrete reminder that third-party cloud availability risk belongs on the vendor risk register; useful context for business continuity discussions with leadership, though the specific provider is Japan-regional with no disclosed IOCs or attacker attribution.
2026-08-20 · BleepingComputer · source ↗ #data-breach#cloud-provider#vendor-risk
  • Engineer — Skip
  • SOC/IR — Skip
  • Leader — Act: If your organization uses Sakura Internet for cloud or data center services, confirm whether your account data was affected and request an incident report from the vendor this week.