Cyber trends 2026

Cloud Misconfiguration and Leaked Secrets: The Quiet Cause of Big Breaches

Many cloud breaches do not involve any clever hacking. A storage bucket is public, a key sits in a GitHub repository, or a role can do far more than it should. In 2026, AI tools started finding these mistakes faster than ever.

cloud securitysecretsIAMmisconfiguration

Updated November 2026

Why misconfiguration is so common

Cloud platforms make it very easy to create resources. A developer can spin up a database, storage bucket or API in minutes. But secure defaults, access policies and cleanup often get skipped under deadline pressure. Under the shared responsibility model, the cloud provider secures the infrastructure, but the customer is responsible for these settings. Our cloud security basics post explains that model.

What CERT-In found in 2026

CERT-In's advisory CIAD-2026-0049, issued on 15 October 2026 with Critical severity, covers incidents where AI agents accessed Indian organisations' systems. It says that across these incidents, the root weaknesses were conventional, including:

  • Credentials and keys exposed in source code, public repository history, configuration files, client applications and public web content.
  • Dormant, deprecated and test APIs reachable from the internet.
  • Payment API keys stored in plaintext.
  • Over permissive cloud and backend as a service roles that allowed broad reads and writes by ordinary or anonymous callers.
  • Exposed management interfaces with weak credentials or no MFA.

The advisory also says the affected organisations could not detect the unauthorised access on their own. That is the scary part: misconfigurations are silent.

Leaked secrets: the number one fix

A "secret" is anything that grants access: API keys, database passwords, cloud access keys, tokens. They leak through:

  • Code pushed to public repositories, including old commits where the key was "deleted" later.
  • Mobile apps and websites that ship keys in client side code.
  • Logs, screenshots, tickets and chat messages.
  • CI/CD pipeline variables visible to too many people.

Fix: use a secret manager, keep secrets out of code, turn on secret scanning in your repositories, and if a key leaks, rotate it immediately. Deleting the file is not enough, because history keeps it.

Over permissive access

"Just give it admin for now, we will fix it later." Later rarely comes. CERT-In recommends least privilege in cloud and backend as a service deployments, row level security, least privileged client roles, never placing privileged or service keys in client side code, and allowing writes only to authenticated, authorised roles. A simple test it suggests: check what an anonymous caller can read and write. You may be surprised.

Verizon's 2026 DBIR also noted third party involvement in 48% of breaches, which makes vendor and integration access another area to review.

A practical cloud hygiene checklist

  1. Turn on MFA for all admin and console users.
  2. Inventory all storage buckets and confirm none are public unless intended.
  3. Enable secret scanning on all repositories and scan history once.
  4. Rotate any key older than your policy allows, and any key that was ever exposed.
  5. Inventory APIs. Remove old, test and unused ones.
  6. Move admin panels behind VPN or zero trust access, off the open internet.
  7. Review roles quarterly. Remove unused permissions.
  8. Enable audit logging and keep logs for at least 180 days, which CERT-In also recommends in this advisory.
  9. Set alerts for risky changes, such as public access or new admin users.

For startups and small teams

Small teams often move fastest and skip these steps. Start with three: MFA everywhere, no secrets in code, and a monthly check of what is public. CERT-In's 15 Elemental Cyber Defense Controls for MSMEs is a free baseline you can adapt.

For learners

Cloud security posture is a high demand skill. In a free tier account, create a deliberately public bucket, find it with the provider's own tools, fix it, and document the process. Then turn on secret scanning in your GitHub. These two small projects teach you more than many long videos, and they look great in a portfolio.

Frequently asked questions

I accidentally pushed a key to GitHub and deleted it. Am I safe? No. Treat the key as compromised. Rotate or revoke it immediately with the provider, check logs for misuse, and clean the repository history.

Are private repositories safe for secrets? Safer than public, but still not a good place. Private repositories can be shared, cloned or leaked. Use a secret manager.

Educational content, not legal advice. Check official sources before you rely on it. If you have lost money, call 1930 now. Terms