Vulkro for Salesforce
Most Salesforce risk isn’t in the code.
Vulkro checks your code and your org’s settings together, and shows how a visitor to your public site could reach your data.
Set in SetupChanged with clicks, not commits, so a scan of the code never sees it.
Written in codeA check of the settings never reads it, so it never learns what runs next.
SF-GUEST-LIVE-002sf-access-guest-permset-escalationapex-without-sharing-class-infoapex-crud-fls-gap-exposed-methodsf-guest-meta-sensitive-field-readOne path from a stranger to bank details. Vulkro flags the root cause: one class, one change.
01The evidence
Every step comes with its proof.
Open any step to see the exact setting or line of code behind it, then fix the one place that closes the whole path.
Recent Salesforce attacksWhoGuest user
Anyone on the internet is this user.
The customer site is live and lets people in without a login. Salesforce serves every one of them as the same guest user, so whatever it can reach, a stranger can reach.
SF-GUEST-LIVE-002
<CustomSite><active>true</active><guestProfile>Customer Portal Profile</guestProfile><siteType>ChatterNetwork</siteType></CustomSite>
Make the invoice code respect sharing and field access. One change in one class closes all five steps.with sharing · WITH USER_MODE
02What it checks
Your code and your org, read as one.
814 checks across both halves (vulkro-sf 0.34.1), joined into the paths an attacker would take.
The full check catalogueIn your code
642checks on code and project files
- Server codeApex classes and triggers
- Pages and componentsLWC, Aura, Visualforce
- AutomationFlows
- AI agent actionsAgentforce
- AI responsesEinstein and LLM output
- Project settingsMetadata
In your org
172checks on the live org’s settings
- Who can sign in, and howMFA, sessions, login policy
- Who holds which powersProfiles, permission sets
- Who sees which recordsSharing rules, org-wide defaults
- What visitors can reachSites, guest user
- Which apps are connectedConnected apps, OAuth
- Which services it callsNamed Credentials
- Read-only. It never changes the org and never deploys.
- Reads settings and definitions, never your business records.
- Your code is scanned on your machine. No AI in detection.
Checks on the live org are part of Pro and of Vulkro Cloud.
03For ISVs
Catch Security Review issues before you submit.
The AgentExchange (formerly AppExchange) Security Review finds problems after you submit. Vulkro checks the same areas while you build.
Security Review, in depthAgentExchange (formerly AppExchange) Security Review checklist- Save $999
- Salesforce charges $999 for every review attempt on a paid solution, the first one included (Salesforce). Each failed round you avoid is one fee you keep.
- Save weeks
- A review typically takes four to five weeks, in Salesforce’s words. Every fix and resubmit starts that wait again.
- SF-ASRR-001Authorization: CRUD, FLS and sharingData read with no access check
apex-crud-fls-unenforced-statementGap - SF-ASRR-002Input validation and output encodingSearch text built into a query
apex-taint-soql-injectionGap - SF-ASRR-003Secrets and credential handlingReady
- SF-ASRR-004External communication and integrationsReady
- SF-ASRR-005CryptographyReady
- SF-ASRR-006Logging, error handling and sensitive dataCustomer records written to the browser console
lwc-console-log-record-dataGap
The fee and the timing are Salesforce’s, not Vulkro’s. The readiness checklist, the report for the reviewer and the CI gate are all part of Salesforce Pro.
04The product
See it in the product.
Vulkro Cloud: the shared workspace for your team’s orgs, set up for you with a 14-day trial. The same findings show up wherever you work.
Vulkro Cloud- Local console Your scan in the browser, served from your own machine.
- macOS
- Linux
- Windows
- VS Code extension The problem on the line that causes it, as you write it.
- VS Code
- Cursor
- Windsurf
- VSCodium
- CI pipelines Hold the deploy until the build is clean.
- GitHub Actions
- GitLab CI
- Bitbucket
- Jenkins
- CircleCI
- AI coding agents Your assistant asks Vulkro instead of guessing.
- Claude Code
- Cursor
- Codex
- GitHub Copilot Chat
05Further reading
Salesforce security, in more depth.
- With sharing vs without sharing in Apex, and inherited sharingWhat each sharing keyword enforces, and which one a class should declare.Article
- Salesforce security audit: a repeatable method for consultanciesThe order to check an org in, and what to hand the client.Article
- Salesforce Health Check vs a security audit: what each coversWhere the built-in score stops and an audit of code and access starts.Article
- A read-only Salesforce security auditWhat a live-org scan can see without changing anything, and what it cannot.Article
- Salesforce Flow governanceWho builds, activates and runs your flows, and in whose context.Article
- AgentExchange Security Review checklistWhat to check before you submit a package for review.Article