The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

How Salesforce Guardian's AIforce security tools govern admin and agent access (opens in a new tab)

You will learn how Salesforce Guardian is organised into three pillars and what the new Compliance Agent, Security Mesh and MCP Security beta each do.

Why read this

You will also get a short set of practices for moving from reactive to proactive security.

Salesforce Guardian

  • Data Security
  • Data Compliance
  • Data Resilience
Salesforce Guardian is built on three pillars, each with its own products

Salesforce describes security as a shared responsibility. It provides the foundational platform security, admins configure the built-in controls such as multi-factor authentication, IP allowlisting and Permission Sets, and Salesforce Guardian sits on top as a portfolio of enterprise security, privacy and data protection products. The article frames this as three layers: Foundationals, Configurables and Enhanceables.

Salesforce Guardian rests on three pillars. Data Security covers Shield, for encryption, event monitoring and audit trails, and Security Center, for a single view of posture across orgs. Data Compliance covers Privacy Center, for retention and privacy rights requests, and Data Mask & Seed, for protecting sensitive data in sandboxes. Data Resilience covers Backup & Recover, for restoring lost or corrupted data, and Archive, for keeping the org lean while retaining what compliance requires.

The article names three AIforce security enhancements. Compliance Agent, part of Privacy Center, scans core metadata to set a compliance baseline and produce a score tied to regulatory goals, with actionable remediation plans. Because it relies on retrieval-augmented generation, the author stresses that grounding data must be classified, for example under GDPR, HIPAA or other PII categories, or the agent cannot tell public data from restricted data. Security Mesh, part of Security Center, normalizes signals from partners such as Okta and CrowdStrike and adds detections such as Impossible Travel. MCP Security, currently in beta, scans external MCP servers at registration and assigns Low, Medium or High risk scores before agents can reach them.

For implementation, the article recommends adopting a Zero Trust framework and the Principle of Least Privilege for both human and agent users, and setting up escalation paths for high-risk transactions to handle false positives and any human-in-the-loop regulatory requirements.

Read the original at Salesforce Admins Blog (opens in a new tab)

Worth reading?

Recommended

AIforce exposes Salesforce configuration to outside agents through MCP and the Headless Toolkit (opens in a new tab)

You will learn what AIforce and the Headless Toolkit expose from your org, the five tools that make it up, and how the security model applies to agents acting as users.

Why read this

You will also see what admins should review before opening the org to external agents.

Headless Toolkit

  • MCP servers
  • APIs
  • Skills
  • Plugins
  • Developer tools
The Headless Toolkit has five parts that expose org configuration outward

Salesforce’s AIforce strategy lets people work with Salesforce from the tools they already use, such as Slack, Claude and other AI clients, rather than only from the Salesforce UI. The article places AIforce as the interface layer above Data 360, Customer 360 and Agentforce. It stresses that the Lightning UI, Reports and Dashboards are not going away.

The Headless Toolkit, formerly called Headless 360, is the set of technologies that makes this work. It has five parts: MCP servers, which use OAuth and may be Salesforce-hosted or custom; APIs, including the Agent API and the platform data APIs; skills, which are instruction folders that AI clients load for a task; plugins, which package skills with commands and MCP connections; and developer tools such as the Salesforce CLI, Agentforce Vibes and the declarative Agent Script format. The article says this is an umbrella over existing capabilities rather than a new product, citing 60+ MCP tools, 4,000+ APIs and 220+ CLI commands.

For developers building external applications, there are two routes: the Headless Experience Layer, which renders workflows natively in channels such as Slack, WhatsApp, voice or mobile, or direct calls to the APIs and MCP tools with a custom UI. Either way, the flows, data models and guardrails configured in the org are what they build on.

On security, the article says Sharing Rules, field-level security and Permission Sets are respected however data is accessed, and that calls pass through the Trust Layer. Every call carries identity, access, capability and governance controls, so Validation Rules, triggers and governor limits still apply. Because an agent can do anything the acting user can do, the article advises reviewing profiles and Permission Sets before exposing the org. Agentic Identity, where agents have their own permissions and credentials, is described as planned for the near future.

Read the original at Salesforce Admins Blog (opens in a new tab)

Worth reading?