Verwenden Sie dies, wenn
Stream live traffic using Packet Mirroring, deploy sensor VM with Terraform, and ingest findings via the managed SIEM connector.
Stream live traffic using Packet Mirroring, deploy sensor VM with Terraform, and ingest findings via the managed SIEM connector. Zielgruppe: Platform engineers, GCP administrators, security engineers. Typische Einrichtungszeit: 15 minutes.
Stream live traffic using Packet Mirroring, deploy sensor VM with Terraform, and ingest findings via the managed SIEM connector.
Kopieren Sie ein Starter-Setup, führen Sie es in Ihrer Umgebung aus und kehren Sie für tiefergehende Details hierher zurück.
Demonstration only
This configuration is designed for ease of use. To deploy scanner clients at scale, please plan your deployment architecture accordingly or contact us for enterprise best practices.
Download the exact source files referenced on this page, or run the one-command installer to write them locally before following the deployment steps.
Creates the GCP Terraform project under `deploy/gcp-network-sensor/` with the current platform API URL prefilled for packet mirroring-based network telemetry ingestion.
BLACKSHIELD_NETWORK_SENSOR_IMAGE=public.ecr.aws/blackshield-security/network-sensor:1.0.11 \
BLACKSHIELD_API_URL=https://api.blackshield.chaplau.com \
bash <(curl -fsSL https://blackshield.chaplau.com/source-bundles/gcp-network-sensor.sh)
cd deploy/gcp-network-sensor#!/bin/bash
# Complete GCP Packet Mirroring setup
PROJECT_ID="my-project"
REGION="us-central1"
SUBNET="my-subnet"
NETWORK="my-vpc"
SENSOR_MIG="network-sensor-mig" # The Instance Group from your Terraform deployment
echo "1. Creating Health Check & Backend Service..."
gcloud compute health-checks create tcp network-sensor-hc --port=8080 --project="$PROJECT_ID"
gcloud compute backend-services create network-sensor-backend \
--region="$REGION" \
--health-checks=network-sensor-hc \
--load-balancing-scheme=INTERNAL \
--protocol=TCP \
--project="$PROJECT_ID"
gcloud compute backend-services add-backend network-sensor-backend \
--region="$REGION" \
--instance-group="$SENSOR_MIG" \
--project="$PROJECT_ID"
echo "2. Creating Forwarding Rule (Mirroring Target)..."
gcloud compute forwarding-rules create network-sensor-fr \
--region="$REGION" \
--network="$NETWORK" \
--subnet="$SUBNET" \
--load-balancing-scheme=INTERNAL \
--backend-service=network-sensor-backend \
--is-mirroring-collector \
--project="$PROJECT_ID"
echo "3. Creating Packet Mirroring Policy..."
gcloud compute packet-mirrorings create prod-workload-mirror \
--region="$REGION" \
--network="$NETWORK" \
--collector-ilb=network-sensor-fr \
--mirrored-subnets="$SUBNET" \
--project="$PROJECT_ID"
echo "Success! Packet mirroring policy active."# 1. Configure Terraform Variables
cat > deploy/gcp-network-sensor/terraform.tfvars << EOF
gcp_project_id = "my-project-id"
gcp_region = "us-central1"
vpc_network_name = "default"
api_key = "sp_your_ingestion_key"
EOF
# 2. Deploy Infrastructure
cd deploy/gcp-network-sensor
terraform init
terraform apply -auto-approve# GCP Terraform snippet for Network Sensor Deployment
resource "google_compute_instance" "network_sensor" {
name = "blackshield-network-sensor"
machine_type = "e2-medium"
zone = "us-central1-a"
boot_disk {
initialize_params {
image = "ubuntu-os-cloud/ubuntu-2204-lts"
}
}
network_interface {
network = var.vpc_network_name
subnetwork = var.monitoring_subnet_name
}
metadata = {
startup-script = templatefile("${path.module}/startup.sh.tftpl", {
api_url = "https://api.blackshield.chaplau.com"
sensor_type = "suricata"
min_severity = "high"
})
}
service_account {
scopes = ["cloud-platform"]
}
}Nutzen Sie die folgenden Schritte, um den Rollout anzupassen, Verantwortlichkeiten zu prüfen und die Bereitstellung sicher zu erweitern.
Schritt 1
Use the provided Terraform module to deploy the sensor VM (or Managed Instance Group). This acts as the destination for your mirrored traffic.
Erfolgreicher Abschluss
Note the generated Managed Instance Group (MIG) name from the Terraform output — you'll need this to set up the Internal Load Balancer target.
Schritt 2
Create a packet mirroring policy to duplicate traffic from your production VMs and route it to the sensor instances via an Internal Load Balancer.
Erfolgreicher Abschluss
Verify the mirroring policy status is 'ACTIVE' in the GCP Console.
Hilfreicher Kontext
Schritt 3
Confirm the sensor container is running properly on your VM and receiving the mirrored VXLAN traffic.
Erfolgreicher Abschluss
Check the platform Findings view to see network-based alerts within 5 minutes.
Keep your rollout moving with the next recommended step.
Findings prüfen und priorisieren