Back to resources
CostCheat sheet

Zenta Pulse Best Practices: The 15-Minute Setup That Earns Its Keep

Cheat sheet · 1 pages · 3 min read

Most GCP exposure incidents and misconfigurations don't end in a breach — they end in a bill, because nothing was watching spend in real time when the key started getting hit. This quick guide walks through the six settings that turn Zenta Pulse from "connected" into an active layer on your Google Cloud: budgets, threshold alerts, and — critically — Kill Switch, Pulse's automatic billing disconnect that caps damage at the project or service level before a compromised key or runaway service turns into a five-figure surprise. Follow the steps in order; the whole setup takes about 15 minutes.

What's inside

  • Setting org-wide and per-project budgets (the foundation every alert and cap depends on)
  • Tuning cost-spike and threshold alerts to fire at 80%, not 100%
  • Arming Auto-Protect (Kill Switch) as a hard-cap safety net at 120–150% of budget
  • Scoping Kill Switch to individual services (e.g., BigQuery, Cloud Run) instead of a whole project
  • Enabling Weekly Cost, Monthly Security, and Monthly Executive Summary reports
  • A monthly review cadence: Quick Wins, AI remediation plans per SecureMonitor finding, and using Ollie