Security — Lucidrail
Security

A control plane has to be the most boring system you run.

Lucidrail sits in the path of consequential actions, so its own failure modes matter as much as the agents it governs. These are the principles we design to.

Fails closed

If a governance check cannot run, or Lucidrail cannot be reached, a consequential action is refused — never waved through.

Credentials out of the model’s reach

Lucidrail stores the credentials your tools need encrypted and uses them on the agent’s behalf, so the model never sees a tool’s secret. A secret an agent’s own runtime needs is granted by a person, and no agent can pass on one it does not hold.

Tenant and company isolation

Organizational boundaries are enforced on every request and in every governance decision, not only in the UI. Content moving from one company into another is held for a person.

Data minimization

Evidence records store references and the fields needed for review. Retention is configurable per deployment.

Separation of duties

Policy authorship, approval and administration are separate permissions you can give to different people, and no one approves their own request while someone else can. An agent can never modify its own permissions.

Honest claims

We state which records are signed, which controls are enforcing, and which certifications we hold — only when true. Signed with our platform key: audit-chain checkpoints, retention purge receipts, agent certificates and our agent card. We will publish our compliance status as it is achieved.

Security review or disclosure

For architecture reviews, questionnaires or to report a vulnerability, email security@lucidrail.ai.

Contact security