Cloud and SaaS
Salesforce Penetration Testing
Validate record, field and function permissions in the deployed Salesforce organisation. The assessment examines custom logic and integrations that could expose customer information or undermine transaction control.
01 / Overview
Assessment objectives and control obligations
Salesforce testing reconstructs effective entitlements from profiles, permission sets, sharing rules and record ownership. Representative internal, external and guest identities support differential access checks within the authorised organisation and Experience Cloud sites. Object permissions, field-level security and record sharing are assessed as distinct enforcement obligations.
Custom Apex, Lightning and API operations are examined against their API version and execution mode. Integration grants and connected applications receive separate authority analysis. Findings establish whether direct requests or privileged code paths bypass intended restrictions, with shared platform infrastructure and unrelated organisations excluded.
02 / Technical analysis
Failure mechanisms and security implications
Record sharing and field permissions are separate controls. Code execution mode can alter both. We retain effective permissions and API version so correction addresses the actual enforcement point.
03 / Scope
Technical coverage and authorisation boundaries
Coverage is agreed in writing before testing begins. The rows below describe what this service normally examines. Exclusions, testing windows and escalation contacts are recorded in the rules of engagement.
- Access model
- Profiles, permission sets, sharing and record ownership.
- Custom and guest paths
- Apex, Lightning, Experience Cloud and public endpoints.
- Integrations
- OAuth grants, connected applications and API authority.
- Supporting tools
- Environment-appropriate instrumentation may include Salesforce CLI, Apex analysis, Burp Suite, Postman, Salesforce Health Check. Selection follows the investigative objective, compatibility requirements and approved operating constraints. Automated output requires corroboration against implementation evidence or observed execution before classification as a substantiated finding.
04 / Methodology
Investigation and validation methodology
Threat-informed test design aligns architectural trust boundaries, attacker prerequisites and consequential business outcomes. Automated discovery supports attack-surface coverage; manual validation establishes reachability, effective authority and the causal mechanism of each substantiated control failure.
01
Scope and safeguards
Before active work
We agree assets, test identities, techniques, windows, exclusions and stop conditions, and confirm required third party permissions.
02
Define representative access
Prepare users and records with known ownership and restrictions.
03
Compare interface and direct behaviour
Examine selected operations using authorised application and API paths.
04
Review and verification
Agreed delivery
Findings pass technical review. We explain remediation and, where agreed, verify the correction during the retest window, including relevant bypass cases.
05 / Assessment options
Access models and evidential confidence
Supplied access determines investigative reach, validation depth and evidential confidence. The proposal records the access model, supporting material and unresolved coverage limitations; no model implies unrestricted authority or exhaustive verification.
- Black box
- Testing starts without supplied credentials or internal design material. External exposure is examined, while authenticated workflows may remain inaccessible.
- Grey box
- Representative accounts and selected design information support direct comparison of roles, tenants and sensitive workflows.
- White box
- Source, configuration and design evidence support root cause analysis. Runtime and access limitations are still recorded.
06 / Deliverables
Decision-support and verification deliverables
Deliverables distinguish what was observed, what was concluded and where the evidence stops. The agreed scope states which evidence, review sessions and retesting are included.
Executive summary
The summary explains the demonstrated exposure, the business functions affected and the treatment decisions required, including material uncertainty.
Technical findings
Each confirmed issue records the affected assets, prerequisites, reproduction evidence and a specific remediation. Technical severity is presented separately from business priority.
Coverage and limitations
The record identifies the systems, identities and conditions tested, together with exclusions and assumptions that affect interpretation.
Treatment and retest status
Recommendations are sequenced by risk, dependency and ownership. Any agreed retest records resolved, partly resolved and unresolved issues without implying a new assessment.
Service specific evidence
User context, record ownership, execution mode and sanitised requests define reproducible findings.
07 / References
Applicable technical references
References are selected for the technology and objective in scope, and the edition applied is recorded. A framework mapping supports review; it is not certification or proof of complete compliance.
- Salesforce secure Apex guidance
- Official guidance describes access enforcement in Apex. The reviewed API version and explicit execution mode are recorded because defaults and mechanisms can differ.
- OWASP API Security Top 10
- The 2023 risk taxonomy distinguishes object, property and function authorisation, resource consumption and inventory risks. It is not an exhaustive test specification.
08 / Safeguards
Operational safeguards and evidence governance
Active work is conditional on written authority from the appropriate asset owner and approved rules of engagement. The operating plan specifies permitted procedures, testing windows, prohibited actions, third-party restrictions and nominated stop authority. Unexpected instability or suspected genuine compromise triggers suspension of affected activity pending the client’s operational decision.
Evidence governance applies purpose limitation, data minimisation and access proportionality to collection, transfer, processing, retention and disposal. The signed terms define authorised recipients and any external processing arrangement. Publication, secondary use and disclosure of client material require the applicable written permission.
Conclusions distinguish substantiated exposure, untested consequence and residual uncertainty. Each material finding identifies the control obligation, causal mechanism, observed outcome and verification criteria for the proposed treatment. Technical severity informs analysis; prioritisation and acceptance of residual risk remain decisions for the client’s authorised risk owner.
Salesforce shared infrastructure and unrelated organisations are excluded.
09 / Suitability
Commissioning criteria
Use for new external portals, custom development or changes to sharing and integration permissions.
Next step
Define the assessment you need
Tell us the business decision, the systems involved and any operational constraint. We will explain the coverage proposed, the access required and the evidence the engagement can provide.
- Confidentiality first
A mutual confidentiality agreement is signed before any technical detail is exchanged, so scope discussions can happen safely.
- Scope and cost in writing
Deliverables, access expectations, timeline and fee are confirmed before the engagement begins, and a scope change needs agreement.
- Answered by the delivery team
The consultants who scope an engagement are the consultants who perform it and explain the result to your team.
