Security & Access Control | LogNexis
Lognexis
DocumentationFeaturesAccess Control

API Key Management

When you create a Project in LogNexis, we generate a cryptographically secure, UUID v4 Ingestion Key. This key is used by the SDK to authenticate telemetry payloads.

  • Zero-Downtime Rotation: If a key is compromised (e.g., accidentally committed to GitHub), you can generate a new one immediately. We offer a 24-hour overlap period so your old key continues to work while you deploy the new one.
  • Project Isolation: Keys are strictly scoped to individual projects. A compromised key for your Staging project cannot be used to read or write data to your Production project.

Role-Based Access Control (RBAC)

For teams on the Pro and Enterprise plans, you can invite team members to your organization with strictly defined roles:

Admin

Full access. Can invite members, delete projects, rotate API keys, and view billing information.

Editor

Can view all analytics, set up new custom alerts, and configure ML sensitivity, but cannot rotate API keys or invite users.

Viewer

Read-only access. Perfect for product managers or stakeholders who need to see dashboards but shouldn't modify alerting rules.

Automatic Data Masking (PII)

By default, LogNexis does not log request or response bodies. However, if you opt-in to body logging for debugging purposes, you must ensure Personally Identifiable Information (PII) does not leave your server.

The SDK supports automatic payload scrubbing. When initializing the SDK, provide a blocklist of keys:

lognexis.init({
  apiKey: process.env.LOGNEXIS_KEY,
  logBodies: true,
  maskFields: ['password', 'credit_card', 'ssn', 'authorization']
});

Any matching JSON keys in the header or body will be replaced with [REDACTED] before the HTTP request is even sent to our ingestion servers.