After a discovery is completed, you need to inspect the results. GEODI provides many ways of inspection: reports, panels, and predefined queries. Here, we will give details about the predefined queries.
Let’s assume that we have carried out a discovery for PCI/DSS and inspection the results. The following query will tell you which content and source has findings related to PCI/DSS.
predefined:PCI
This query covers all credit card, CVV, PIN, or Password findings. GEODI will list all content, and the facet will show you details about data sources and the number of findings.
This will give you an essential initial insight into conforming and non-conforming sources. The rest is yours to take precautions, like delete or quarantine actions. You may repeat the process until you see 0 findings on risky sources.
Queries affect reports and panels, so you can use predefined:PCI
along with ContentFinding,
ContentFindng(DB)
, and ContentFinding(Sources)
reports. This report will have more detailed information if you need it.
The following predefined query queries PII data. PII data has some rules in GDPR and in other regulations. This query covers all the rules. The details mentioned for predefined PCII are also valid for this one.
predefined:PII
You may wonder how GEODI handles country-specific situations, how it knows which ID is used, etc. Don’t worry; we have taken all this into account while developing the recognizers. Predefined:PII
query works for all countries as expected.
For deletion, quarantine, or masking, you need to address legacy data older than 5 years. While this is possible with GEODI, it is easier to do it with predefined queries.
The following query will address legacy data older than five years, taking only content dates into account.
predefined:O5Y
predefined:O10Y
There are more predefined queries for various purposes; here is the list:
query | purpose |
---|---|
predefined:DB | |
predefined:Videos | |
predefined:Images | |
predefined:? | |
**