Share

Most Salesforce orgs do not lose data because someone missed a checkbox. They lose it because an integration user was cloned from System Administrator years ago and never revisited.

In this session, Matt Meyers, CTA and Founder and CEO of EzProtect, is joined by Crystal Zhu, Enterprise Architect and Senior Salesforce Technical Architect at CGI, to show how to architect and secure Salesforce integration users and limit your breach blast radius before it is too late.

This session covers:

  • One integration, one identity, one scope. Every integration gets a dedicated API-only user, so you keep accountability and shrink the blast radius if credentials are compromised.
  • Start from zero. The Integration User license and Minimum Access API Only Integrations profile assume no access, so you build up only what each integration needs through scoped permission sets.
  • Trust is a foundation, not a feature. The Well-Architected Framework becomes the audit checklist you run against your own org.

Watch a Health Cloud use case built from a decade of org audits go from anti-pattern to trusted architecture, and leave with an action plan to bring back to your teams. 

 

 

Your Salesforce data is invaluable—is it truly secure? If you are allowing users to upload files into your Salesforce orgs, you are risk of also uploaded viruses and consequential data breaches. Get in contact with us today. 

Share

Did you love this blog and wish there could be more?

It is our goal to keep you informed about everything you need to know about Salesforce security to keep your Salesforce data and company safe and secure by providing you with the highest quality of original content.

If this sounds good to you, then sign-up below to be one of the first to know when the next super awesome Salesforce security blog has been released.

Download your free guide today!

Learn if you are at risk and how to start protecting your users!

GET THE FACTS NOW