Secure Private Connectivity for Splunk Cloud on Google Cloud

Partners Alexey Bokov

Key takeaways

  1. Google Cloud Private Service Connect now enables a private network connection between Google Cloud and Splunk Cloud Platform at no additional Splunk cost.
  2. Private Connectivity helps organizations reduce public internet exposure, support compliance needs, and simplify networking for secure cloud environments.
  3. Customers can send Splunk telemetry over a dedicated private connection, maintaining network isolation while continuing security and observability monitoring.

Organizations are continuously strengthening cloud security postures, including limiting public internet exposure, using Zero Trust Network Access, and deploying applications in Google Cloud Virtual Private Cloud (VPC) environments. Some Splunk customers have also asked for a way to keep their encrypted Splunk Cloud Platform telemetry data on a private network path instead of the public internet.

You asked. We listened.

Splunk now supports Google Cloud Private Service Connect (PSC), giving customers a dedicated, private connection between Google Cloud and Splunk Cloud Platform at no additional Splunk cost.

Customers have been asking for a simpler way to extend their private Google Cloud environments to Splunk Cloud. Private Connectivity makes that possible with a dedicated network path to Splunk, making it easier to build secure, resilient cloud architectures. — Jason Conger, Field CTO, Splunk

This new capability is a direct response to customer requests for additional ways to build more secure cloud architectures, simplify networking, and meet increasingly stringent security and compliance requirements. It's another milestone in partnership and roadmap with Google Cloud to deliver modern cloud experiences shaped by real customer needs.

What is Google Cloud Private Service Connect?
Google Cloud Private Service Connect (PSC) is Google's native networking capability for privately connecting Virtual Private Cloud (VPC) environments to services like Splunk Cloud Platform. It prevents network traffic from being exposed to the public internet by keeping data inside Google Cloud network backbone and removes the need for internet gateways or VPC peering connections.

Why Private Connectivity Matters

As SOC and cloud application teams build digitally resilient infrastructures, many design sensitive and highly secure cloud workloads, apps, and VMs inside a private network with restricted or even no direct internet access. Until now, many of these environments that use Splunk required a networking exception to allow encrypted telemetry data to leave the private network before reaching Splunk Cloud.

Private Connectivity removes that exception.

Organizations can now securely send telemetry from Google Cloud environments to Splunk Cloud Platform over a dedicated private connection, maintaining network isolation while continuing to collect the observability and security data required to keep the business running.

Why Customers Choose Private Connectivity

Getting Started

Enabling Private Connectivity only requires a few configuration steps and comes at no additional Splunk cost. Splunk admins need to enable Private Connectivity in the Splunk Admin Config Service (ACS) and update data sources to communicate using the private connections.

Ready to bring Splunk Cloud into your private networking strategy? Review the deployment guides below to learn how to plan and deploy Private Service Connect for Splunk.

/en_us/blog/fragments/managing-your-cloud-costs-a-how-to-guide
style
two-column

Related Articles

Infostealer Campaign against ISPs
Security
20 Minute Read

Infostealer Campaign against ISPs

The Splunk Threat Research Team observed actors performing minimal intrusive operations to avoid detection, with the exception of artifacts created by accounts already compromised.
Assigning Role Based Permissions in Splunk Enterprise Security
Security
2 Minute Read

Assigning Role Based Permissions in Splunk Enterprise Security

Learn how to add a new role in Enterprise Security and apply capabilities to it
STRT-TA03 CPE - Destructive Software
Security
5 Minute Read

STRT-TA03 CPE - Destructive Software

The Splunk Threat Research Team is monitoring several malicious payloads targeting Customer Premise Equipment (CPE) devices. These are defined as devices that are at customer (Commercial, Residential) premises and that provide connectivity and services to the internet backbone
/en_us/blog/fragments/about-splunk
/en_us/blog/fragments/perspectives-promo