How Secure Is the Cloud?

Akins IT • June 23, 2016
Connect with us

We all remember The Fappening, the iCloud hack from 2014 where nude pictures of celebrities were leaked over the internet. While it has started serious conversations over privacy rights and other laws relating to the internet, it has also led some to question how secure the cloud really is.


The major benefits of cloud-based security include ease of deployment and maintenance, performance, and ability to scale. Perimeter protection for on-premise IT and the cloud are very similar. Often, however, security issues arise due to human error and employees who accidentally click on a link from an email with Cryptolocker or fail to keep their software updated. Moving data to the cloud reduces the likelihood of employees harming data in this way. 


Wieland Alge, VP and GM of EMEAR at Barracuda Networks stated, “Almost all of the massive data breaches we’ve seen as of late were within traditional on-premise IT. Sometimes we are too quick in stating that the cloud is an inherently insecure element.”


Albert Logic investigated cloud security and how it measures up to on-premise security. It completed a survey pulled from 2,200 customers and 232,364 verified security incidents in both cloud and on-premise systems and found that brute force attacks occurred as frequently in the cloud as in on-premise IT systems. On the other hand, 56% of on-premise systems had malware attacks, whereas only 11% of cloud systems were attacked. Likely, we'll begin to think differently about cloud security as more and more companies deploy public cloud systems. 

By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts