Best practices for inspecting sensitive data
There are several things that you need to consider before starting an inspection. We will go over them now:
- Identify and prioritize scanning: It’s important to identify your resources and specify which have the highest priority for scanning. When just getting started, you may have a large backlog of data that needs classification, and it’ll be impossible to scan it all immediately. Choose data initially that poses the highest risk—for example, data that is frequently accessed, widely accessible, or unknown.
- Reduce latency: Latency is affected by several factors: the amount of data to scan, the storage repository being scanned, and the type and number of infoTypes that are enabled. To help reduce job latency, you can try the following:
- Enable sampling.
- Avoid enabling infoTypes you don’t need. While useful in certain scenarios, some infoTypes—including
PERSON_NAME,FEMALE_NAME,MALE_NAME,FIRST_NAME...
