📂 Adding Data Sources

GEODI can connect to many different data sources. These sources can be indexed and discovered within a single project or across multiple projects. Data sources are defined through the Project Wizard.

Project Wizard

Apart from source-specific settings, the following features apply to all sources:

• 📑 File format support → File formats are processed in the same way regardless of the source.

  • Example: A PDF located in a folder, a PDF attached to a web page, or a PDF embedded in a database record are all processed in the same way.

  • Copies and similar files may exist across sources. For example, a file attached to an email may be a duplicate of a file stored in a folder.

• 📊 Sampling discovery → Available for all sources. For instance, you may process one out of every N files, or M records per table.

• 🛡️ Data Remediation Workflows → Actions such as deletion, quarantine, or classification are supported across many cloud and on-premise sources.

  • To enable this, you must allow it on a per-source basis and provide a user/credential with the necessary permissions.

• 🔎 OCR → OCR processes can be activated per source.

• 🔒 Permissions → You can define who can access or download data on a per-source basis. You should check Read content permissions for the source. ( For GDE, you must enable it from the GDE settings. )

⚠️ Risk Score

• 📌 Risk score value should be set for each source.
  This score is used in reporting and helps prioritize actions such as deletion or quarantine after discovery. The risk score ranges between 0–100.

  ⚡ Higher risk scores indicate higher priority.
  Findings with higher risk scores should be addressed first.
  Example: Shared or public areas typically have higher risk scores.

  📑 Risk scores are displayed in Content List reports.

File Content Filtering

Any corpus contains various file types. Some may not be necessary for the project scope, and some may be too large for the network or the system.

GEODI comes with default rules to avoid some file types and place some size limitations, collected from the best practices of many Discovery projects. Here, we documented the rules and how you can modify them.

These filters apply to all files, whether they come from a folder, from an email attachment, from GDE, or embedded into a database.

Filters (%100)	Explanation

Filters (%100)	Explanation
IgnoreRules	Ignore rules contain file extensions, directory names, and some patterns. The default list contains *.DLL, *.SYS, “program files” and similar. Any file matches the ignore rules are not indexed and logged at all. Settings are in: <geodi>Settings\IgnoreFileTypes <geodi>\Settings\IgnoreFolders If you need to override defaults please do it in %appdata% GDE has some additional ignorerules documented in the related page.
KnownFiles	These files are the ones GEODI has a reader like PDF, DOCX etc. The fu l list is Supported Formats These files are processed as expected unless there is an IgnoreRule or ProtectRule. Ignorule will set the file type invisible. Protec rule may set so size limitation.
UnknownFiles	By default, unknown file types are ignored. You may use advanced settings. If you use “only name and date” then all unknown extensions will be indexed. You may add any unwanted to ignore list but these actions requires to run discovery all over again.   Open
ProtectRules	These rules protect the system and network against large files. Protec rules apply to known and unknown files. The content is grouped as local and far. There's no limitation for local content, which resides in local folders and network folders. Far me ns files from GDE, email attachments, and files from web pages. By default, Far content is filtered as any file greater than 100Mb, and Compressed files greater than 500Mb are indexed as name only. You wi l know these files but not their content. Settings are in: <geodi>\Settings\Engine\ResourceBalancing If you need to override defaults, please do it in %appdata%