Trust & evidence
Evidence before commitment.
Understand the controls, verify the boundaries and decide what evidence your organization needs.
No NDA required for an introductory walkthrough.
A practical starting point for due diligence.
Security decisions need evidence that matches the product version, environment and scope being evaluated. This page brings our public product documentation, company information and evaluation boundaries together.
Last reviewed: November 16, 2026. A product demonstration is not an independent audit or a customer outcome study.
What you can review now.
| Evidence | What it establishes | Review |
|---|---|---|
| Sentri capability and scope page | Our published description of enrolled-agent controls, limitations and development status. | Read Sentri capabilities |
| EYEQ status | Behavioral intelligence is advisory. Proposals and operator decisions remain distinct. | Read EYEQ scope |
| Company leadership | Named accountability and the founder's stated identity security experience. | Meet Cipherion |
| The Colony Chamber directory | An external business listing linking to Cipherion. A listing does not validate product performance. | View the directory listing |
| Company LinkedIn page | Company-published background and updates, not independent customer validation. | View company updates |
| Privacy policy | Our published data handling and contact information. | Read the privacy policy |
Keep capability, coverage and proof separate.
- Enrolled scope: Sentri governs agents using its gateway. A system outside that path is not covered merely because the console exists.
- Advisory signals: EYEQ findings support review. They are not a guarantee that malicious intent has been detected.
- Network visibility: DNS evidence concerns resolver activity. It does not reveal all application actions or hidden model reasoning.
- Demonstrations: Illustrated scenarios and 4D replay demonstrations are labeled. They are not presented as customer incidents.
- Independent assurance: This page does not publish an independent audit report or permissioned customer case study. Request the evidence available for your proposed scope before relying on a control.
Agree on a pilot that can be evaluated.
Discuss an observation-first pilot with an agreed inventory, deployment boundary, review owners and reporting cadence. Before it starts, record what constitutes success and what remains outside coverage.
- Identify the agents, identities, hosts and connections in scope.
- Agree on which activities are observed, which require a person and whether any enforcement is authorized.
- Use approved test scenarios with clear expected results and retained evidence.
- Review gaps, false positives, operational effort and exit steps before expanding deployment.
Customer references, audit reports and deployment results are shared only when they exist and disclosure is authorized. We do not substitute invented testimonials or customer logos.
Start with your priorities.
Tell us what you need to evaluate. We will follow up to arrange a conversation and agree on the scope before any technical work.
Request a Demo →