Finds and reports
Cloud Drive DiscoveryFind the sensitive data .
Files pile up in Microsoft 365 and Google shared drives for years, and nobody can say which of them hold sensitive data. In a pilot, you point RedactWall at a folder and it reports what it finds, with a date on the answer.
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, so coverage of a whole drive is something you assemble deliberately.
- 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.
Start with the drive that worries you most
Findings appear in the reviewer console alongside the decisions made on your AI and email paths, on a record your own team can check. Per-provider detail is under Integrations.