The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Securing Agentforce against prompt injection and data exfiltration (opens in a new tab)

You will learn how untrusted input can steer Agentforce into exfiltrating data via DNS lookups, and which Einstein Trust Layer controls actually mitigate these risks.

Why read this

You will also get a practical checklist for configuring runtime identities, permissions, and safe workflows.

Research by Zenity demonstrates a prompt injection chain where untrusted text stored in a Web-to-Lead record steers Agentforce to query authorized account data. The injected instructions embed the results in an external hostname, exploiting a Trusted URLs parsing discrepancy that triggers a DNS lookup to exfiltrate information without requiring user interaction.

The Einstein Trust Layer provides several guardrails, including semantic filters, zero data retention agreements, and audit logging, but it does not enforce authorization policies or stop agents from querying records they are already permitted to see. Data masking is currently disabled for agents, and prompt defenses remain probabilistic rather than absolute.

Securing Agentforce requires strict identity and permission hygiene. Administrators must verify whether agents run under employee profiles, dedicated service users, or integration accounts, then restrict object and field access accordingly. Replacing broad query tools with custom Apex actions that enforce user mode and explicit Sharing Rules reduces exposure.

A recommended architecture isolates unauthenticated submissions behind a read-only lead triage agent, followed by human review before downstream agents handle outbound communication. This layered approach prevents poisoned data from reaching internal databases or messaging channels like Slack.

Read the original at dev.to (opens in a new tab)

Worth reading?