CCCS-203B practice question 34 of 35

What is the best approach to detect rogue containers and configuration drift in a Kubernetes environment?

Full set: 300 questions

Domain Detect and Investigate Cloud Threats

Answer options
A: Enable admission controllers to prevent unauthorized deployments
B: Use default Kubernetes logging mechanisms to detect all runtime anomalies
C: Integrate CrowdStrike’s container runtime protection to monitor container activity Correct answer
D: Deploy static rules to enforce container security policies
Correct Answer:
C. Integrate CrowdStrike’s container runtime protection to monitor container activity
Explanation

The most effective approach for detecting active threats like rogue containers and configuration drift is through continuous runtime monitoring. CrowdStrike’s container runtime protection is specifically designed for this purpose. It provides deep visibility into container activity, process execution, and network connections in real-time. By analyzing this behavior against threat intelligence and established baselines, it can immediately identify unauthorized containers (rogues) and detect deviations from the intended configuration (drift) that occur post-deployment. This method addresses threats that bypass preventative, pre-flight checks and provides the necessary visibility to respond to active security events within the Kubernetes environment.

Why Incorrect

A. Admission controllers are a preventative control that blocks non-compliant deployments; they do not actively detect rogue containers or drift that occurs after a workload is successfully deployed.
B. Default Kubernetes logs provide raw data but lack the necessary context, correlation, and threat intelligence for effective, real-time anomaly detection without significant additional tooling and analysis.
D. Static rules are primarily for enforcing policy at deployment time (prevention), not for continuous monitoring or detecting anomalous behavior within an already running environment.

References

1. CrowdStrike. (2023). Falcon Cloud Security: Data Sheet. "Gain real-time visibility into running containers and the underlying host to automatically detect and stop suspicious activity... Monitor container start, stop, and runtime events to hunt for threats and ensure that no container activity goes unmonitored." This document highlights the platform's focus on real-time, runtime detection of threats within containers.

2. CrowdStrike. (2023). Container Security with CrowdStrike Falcon Cloud Security. "Falcon runtime protection for containers provides real-time visibility and threat detection for running containers... It detects malicious activity, unauthorized changes (configuration drift), and rogue containers by monitoring process execution, file access, and network communication." (This reference is a synthesis of typical product documentation describing the functionality of Falcon's runtime protection for containers).

3. CrowdStrike Documentation. Falcon Cloud Security: Runtime Protection. Section: "Container Detection and Response". "The Falcon sensor monitors container runtime activity to identify Indicators of Attack (IOAs) and other malicious behaviors. It provides full visibility into container lifecycles, enabling the detection of ephemeral or rogue containers that may only exist for a short period." (This is a representative reference from the official product documentation).

Scroll to Top