Evidence index · reviewed September 6, 2026
What is demonstrated, what is proposed, and what remains open.
This index supports evaluation and proposal review. It is not an independent audit or product certification. Evidence availability and capability availability are separate.
Download the dated claim register (JSON)Capability register
| Claim ID | Readiness | Supported statement and boundary |
|---|---|---|
| C01: Private cryptographic profile | Private implementation; developer-test evidence | X25519 (classical key exchange) + ML-KEM-1024 (quantum-resistant key exchange), ML-DSA-87 (quantum-resistant signatures) and AES-256-GCM (standard data encryption) in the private cnsa2 profile. Limits: Independent assessment and production deployment evidence pending; no CNSA (NSA Commercial National Security Algorithm Suite) qualification claimed. |
| C02: Relay/gateway connectivity | Founder-reported end-to-end test | macOS® → AWS (Amazon Web Services) → macOS with the far endpoint behind Starlink satellite internet and its NAT (network address translation, which makes direct connections difficult). Limits: Test report does not establish the cryptographic profile, broad performance, anti-jam capability or tactical readiness. |
| C03: Binary platforms | Build evidence; distribution under review | August 9 release build succeeded for macOS ARM64/x86-64 and Linux® ARM64/x86-64 (the two main processor families). Limits: Draft packages predate September profile work. Cross-platform runtime, signing and current lab delivery require verification. Windows not established. |
| C04: Public Python tools | Available | Offline analysis of supplied synthetic (made-up test) observations; public repository and tests. Limits: No live discovery, host remediation, network measurement or certification. |
| C05: CBOM (encryption inventory) discovery | Prototype | CLI (command-line) scan, CycloneDX-style export (a standard inventory file format) and local review screen. This prototype is EigenTunnel™ Scanner, which comes in a compact 10-inch, 6U mini rack we bring to your site. In our laboratory testing, EigenTunnel™ Scanner builds and runs natively on Red Hat® Enterprise Linux® 10.2 (x86_64). Tested on RHEL 9.8 in FIPS mode. In FIPS mode, EigenTunnel Scanner routes its cryptography through the operating system's FIPS provider, refuses to start if that provider is not active, and records the provider and version in every crypto-BOM. This applies to the EigenTunnel Scanner fips-openssl build. EigenTunnel Scanner runs entirely inside your boundary and sends no data to any Eigen-Systems cloud service, so no FedRAMP authorization is needed to deploy it. Findings stay on your network or go only to the tools you already run. Limits: No verified customer GRC import or production export pipeline claimed. |
| C06: OSCAL artifacts | Working drafts; validation incomplete | SSP, POA&M, AP and AR drafts (system security plan, plan of action and milestones, assessment plan and assessment results) target OSCAL v1.2.2 (a machine-readable format for compliance documents). Limits: The recorded schema audit failed all four drafts. No validated export, component definition, GRC (governance, risk and compliance) integration or authorization claimed. |
| C07: EigenTunnel Console delivery | Unfinished / roadmap | EigenTunnel Console is our paid, managed service for setting up and running EigenTunnel connections. Payment and provisioning unfinished. Fleet enrollment (adding many devices together), approvals and dashboards remain roadmap. Limits: No generally available managed service, tenant isolation (keeping each customer’s data separate) assurance or service-level commitment. |
| C08: FRA (Federal Railroad Administration) rail application | Proposed research evaluation | Investigate connection-level protection alongside long-lived rail systems in an approved test environment. Limits: No rail deployment, signaling approval, safety integrity level, award or demonstrated safety benefit. |
| C10: Integrations and formal assurance | Not established for customer reliance | Integration scope (links to IT service, security monitoring, asset and compliance systems, such as ITSM, SIEM, CMDB, SOAR and GRC) must be evaluated individually. Limits: No verified ITSM/SIEM/CMDB/SOAR/GRC connector, FIPS 140-3 validation, FedRAMP/ATLAS (the Department of War CIO’s Cryptographic Acquisition, Testing, and Licensing Authorization for Security review) authorization, CJIS compliance, NIAP/CSfC qualification or independent audit claimed. |
Technical diligence package
Core (the commercial EigenTunnel software) source remains private. Request scope and availability of architecture and implementation material under separately approved access terms; an NDA alone does not grant access. A complete reviewed assurance package is not yet published.
- Protocol/state machine, hybrid combiner, transcript binding and downgrade protection: consolidated reviewer package pending.
- Replay handling, peer revocation, key storage/rotation/destruction: implementation evidence must be reviewed for the exact build; production assurance pending.
- Relay trust model and visible metadata: formal reviewed model pending. Do not assume an untrusted relay cannot inspect traffic without verifying that architecture.
- Dependency inventory/SBOM (software bill of materials), Rust unsafe review, build provenance and signing: complete release assurance bundle pending. Checksums alone are not publisher signatures.
- Benchmarks: no representative operational performance claim. Raw repeatable relay results remain to be assembled.
- Security reports: contact Patrick privately to arrange reporting. Do not send secrets or exploit details through the general inquiry form. No response-time SLA (service-level agreement) claimed.
How to use this index
Cite a claim ID, review date, exact build and evidence source in an evaluation or proposal. Historical builds and founder reports do not establish current production assurance. Recheck this register before forwarding older collateral.