Q: During a pentest, the testers found they could exploit a vulnerability in your Node.js app to read `/etc/passwd`. What OS-level container configuration should standardly prevent this kind of filesystem roaming?
A fundamental tenant of container hardening is running the container with a Read-Only Root Filesystem.
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: "When an interviewer asks how I respond to this security vulnerability, I emphasize immediate blast-radius containment. The interviewer is testing: Read-only root filesystems, container hardening.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
A fundamental tenant of container hardening is running the container with a Read-Only Root Filesystem. In Kubernetes, this is achieved by setting readOnlyRootFilesystem: true in the pod's securityContext. In Docker, it's the --read-only flag. When enabled, the application cannot overwrite binaries, modify /etc/passwd, or drop malicious payloads onto the disk during an exploit. Any directory the app legitimately needs to write to (like /tmp for caching) must be explicitly mounted as an ephemeral emptyDir or tmpfs volume, leaving the rest of the OS immutable and highly frustrating for attackers.
- Immediate Triage: A fundamental tenant of container hardening is running the container with a Read-Only Root File
- 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 pentest testers 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 pentest testers 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 pentest testers
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 pentest testers Static long-lived API tokens shared across internal services represent the highest-probability vector for supply-chain credential compromise.