Skip to contentIntroducing the Integration Factory
Back to Blog
Marketplace

Salesforce Security Review Help: What a Partner Can Do and What Stays With You

Sunny Chauhan

A partner can do most of the work that decides whether your managed package passes the Salesforce security review. A partner can build the package to Salesforce's secure coding rules and run the required scans. It can also write the false-positive document, set up the test org reviewers log into, and answer findings. What a partner can't do is take over the parts Salesforce ties to your company, or promise the result. The review starts from your own Partner Console, your company signs the security attestations, and Salesforce says plainly that "People make the final decision on each review," per its security requirements for ISV partners.

For a SaaS company, the decision is less about whether to get help and more about which half of the work to hand off. The build and the submission package can move outside your team. The security program, the listing and the follow-up reviews stay with you after launch. Appnigma's marketplace apps service is built around that split. It covers "a native app, marketplace listing preparation, and review support." Review support means "Salesforce security review preparation and responses." If you want the full list of requirements instead, start with our Salesforce security review guide.

Updated October 2026. Checked against Salesforce's ISVforce Guide, Secure Coding Guide and Trailhead. An earlier version of this post promised a guaranteed pass, offered to cover resubmission costs, described a drag-and-drop builder and told two client stories. Salesforce controls approval, and none of those claims match what Appnigma offers today, so they are gone. The update also corrects the claim that declarative builds enforce field-level security by default.

What a partner can do and what your company still owns

Salesforce's own partner program describes outside builders. Its ISV track overview says product development outsourcers "can help architect and design a commercial app" or "augment your development team." The review process itself, though, is built around the ISV (independent software vendor, the company that owns the app). The table splits the work along that line.

TaskCan a partner do it?What Salesforce ties to your company
Build the package to the secure coding rulesYesNothing, this is engineering work
Run Code Analyzer and the Source Code Scanner (Checkmarx)Yes, with access you grantScanner runs come from your Partner Security Portal account
Scan or pentest your external API and web appYes, with your permissionThe endpoints are your infrastructure
Write the false-positive documentYesYou submit it
Set up the Developer Edition test org for reviewersYesCredentials must work when Salesforce logs in
Start the review in the Partner Console wizardOnly through your partner accountNeeds a Partner Community login with Manage Listings
Pay the review feeNoYour company pays for a paid solution
Security policies, certification reports, security contactsHelp drafting onlyYour company's program and attestation
Answer findings and fix codeYesResults email your listed security contacts

Three rows deserve a closer look. The wizard runs inside the AgentExchange Partner Console, and Salesforce notes in its publishing FAQ that "the Manage Listings permission provides access to all Partner Console features." Giving an outside engineer that permission gives them your listings too, so most teams keep the login in house and have the partner prepare everything they upload. The security program row is not paperwork you can borrow. Salesforce asks every partner to have "a security program that demonstrates your company's commitment to security" and to confirm its security leadership contacts "every six months," per Security Policy Requirements. And the results row matters for speed. Findings go to the security review contacts on your Partner Console and the Add Contacts page, per Feedback During Technical Testing, so put the person who will fix the code on that list.

Can anyone guarantee you pass the Salesforce security review?

No. Salesforce's review guidelines state that even after a review "Salesforce makes no guarantees regarding the quality or security of any Partner Application," and the decision on your app is made by Salesforce's Product Security team. The review is also sampled. Salesforce calls it "a black-box, time-limited process" and says reviewers can't list every instance of an issue, per How the AgentExchange Security Review Works. A partner who promises approval is promising an outcome nobody outside Salesforce controls.

Appnigma's own page answers the same question the same way. The marketplace apps FAQ asks "Can you guarantee approval or a faster review?" The answer is "Platform approval and queue timing are controlled by Salesforce or HubSpot." What a partner can credibly commit to is the part it controls, a complete submission, scan reports with every finding fixed or explained, and fast responses when results arrive.

Pass-rate claims need the same reading. Salesforce separates a review that is returned (something was missing, resubmitting costs nothing) from one that fails (real findings, a paid retest of a new version), per its review stages page. Ask any firm quoting a first-time pass rate how it counts returned reviews and how many reviews sit behind the number. Salesforce's own baseline is modest. "Many solutions don't pass on the first try," according to its follow-up review page, and Trailhead's submission unit adds that "most submissions pass on the second attempt."

Does a declarative build make the review smaller?

Less custom Apex means less code to scan, but it doesn't shrink the review the way the earlier version of this post claimed. Flows are reviewed too, and most of them don't enforce object and field permissions by default. Salesforce's secure coding guidance for flows says flows started from the UI run in user mode. "Any other flow runs in System Mode Without Sharing by default." In system mode, "CRUD/FLS rules aren't enforced." CRUD/FLS means object permissions (create, read, update and delete) plus field-level security. Record-triggered flows run in system mode. Salesforce's 2023 list of the top 20 review findings names flows set to run in system mode without sharing as one cause of its third most common finding, the sharing violation.

Packaging adds a twist that in-house admins never hit. A flow shipped in a managed package can be called by "any code on the subscriber org," in any context, per the same flow guidance. So a flow you designed for one screen can be started from automation you have never seen in a customer's org. Salesforce recommends setting the run mode explicitly on every flow. The scan requirement doesn't go away either. Trailhead's submission unit says "if you're listing a managed package, you're required to upload your Salesforce Code Analyzer scan reports," whether the package holds Apex or only flows.

Apex went the other direction this year. From API version 67.0, Apex "runs in user context by default," per the Apex versioned behavior changes, and classes without a sharing declaration run with sharing. A new package written at the current API version now starts from the safer default in code and the riskier default in background flows. The old rule of thumb that clicks are safe and code is risky no longer describes what reviewers find.

The bigger scope question for most SaaS companies sits outside Salesforce. If your package calls your own API or your users sign in to your web app, those endpoints are in scope. Salesforce's rule is "wherever the customer goes, we go," per Required Materials for Security Review Submission. You submit reports from a dynamic scanner (DAST, a tool that attacks the running app) or full pentest results, preferably from within 30 days of submission, per the Partner Security Portal help. The package can be small and declarative and the review can still spend most of its time on your backend.

What one failed round costs compared with getting help

The case for outside help is easiest to judge in weeks, because Salesforce publishes its own estimates. A first pass takes "approximately 4 to 6 weeks," per Act on Security Review Results. A failure that needs code changes means a new package version, which goes back through 1 to 2 weeks of submission verification and a 2 to 3 week retest, per the ISVforce Guide. Remediated retests are paid for paid solutions, while returned submissions and false-positive responses are not.

Here is the arithmetic from those published estimates, not from a measured project. A clean pass ends 4 to 6 weeks after submission. One failed round with code changes ends 7 to 11 weeks after submission, plus however long your engineers need for the fixes. Fixes usually take longer than the published figures suggest, since Salesforce asks you to treat each finding as one of the "representative examples of the types of issues you must fix" and to search the whole codebase for the same pattern. For a SaaS company with an enterprise deal waiting on the listing, that is one to two months of a sales cycle. That gap, not the review fee, is what outside help should be priced against.

The published Appnigma example fits inside the first range. Warmly's project took eight weeks from kickoff to launch on AgentExchange, "including six weeks of Salesforce security review," and the marketplace apps page calls it "a project example, not a guaranteed schedule."

Questions to ask before you hire security review help

Use these to separate a partner who has shipped packages through review from one who has read about it. Each question maps to a place where submissions get returned or fail.

  • Who will start the review in the Partner Console, and whose login will it use?
  • Which scans does our architecture need, and who will scan or pentest our external API?
  • Will you write the false-positive document, and do you know which findings Salesforce expects to see explained? For Checkmarx that means every issue not labeled Code Quality, per Document Responses.
  • What run mode will each packaged flow use, and why?
  • Where will API keys and other secrets live? The Secure Coding Guide points to protected custom metadata for package-wide secrets, protected custom settings for secrets set at install, and Named Credentials for external services.
  • If our package uses OAuth to call back to our service, does the app meet Salesforce's connected app and external client app requirements, such as PKCE and refresh token rotation?
  • Who answers findings when results arrive, and how fast?
  • Who handles the periodic re-review after launch?

The last question is the one teams forget to ask. A partner whose engagement ends at approval leaves you holding the re-reviews, and those come with deadlines. For choosing the build partner itself, including code ownership and how many review rounds a quote covers, see what an AppExchange development company's services should include.

Help Salesforce gives you before you hire anyone

Salesforce runs two kinds of free office hours for ISV partners, booked through the Partner Security Portal, per Types of Security Review Office Hours. Operations office hours cover "logistics and submission requirements," such as which components are in scope. Technical office hours with Product Security cover vulnerabilities and questions like "What security scan results can I regard as false positives?" Salesforce's submission page suggests booking a technical slot for 3 to 4 weeks after you submit, so it lands as results arrive.

Office hours answer questions. They don't build the package, run your pentest or write your documentation, and that is where the time goes for a first submission. A reasonable split for a team doing its first review is to use office hours for scope questions and hand the build and the submission package to whoever will also handle the follow-ups.

After you pass, the review keeps coming back

Passing makes the listing public on AgentExchange (formerly AppExchange) and turns on features such as push upgrades. New versions built on the passed version inherit its status with "a quick attestation," per Trailhead. Salesforce says that saves "time, resources, and security-review fees," per Listing Readiness for Managed Packages. The work doesn't end there. Trailhead says solutions are "typically" reviewed again once a year. A periodic re-review "takes up to 6 weeks," per Submit Your Solution for Periodic Security Re-Review. Fees apply, and when Salesforce finds problems it gives a fix window of "typically 60 days," per Periodic Security Re-Reviews. Miss a re-review and approval "expires for all versions of the solution," per Expired AgentExchange Security Review.

That is why the maintenance question belongs in the first conversation with any partner. Appnigma scopes marketplace apps as standalone projects. The marketplace apps page says "ongoing fixes, upgrades, and customer-specific changes can be covered by a separate maintenance retainer." If your app also needs integrations maintained per customer, the done for you service covers implementation and ongoing maintenance from a named integration engineer.

Frequently Asked Questions

Can a consultant submit the Salesforce security review for us?

Not on their own account. The review starts in your company's AgentExchange Partner Console, which needs a Partner Community login with the Manage Listings permission. A partner can prepare every file you upload and be listed as a contact.

Can anyone guarantee we pass the security review?

No. Salesforce's Product Security team makes the decision, and Salesforce says people make the final call on each review. A partner can guarantee a complete submission and fast responses, not approval.

Does a Flow-only managed package still need the security review?

Yes. Any managed package listed on AgentExchange must pass and include Code Analyzer scan reports. Flows that aren't started from the UI run in system mode without sharing by default, so reviewers check their run mode.

How long does the review take with outside help?

Salesforce's queue is the same for everyone, about 4 to 6 weeks for a first pass. Help shortens the weeks before you submit and lowers the chance of a 3 to 5 week retest.

Can Appnigma help with our security review?

Yes. Appnigma's marketplace apps service builds the native app and covers listing preparation and review support, meaning security review preparation and responses to findings.

About the author

Sunny Chauhan is the co-founder and CEO of Appnigma AI, which builds and maintains customer integrations and native Salesforce and HubSpot apps for B2B SaaS teams. Before Appnigma, he was on Salesforce's AppExchange team, where he worked with more than 300 SaaS partners. He has spent close to a decade on the Salesforce platform, including work at Zennify, and holds Salesforce certifications including Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate.

Sources

  1. Salesforce Developers, ISVforce Guide, Security Requirements for ISV Partners
  2. Salesforce Developers, ISVforce Guide, Pass the AgentExchange Security Review
  3. Salesforce Developers, ISVforce Guide, How the AgentExchange Security Review Works
  4. Salesforce Developers, ISVforce Guide, AgentExchange Security Review Stages
  5. Salesforce Developers, ISVforce Guide, Access the Partner Console
  6. Salesforce Developers, ISVforce Guide, Publishing FAQ
  7. Salesforce Developers, ISVforce Guide, Security Policy Requirements
  8. Salesforce Developers, Secure Coding Guide, Flow Design Considerations
  9. Salesforce Developers, Apex Developer Guide, Versioned Behavior Changes
  10. Salesforce Developers Blog, The Top 20 Vulnerabilities Found in the AppExchange Security Review (2023)
  11. Salesforce Developers, ISVforce Guide, Required Materials for Security Review Submission
  12. Salesforce Partner Security Portal Help
  13. Salesforce Developers, ISVforce Guide, Act on Security Review Results
  14. Salesforce Developers, ISVforce Guide, Document Responses to Scan Findings
  15. Salesforce Developers, Secure Coding Guide, Storing Sensitive Data
  16. Salesforce Developers, ISVforce Guide, Secure Connected Apps and External Client Apps
  17. Salesforce Developers, ISVforce Guide, Types of Security Review Office Hours
  18. Salesforce Developers, ISVforce Guide, Periodic Security Re-Reviews
  19. Salesforce Developers, ISVforce Guide, Expired AgentExchange Security Review
  20. Trailhead, Submit Your Solution for Security Review
  21. Salesforce, AgentExchange ISV Track Overview (PDF)

Which integration is your next deal waiting on?

Bring the customer requirements and your current setup. Get a clear scope and delivery timeline to take back to them.