Home >> Articles >> The Salesforce Security Review Is Not A Horror Movie. How To Pass It On The First Try

The Salesforce Security Review Is Not A Horror Movie. How To Pass It On The First Try

Salesforce security review checklist for an AppExchange app with scanner results and fixes
APPEXCHANGE / SALESFORCE SECURITY REVIEW The Security Review Is Not A Horror Movie How to pass it on the first try CRUD and FLS checked Scanners run clean False positives explained TRUESOLV.COM
Calm confidence, not fear. The bats fly away from a prepared app.

For many ISV teams, the scariest email of the year starts with “Unfortunately”. 🦇

Last updated October 2026

The Salesforce security review is strict, but it is not mysterious. Most apps fail for the same handful of reasons, and every one of them can be fixed before you submit. Here is what reviewers check and how to pass on the first try.

Key takeaways
  • Every app listed on AppExchange must pass the Salesforce security review first
  • The fee is currently $999 per attempt for paid apps and free for free apps
  • Plan for about 6 to 9 weeks for the first review including queue time, and 2 to 3 weeks for a resubmission
  • Missing CRUD and field level security checks are the most common reason apps fail
  • Run Salesforce Code Analyzer and the partner source scanner before you submit, and explain every false positive
FIRST SUBMISSION, ABOUT 6 TO 9 WEEKS Prepare and scanYour team, before submit QueueWaiting for a reviewer Review and testingCode, config and endpoints IF IT FAILS, RESUBMISSION ABOUT 2 TO 3 WEEKS Fix every findingRerun scanners, update explanations ResubmitPaid apps pay the fee again Listed
Durations from a 2026 partner guide. Confirm in the Partner Community before you plan a launch date.

What is the Salesforce security review?

The Salesforce security review is the mandatory security assessment every app must pass before it is listed on AppExchange. Reviewers look at your code, your configuration and any external services your app connects to, and they test it the way an attacker would.

It exists for a good reason. Customers install your app into the system that holds their most sensitive data, and the review is what lets them trust an app from a company they have never met. That protects every customer on AppExchange, including yours.

What do reviewers actually check?

  • Code scan results. Reports from Salesforce Code Analyzer and the source code scanner available through the Partner Security Portal
  • CRUD and field level security. Whether your Apex respects what each user is allowed to see and edit
  • Sharing. Whether classes run with sharing unless there is a documented reason not to
  • Injection and XSS. Dynamic SOQL built from user input, and unsafe output in Visualforce or LWC
  • Secrets. Where API keys and credentials are stored, and whether they ever appear in logs or code
  • External endpoints. A dynamic scan report for any web service your app calls, and secure TLS on every endpoint

Why do apps fail the security review?

Missing CRUD and field level security checksUse WITH USER_MODE in SOQL and AccessLevel.USER_MODE for DML.
“without sharing” with no documented reasonDefault to with sharing and write down every exception.
Dynamic SOQL built from user inputUse bind variables or escape the input.
Secrets in code or custom settingsMove them to Named Credentials or protected custom metadata.
Outdated JavaScript librariesUpdate or remove anything with known vulnerabilities.
Unexplained false positivesReviewers treat them as real until you explain them.
// Respect the running user's permissions in queries and DML
List<Account> accts = [SELECT Id, Name FROM Account WITH USER_MODE LIMIT 50];
Database.update(accts, AccessLevel.USER_MODE);
User mode enforces object and field level security for the running user, the fix reviewers most often ask for.
🦇

Preparing an AppExchange app?

Book a pre review audit. We check your code and architecture with a reviewer's eyes before you submit.

How do you prepare for the security review?

1
Design for security from the first sprintDecide on user mode, sharing and secret storage before the first feature ships.
2
Run Salesforce Code Analyzer on every pull requestFix findings while the code is still fresh in someone's head.
3
Fix or document every findingEach false positive gets a short written explanation.
4
Scan your external endpointsSince the hosted Chimera scanner was retired in June 2025, teams run OWASP ZAP or Burp Suite and attach the report.
5
Prepare the submission packageA test org with sample data, credentials, architecture notes and your false positive explanations.
6
Do an internal mock reviewBefore you submitSomeone who did not write the code tries to break it before Salesforce does.

What happens if you fail?

Failing is common, and it is not the end of the road. The report lists each finding with its location and category. Fix every item, including the ones that look minor, rerun the scanners and resubmit with a short note on what changed. A resubmission usually takes 2 to 3 weeks, and paid apps pay the fee again for each attempt, so a careful first submission saves both time and money.

How do we help ISVs?

We build and maintain our own AppExchange products, so we go through the same process as our clients. Five of our apps are listed on AppExchange, including True Time Tracker and True Field History.

For one client we built a user management package that handles profiles, roles and permission sets for an org with 1,000+ users. It passed the Salesforce security review and brought configuration errors down to zero. 🧙

5own apps listed on AppExchange
1,000+users managed by the package we built
0configuration errors after it passed the review

See the user management AppExchange package case, browse our own apps, or read about our AppExchange app development services. Agencies can use the same team under their own brand through white label Salesforce development.

Common questions

How long does the Salesforce security review take?

Plan for about 6 to 9 weeks for a first review, including time in the queue and the review itself. Resubmissions after a failed review usually take 2 to 3 weeks. Minor version updates are often approved faster unless they add new objects, callouts or major architecture changes.

How much does the Salesforce security review cost?

The fee is currently $999 per submission attempt for paid apps and nothing for free apps. Paid apps pay again for each resubmission, so fixing issues before the first attempt is the cheapest path. Check the current fee in the Partner Community before you budget.

Do free apps need a security review?

Yes. Every app listed publicly on AppExchange must pass the security review, whether it is paid or free. Free apps do not pay the review fee, but they go through the same checks for code, sharing, data access and external endpoints.

Can I resubmit after failing the Salesforce security review?

Yes. Fix every finding in the report, rerun the code scanners, update your false positive documentation and resubmit. There is no limit on attempts, and most teams that fix the full list pass on the next try.

The security review is only scary when it is the first time anyone looks at your code with an attacker's eyes.

🦇

Book a pre review audit

We review your code, architecture and submission package before Salesforce does.

If you are preparing an AppExchange app, book a pre review audit with us, and follow TrueSolv on LinkedIn for more guides for Salesforce product teams.

Share:
Free Consultation

Ready to solve your Salesforce challenges?

Get a free consultation with our certified Salesforce experts. No commitment required.

See our packages →