ferno

Security / Built into the path

Every signal stays in its lane.

Ferno’s architecture keeps workspace boundaries, credentials, ingestion, investigations, and actions explicit.

Last updated 17 October 2026

Project-scoped ingestion

Every API key belongs to one workspace and project. The ingestion service resolves that trusted scope from the credential instead of accepting tenant identifiers from the client.

Credential handling

Plaintext project keys are returned only when provisioned. Ferno stores a cryptographic digest and display prefix. Connected integration credentials are encrypted at rest.

Durable event delivery

Event batches are validated before they enter the stream. A successful ingestion response is sent only after durable publish acknowledgement.

Workspace authorization

Roles and named capabilities control who can view workspace resources, manage projects, provision keys, connect integrations, invite members, and change workspace settings.

Approval-first actions

Investigations are read-only. Actions that affect connected systems must be explicit, scoped, permission-aware, and verified after execution.

Reporting concerns

If you believe you found a security issue, contact the Ferno team through the support channel available in the product. Do not include live credentials or customer data in the initial report.