The correct item to select is Process ID. In Falcon investigations, a Process Timeline requires the sensor- specific process identifier, not merely the operating system PID. The OS PID can be reused over time and is not sufficiently unique for reliable historical telemetry correlation. The Falcon Process ID maps to the process record used by the platform to retrieve process-related events such as file writes, network connections, registry activity, DNS requests, and child process creation. Selecting the command line may provide useful context, but it does not pivot directly into the process timeline. Selecting PID is less precise because it refers to the local operating system process identifier. For accurate process-scoped investigation, the Process ID is the correct pivot point.

Domain name-based IOCs in Falcon are used for detection-oriented visibility, not endpoint prevention in the same way as file-hash indicators. File hashes can support blocking or allowing because the sensor can evaluate executable content directly. Domains are network indicators, so the practical actions available are limited to detection or no enforcement action. "Detect only" creates visibility when matching activity is observed, while "No action" allows the indicator to be stored or staged without triggering enforcement behavior. Options that include "Block" or "Allow" are incorrect because domain-based IOCs do not work like hash allowlists or prevention hashes in Falcon IOC Management.
This distinction is important for responders because choosing the wrong IOC type or expected action can lead to false assumptions about containment capability.