Salesforce security: a foundation for trust
Salesforce orgs keep getting more complicated as AI adoption and integrations pile up, and the security posture has to keep pace. Most of the attention goes to new features and automation instead, so security stays the thing everyone means to get to. Three principles sit underneath all of it, and every Salesforce developer, architect and admin should be able to explain and implement them.
The survey says: security lags behind
A recent survey puts security at the bottom: it is the skill Salesforce administrators feel least confident about, at every experience level. Flow and the new feature list get the attention, and security takes a backseat. That gap is more worrying now that AI tools such as Agentforce are doubling adoption rates annually. Agentic behavior and automated actions move processes along faster than traditional oversight can follow, which amplifies the risk.
Three pillars of Salesforce security
The shared responsibility model divides security duties between Salesforce and its customers. Salesforce is responsible for the security of the platform, meaning the infrastructure and core services. You are responsible for the security in the platform: your data, your user access, your custom configurations and your integrations.
In practice that means an overly permissive permission set is yours, a user who falls for a phishing email is yours, and a security control implemented incorrectly is yours.
The principle of least privilege says users, systems and processes get only the minimum permissions their intended function needs. Granting excessive access is the path of least resistance, and it creates significant security risk.
Over-provisioned access turns into permission sprawl, or privilege creep, the same shape as agent sprawl in AI. Many organizations never finish the move from profile-based access to a permission set led model, and what is left behind is a complex, layered set of access configurations.
Zero trust runs on never trust, always verify. No user, device or system is inherently trusted, including everything inside the network perimeter, and access is verified continuously. The working assumption is that any user or device could be compromised at any time, so neither location nor a prior authentication grants access on its own.
In Salesforce that means multi-factor authentication (MFA), Trusted IP Ranges and session security settings. It matters most in exactly the orgs that are most connected: extensive integrations, mobile access, remote work.
Leave a Comment