From a first scan to evidence.
Six steps, two screens: the Console and your org.
Every name and number in the screens below is made up.
- 1.
Compose the scan in the Console.
Choose the org, the question (where personal data is held, who can read it, or what your files contain), the rules to run and the scope. Before you download anything, the Console tells you how much the scan will read. What you download is a small scan file. It describes the scan and holds no data.
fig. 2.1start a scan · made-up data Org Warden Console · Start a scanOrgGroup FinanceQuestionWhere is personal data held?Rule PackUnited KingdomScopeThe whole org, live recordsThis scan will read 214 objects and about 1.3 million records. Files are a separate scan.Download the scan file - 2.
Import it into your org.
In the org’s Scans tab, an administrator picks the file. The org shows what the scan will do, including any rule that will not run and why, before anything is written. Import it, and the scan starts.
fig. 2.2import · made-up data Your Salesforce org · Org Warden Core · ScansBefore anything is written, the import shows what the scan will do:Detection over 214 objects, live records, United Kingdom rules. 2 rules will not run: their category is not turned on in this org.ImportImported. Its row is below. - 3.
Let it run.
The scan runs in the background, inside your org. Its row shows how far it has got, and you can cancel it at any point. Nothing connects the org to Org Warden while it runs.
fig. 2.3run · made-up data Your Salesforce org · Org Warden Core · ScansWhere is personal data held? · the whole orgRunning · 96 of 214 objects · 4 min 12 s elapsed · now ContactCancelWhere is personal data held? · the whole orgDone · 214 of 214 objectsGenerate pack - 4.
Generate the Evidence Pack.
When the scan has finished, press Generate pack. The org writes the Evidence Pack and its hash, and you download them as one file. The pack carries counts, classifications and the name of each rule that matched. It never carries a record or field value.
fig. 2.4generate the pack · made-up data Your Salesforce org · Org Warden Core · ScansWhere is personal data held? · the whole orgEvidence Pack readyDownloadOne file saves to your computer. It holds counts, classifications and rule names, and no record or field value. - 5.
Add the pack to the Console.
Upload the file on the Console’s Evidence Packs page. The Console checks every pack against its hash before it shows anything, so you know the file was not altered on the way. Each pack says what the scan read, and names what it did not read.
fig. 2.5add the pack · made-up data Org Warden Console · Evidence PacksVerified against its hash fileOrgGroup FinanceScanWhere is personal data held? · the whole orgWhat it read214 objects, live records. Not read: the objects kept out by default, each named in the pack, archived activities and the recycle bin.FindingsPersonal data on 38 objects - 6.
Read the Estate.
The Estate is every org your packs came from, in one place. Open an org, then an object, then a field, and every finding names the rule that produced it and the pack it came from. Scan the same org again later and the two packs show what changed.
fig. 2.6read the Estate · made-up data Org Warden Console · EstateEvery org your packs came from- Group Finance3 packspersonal data on 38 objects
- Scotland Sales2 packspersonal data on 52 objects · the newest scan did not look everywhere
- Broker Portal1 packpersonal data on 17 objects
- Group Risk1 packno scan for personal data yet
We set up your Console account. The Setup guide does the rest.
- 1.Write to us.
Email hello@orgwarden.co.uk. We set up your organisation’s Console account and add your first administrator by their work email. One account holds every Salesforce org you scan.
- 2.Sign in.
Your administrator signs in at app.orgwarden.co.uk with a one-time code sent to that email. There is no password.
- 3.Follow the Setup guide.
The Setup guide is the first page in the Console. For each org, it takes a Salesforce administrator through installing the package, giving the right people access, deciding whether the person who scans files can read every file, and choosing which kinds of data to look for. Nothing in it needs a command line. There is no public install link yet; when there is, it will be in the Setup guide.
The pack is the scope for your own controls.
Your packs list the fields that hold personal data and, from an access scan, who can read them. That list is what encryption, field access and field history need to be aimed at: the fields where regulated data actually sits, rather than everywhere or nowhere.
Org Warden makes none of those changes. Your team makes them through your own change process, and the next scan, compared with this one, shows anything that has moved outside the scope.
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.