Salesforce Penetration Testing

Set to private. Shared with a guest.

One sharing rule flips an object to public, and a community guest with no login reads your customer records. A senior U.S. engineer maps every object against every role and finds the one that leaks. When we reach what matters, we leave a card.

What We Test

Salesforce secures the platform. Everything above it is yours: the objects, the profiles, the sharing rules, the Apex, and every app you installed. That is what we test.

Sharing Rules & OWD

Org-wide defaults, sharing rules, and “without sharing” Apex that quietly bypass record-level security.

Guest Users & Communities

Experience Cloud guest access, the vector behind the 2024 account-takeover disclosures.

Profiles & Permission Sets

Overprivileged roles, “View All” and “Modify All Data,” and permission drift over time.

Apex & SOQL Injection

Custom Apex, triggers, and Aura controllers tested for injection and logic flaws.

APIs & AppExchange

REST and SOAP endpoints and third-party packages, tested the way an API engagement would.

Config & Metadata Drift

Insecure defaults and metadata changes that slip past review and expose fields or logic.

How We Test

Our own Salesforce toolset puts every object, permission, and line of Apex in front of a senior engineer, who proves which of them an attacker can actually use.

01

Map the Org

We chart objects, profiles, permission sets, sharing rules, guest access, and integrations, the full permission surface.

02

Work the Org

With a toolset Raxis built for Salesforce penetration testing, the engineer works through misconfigurations, weak permissions, and risky code across your metadata.

03

Exploit by Hand

We validate each finding with a proof of concept: guest data access, privilege escalation, SOQL injection, exposed APIs.

04

Report & Retest

Findings land in Raxis One with proof and a fix. You remediate, we verify.

Findings We See in the Wild

Not one of these is a flaw in Salesforce. Every one of them is in orgs we test.

Overprivileged Profiles

“View All” and “Modify All Data” granted far beyond what any role needs.

Guest User Exposure

Community guest access reaching objects and records it was never meant to.

Without-Sharing Apex

Apex classes that run past record-level security and hand back restricted data.

SOQL Injection

Unvalidated input in custom Apex and Aura controllers, used to read the database.

Unauthenticated APIs

Endpoints and site pages that answer without checking who is asking.

Permission Drift

Access that accumulated over three releases a year until nobody could say who could see what.

Built by Pentesters, for Pentesters

No off-the-shelf scanner reads a Salesforce org the way an attacker does, so we built our own. Raxis engineers wrote a Salesforce assessment toolset for one job: putting every object, permission, sharing rule, and line of Apex in front of a tester who can decide what matters. It does not replace the engineer. It makes the engineer faster.

Made for Pentesting

Developed in-house for Salesforce penetration testing, not adapted from a compliance dashboard.

Interactive, Not Automated

The engineer drives it, pivoting from a suspicious sharing rule to the records it exposes while the finding is still warm.

The Whole Org

Objects, fields, profiles, permission sets, sharing rules, guest access, Apex, and integrations, so nothing is left to a sampled checklist.

Proof, Not a Score

Every concern the toolset raises is exploited by hand before it reaches your report.

Two Ways to Test Your Org

Same senior engineers, same manual tradecraft, same live findings. The difference is when you want us on it: once, for a fixed window, or all year.

What You Get

Written by the engineer who mapped your org, for the admins and developers who have to change it. Track findings in real time with Raxis One.

Technical Findings

Each with a proof of concept, the object and permission at fault, and the fix.

Executive Summary

A board-readable read on the risk and what it means for your data.

Compliance Mapping

Findings mapped to the control language your auditor uses, with an attestation letter.

Included Retest

We verify your fixes and deliver a clean final report, at no extra cost.

FAQ: Salesforce Penetration Testing

Why does Salesforce need penetration testing if it’s a secure cloud platform?

Salesforce secures the infrastructure; you are responsible for configuring it. The permission system, custom Apex, Lightning components, and integrations introduce many opportunities for misconfiguration. Our testing finds the vulnerabilities unique to your implementation, custom code, permission sets, sharing rules, and integrations, that automated tools and Salesforce's own security cannot catch for you.

What’s the difference between an automated Salesforce security scan and full penetration testing?

An automated scanner finds known misconfigurations, permission issues, and code-quality problems in your metadata and reports a score. It cannot tell you which of them an attacker can use. Raxis built its own Salesforce toolset for the other half of that problem: it is interactive, and a senior engineer drives it to find every security concern in your org, then manually validates each one, builds proof-of-concept exploits, tests business logic, attempts privilege escalation, and simulates real attacker techniques automation cannot. A scanner tells you what might be vulnerable; a pentest proves how an attacker exploits it and what the business impact is.

Will penetration testing disrupt our Salesforce production environment?

No. Our testing is designed to be safe and non-disruptive. We use read-only queries where possible, create test records that do not interfere with real data, and coordinate timing with your team. We can test in a sandbox first, though we recommend some production testing since sandbox configurations often differ. We have tested live Salesforce environments for large enterprises without incident.

Can you test Salesforce Communities and Guest User configurations?

Yes, and you should prioritize it. Communities with Guest User access are among the most exploited Salesforce attack vectors, and the 2024 account-takeover disclosures targeted Guest User misconfigurations specifically. We test guest permissions, community sharing settings, unauthenticated access points, and the boundary between authenticated and unauthenticated functionality.

Do you test custom Apex code and Visualforce pages?

Yes. Custom code is where the most critical vulnerabilities often hide. We test Apex classes, triggers, controllers, and Visualforce pages for SOQL/SOSL injection, improper input validation, "with sharing" versus "without sharing" mistakes, sensitive data in debug logs, hardcoded credentials, and business logic flaws, along with custom Aura and Lightning Web Components. We do not just read the code; we exploit it to prove real-world impact.

What Salesforce compliance requirements can penetration testing help with?

Our testing supports PCI DSS (Requirement 11.4), the HIPAA Security Rule, SOC 2 Type II, GDPR, and ISO 27001. Reports map findings to specific control requirements to make audits straightforward. For PCI DSS, if you store, process, or transmit cardholder data in Salesforce, annual penetration testing is mandatory and must cover your application, custom code, integrations, and external-facing components.

How do you test Salesforce AppExchange apps and third-party integrations?

We assess both the AppExchange apps installed in your org and the integrations connecting Salesforce to external systems. For apps, we review requested permissions, test for data leakage, and analyze their API calls. For integrations, we test authentication (OAuth, API keys, JWT), data transmission, endpoint security, webhook validation, and whether a third-party system can be leveraged to compromise Salesforce. A vulnerable integration can become a backdoor into your data.

Can you find issues introduced by recent Salesforce updates or configuration changes?

Yes, which is why periodic testing matters. Salesforce ships three releases a year, and each can change defaults or expose new vectors, while your team makes ongoing configuration and code changes. We test your current state for issues from recent updates, permission drift from accumulated changes, and misconfigurations that were not present at your last assessment.

What happens if you find critical vulnerabilities during testing?

We notify your team immediately rather than waiting for the report. For high-severity issues like exposed customer data, authentication bypass, or privilege escalation, we provide verbal notification with emergency mitigation guidance. After testing, you receive a detailed report with proof-of-concept exploits, remediation steps, and prioritized actions, plus a complimentary retest once you have implemented fixes.

Who performs the testing?

Senior US-based Raxis engineers holding certifications such as OSCP and OSCE, with hands-on Salesforce platform experience. No outsourcing, and no junior testers learning on your org.

How much does Salesforce penetration testing cost and how long does it take?

It depends on the complexity of your org: custom objects and fields, lines of Apex, number of integrations and APIs, whether you run Communities or Experience Cloud, the number of profiles and permission sets, and your compliance requirements. A focused assessment typically starts around $15,000 to $35,000 and takes one to four weeks. Comprehensive testing of a complex enterprise org with extensive customization runs $35,000 to $75,000 or more and takes four weeks or longer. Contact us for a quote sized to your implementation.

Request a quote

Tell Us What You Need Tested

We usually respond in one business day.

Please let us know what's on your mind. Include any details about your target environment, timeline, or compliance drivers.