Building trustworthy systems
A security platform must be secure by design.
Ordrani observes some of the most privileged activity in an organization. That position carries obligations, and we design for them from the first line of code.
Our position
We hold ourselves to the standard we help customers enforce.
To detect misuse of machine identities, Ordrani needs visibility into how those identities operate: workflow runs, federation events, cloud audit logs and IAM configuration. That is sensitive information, and access to it must be narrow, observable and revocable.
The platform never needs more access than detection requires, never holds secrets it does not need, and never takes action in a customer’s environment on its own authority.
We are glad to walk through the specifics of our security design — architecture, data handling and controls — with any organization evaluating Ordrani.
Commitments at a glance
- Read-only, narrowly scoped integrations
- No secret values or credential material ingested
- Strict logical isolation between customer tenants
- Encryption in transit and at rest
- Human approval for every change to your environment
- AI constrained to the evidence of a single case
Data lifecycle
How customer data is handled.
01
Collect
Only the metadata that detection requires, through read-only integrations the customer can scope, review and revoke.
02
Process
Within a logically isolated tenant, encrypted in transit and at rest.
03
Retain
For a configurable period, with deletion on request and at the end of service.
04
Access
Limited to the people and services that need it, with every access to customer data logged for audit.
Commitments
Where our obligations lie.
01
Least privilege, applied to ourselves
02
Secrets stay where they are
03
Tenant isolation
04
Encryption and retention
05
Responsible AI
06
Honest representation
Questions about our security design?
We are glad to discuss architecture, data handling and controls in detail with any team evaluating Ordrani.