This page describes the Sumo pipeline for ingesting logs from Google Cloud Platform (GCP) services, and provides instructions for configuring log collection for the Google Cloud Firewall App.
Enable logging for firewall rules
Enable firewall rule logging individually for each firewall rule whose connections you want to log, by including
--enable-logging in the rule definition. For example:
gcloud beta compute firewall-rules create rule-b \
--network example-net \
--action allow \
--direction ingress \
--rules tcp:80 \
--source-ranges 10.10.0.99/32 \
--priority 10 \
For more information, see Firewall Rules Logging Overview.
Collection process for GCP services
The key components in the collection process for GCP services are: Google Logs Export, Google Cloud Pub/Sub and Sumo’s Google Cloud Platform (GCP) source running on a hosted collector.
The integration works like this: The GCP service generates logs which are exported and published to a Google Pub/Sub topic via Stackdriver. You will then setup a Sumo Logic Google Cloud Platform source that subscribes to this topic and receives the exported log data.
Configuring collection for GCP uses the following process:
- Configure a GCP source on a hosted collector. You'll obtain the HTTP URL for the source, and then use Google Cloud Console to register the URL as a validated domain.
- Create a topic in Google Pub/Sub and subscribe the GCP source URL to that topic.
- Create an export of GCP logs from Google Stackdriver Logging. Exporting involves writing a filter that selects the log entries you want to export, and choosing a Pub/Sub as the destination. The filter and destination are held in an object called a sink.
See the following sections for configuration instructions.
Configure a Google Cloud Platform Source
The Google Cloud Platform (GCP) Source receives log data from Google Pub/Sub.
This Source will be a Google Pub/Sub-only Source, which means that it will only be usable for log data formatted as data coming from Google Pub/Sub.
- In Sumo Logic select Manage Data > Collection > Collection.
- Select an existing Hosted Collector upon which to add the Source. If you don't already have a Collector you'd like to use, create one, using the instructions on Configure a Hosted Collector.
- Click Add Source next to the Hosted Collector and click Google Cloud Platform.
- Enter a Name to display for the Source. Description is optional.
- (Optional) For Source Host and Source Category, enter any string to tag the output collected from the source. Category metadata is stored in a searchable field called _sourceCategory, for example, "gcp".
- Fields. Click the +Add Field link to add custom log metadata Fields, then define the fields you want to associate. Each field needs a name (key) and value. Look for one of the following icons and act accordingly:
- If an orange triangle with an exclamation point is shown, use the option to automatically add or enable the nonexistent fields before proceeding to the next step. The orange icon indicates that the field doesn't exist, or is disabled, in the Fields table schema. If a field is sent to Sumo that does not exist in the Fields schema or is disabled it is ignored, known as dropped.
- If a green circle with a checkmark is shown, the field exists and is already enabled in the Fields table schema. Proceed to the next step.
- Advanced Options for Logs.
- Enable Timestamp Parsing. This option is selected by default. If it's deselected, no timestamp information is parsed at all.
- Time Zone. There are two options for Time Zone. You can use the time zone present in your log files, and then choose an option in case time zone information is missing from a log message. Or, you can have Sumo Logic completely disregard any time zone information present in logs by forcing a time zone. It's very important to have the proper time zone set, no matter which option you choose. If the time zone of logs can't be determined, Sumo Logic assigns logs UTC; if the rest of your logs are from another time zone your search results will be affected.
- Timestamp Format. By default, Sumo Logic will automatically detect the timestamp format of your logs. However, you can manually specify a timestamp format for a Source. See Timestamps, Time Zones, Time Ranges, and Date Formats for more information.
- Processing Rules for Logs. Configure desired filters—such as include, exclude, hash, or mask—as described in Create a Processing Rule. Processing rules are applied to log data, but not to metric data. Note that while the Sumo service will receive your data, data ingestion will be performed in accordance with the regular expressions you specify in processing rules.
- When you are finished configuring the Source click Save.
Create export of Google Cloud VPC logs from Google Logging
In this step you export logs to the Pub/Sub topic you created in the previous step. Google Cloud Firewall runs on Google Cloud VPC, so you will collect VPC logs.
- Go to Logging and click Logs Router.
- Click Create Sink.
Click the arrow to Filter by label or text and select Convert to advanced filter.
For resource_type, replace
In the Edit Export window on the right:
- Set the Sink Name. For example, "gcp-subnetwork."
- Set Sink Service to “Cloud Pub/Sub”
- Set Sink Destination to the newly created Pub/Sub topic. For example, pub-sub-logs.
- Click Create Sink.
- By default, GCP logs are stored within Stackdriver, but you can configure Stackdriver to exclude them as detailed here without affecting the export to Sumo Logic as outlined above. To understand how to exclude Stackdriver logs, please follow the instructions in this GCP document.
Denied Ingress Traffic by Network Over Time
_sourceCategory=*gcp* logName reference resource "\"type\":\"gce_subnetwork\"" "\"direction\":\"INGRESS\"" "\"disposition\":\"DENIED\"" | parse regex "\"logName\":\"(?<log_name>[^\"]+)\"" | parse regex "\"reference\":\"network:[^\"/]+/firewall:(?<rule_name>[^\"]+)\"" | where log_name matches "projects/*/logs/compute.googleapis.com%2Ffirewall" | json "message.data.resource.labels", "message.data.jsonPayload" as labels, payload | json field=labels "location","project_id","subnetwork_id","subnetwork_name" as zone,project,subnetwork_id,subnetwork_name nodrop | json field=payload "disposition", "instance.vm_name", "vpc.vpc_name", "rule_details" as disposition, vm_instance, network, rule_details | json field=rule_details "action", "priority", "direction" | timeslice 1h | count as denied by _timeslice, network, project | transpose row _timeslice column network, project