Search for a command to run...
Series
Hands-on cloud security projects focused on real-world failures, design trade-offs, and failure-driven testing in AWS.
Why This Project Exists Most cloud security problems don’t start with advanced attacks.They start with a weak baseline. Before testing failures, alerts, and abuse scenarios, I wanted to answer a basic but critical question: What does a “secure enoug...
Why This Project Exists After building a clean security baseline in Project 1, everything looked reasonable. But real systems don’t stay clean. As soon as applications, teams, and delivery pressure enter the picture, trade-offs appear — often silentl...
📌 Why This Project Matters Security controls appear perfect on paper — until real-world traffic, misconfigurations, and human errors expose the gaps. In Project 3, I focused on implementing core cloud security controls and then actively testing them...
SSH-based access to cloud workloads remains common, but it introduces unnecessary attack surface: open inbound ports, long-lived credentials, key sprawl, and limited auditability. Modern AWS environments do not require SSH for interactive access to E...
Introduction SSH has been the default way to access Linux servers for decades. In cloud environments like AWS, however, SSH introduces unnecessary risk: static keys, open network ports, weak identity attribution, and poor auditability at scale. In th...
Time-bound access, automatic revocation, and full auditability Why This Project Exists Permanent SSH access to EC2 instances is one of the most common and dangerous cloud misconfigurations.Open port 22, long-lived keys, and forgotten security group r...