Unassessed images pose a security risk because theyexist in connected image registries but have not been evaluated for vulnerabilities. Even if they are not currently running, these images can be deployed at any time, potentially introducing critical vulnerabilities, secrets, or malware into production environments.
Falcon Cloud Security emphasizes proactive image assessment to ensure risks are identifiedbefore deployment. Unassessed images represent blind spots where vulnerabilities may go unnoticed until runtime, increasing exposure and response time.
Options describing actively running containers are incorrect because running workloads are typically assessed through runtime sensors. The primary concern with unassessed images is theirunknown risk posture prior to use.
Therefore, the correct answer isThey are in one of your connected image registries but have not been checked for vulnerabilities.

Option A: Developers accessing repositories during normal hours is expected behavior, unless there are signs of unauthorized activity.
Option B: Privilege escalation and modification of security policies by a non-administrative user is a strong indicator of risk. This could suggest account compromise, insider threats, or policy violations, requiring immediate investigation.
Option C: Temporary access requests for databases that follow approval workflows do not indicate unauthorized activity or risk.
Option D: A new geographic login might warrant further monitoring, but without additional suspicious actions, it is not a definitive security risk.

Option A: The Falcon Container Sensor uses a privileged DaemonSet to gain access to host-level resources, allowing it to monitor containerized workloads effectively.
Option B: The sensor is compatible with various Linux-based operating systems, not just CoreOS.
Limiting the deployment to CoreOS is unnecessary and incorrect.
Option C: Disabling RBAC is not required and is strongly discouraged as it would reduce the security of the Kubernetes cluster. The Falcon Container Sensor can operate within an RBAC- enabled environment.
Option D: The Falcon Container Sensor monitors all containers across the cluster, not just those in a specific namespace. It operates at the cluster level to provide comprehensive security.

Option A: Using the CrowdStrike API to trigger one-time scans can supplement assessments but is not a replacement for an automated schedule. Without regular scans, potential vulnerabilities may go unnoticed, reducing overall security efficacy.
Option B: Manually initiating security posture assessments each time is inefficient and prone to human error. CSPM tools like CrowdStrike support automated scheduling to ensure consistent monitoring and compliance without manual intervention.
Option C: While enabling default cloud provider security tools is a good practice, these tools are separate from CrowdStrike's CSPM capabilities. Assuming synchronization without explicitly setting up a schedule in CrowdStrike will leave the assessments incomplete.
Option D: Defining a schedule in the CrowdStrike console is the correct approach. The console provides options to set frequency (e.g., daily, weekly) and scope (e.g., specific cloud accounts or all accounts), ensuring continuous posture monitoring. This setup is foundational for proactive security management.