Q: A developer accidentally pushed an AWS Access Key and Secret Key to a public GitHub repository. What steps do you take?
This is a critical security incident. The immediate priority is Containment:
Master cloud-native security and container runtime defense: Prepare with KodeKloud's CKS course with live browser-based terminal sandboxes.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Security in modern DevOps must be automated into the pipeline rather than bolted on after deployment. The interviewer is testing: Incident response workflow for leaked credentials, containment vs. investigation.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
This is a critical security incident. The immediate priority is Containment:
- Go directly to AWS IAM and Deactivate (do not immediately delete) the leaked access key. Deactivating stops any further use while preserving it for forensics.
- Check AWS CloudTrail immediately for any actions performed by that specific access key since the time of the leak. Look for EC2 instance spawning (crypto-mining), IAM privilege escalation, or data exfiltration.
- Review the code repository and rewrite the Git history to remove the credentials permanently, then force push the clean history.
Remediation & Permanent Safeguards
- If the key was used maliciously, initiate your organization's Incident Response Plan (e.g., isolating compromised instances, rotating related secrets).
- Architectural Prevention: To permanently eliminate static AWS keys in CI/CD pipelines, configure GitHub Actions to authenticate via AWS IAM OIDC roles. See Security Q37: GitHub Actions Deployment to AWS Without Long-Lived Keys (OIDC).
- Go directly to AWS IAM and Deactivate (do not immediately delete) the leaked access key. Deactiva...
- Check AWS CloudTrail immediately for any actions performed by that specific access key since the ...
- Review the code repository and rewrite the Git history to remove the credentials permanently, the...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Revoking compromised credentials immediately without analyzing forensic audit trails for active exploitation when configuring Security developer accidentally Deactivating a compromised access key prevents abuse while preserving forensic identity for CloudTrail investigations to assess blast radius.
- Terminating compromised instances immediately during incident triage without isolating volatile RAM state when configuring Security developer accidentally Terminating compromised instances immediately destroys volatile memory evidence (RAM dumps) required to establish intrusion timelines.
-
Injecting plaintext secrets into container environment variables rather than fetching from dynamic secret vaults when configuring Security developer accidentally
Container environment variables are visible via
docker inspector Kubernetes API queries, leaking sensitive API tokens to developers. - Failing to enforce automated credential rotation for third-party SaaS integration tokens when configuring Security developer accidentally Static long-lived API tokens shared across internal services represent the highest-probability vector for supply-chain credential compromise.