Argument 3Security and architecture

Metadata-only, drawn.

Nothing connects your org to Org Warden. What the package writes down, in its own records inside your org and in the Evidence Pack a person carries out of it, is counts, classifications, telemetry and error codes. Never values, file contents, record Ids used as data, or per-record findings. Tests check this on every change.
For your procurement team

The answers a security review asks for first.

If you stop using Org Warden, nothing in your org depends on us. Your scans are records in your own org and can be run again from its Scans tab, and your Evidence Packs are files you already hold. The packages uninstall from Salesforce Setup.

What leaves the org

Everything an Evidence Pack may carry, and what has no way out.

fig. 3.1leaves in the pack · stays in the org
Passes the boundary
countsclassificationstelemetryjob statuserror codesrule namessnapshot hashwrite-gate recordsorg name · domainprofile · permission set namesUser Id of who generated it
Every item that leaves the org is a shape or a signal, never the underlying value. A pack does name the org it came from, and carries one User Id: the person who generated the pack. Once uploaded to the Console, that is personal data we process for you.
org boundary
Never leaves the org
valuesfile contentsrecord Ids as dataper-record findingsraw rule matchesquery resultsuser names · emails
There is no code that would move these items out of your Salesforce org.
What we promise, and how it is tested

Eight promises. Each one has its own tests, and if a test fails the release does not ship.

A security reviewer can find each one in the code and its tests.

1
No value leaves your org.
Scan results and Evidence Packs carry counts, classifications, telemetry and error codes. Never values, file contents, record Ids used as data, or per-record findings.
pack contract tests
2
The production package cannot change your records.
Org Warden Core has no code that changes your records. Not switched off: not there. A static check flags any write statement in it on every change, and the package’s own tests check that nothing in it is registered to write.
static check · package tests
3
Records change only in a sandbox, behind three controls.
Only Org Warden Redact, the redaction package, changes records. It refuses in any org that is not a sandbox: checked once before a redaction starts, and again inside it. A live run also needs all five checks of the write gate to pass: the org is a sandbox, redaction is switched on there, the person running it holds the approver permission, a finished dry run of exactly the same scope came first, and every field to change can be edited. A refusal is recorded as a result, not hidden as an error.
dispatch and gate tests
4
One way in.
Every scan and every redaction is admitted through one checkpoint in the package. Nothing runs around it.
dispatch tests
5
Every scan is a record in your org.
A scan is requested, scoped and reported in ordinary records you can query and report on. Neither package needs a connection to us.
contract objects
6
Scans run at a measured pace.
Scans run in the background, and every background job a scan uses is counted on the scan. A stalled scan is picked up again, never re-run blind.
background job counts
7
Each customer's Console data is kept apart.
The database enforces the separation on every customer table, and who you are comes from your signed-in session, never from the request. Signing in to the Console takes an emailed one-time code and an authenticator app, and a session ends after 30 minutes idle or 12 hours.
database rules · signed session
8
Each user's own access, by default.
Org Warden runs with the user’s own access. Eight named parts of the scan read with full access, so a scan is not narrowed by who launched it: a narrower scan would report clean results for data it never looked at. Seven only read and keep counts; the eighth is the Redact write, in a sandbox, behind the five-check gate. In a test on the installed package, a user who could see none of an object’s records and could not read the field being scanned got the same counts as an administrator. Files and some access views have not yet been through the same test.
sharing and access tests
fig. 3.2three controls · one change to a record at the centre
in production · the code does not exist
1 · The production package has no write code
2 · Refused unless the org is a sandbox, checked twice
3 · The five-check write gate
A change to a record
reached only through all three
in a sandbox · after a dry run and the gate
Redaction in sandboxes

One package reads. A separate package writes, and only in a sandbox.

Org Warden Redact replaces personal data in a sandbox copy of your org, so testers and developers work without real customer data. It is a second package. Org Warden Core, the package in your production org, does not contain it and has no direct reference to it: the two meet only through a list of jobs that an administrator can read in Setup.

fig. 3.3two packages · one meeting point
Production orgread only
Org Warden Core
reads schema, values, access and files
code that changes your records
not in the package
Redaction plans
plain records
inert without the Redact package
Sandbox orgread and write
Org Warden Core
the same package as production
Org Warden Redact
the only code in the product that changes a record
refuses outside a sandbox
write
Sandbox records
changed by Org Warden Redact
only after a dry run and the write gate
The job listone way in · readable in Setup
JobPackageReads or writesRuns in
Schema: what objects and fields existCorereadsproduction and sandbox
Detection: which values match a ruleCorereadsproduction and sandbox
Access: who can readCorereadsproduction and sandbox
Files: what documents containCorereadsproduction and sandbox
RedactionRedactwritessandbox only
On refreshplans copy from production to the sandbox · the Redact package does not · a redaction waits until an administrator installs it
A
Org Warden Core
The production package reads: what objects and fields exist, what the values match, who can read them, and what the files contain. It cannot write.
B
The meeting point
A redaction job waits safely until the Redact package is installed. It never fails half-way.
C
Org Warden Redact
The Redact package writes, and refuses to unless the org is a sandbox.

From a sandbox refresh to a redaction, in five steps.

Redaction plans are kept in production as plain records, so no write code is needed to hold them, and a refresh copies them into the sandbox. Nothing runs on refresh by itself: an administrator starts the redaction.

fig. 3.4sandbox refresh · five steps
  1. Step 1plan
    Plans copied
    A refresh copies production into the sandbox. The redaction plans arrive. The Redact package does not.
  2. Step 2requested
    A redaction requested
    An administrator asks for a redaction from a plan, in the org or by importing one composed in the Console.
  3. Step 3waiting
    Waiting, not failed
    With no Redact package in the org, the job waits. Nothing that changes a record is attempted.
  4. Step 4install
    Redact installed
    An administrator installs Org Warden Redact in the sandbox. The waiting job can now run.
  5. Step 5ready
    Dry run, then the gate
    A dry run shows what would change. Only then does the five-check write gate open.
Reporting a vulnerability

If you think you have found a security vulnerability in an Org Warden package, the Console or this site, email security@orgwarden.co.uk with what you found and how to reproduce it. Please give us time to correct it before you make it public, and test only against a Salesforce org and data that are yours.

The Console and this site check their dependencies against published security advisories on every change and again every morning. A security update to the Console is deployed by us and needs nothing from you. A security update to a Salesforce package reaches your org only as a new package version, which your administrator installs.

What we will not say

We do not publish a statistic we cannot back, show a wall of badges, or imply a certification we do not hold.

To reproduce anything on this page yourself, email security@orgwarden.co.uk and we will walk you through it in the code.

See it working

Book a demo.

In a demo we take you through the Console on a demonstration estate whose data is all made up: a rule opened onto every org where it matched, and an Evidence Pack checked by its hash.

Work email · or write to hello@orgwarden.co.uk · we reply within 1 business day
Next argument · 4
Compare. Why not Shield, Varonis, or AppOmni.
Adjacent tools, side by side with what Org Warden does.