Where this offering fits
GTB data discovery concerns sensitive information stored in selected repositories rather than only information crossing a network boundary. Use it to establish where content-based policies should apply and which data owners need to review exposure. The outcome should be a verified finding with a location and owner, not simply a count of pattern matches.
Architecture and rollout decisions
Build a source schedule covering the agreed file stores, endpoints or supported cloud locations. Define the detection examples and scan permissions, then assess a bounded dataset with known positive and negative samples. Review false positives and unreadable items explicitly. Remediation actions such as changing access or moving files should have separate approval; a discovery scan should not silently become a data migration or deletion task.
An evaluation scenario for this offering
Select a file share with known test content and a documented owner. Compare matches across supported document formats, then review an encrypted or unreadable item. Agree whether the result should update an inventory, apply a supported label or enter a remediation queue. The acceptance record should show that each action has an authorised owner. A discovery finding should not quietly trigger a destructive operation merely because the platform offers an additional function.
Evidence to request for this scope
- State whether the engagement reports findings, applies labels or also remediates selected locations.
- Measure scan coverage against the authorised repository list, including inaccessible exceptions.
- Ask owners to validate representative matches before using results in the information inventory.