Salesforce Security Readiness & Compliance Dashboard

Salesforce is changing a long list of security rules. Some already changed; others change later. This page checks your org against every one of them and tells you, in plain words, what is broken, what is about to break, and what to do about it. It works with any org — Production or any kind of sandbox. It only reads. It never changes anything in your org.

1 · Connect to an org

Not connected
Production: https://mycompany.my.salesforce.com · Sandbox: https://mycompany--uat.sandbox.my.salesforce.com. Paste the origin only — no path.
From the connected app you set up once. Safe to save, so this box remembers it. See the setup steps on the right.
You are sent to Salesforce to sign in, with your own username, password and multi-factor check. This page never sees your password.
One-time setup for logging in

Logging in needs a connected app. You set one up once, and then use it against any org you audit. In the org you want to check:

  1. Setup → App Manager → New Connected App. Give it a name, your email, and tick Enable OAuth Settings.
  2. Callback URL: the exact address this page is running at. It is shown here so you can copy it:
    (loading)
  3. Scopes: add Manage user data via APIs (api) and Access the identity URL service (id). Nothing else is needed.
  4. Tick Require Proof Key for Code Exchange (PKCE). Leave Require Secret for Web Server Flow unticked — a page running in a browser cannot keep a secret.
  5. Save, wait a few minutes, then copy the Consumer Key into the box on the left.
  6. Setup → CORS → tick Enable CORS for OAuth endpoints. Without this the browser cannot finish the login.

The access token you get back is held in memory only, expires on its own, and can be revoked by logging out. That is a smaller blast radius than a pasted Session ID, which carries your whole login.

Where do I get a Session ID? (the other option)
  1. Browser console (no tools): open your org, press F12, and run document.cookie.split('; ').find(c=>c.startsWith('sid=')).slice(4) on a *.my.salesforce.com tab (not a Lightning .lightning.force.com tab — that cookie is a different, non-API session).
  2. Salesforce Inspector Reloaded: the extension popup shows the session id.
  3. Workbench: log in, then Info → Session Information → Session Id.

The session must belong to a user with API Enabled. If Setup → Session Settings has Lock sessions to the domain in which they were first used enabled, use a session id taken from the same My Domain host you paste above.

Handling browser CORS restrictions (read this if Connect fails)

Opening this file by double-clicking gives the page the opaque origin null, which the Salesforce CORS allowlist generally will not accept. Pick one of these, in order of preference:

  1. Serve it from localhost (recommended). In the folder holding this file run one line, then open http://localhost:8000/security-audit-dashboard.html:
    python -m http.server 8000
    npx --yes http-server -p 8000
    Then in your org add that origin: Setup → Security → CORS → Allowed Origins List → New, Origin URL Pattern http://localhost:8000.
  2. Try the file:// origin anyway. Add null as an origin pattern in Setup → CORS. Some org configurations accept it; many do not.
  3. Make it same-origin. Upload this file as a Static Resource and open it from your My Domain host. Same-origin requests skip CORS entirely and need no allowlist entry at all.

A CORS failure shows up as “Failed to fetch” with no HTTP status. A wrong or expired session id shows up as HTTP 401 INVALID_SESSION_ID — those are different problems.

Enforcement dates were compiled from the Salesforce Release Updates page, Winter ’27 release notes and the architect/developer release blogs. Salesforce postpones, re-scopes and cancels release updates, and some dates are reported inconsistently across sources — always confirm the date for your org in Setup → Release Updates before committing to a remediation plan.