All articles

    Cloud security

    The Cloud Misconfigurations Behind Most Breaches

    Written by Khalid NamraPublished: 25 June 2026Updated: 16 September 20267 min read
    The Cloud Misconfigurations Behind Most Breaches

    In three lines

    • Cloud providers secure the platform.
    • Wildcard permissions granted "temporarily" during a migration are the single most common finding.
    • Public object storage remains a steady source of data loss, usually because a bucket was opened for a legitimate reason and never closed.

    Cloud providers secure the platform. Everything above it — identity, network policy, storage permissions, key handling — is yours. Almost every cloud breach investigated in practice traces back to a small set of avoidable configuration decisions.

    Over-permissive identity

    Wildcard permissions granted "temporarily" during a migration are the single most common finding. Roles accumulate privileges and never lose them, service accounts hold administrative rights for a task they performed once, and human users keep standing access to production.

    • Review effective permissions, not attached policies
    • Use just-in-time elevation for production access
    • Alert on any new role with wildcard actions

    Storage and network exposure

    Public object storage remains a steady source of data loss, usually because a bucket was opened for a legitimate reason and never closed. The same applies to management ports, database endpoints and internal dashboards reachable from the internet because a security group was widened during troubleshooting.

    Keys, secrets and logging

    Long-lived access keys in code, CI variables or laptops are the currency of cloud intrusions. Replace them with short-lived federated credentials wherever the platform supports it, and scan repositories continuously rather than at review time.

    Finally, control-plane logging must be enabled in every region and account and shipped somewhere the account owner cannot delete. Without it, an investigation cannot establish what an attacker did.

    The practical takeaway

    Audit effective permissions, close what was opened temporarily, replace static keys with short-lived credentials, and log the control plane somewhere immutable.

    Related RASED services

    Official references

    Written by Khalid Namra

    Founder & CEO, RASED Solutions — engineering lead of RASED Solutions

    Khalid Namra building software since 2015 and leads the engineering and security teams behind RASED Solutions in Riyadh.