Cloud Drive DiscoveryFind the sensitive data already in your drives.
Files pile up in Microsoft 365 and Google shared drives for years, and nobody can say which of them hold sensitive data. This broader product capability reports findings from a configured folder, with a date on the answer. Cloud-drive discovery is outside the proposed first pilot and requires separate live verification.
Inspected, not retained
What that looks like in practice
Your board asks which drives hold account numbers
Scan the ones in question and answer with a dated result, not a guess.
A shared folder left from an old system-of-record conversion is still open to everyone
You learn what member data is sitting in it.
A finding needs someone to act on it
It reaches a reviewer under the same rules that govern every other path.
Staff are working in those files while the scan runs
Nothing at the provider changes, because it only reads.
What you get
An answer about a folder you name
A scan covers the folder you point it at, and the result carries the date it was run.
A record that is not a second copy
What was found is written down; the data itself is not carried into evidence.
Nothing installed anywhere
No software on a staff machine, and nothing written back to Microsoft or Google.
Coverage you can state plainly
RedactWall reads the stored files in Microsoft 365 and in Google shared drives, and Disclosures lists what each provider covers.
Explore the guided pilot
Cloud-drive discovery is part of the broader implementation. The proposed first pilot covers the browser and gateway paths below.
- Only configured provider scopes are scanned
- Findings report after the file is already there
- Inspected file content stays out of evidence records
- Per-provider proof status is published