Q: Explain the difference between Phishing and Spear Phishing.
Phishing is a broad, untargeted attack where malicious actors send mass emails (e.g., "Your PayPal account is locked") to millions of random people simultaneously.
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: Social engineering attack vectors and targeted threat actors.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
Phishing is a broad, untargeted attack where malicious actors send mass emails (e.g., "Your PayPal account is locked") to millions of random people simultaneously. The goal is sheer volume, hoping a small fraction of recipients will mistakenly click the malicious link and enter their credentials. Spear Phishing is a highly targeted attack directed at a specific individual or organization. Attackers conduct deep reconnaissance (LinkedIn, social media) to craft a highly convincing, personalized message (e.g., an email appearing to come from the CEO to the CFO requesting an urgent wire transfer to a specific vendor). It is much harder to detect and is often the entry point for major corporate breaches.
- Immediate Triage: Phishing is a broad, untargeted attack where malicious actors send mass emails (e.g., "Your Pay
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
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 Explain difference 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 Explain difference 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 Explain difference
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 Explain difference Static long-lived API tokens shared across internal services represent the highest-probability vector for supply-chain credential compromise.