BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//EzProtect - ECPv6.17.0//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:EzProtect
X-ORIGINAL-URL:https://ezprotect.io
X-WR-CALDESC:Events for EzProtect
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-Robots-Tag:noindex
X-PUBLISHED-TTL:PT1H
BEGIN:VTIMEZONE
TZID:America/Vancouver
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:20250309T100000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:20251102T090000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:20260308T100000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0700
TZNAME:MST
DTSTART:20261101T090000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Vancouver:20260820T090000
DTEND;TZID=America/Vancouver:20260820T100000
DTSTAMP:20260814T171932Z
CREATED:20260730T172722Z
LAST-MODIFIED:20260814T171932Z
UID:2393-1787216400-1787220000@ezprotect.io
SUMMARY:Salesforce Security Office Hours with Matt Meyers\, CTA
DESCRIPTION:A 2025 Sophos study of 3\,400 organizations hit by ransomware found that in one in four cases\, the team’s leadership was replaced as a consequence of the attack. It takes one file moving through a workflow nobody thought to inspect. A partner uploads a contract to a portal case\, the only hostile element is a link in the footer\, and the rep forwards it to the customer under your company’s name. \nSummer ’26 malware scanning became generally available for Salesforce Files\, it is on by default\, and every org should leave it on. Salesforce is also direct about what it is for\, stating that scanning flags files only when they have a high probability of being malicious\, that files above 100 MB are neither scanned nor blocked\, and that organizations requiring more stringent scanning should consider one of its scanning partners. This session takes that documentation apart line by line and gives you what you need to know before the next file lands. \nAttendees will leave understanding what Summer ’26 native scanning is documented to do\, where the published limits sit\, and what a breach costs the people held responsible for it. They will also leave with clear action items to bring back to their own org and to the leadership team that signs off on them. Bring your burning questions for Matt Meyers\, CTA\, CoFounder and CEO of EzProtect and author of Securing Salesforce Digital Experiences. \nRegister for this event and we will see you online.  \n		\n						\n				\n									\n					\n						\n									Register
URL:https://ezprotect.io/event/salesforce-summer-26-malware-scanning-limits/
CATEGORIES:Virtual
ATTACH;FMTTYPE=image/jpeg:https://ezprotect.io/wp-content/uploads/2026/07/Salesforce-Security-Office-Hours_Web-2026-08-14T121432.856-scaled.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Vancouver:20260903T090000
DTEND;TZID=America/Vancouver:20260903T100000
DTSTAMP:20260808T184722Z
CREATED:20260808T184722Z
LAST-MODIFIED:20260808T184722Z
UID:2415-1788426000-1788429600@ezprotect.io
SUMMARY:Salesforce Security Office Hours with Saman Attar
DESCRIPTION:Winter ’27 enforcement begins in September 2026\, and two of its changes reach into custom code that admins are often asked to approve without being able to read it. Profile Filtering limits users to seeing their own profile name unless they hold the View All Profiles permission\, so anything that reads another user’s profile name stops working for the people who lack it. Those references appear in validation rules and flows\, and they appear in Apex. The real security question is what happens next? \nGranting View All Profiles more widely restores the broken feature immediately and widens profile visibility across the org at the same time\, which makes the faster remediation the weaker one. The retirement of the OAuth 2.0 username-password flow raises the same question\, because Salesforce is removing that flow for the specific reason that it passes user credentials directly in HTTP requests\, and every connected app integration still using it will break. \nThis session gives admins and consultants enough Apex reading ability to open a class\, follow what a query is asking for\, how to check your Flows\, and Validation Rules as well. and judge whether it is exposed to either change. Demo will only be for how to do an Apex profile check and will not demo anything for the OAuth 2.0 retirement. \nNo prior Apex experience is assumed. Attendees will leave able to assess their own org’s code against the Winter ’27 changes\, where to go in Setup to enable settings ahead of the next release in your Sandbox\, and to recognize when a proposed fix restores a feature by loosening access. \nGuest speaker Saman Attar\, Senior Software Engineer at F5 and Founder of CampApex.org\, joins Matt Meyers\, CTA\, CoFounder and CEO of EzProtect. \nRegister for this event and we will see you online.  \n		\n						\n				\n									\n					\n						\n									Register
URL:https://ezprotect.io/event/salesforce-security-winter-27-apex-profile-filtering/
CATEGORIES:Virtual
ATTACH;FMTTYPE=image/jpeg:https://ezprotect.io/wp-content/uploads/2026/08/Salesforce-Security-Office-Hours_Web-2026-08-08T134409.244-scaled.jpg
END:VEVENT
END:VCALENDAR