Talk this topic through with an AI

You get an answer from the documentation and the page it comes from.

Console & fleet

Send events to Google Security Operations (Google SecOps, SIEM)

PoisonZero sends its events to Google SecOps as UDM events. Setup takes about 5 minutes. You need no parser and no forwarder.

~4 min read · Console & fleet

What you need

  • An Enterprise plan.
  • A Google SecOps instance and the Google Cloud project it belongs to.
  • A Google Cloud account that may create roles and grant access in that project, and the gcloud command line (Cloud Shell works too).
  • No parser and no forwarder.

Step 1: Enter the instance in the console

  1. Open Settings > Devices & Model and find the section Google SecOps. Turn on Enable export. As Method choose Chronicle API.
  2. Enter Project ID, Region and Instance ID. The region is the SecOps region ID, for example eu or europe-west3.
  3. Click Save. At the first save PoisonZero creates a service account for your tenant. Its e-mail address then appears under Service account.

Step 2: Grant access

Copy the e-mail under Service account and run the two commands. Replace PROJECT_ID and SA_EMAIL. The role only allows chronicle.events.import.

bashgcloud
gcloud iam roles create poisonzeroSecopsImport --project=PROJECT_ID --title="PoisonZero SecOps import" --permissions=chronicle.events.import
gcloud projects add-iam-policy-binding PROJECT_ID --member=serviceAccount:SA_EMAIL --role=projects/PROJECT_ID/roles/poisonzeroSecopsImport

No key and no secret changes hands. Remove the binding to withdraw the access at any time.

Step 3: Send a test event

Click Send test event. The console shows whether Google SecOps accepted the event.

Step 4: Check that events arrive

In Google SecOps, open the UDM search and run this search. It shows all PoisonZero events:

textUDM search
metadata.vendor_name = "PoisonZero"

The console shows the status under Last export: time, HTTP status, error and number of events. Events appear in SecOps within minutes.

What is sent

Every hit from exec0, poison0, leak0 and inject0 is sent as a UDM event with the vendor PoisonZero and the action BLOCK, QUARANTINE or ALLOW. Command text and file contents never leave PoisonZero. The details are in the sections below.

All events
PoisonZero eventevent_typeactioncategorySeverity
exec0 blocks a tool call
toolgate_denied, toolgate_rule_override_denied
Depends on the tool, see belowBLOCKPOLICY_VIOLATIONFrom the threat level
You deny a tool call that exec0 asked about
toolgate_asked_denied
Depends on the tool, see belowCHALLENGE and BLOCKPOLICY_VIOLATIONFrom the threat level
You allow a tool call that exec0 asked about
toolgate_asked_allowed
Depends on the tool, see belowCHALLENGE and ALLOWPOLICY_VIOLATIONFrom the threat level
A rule override lets a blocked call through
toolgate_rule_overridden
Depends on the tool, see belowALLOWPOLICY_VIOLATIONHIGH
exec0 observed or did not check a tool call
toolgate_observed, toolgate_unchecked
Depends on the tool, see belowALLOWPOLICY_VIOLATIONFrom the threat level
poison0 quarantines or holds a change
quarantine_reversible, hold_awaiting_review
SCAN_FILEQUARANTINESOFTWARE_SUSPICIOUSFrom the threat level
poison0 keeps a change
detected_kept, hold_kept_review, observed_would_hold, observed_would_quarantine
SCAN_FILEALLOW (hold_kept_review: CHALLENGE and ALLOW)SOFTWARE_SUSPICIOUSFrom the threat level
poison0 reverts a change
revert, meta_attack
SCAN_FILEBLOCKSOFTWARE_SUSPICIOUSFrom the threat level
leak0 blocks a leak
leak0_blocked
GENERIC_EVENTBLOCKDATA_EXFILTRATIONFrom the threat level
leak0 removes the secret from the output
leak0_redacted
GENERIC_EVENTALLOW_WITH_MODIFICATIONDATA_EXFILTRATIONFrom the threat level
leak0 warns or observes
leak0_warned, leak0_observed
GENERIC_EVENTALLOWDATA_EXFILTRATIONFrom the threat level
leak0 asks
leak0_asked
GENERIC_EVENTCHALLENGEDATA_EXFILTRATIONFrom the threat level
inject0 withholds fetched content
inject0_withheld
GENERIC_EVENTBLOCKSOCIAL_ENGINEERINGFrom the threat level
inject0 marks fetched content
inject0_marked
GENERIC_EVENTALLOW_WITH_MODIFICATIONSOCIAL_ENGINEERINGFrom the threat level
inject0 observes
inject0_observed
GENERIC_EVENTALLOWSOCIAL_ENGINEERINGFrom the threat level

Bash, Shell and PowerShell are PROCESS_LAUNCH, all other tools GENERIC_EVENT. The severity follows the threat level. Use metadata.product_event_type and security_result.action in rules.

Fields and mapping

PoisonZero maps its audit events to UDM. Command text, file content and prompt text are not part of any event, they never leave PoisonZero. Sent are the tool name, the agent, the decision, the reason, the threat level, the name of the device and, for poison0, the path of the file.

Fields you can search and filter on:

  • metadata.vendor_name and metadata.product_name: always PoisonZero.
  • metadata.product_event_type: the PoisonZero action from the first column.
  • principal.hostname: the name of the device.
  • security_result.action, security_result.severity and security_result.category.
  • security_result.rule_name: the reason, for example the rule that fired.
YARA-L sample rules

Paste each rule into the rules editor of Google SecOps. Run it as a test over the last few days first, then enable it.

exec0 blocked a tool call

yara-lYARA-L
rule poisonzero_exec0_block {
  meta:
    author = "PoisonZero"
    description = "exec0 blocked a tool call of an AI agent"
    severity = "HIGH"

  events:
    $e.metadata.vendor_name = "PoisonZero"
    $e.metadata.product_event_type = /^toolgate_(asked_|rule_override_)?denied$/
    $e.security_result.action = "BLOCK"

  condition:
    $e
}

poison0 quarantined or held a change

yara-lYARA-L
rule poisonzero_poison0_quarantine {
  meta:
    author = "PoisonZero"
    description = "poison0 quarantined or held a dangerous change to an agent file"
    severity = "HIGH"

  events:
    $e.metadata.vendor_name = "PoisonZero"
    $e.metadata.product_event_type = /^(quarantine_reversible|hold_awaiting_review)$/
    $e.security_result.action = "QUARANTINE"

  condition:
    $e
}

leak0 stopped an exfiltration

yara-lYARA-L
rule poisonzero_leak0_exfiltration {
  meta:
    author = "PoisonZero"
    description = "leak0 stopped a secret from leaving a device"
    severity = "HIGH"

  events:
    $e.metadata.vendor_name = "PoisonZero"
    $e.metadata.product_event_type = "leak0_blocked"
    $e.security_result.category = "DATA_EXFILTRATION"
    $e.security_result.action = "BLOCK"

  condition:
    $e
}
Alternative: webhook feed (OCSF)

If Domain Restricted Sharing blocks the access grant in step 2, PoisonZero sends the events in OCSF format to a webhook feed.

  1. In SecOps, create a feed under Settings > Feeds: source type Webhook, log type OCSF. Copy the endpoint URL and the secret key.
  2. In the Google Cloud console, create an API key restricted to the Chronicle API.
  3. In the PoisonZero console, set the method to Webhook feed (OCSF), enter URL, API key and secret, and send a test event.

Field values can differ from the UDM path.

Troubleshooting
What you seeWhat to do
HTTP 403 and Permission 'chronicle.events.import' deniedThe role is missing or belongs to another account. Run the commands from step 2 again. PoisonZero retries after 5 minutes on its own, nothing is lost.
service account still propagatingThe new service account is not available everywhere yet. Wait a minute and click Send test event again.
HTTP 404 or a message about an unknown instanceProject ID, region and instance ID do not belong together. Copy the three values from your SecOps instance, without spaces.
SecOps not yet provisionedThe export is not set up for your environment yet. Contact PoisonZero support.
Step 2 is rejected because the Domain Restricted Sharing policy blocks the access grantUse the webhook feed (OCSF) from the Alternative section.
The webhook feed reports HTTP 401 or HTTP 403Check the API key and the secret. Create a lost secret again with Generate Secret Key.
The test works, but nothing shows up in SecOpsEvents appear within minutes. Last export shows the status and the error.

SIEM export (local files, private devices, setup without the console). CrowdStrike Falcon Next-Gen SIEM. OpenTelemetry export. Incidents and audit.