---
title: "GEODI Data Privacy and Security"
canonical: "https://support.decesoftware.com/space/geodien/3968073729/GEODI+Data+Privacy+and+Security"
format: markdown
---
> Macro (toc)

---

# Security of Usernames, Passwords, and Credentials

GEODI encrypts Workspace settings and other sensitive configuration data according to the selected security level. Security options range from allowing settings to remain portable to restricting them to a specific server.

Sensitive information—such as database connection strings and credentials used to access OneDrive or other data sources—is stored securely. By default, protected configuration files can be used only on the server where they were created.

When LDAP authentication is enabled, GEODI does not store users’ LDAP passwords. When GEODI’s built-in user management and authorization are used, passwords and other sensitive information are stored securely using appropriate cryptographic protection.


# PAM & Secret Provider Integration

GEODI integrates with secret providers—CyberArk Cloud/Self-Hosted, AWS Secrets Manager, and HashiCorp Vault—documented in the support space. This lets you manage credentials outside GEODI while GEODI adapts to credential changes.


# Data Security

GEODI processes data directly from the configured sources and generally requires only read access. During discovery, it does not modify the source data.

Source data and extracted information remain within the configured GEODI environment unless an authorized integration, workflow, export, or remediation action is explicitly configured.

# Two-Factor Authentication

For information about enabling two-factor authentication, see:

[2FA Activation](https://decesw.atlassian.net/wiki/spaces/geodien/pages/4096720897)

# Server Security Settings

For information about system configuration and server security settings, see:

**System Configuration and Security Settings**  
*The current URL is a “create page” link and should be replaced with the published documentation URL.*

# Default `geodiadmin` User

GEODI installation creates a default administrative user named `geodiadmin`.

We recommend creating separate administrative accounts with only the permissions required for each role and avoiding routine use of the default `geodiadmin` account.

The default password should be changed immediately after installation.

# Logging and SIEM Integration

GEODI logs queries, administrative operations, and other relevant actions. Logs can be exported or generated in formats such as CSV and analyzed using many SIEM platforms.

Access to logs should be restricted because they may contain usernames, queries, source references, and other operational information.

# Penetration Testing

GEODI is regularly assessed for cybersecurity risks. Customers operating in sectors such as defense, security, and financial services also conduct security assessments and penetration tests as part of their own assurance processes.


# Security Assessment Findings and Remediation Guidance

Security assessments, vulnerability scans, and penetration tests may identify findings related to GEODI, its hosting environment, or underlying infrastructure.

This section addresses commonly reported security findings, some of which are configuration issues rather than product vulnerabilities, and provides recommended actions.


| Question | Recommended Action |
| --- | --- |
| Missing HSTS Header. | Enable the `Strict-Transport-Security` header using the `HttpHeaders` setting in `SystemSettings.json`, or configure it at the IIS/reverse proxy layer. Apply `includeSubDomains` only if all affected subdomains support HTTPS.<br>- For detailed information about definitions, see [https://support.decesoftware.com/space/DEV/1390184262/System+Configuration+-+Security+Settings](https://support.decesoftware.com/space/DEV/1390184262/System+Configuration+-+Security+Settings)
- Add the following setting to the existing SystemSettings.json file:<br>```json
{
  "HttpHeaders": [
    "Strict-Transport-Security: max-age=31536000"
  ]
}
``` |
| A TLS 1.0 or TLS 1.1 vulnerability. | Disable TLS 1.0 and 1.1 at the HTTPS termination layer and allow TLS 1.2 or 1.3. If HTTPS is terminated directly on Windows, review the operating system's TLS configuration.<br>TLS 1.0 and 1.1 can be disabled on the operating-system server that handles the HTTPS connection. GEODI listens on all enabled protocols; if specific protocols should be listened to, details are available at [https://support.decesoftware.com/space/DEV/1390184262/System+Configuration+-+Security+Settings](https://support.decesoftware.com/space/DEV/1390184262/System+Configuration+-+Security+Settings) |
| XSS Vulnerability | Security improvements addressing identified XSS vulnerabilities have been included in GEODI 10.0.160. Update to the latest GEODI version. If the finding persists, provide DECE Support with the affected endpoint, payload, and reproducible PoC.<br>GEODI includes input validation and output encoding/sanitization controls to mitigate XSS vulnerabilities. The `XSSSecurityMode` setting in `SystemSettings.json` provides additional request filtering options when required.<br>For configuration details, see [https://support.decesoftware.com/space/DEV/1390184262/System+Configuration+-+Security+Settings](https://support.decesoftware.com/space/DEV/1390184262/System+Configuration+-+Security+Settings) . |
| The RDP port is open on the GEODI server. | This is not a GEODI product vulnerability; it is a network and system administration matter. Management ports, including RDP, should not be exposed to the internet. Restrict access to authorized management networks or VPN connections, enforce MFA where supported, and disable RDP when unnecessary. |
| Full Control or Write permissions have been granted to the "Authenticated Users" group in the GEODI installation directory or service file (`geodi.exe`). | This is an infrastructure/operating-system authorization issue rather than a GEODI product vulnerability. Review and tighten NTFS permissions on the GEODI installation directory and executable files. Remove unnecessary Write/Modify permissions from "Authenticated Users" and other non-administrative groups, while preserving the permissions required by SYSTEM, authorized administrators, and GEODI service and update processes. |
| A missing X-Frame-Options header | Configure `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors 'none'` through `HttpHeaders` or the reverse proxy. If trusted applications must embed GEODI, configure an appropriate framing policy.<br>> This header can be added via the `HttpHeaders` setting in `SystemSettings.json`, in the same way as HSTS:
> 
> ```
> "HttpHeaders": [
>   "X-Frame-Options: DENY",
>   "Content-Security-Policy: frame-ancestors 'none'"
> ]
> ```
> 
> If GEODI must be embedded in a trusted application, use SAMEORIGIN for same-origin embedding or configure CSP frame-ancestors with explicitly trusted origins. If IIS or a reverse proxy is used, the headers can be configured at that layer instead.
> 
> Preserve other existing HttpHeaders entries and verify compatibility with embedded GEODI components. |
| Unauthorized data access was detected in the GEODI API. | Verify the test user's effective permissions, including group memberships, project sharing, and administrative privileges. Reproduce the finding on the current GEODI version using an account without the expected access rights. If unauthorized access is confirmed, provide the affected endpoint, user roles, and sanitized request/response examples to DECE Support. |
| CORS Misconfiguration is reported in the GEODI API. | Review the `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` response headers. Credentialed cross-origin requests should be restricted to explicitly trusted origins. If CORS headers are configured through IIS or a reverse proxy, review the corresponding configuration. Verify whether an unauthorized origin can actually access sensitive responses before classifying the finding as exploitable. |
| An outdated jQuery version is reported for GEODI. | The jQuery dependency has been updated in GEODI 10.0.160. Update GEODI to the latest version. If the scanner continues to report a vulnerable jQuery version, provide the detected version, file path, and CVE to DECE Support. |