Back to Pulse

Security

Security controls are documented as enforceable behavior, defaults, and operator responsibilities.

Data retention model

Plan limits define metadata retention, trace retention, payload storage mode, eval replay, and archive/export limits.

Encryption in transit/at rest

TLS protects traffic in transit. Managed data stores, R2, and Cloudflare-managed services provide at-rest encryption. Virtual keys add application-layer encryption before storage.

Virtual key encryption

Provider credentials are encrypted server-side; plaintext is not returned to the browser after creation.

Raw prompt storage policy

Raw payload retention is off or redacted by default for builder plans. Full payload retention requires explicit configuration and a higher-trust plan.

Redaction defaults

Incident exports include omitted/redacted data sections and should redact secrets before sharing.

Tenant isolation

Rows are tenant/project scoped; export and dashboard APIs enforce tenant/project isolation.

Audit logging

Admin, policy, key, and org changes write audit entries where available.

SSRF protections

Custom endpoints, OTLP, webhooks, SSO metadata, and MCP egress use allowlists and private-network guards.

Key rotation

Rotate Pulse keys from the dashboard and rotate upstream virtual keys by replacing encrypted credentials.

Responsible disclosure

Report suspected vulnerabilities to security@orionslock.com with affected endpoint, reproduction steps, impact, and relevant request IDs. Do not test against other tenants or production customer data.

Security | OrionsLock Pulse