Infrastructure data deserves the rigor of your production systems
Cordant receives telemetry from your infrastructure, and we treat that responsibility seriously. This page explains our data protection, access controls, and offboarding process.
Security architecture
The principles governing data handling from ingestion through storage and deletion.
Encryption in transit and storage
Data sent from your infrastructure to Cordant's ingestion layer uses TLS 1.2 or higher. Data stored in our pipeline, including incident logs, diagnostic traces, and runbook outputs, is encrypted at rest with AES-256.
Credential handling
API tokens for PagerDuty, Datadog, Slack, and similar integrations reside in a secrets vault separate from the application tier. They are never logged or included in diagnostic output.
Least-privilege access
Cordant requests only the permissions needed for diagnosis and remediation. Scopes are set per integration, documented during setup, and reviewable or revocable by any workspace admin at any time.
Retention and deletion
Incident data follows your plan: 14 days on Starter, 90 days on Pro, configurable on Enterprise. Deleting a workspace starts a 30-day grace period, then permanently erases its data. No archive copies remain.
Infrastructure isolation
Runbook actions execute in isolated, single-tenant environments. Storage-layer access controls enforce logical separation between your diagnostic data and other customers' data, rather than relying only on the application layer.
Audit logging
The Cordant agent records every action, including diagnostic steps, runbook executions, and escalation decisions, in a tamper-resistant audit log. Enterprise customers can export it to their SIEM or log management system.
Operational security practices
Vulnerability disclosure
We maintain a responsible disclosure process. Researchers can report Cordant system issues to [email protected]. We acknowledge reports within 3 business days and share status updates during remediation.
Employee access controls
Only a small group of engineers with an explicit need can access production systems. Production access requires hardware security keys and is logged. Cordant employees access customer data only to resolve a support request you opened.
Dependency and supply-chain hygiene
Automated dependency scanning runs on every build. We check third-party dependencies for known CVEs before inclusion and pin them to version hashes to help prevent supply-chain substitution attacks.
Security contact
For security questions, vulnerability reports, or data handling inquiries, contact [email protected]. For general compliance documentation, contact [email protected].
Security questions?
For specific security requirements or procurement documentation, contact us directly and we will work with you.