Palo Alto Networks is reportedly in talks to buy Clutch Security for about $500 million in cash, plus milestone payouts. The Information reported the talks first. TechCrunch and Calcalist’s Ctech later filled in the price. Neither company confirmed a deal, and talks may stop short of one.

Clutch sells identity security for non-human identities: API keys, service accounts, tokens, and other credentials software systems use. AI agents use those credentials, and so do ordinary integrations with no chatbot involved. The reported price still matters, because large buyers are watching the keys that open calendars, CRMs, and billable records.

When you connect an assistant to Google Calendar, Jobber, ServiceTitan, QuickBooks Online, or your CRM, you usually hand it a key. That key can open the same doors a staff login can. The approval prompt that asks whether the bot may refund a customer is a separate control. Scope is what the key can do even when nobody clicks approve.

An illustration, not a customer story

Picture a Burbank HVAC shop with three trucks. The owner hooks a booking assistant to the calendar and the CRM so it can offer open windows and log new leads. To finish fast, the setup uses the owner’s Google login and a CRM API key that can create, edit, and delete contacts, plus read and write every job note.

A week later a contractor pastes a support dump into a shared chat, CRM key included. Nobody notices for two days. The bot keeps working, and so does anyone else who found the key.

The fix was simpler than buying an enterprise suite: a separate service login for the bot, secrets kept out of prompts and chat logs, a written revoke-and-rotate plan, and desired limits such as create-and-read on one booking calendar and on leads. A calendar service account alone does not guarantee create-only access. Native Google Calendar and CRM roles differ, and some APIs bundle write with delete. When the app cannot enforce those limits, keep the broader credential in the integration, allow only the actions you want there, and do not hand the agent a key that can do more.

What to set up before the bot goes live

Give the bot its own credentials. Do not reuse the owner’s login or a shared office password. Use a service account or API key that exists only for that automation.

Write the access you want before you connect anything: create and read on the booking calendar, not delete across the company; create leads and read status in the CRM, not wipe the pipeline; read unpaid balances for “did they pay?”, with refunds and payment links behind a human click. Enforce those limits in the app when a role can. When it cannot, restrict the actions through the integration and avoid giving the agent the broader credential directly. (We wrote earlier about connecting the narrow version first.)

Store secrets in a password-manager vault, the host’s secret store, or the automation platform’s credential field. Do not paste keys into system prompts, Google Docs, Slack, GitHub, or a “don’t ask again” settings file. If the model can see the secret in the prompt, treat that as exposure.

Write a revocation plan: who rotates each key, where the new value goes, and how you confirm the bot still works. Lost laptop, departing contractor, or a key in a log: rotate the same day.

Keep an activity log the owner can read: which credential ran, which app, which action, and when. Model spend caps help with runaway chat bills. They do not stop a stolen CRM key from editing your customer list.

Credentials are not the approval workflow

Owners often mix the two. An approval rule says the bot drafts a refund and waits for a person. Credential scope says the refund key was never issued to the bot. Use both. Approvals catch bad judgment, and narrow keys limit damage when something leaks.

Kush AI Automation builds shop assistants with that split: separate service credentials, app scopes where roles allow them and integration action limits where they do not, secrets kept out of prompts, rotation steps written down, and an activity trail the owner can check. If you want that setup on the tools you already pay for, book a free call.

Sources