There are more reports with GEODI Discovery.
The reports can be accessed by system admins and members of the "ACC.Discovery" group can access the reports. The reports . They are visible in the workspaces only if the "ACC.Discovery":true
settings exist in the GenericSettings in Workspace Advanced settings.
Table of Contents |
---|
Report: Discovery-Content Findings
The Content Finding Report lists metadata types (Identifiers) extracted for each document. It is simpler compared to the Content Summaries report and can be used to identify compliant/non-compliant content.
Info |
---|
You can obtain a similar report based on the source. It's called the Content Finding Source Report. |
View file | ||
---|---|---|
|
Report: Discovery- Content Findings(DB)
This report tells about which table/column contains sensitive data. It works only for DB content. For unstructured data, please use the Content Findings report.
View file | ||
---|---|---|
|
Report: Discovery- Content Findings Summary(DB)
Content Discovery (DB) Report gives the table/column information containing sensitive data. It works only for Databases. For unstructured data, please use Content Discovery report.
View file | ||
---|---|---|
|
Report: Risk Report
GEODI Content Risk Report allows you to calculate risk scores on a content basis post-discovery. Risk calculation is performed as follows:
...
GEODI Discovery has 4 reports for different purposes. Each report is designed to give more details about findings. All reports except summary are Excel or CSV formats.
Table of Contents |
---|
Discovery:Summary Report
Summary has sub reports in it and PDF format.
Discovery:Content List
Each line is a content/file and risk value. Risks are calculated using the risk score given to the source and findings.
Content List covers all kinds of content, files, database rows, e-mails, and GDE-fed files. You can limit content types by using queries.
You should set a risk score from 0 to 100 to for each source. Sources that you do not assign have a risk score to are assumed to have a risk score of 0 (meaning no risk). In sensitive areas such as shared file repositories where sensitive data should not exist, the risk score should be high. In protected areas like databases, the risk score should be low. Users determine the risk score for each source themselves.
The findings include identifiers in the calculation. In the default report, identifiers labeled as IsFinancial (credit card, IBAN, CVV, PIN, password) and PII (name, ID number, email, address, tax number, foreign ID, passport) or tagged as IsRisky are considered risky.
In the report, each content includes values from the Content List and additionally includes the following values:
The risk score of the source
Number of risky identifiers
Calculated Risk Score → Source risk score x Number of risky identifiers.
A content/file's risk score is calculated using source risk and findings. Each finding has a risk score. PII and PCI findings are high-risk, but a city name has a low-risk score.
View file | ||
---|---|---|
|
Discovery:Findings
Each line is a finding type and count. If a file contains a credit card and ID then there will be two lines.
View file | ||
---|---|---|
|
Discovery:Findings Details
This is the most detailed report. Each line is a finding. If a file/content has 100 credit cards and 100 IDs, then there will be 200 lines.
We suggest limiting the source content by using queries.
View file | ||
---|---|---|
|