Security

How we handle your destination credentials

Logcannon sends logs into a security platform you already operate. The tokens and keys for that destination never belong in the browser, in job history, or in support copies of a run.

Encrypted at rest

Destination credentials (for example HTTP Event Collector tokens and Elasticsearch API keys) are encrypted before they are stored. They are decrypted only on the server when a send actually runs.

Not returned to you as raw secrets

After you save a destination, the product confirms that a credential is configured. It does not show the original token or key again.

Not exposed in job output

Job history and insert results describe what was sent and whether it succeeded. They do not include destination secrets.

Questions: contact@logcannon.com.