Your organization's Google Security Operations (SecOps) tenant is ingesting a vendor's firewall logs in its...

Comprehensive and Detailed 150 to 250 words of Explanation From Exact Extract Google Security Operations Engineer documents:

The correct, low-impact solution for augmenting a Google-managed parser is to use a parser extension. The problem states that the base parser is still working, but needs to be supplemented to map two new fields.

Copying the entire parser (Option A) is a high-impact, high-maintenance solution ("Customer Specific Parser"). This action makes the organization responsible for all future updates and breaks the link to Google's managed updates, which is not a minimal-impact solution.

The intended, modern solution is the parser extension. This feature allows an engineer to write a small, targeted snippet of Code-Based Normalization (CBN) code that executes after the Google-managed base parser. This extension code can access the raw_log and perform the specific logic needed to extract the two unmapped fields and assign them to their proper Universal Data Model (UDM) fields.

This approach is the fastest to deploy and minimizes change management impact because the core parser remains managed and updated by Google, while the extension simply adds the custom logic on top. Option B, "Extract Additional Fields," is a UI-driven feature, but the underlying mechanism that saves and deploys this logic is the parser extension. Option D is the more precise description of the technical solution.

(Reference: Google Cloud documentation, "Manage parsers"; "Parser extensions"; "Code-Based Normalization (CBN) syntax")