Redacting support evidence

Use this article to redact screenshots, logs and error details before you email them to VaultPilot support at support@vaultpilot.io.

Symptom

The problem concerns installation, update, the browser extension, Discovery, the DC Agent or sharing, but the available screenshots or logs include environment-specific values.

Evidence that is safe to send

You may include in a support email:

• VaultPilot version and affected component name.
• Windows Server version.
• Installer file name and version.
• Redacted timestamp and error state.
• Browser name and extension ID when relevant.
• Placeholder host shape such as <VAULTPILOT_URL> or <SERVER_HOST>.
• Short log excerpts after token, host, user, path and secret values are replaced with <REDACTED>.

Redact before sending

Replace these values before sending:

• Customer, tenant, domain, OU, group and user names.
• Internal URLs, IP addresses, machine names and local paths.
• Vault record titles, usernames, URLs, notes, files and custom fields.
• Agent IDs, agent tokens, API client IDs, API secrets, license codes and private license material.
• Session IDs, cookies, certificate subjects and certificate private material.

Never send

Never send databases, backups, certificate packages, private keys, PFX/P12 files, MSI evidence bundles, raw logs, support exports or screenshots that still reveal real vault data.

Decision

• If the evidence is fully redacted, email it to support@vaultpilot.io with the version, component and steps to reproduce.
• If support needs a value you cannot redact, say so in the email and wait for instructions instead of attaching it.
• Report a suspected vulnerability through responsible disclosure, not through support.

Related

• support evidence pack

Back to Knowledge base →