Salesforce Penetration Testing
Salesforce penetration testing for a platform that is secure by default and configurable into almost anything. One guest user sharing rule gives anyone on the internet every matching record, no login needed. CREST-certified testers, fixed price from £4,180 for a 3-day single-platform scope, quoted within 24 hours.
- Unlimited retesting
- No rescheduling or cancellation fees
- Fixed quote within 24 hours
“I would highly recommend EJN Labs to any organisation seeking reliable, detailed, and well-managed penetration testing services, particularly for government or enterprise-level projects.”
“There wasn’t another company we could find that could deliver what we needed in the timeframe we needed. The client loved it, and we got instant ROI from the engagement.”
Nobody finds a flaw in Salesforce itself on a client engagement. What they find is an org where organisation wide defaults were relaxed for one use case, a permission set that granted View All to a team, and a profile that still has API access it never needed.
Why sharing, FLS and guest rules decide everything
The failure modes are specific and repeatable. Apex classes declared without sharing. Apex that queries in system mode, so field-level security never applies. A guest user sharing rule on an object nobody meant to publish. Organisation-wide defaults set to Public Read/Write. A connected app granted the full scope.
Declaring a class without sharing lets it access records the current user otherwise cannot, and sharing keywords never enforce object or field permissions. Apex on API version 66.0 or earlier runs in system mode by default, while 67.0 and later runs in user context. Sharing features can only add access beyond the org-wide default, never restrict it. See the Apex sharing keywords documentation.
We sign in as a standard user, a privileged user and an Experience Cloud guest. As each, we query objects through the API and the site endpoints, call every Apex method the components expose, and try to read fields the profile should hide. Anything a guest returns without logging in is a finding. A Salesforce pentest (Salesforce pentesting) covers all three areas: configuration, custom code and the public edge. ISO 27001, SOC 2, PCI DSS and Cyber Essentials Plus audits accept manual penetration test evidence. Scan-only evidence is generally insufficient.
SALESFORCE SPECIFICS
What We Actually Test in a Salesforce Org
Ten areas that apply because the platform is Salesforce, on top of the standard application checks. Every finding is verified, reproducible and mapped to OWASP, CWE and CVSS 3.1.
Object and field level security
Profiles and permission sets, field visibility, and what a low privileged user can actually read and change.
Sharing model
Organisation wide defaults, role hierarchy, sharing rules, manual shares and territory settings.
Guest and community access
Experience Cloud guest profiles, public objects, and records reachable without logging in.
Apex code
Sharing keywords, SOQL injection, controllers that return more than the interface shows, and code that runs as system.
Lightning components
Aura and Lightning Web Component controllers, client side checks, and data exposed to the browser.
Connected apps and integrations
OAuth scopes, refresh token handling, named credentials and the rights of the integration user.
Flows and automation
Automation that escalates privilege, writes unchecked input, or exposes data through a screen flow.
Data export paths
Reports, list views, Data Loader, the API and what can leave the platform without anyone noticing.
Installed packages
AppExchange packages, the permissions they hold, and their update posture.
Monitoring and audit
Event monitoring coverage, setup audit trail, login history and what a compromise would look like in the logs.
METHODOLOGY
What a Salesforce finding looks like
Written the way a finding appears in our reports. The example below is reconstructed from publicly documented research, with hosts, paths and identifiers redacted. We do not republish client findings, named or anonymised.
Guest user profile on a public Experience Cloud site exposes internal records
- Affected
- A public community site at [redacted], with a custom object used for case handover.
- What we found
- The guest user profile held read access on the custom object, and organisation wide defaults were not private. Querying the site endpoints without authentication returned records containing customer names, free text case notes and internal owner assignments.
- Why it matters
- Unauthenticated disclosure of customer case data at a volume limited only by page size, from a site that was intended to show marketing content and a contact form.
- Fix
- Enable the guest user record access controls, strip object and field permissions from the guest profile, set sharing to private and grant access through sharing sets, then review every object reachable from the site rather than only those used on the page.
Reconstructed from public research: Salesforce guest user security settings documentation, and the published research on unauthenticated data exposure in Experience Cloud communities (Varonis, 2021).
Salesforce Penetration Testing: From Scope to Attestation
CREST-aligned methodology built on OWASP Web Security Testing Guide, OWASP ASVS, NIST SP 800-115, and PTES. Each finding maps to all four standards plus your specific compliance regime.
Reconnaissance
Application mapping, technology fingerprinting, content discovery, parameter enumeration, authentication-flow analysis, role-matrix construction.
Vulnerability Assessment
Authenticated and unauthenticated automated scanning across every user role, plus targeted manual checks for known weakness patterns.
Manual Exploitation
Hands-on testing by a CREST-certified pentester. Business-logic exploitation, chained vulnerabilities, privilege escalation, impact validation.
Reporting + Retest
Executive summary, technical report with CVSS scores and reproduction steps, walkthrough call, free retest after remediation, attestation letter.
CREDENTIALS
Verified Accreditations Auditors Accept
Every credential below is independently verifiable. UK procurement teams, FCA supervisors, ISO 27001 / SOC 2 auditors, and cyber insurance underwriters all recognise these standards.
GET YOUR QUOTE
Get a CREST Salesforce assessment pen test quote in 24 hours
A fixed-price quote back in one business day, from a named CREST assessor. No sales pipeline, no chasing.
- CREST and IASME accredited. Testing your auditors and clients already recognise.
- Fast-track testing within 24 hours where required. Free retest of every fix included.
- Live findings via your client portal, not a four-week PDF.
- Fixed price from £4,180 for a small, single-scope engagement, agreed up front. Most engagements run £5,860 and up. No day-rate surprises.
Dan WilcocksonFounder, CelloriUnder NDA Further named references available on a scoping call.
- We reply within one business day with a fixed-price quote from a named CREST assessor.
- You approve the scope and we book a start date, usually within 24 hours.
- Live findings land in your client portal as we test, with a free retest of every fix.
Get your fixed pen test quote in 24 hours
Quote request received
We will reply within one business day with your fixed-price quote from a named CREST assessor.
Your data stays with us. No newsletter signup.
or book a 20-min scoping call first
We reply within one business day. Your data stays with us. No newsletter signup.
COMPLIANCE READY
Reports Mapped to Every Framework
Findings are explicitly tagged to the relevant control reference. Your audit team submits the report directly without translation work.
ISO 27001:2022
Annex A.8.8 management of technical vulnerabilities plus A.5.15-5.18 and A.8.2-8.5 access control validation.
SOC 2 Type I & II
CC6 logical access, CC7 system operations, CC8 change management evidence.
PCI DSS
Requirement 11.4 application penetration testing across cardholder data environments, including ecommerce penetration testing for online retail platforms.
FCA SYSC
SYSC 4.1.1R, 6.1.1R, 13 mapped to each finding for FCA-regulated firms.
UK GDPR
Article 32 effectiveness testing, customer-data security controls, ICO-acceptable evidence.
Cyber Essentials Plus
Direct certification through our IASME body status, single-vendor delivery.
PRICING
Transparent Salesforce Penetration Testing Pricing
Pricing depends on app complexity, user-role count, business-logic depth, and integration surface. The day count flexes; the included deliverables stay the same across all engagements.
3 to 5 testing days
Single user role, basic CRUD application, marketing website with auth. Around 5 working days from kickoff to report.
Get a fixed quote5 to 7 testing days
Multi-role SaaS, business application with payment integration. Around 8 to 12 working days from kickoff to report.
Get a fixed quote7 to 9 testing days
Multi-tenant platform, complex authorisation matrix, integration-heavy applications. Around 15 to 20 working days from kickoff to report.
Get a fixed quotePart of Technologies We Pen Test. These are examples of the stacks we publish pages for, not a complete list. If yours is not here we still test it. Related pages:
BY SECTOR
Salesforce Penetration Testing for Your Sector
Sector-specialist scoping for UK businesses with sector-specific compliance regimes and threat models.
Fintech & FCA-Regulated
FCA SYSC, Open Banking FAPI 1.0, PSD2 SCA, payment-flow scrutiny, KYC/AML testing.
Fintech sector pageSaaS Companies
SOC 2 Type I & II evidence, multi-tenant boundaries, role escalation, customer-tenant isolation.
SaaS sector pageLaw Firms
SRA Cyber Standard, privileged data, conveyancing fraud defence, partner-tier procurement.
Law firm sector pageHealthcare
NHS DTAC, DSP Toolkit v6, UK GDPR Article 32, EHR systems, telehealth platforms.
Healthcare sector pageInsurance
FCA / PRA Operational Resilience, cyber underwriting, claims data, broker portals.
Insurance sector pagePublic Sector
CCS / G-Cloud framework, NCSC-aligned, citizen-facing services, PSN-compliance scrutiny.
Public sector pageWHY EJN LABS
What You Get From Salesforce Penetration Testing
Six concrete differentiators competitors don’t all match.
CREST-Certified Testers, Verifiable
Every test by a CREST-certified pen tester (CRT, CCT APP, CCT INF where applicable). Verify our company status at crest-approved.org.
24-Hour Startup, Where Required
From signed scope to active testing in a single business day for incident response, audit deadlines, or regulator-driven timelines.
Live Findings, Not 4-Week PDFs
Critical issues reported during testing through your client portal. Your team remediates while testing continues.
Audit-Ready Reports
Executive summary plus full technical report with CVSS scores and explicit framework mappings (ISO 27001, SOC 2, PCI DSS, FCA SYSC).
Free Retests, Standard
Verify remediation of every finding before close-out. Letter of attestation for audit submission included. Most competitors charge £1,500-£3,000 per retest.
UK-Based CREST Testers
Every engagement performed by vetted, UK-based CREST-certified testers, matched to your needs, security clearance, and compliance scope.
FAQ
Frequently Asked
Do you need a full sandbox?
A full or partial copy sandbox is ideal. Testing in production is possible with tight limits, but we prefer a sandbox that mirrors the permission model.
Do we have to tell Salesforce before you test our org?
No. Salesforce’s help article says that since 31 January 2023 customers no longer need prior approval and can start without notifying Salesforce, provided the assessment follows the Security Assessment Agreement. That agreement limits tests to your own accounts, bars denial of service, and restricts automated testing to Friday 21:00 to Sunday 23:59 PST. We test your configuration and custom code, never other customers’ accounts or Salesforce infrastructure.
What accounts do you need?
A standard user, a privileged user if you have one, and guest access to any Experience Cloud site in scope.
Do you review Apex code line by line?
We review the classes reachable from what we can call. A full source review is the secure code review service.
Can you test an Experience Cloud site only?
Yes, and it is a common scope. Guest access is where the surprising findings usually are.
What about other platforms such as SAP or ServiceNow?
Ask us. The approach is the same and we will tell you honestly whether we have tested that platform before.
Our org-wide default is Public Read/Write on an object. Is that a problem?
It means every internal user can read and edit every record of that object. Sharing rules and the role hierarchy cannot take that back, because other record access features can only grant additional access. We sign in as users in different roles and query records they do not own.
Our Experience Cloud guest profile has Read on some objects. Is that a problem?
It can be. Salesforce recommends no guest access to almost all objects and Read at most where there is a business case. A guest user sharing rule then gives anyone, with no login, access to every record matching its criteria. We query the site endpoints unauthenticated and list every object and field that answers.
Our connected app has the full scope. Is that a problem?
The full scope allows access to all data accessible by the logged-in user and encompasses all other scopes, so a stolen token reaches everything that user can. Add refresh_token and the app can keep acting while the user is offline. We compare the scopes each connected app holds with what its integration needs.
20+ CREST-accredited testing services in one place
Web, mobile, API, cloud, AI, infrastructure, red team. Pick the test that fits your environment.
Get your Salesforce org tested properly
Tell us about your org and any public community sites. You will have a fixed scope and a number within 24 hours.
