Managing Data Exposure with Salesforce Rules

Salesforce Inspector Reloaded: Four Security Levels to Fortify Your Org 🔐 Recent breaches have shown how attackers exploit gaps in Salesforce configurations to gain unauthorized access. Let’s break down four security levels from weakest to strongest—and outline concrete actions you can take today to protect your org. 1. Level 1: No API Access Control and Session Token Reuse Without API access control, any external actor can interact with your org’s APIs—no connected app required. - Attackers can call APIs using public client IDs (Data Loader, SIR, etc.). - Valid Salesforce session IDs (extracted from cookies, phishing, or browser dev tools) can be reused to query or manipulate data. - No enforcement on which apps or sessions are allowed, leaving your org fully exposed. Action: - Enable API Access Control immediately. This forces every incoming API call to originate from an explicitly approved connected app. - In a sandbox environment, enable API Access Control first, then test all integrations and connected apps to ensure they function correctly before rolling the change out to production. 2. Level 2: API Access Control Enabled With API access control turned on, only approved apps can call your APIs—but default client IDs are still public. - Open-source forks of SIR or similar tools inherit the same client ID. - A malicious fork could trick your users into installing a fake extension. 😱 - That fake extension operates under your org’s allowed client ID. You’re safer, but not fully secure. 3. Level 3: Use a Custom Connected App Lock down SIR by giving it its own identity. 1. In Salesforce Setup, create a new Connected App named “Salesforce Inspector Reloaded – YourCompanyName.” 2. In SIR settings, replace the default client ID with your custom one. 3. Approve only this Connected App in your API Access Control list. Guide: https://lnkd.in/g3RaUWGn 4. Level 4: Monitor with Transaction Security Policies Even the best controls need active monitoring. Transaction Security Policies (available with Shield or Event Monitoring add-ons) let you: - Detect anomalous API calls in real time. - Enforce custom rules when suspicious behavior occurs. - Receive alerts or block events before they escalate.

Sharing in Salesforce is not just about who can “see” a record — it’s a full architecture designed to balance security, access, and performance. Here’s a clear breakdown of how the sharing model actually works: 1️⃣ Organization-Wide Defaults (OWD) OWD defines the baseline access for everyone in the org. Common settings include: Private – Only owner and users above in the Role Hierarchy can access Public Read Only – All users can view, only owner can edit Public Read/Write – All users can view and edit Controlled by Parent – Inherits access from parent object (MD relationship) OWD sets the lowest level of access. 2️⃣ Role Hierarchy Roles allow access to move upward — managers can see records owned by users below them. Key points: Roles don’t grant permissions, they only open visibility Hierarchy works automatically with Private OWD It’s for reporting + managerial access, not security control 3️⃣ Sharing Rules Sharing Rules open access horizontally across teams. Types include: Owner-Based Sharing Rule – Share records owned by a certain group Criteria-Based Sharing Rule – Share records that meet specific field criteria Use when teams need access to each other’s data, but shouldn’t be in the same Role. 4️⃣ Manual Sharing Record owners (or admins) share individual records manually. Useful when: Temporary access is needed One-off exceptions arise Not scalable → not used for architecture-level design. 5️⃣ Apex Managed Sharing Used when access needs to be controlled programmatically. Benefits: Dynamic Automatable Deployable Works even when logic changes frequently Common use cases: internal apps, partner models, custom collaboration logic. Final Insight OWD sets the default. Roles open access upward. Sharing Rules open access sideways. Apex Sharing handles exceptions. Understanding this hierarchy is the foundation of secure, predictable Salesforce design. #Salesforce #SecurityModel #AdminLife #Apex #FlowBuilder #Hiring #HRTech #USJobs

🔑 Managing Access in Salesforce Just Got Easier As Salesforce orgs grow, one of the trickiest parts of an admin’s job is managing who gets access to what. Relying only on profiles, permission sets, and manual updates often leads to confusion, security risks, and wasted time. That is where User Access Policies come in. Think of them as a traffic signal for access: you set the rules, and Salesforce automatically grants or revokes permissions when user attributes change. A new Sales Rep joins? They can be instantly assigned the right permission set group, public group, and licenses with no manual steps required. 😎 Why this matters: -Consistency: Every new hire gets the right access immediately -Less Admin Overhead: No more chasing down permission requests -Stronger Security: Old access is removed automatically -Audit-Friendly: You can point to clear, rules-based policies But automation is only as good as the data behind it. It's recommended to test policies in a sandbox first, so you can validate rules, check for data issues, and avoid accidental permission chaos in production. ✅ Best practices: -Start small with one team or department -Document your rules -Review quarterly to avoid permission creep -Always test in a sandbox before rollout User Access Policies do not replace everything such as profiles or complex flows, but they add a solid automation layer to keep your org secure and consistent. #SalesforceAdmins #SalesforceDevelopers #Salesforce Image credit: Salesforce Trailhead

"With Sharing" vs "Without Sharing" in Salesforce Apex – When and How to Use Them As a Salesforce developer, understanding sharing rules in Apex is crucial for building secure and scalable applications. 🔹 With Sharing: Enforces the current user’s sharing rules. Use it when you want to respect org-wide defaults and sharing settings. Best for user-facing operations, like record retrieval in a community or portal. 🔹 Without Sharing: Ignores sharing rules, giving full access to records. Use it when dealing with system processes like triggers, schedulers, or integrations that require unrestricted access. Be cautious! Ensure you’re not exposing sensitive data. 🔑 Best Practices: Always be intentional: Default to with sharing unless there’s a solid reason not to. For complex transactions, consider combining both (Without Sharing for data processing, With Sharing for user-facing actions). Document your decision in the code to avoid confusion later. By using these correctly, you’ll improve data security while maintaining flexibility in your Salesforce apps. 🚀 Keep Walking !!!

🔐 𝐒𝐚𝐥𝐞𝐬𝐟𝐨𝐫𝐜𝐞 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 — 𝐖𝐡𝐚𝐭’𝐬 𝐔𝐬𝐞𝐝 𝐌𝐨𝐬𝐭 & 𝐖𝐡𝐲 🔐 If you’re a Salesforce Admin, Developer, or even an intern, you need to know how records are shared in Salesforce. 𝐒𝐨𝐦𝐞 𝐦𝐞𝐭𝐡𝐨𝐝𝐬 𝐚𝐫𝐞 𝐮𝐬𝐞𝐝 𝐝𝐚𝐢𝐥𝐲, 𝐰𝐡𝐢𝐥𝐞 𝐨𝐭𝐡𝐞𝐫𝐬 𝐚𝐫𝐞 𝐧𝐢𝐜𝐡𝐞. 𝐋𝐞𝐭’𝐬 𝐛𝐫𝐞𝐚𝐤 𝐢𝐭 𝐝𝐨𝐰𝐧 👇 💡 𝐌𝐨𝐬𝐭 𝐂𝐨𝐦𝐦𝐨𝐧 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 𝐌𝐞𝐭𝐡𝐨𝐝𝐬 𝐢𝐧 𝐒𝐚𝐥𝐞𝐬𝐟𝐨𝐫𝐜𝐞 1️⃣ 𝐎𝐫𝐠𝐚𝐧𝐢𝐳𝐚𝐭𝐢𝐨𝐧-𝐖𝐢𝐝𝐞 𝐃𝐞𝐟𝐚𝐮𝐥𝐭𝐬 (𝐎𝐖𝐃) – Sets the baseline access (Private, Read Only, Read/Write). Most orgs keep sensitive objects like Opportunities & Cases as Private. 2️⃣ 𝐑𝐨𝐥𝐞 𝐇𝐢𝐞𝐫𝐚𝐫𝐜𝐡𝐲 – Managers automatically see subordinates’ records. Essential for sales orgs with reporting structures. 3️⃣ 𝐏𝐮𝐛𝐥𝐢𝐜 𝐆𝐫𝐨𝐮𝐩𝐬 –  Group users/roles for easier sharing. Frequently used with sharing rules. 4️⃣ 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 𝐑𝐮𝐥𝐞𝐬 –Auto-share records based on criteria or ownership. Example: All “East Coast” Accounts → shared with East Coast Sales Team. 5️⃣ 𝐌𝐚𝐧𝐮𝐚𝐥 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 – One-off, record-level sharing for exceptions. Great for temporary collaboration. 📌 𝐋𝐞𝐬𝐬 𝐂𝐨𝐦𝐦𝐨𝐧 𝐛𝐮𝐭 𝐏𝐨𝐰𝐞𝐫𝐟𝐮𝐥 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 𝐒𝐞𝐭𝐬 –  For external Community/Portal users (partners, customers). 𝐀𝐩𝐞𝐱 𝐌𝐚𝐧𝐚𝐠𝐞𝐝 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 –  Developer-controlled sharing via code. 𝐓𝐞𝐚𝐦 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 – Account, Opportunity, or Case-specific collaboration teams. 𝐓𝐞𝐫𝐫𝐢𝐭𝐨𝐫𝐲-𝐁𝐚𝐬𝐞𝐝 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 – Grants access via territory assignments (ETM). 📖 𝐀𝐁𝐂 𝐂𝐨𝐫𝐩 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: 𝐎𝐖𝐃 : Accounts Private 𝐑𝐨𝐥𝐞 𝐇𝐢𝐞𝐫𝐚𝐫𝐜𝐡𝐲 : Managers see reps’ Accounts 𝐏𝐮𝐛𝐥𝐢𝐜 𝐆𝐫𝐨𝐮𝐩 : “East Coast Sales Team” 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 𝐑𝐮𝐥𝐞 : Auto-share East Coast Accounts to that group 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 𝐒𝐞𝐭: Partners see only their own company’s records 𝐌𝐚𝐧𝐮𝐚𝐥 𝐒𝐡𝐚𝐫𝐢𝐧𝐠: Owner shares one record with a colleague for review ✅ 𝐅𝐨𝐜𝐮𝐬 𝐨𝐧 𝐎𝐖𝐃, 𝐑𝐨𝐥𝐞 𝐇𝐢𝐞𝐫𝐚𝐫𝐜𝐡𝐲, 𝐏𝐮𝐛𝐥𝐢𝐜 𝐆𝐫𝐨𝐮𝐩𝐬, 𝐚𝐧𝐝 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 𝐑𝐮𝐥𝐞𝐬 — 𝐭𝐡𝐞𝐲 𝐡𝐚𝐧𝐝𝐥𝐞 80%+ 𝐨𝐟 𝐫𝐞𝐚𝐥-𝐰𝐨𝐫𝐥𝐝 𝐬𝐡𝐚𝐫𝐢𝐧𝐠 𝐧𝐞𝐞𝐝𝐬. The rest are situational but equally important to know for the right scenario. #Salesforce #SharingRules #PublicGroups #OWD #RoleHierarchy #ManualSharing #SalesforceAdmin #SalesforceDeveloper #DataAccess #Security

🌟 Day8: Salesforce Admin Interview Series 🌟 🚀 How you can provide security in salesforce? 🔒Security is a top priority when working with Salesforce. Whether you're managing a small team or a global enterprise, keeping your data safe ensures trust and compliance. 1️⃣ Object-Level Security (Object Permissions) Controls access to entire objects (Tables in Salesforce). 🔹 Managed through Profiles & Permission Sets. 🔹 Permissions include Read, Create, Edit, Delete (CRUD). 🔹 Example: A Sales Rep can view Opportunities, but only Sales Managers can delete them. ✅ Best Practice: Use Permission Sets instead of modifying Profiles directly for flexibility. 2️⃣ Field-Level Security (FLS) Restricts access to specific fields within an object. 🔹 Also controlled via Profiles & Permission Sets. 🔹 Example: A user can see an Account record but may not have access to the Annual Revenue field. ✅ Best Practice: Never expose sensitive fields like Salary, Social Security Numbers, or Payment Details to users who don’t need them. 3️⃣ Record-Level Security Determines who can access individual records. 🔹 Even if a user has access to an object, they may not see all records. How is Record Access Managed? 📌 Organization-Wide Defaults (OWD): Sets the baseline level of access (e.g., Private, Read-Only, Read/Write). 📌 Role Hierarchy: Higher roles inherit access from subordinates. Example: A Sales VP can see all records owned by Sales Managers, but not vice versa. 📌 Sharing Rules: Grant access to specific users or groups based on conditions. Example: Automatically share High-Value Opportunities with a Finance Team. 📌 Manual Sharing: Users manually share records with others if permitted. 📌 Apex Sharing (Programmatic Sharing): Custom logic to share records dynamically via Apex code. ✅ Best Practice: Always follow OWD → Role Hierarchy → Sharing Rules → Manual Sharing for structured access. 4️⃣ Authentication & Access Control Verifies user identity and restricts unauthorized access. 🔹 Multi-Factor Authentication (MFA) 🔹 Single Sign-On (SSO) 🔹 Login IP Ranges 🔹 Login Hours 🔹 Session Security ✅ Best Practice: MFA is now mandatory for all Salesforce users. Enable SSO for ease of access. 5️⃣ Encryption & Data Protection 🔹 Shield Platform Encryption 🔹 Field-Level Encryption 🔹 TLS (Transport Layer Security) ✅ Best Practice: Use Shield Encryption for storing sensitive data. Avoid storing PII (Personally Identifiable Information) in plaintext. 6️⃣ Application Security (Apex & Visualforce) 🔹 CRUD & FLS Enforcement in Apex 🔹 With Sharing vs. Without Sharing in Apex 🔹 Security Review for Apps ✅ Best Practice: Use “With Sharing” in Apex to respect security rules. 7️⃣ Monitoring & Auditing 🔹 Login History 🔹 Field History Tracking 🔹 Setup Audit Trail 🔹 Event Monitoring (Salesforce Shield) ✅ Best Practice: Regularly review audit logs and login history for anomalies. #SalesforceAdmin #Salesforce #SalesforceDeveloper

Is this your Salesforce org exposing all your accounts to the entire world? 😬 Per Gartner via 2025 research, more than 99% of cloud breaches will have a root cause of preventable misconfigurations or mistakes by end users. Misconfiguring your org can provide pathways to critical data exposure and serious legal and customer ramifications for your business. But what can you do about it? 🤔 💪 When establishing guest user sharing rules, all impacted records become immediately visible to the public. Examine these policies closely and minimize objects and records shared with guest users to only what's absolutely essential. 💪 Shield guest users from accessing Apex classes, particularly AuraEnabled ones. Scrutinize which VisualForce and Apex pages guest users can view and restrict these to only the most necessary components. 💪 To safeguard the protection and accuracy of confidential data within Salesforce objects, implement the most stringent possible object permissions in the guest user profile. These may differ according to company needs, but powerful permissions like View All and ModifyAll require particular attention. 💪 Review and uncheck Salesforce permissions that aren't absolutely required for your operations. Remove sensitive capabilities such as View All Users and Run Flows if guest users don't require these functions. Unless there's a legitimate business justification, it's also recommended to deactivate API access. If you are a business leader and still concerned about your Salesforce data security exposure after reading this post, shoot me a message. #Salesforce #CyberSecurity #DataProtection