Comprehensive and Detailed Explanation
The correct solution is Option C. Google SecOps SOAR includes a specific, built-in feature to address this exact requirement. The SOAR platform needs to be context-aware to differentiate between internal and external IPs for accurate analysis, prioritization, and playbook execution.
This is achieved by configuring the Environment Networks list within the SOAR settings. Here, an administrator defines all of the organization's internal CIDR ranges (e.g., 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12, etc.).
When an alert is ingested from the SIEM (Chronicle) or any other source, the SOAR platform parses its entities. During this ingestion and enrichment process, it automatically cross-references every IP address entity against the configured "Environment Networks" list. If an IP address falls within any of the defined internal CIDR blocks, it is automatically flagged as "Internal." This classification is then visible to analysts in the case and can be used by playbooks to make logical decisions (e.g., initiate an endpoint scan for an internal IP vs. block an external IP at the firewall).
Option A is incorrect because it describes enriching data in the SIEM, not the SOAR ingestion process.
Option B is incorrect because it requires custom connector modification, which is a high-effort solution, whereas a standard, out-of-the-box setting (Option C) already exists.
Option D is incorrect because it describes a post-ingestion playbook action, not a flag set upon ingestion. It's also an unreliable method, as internal assets may not respond to ping due to host firewalls.
Exact Extract from Google Security Operations Documents:
Environment Networks: Google SecOps SOAR provides a configuration setting to define the organization's internal IP address space. This setting, typically found under Organization Settings > Environment Networks within the SOAR platform, allows administrators to list all internal CIDR ranges.
When alerts are ingested into SOAR, the platform automatically enriches entities. During this process, any IP address entity is checked against this defined list. If the IP address falls within one of the specified CIDR blocks, it is automatically marked with an Internal flag. This contextual awareness is critical for analysts to triage cases and for playbooks to execute the correct logic (e.g., different actions for an internal vs. external IP).
[References:, Google Cloud Documentation: Google Security Operations > Documentation > SOAR > SOAR Administration > Organization Settings, , ]
