Ravindra BagaleCourses & study guides मराठी Track your progress

17. Why Learn All This Before Kali Linux?

17.6 From S3, RDS and IAM to Cloud Misconfigurations

By Last updated:

Cloud madhe bahutek breaches "hacking" ne nahi tar chukichya settings ne hotat. Part 7 madhe tumhi pratyek setting swatah kela – tyamule chuk kuthe hote te tumhala mahit aahe.

You learnt (Part 7 and 8) Misconfiguration attackers look for Correct setting
Block Public Access, bucket policy Public or listable buckets, Principal: "*" with write access BPA ON, no public Allow
Presigned URLs Very long expiry, URLs in logs Short expiry, HTTPS
IAM role vs access keys Access keys in code, GitHub or ~/.aws/credentials Roles, least privilege, no long-term keys
IMDSv2 SSRF to 169.254.169.254 stealing role credentials IMDSv2 required, hop limit 1
RDS public access, db-sg Database reachable on 3306 from the internet Private RDS, SG-to-SG rule
RDS snapshots Public snapshots Private, encrypted snapshots
Security groups 0.0.0.0/0 on 22 or 3306 Specific sources only

Why this matters for security

In the cloud security chapter you will use AWS tools (IAM Access Analyzer, AWS Config, GuardDuty, CloudTrail) that detect exactly these misconfigurations. Each alert will make sense instantly, because you created the resource by hand and know what "public", "role" and "security group" really mean.

Ravindra Bagale's Tip

Students think hacking the cloud needs some big exploit. Most of the time, one wrong checkbox or one access key that ended up on GitHub is enough. That's why you should read the checklists in Chapters 14 and 15 again and again – cloud security is a matter of discipline.

Practice task

For your AWS account, list every S3 bucket and check its Block Public Access status, list every security group rule that allows 0.0.0.0/0, and search your laptop and projects for files named credentials or containing AKIA.

Extended teaching notes

Why this lesson matters

Cloud security is mostly IAM, network exposure, logging and secure defaults. The shared responsibility model means the provider patches the metal; you patch what you configure.

  • No public databases or public admin panels.
  • Roles / OIDC instead of long-lived access keys.
  • CloudTrail / Activity Logs / Audit Logs on and retained.
  • S3/Blob/GCS: Block Public Access; encrypt; least privilege.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.