Credential and data protection
How FileAgent protects your credentials and configuration: encrypted at rest on the host, never shown in full, and bound to the machine they live on.
Last updated July 17, 2026
#Credential protection
Connection credentials are encrypted on the FileAgent host and referenced by jobs. Secrets are never embedded in job definitions and are never shown back in full in the console. Rotating a secret is a one-place edit that applies to every job using that credential.
#Encrypted at rest
FileAgent's local application data — jobs, credentials, users, and settings — is stored in an encrypted database at rest on the host. The encryption depends on protected secret material that lives on the same machine, so the data is bound to that host.
#What logs do and don't contain
Application logs are for operational diagnostics. They are not designed to contain full secret values, identity assertions, private keys, or credential material. They can contain hostnames, paths, usernames, error messages, and operational metadata — so restrict access to log folders and any exported logs.