Security Model
Tamandua Sentinel is designed around a strict separation between private endpoint telemetry and public security proof.
The endpoint agent and server are operated by the organization. Sensitive telemetry remains in that self-hosted environment. Solana is used only as a public proof and settlement layer for privacy-safe attestations, bounty settlement, and future security-oracle workflows.
Trust Boundaries
| Boundary | Responsibility |
|---|---|
| Endpoint agent | Collects telemetry, executes response actions, and enrolls with short-lived credentials |
| Agent transport | Uses authenticated WebSocket transport and mTLS-backed runtime channels |
| Tamandua server | Stores telemetry, runs detection logic, manages alerts, and prepares attestations |
| Solana proof layer | Stores hashes and minimal metadata, never raw endpoint data |
| Public verification | Allows third parties to verify that an attestation exists without seeing private telemetry |
Data That Stays Private
Tamandua does not publish raw endpoint telemetry to Solana. The following data must remain inside the operator-controlled environment:
- Hostnames
- Usernames
- Internal IP addresses
- Local file paths
- Process command lines
- Credentials or secrets
- Customer names
- Raw process trees
- Raw event payloads
Data That Can Be Published
Public proofs are limited to fields that are useful for verification without identifying the victim environment:
- Incident hash
- Manifest hash
- Severity
- MITRE technique IDs
- IOC count
- Safe IOC types
- Rule hash
- Malware family label when safe
- Pseudonymous organization and agent identifiers
- Timestamp
- Solana transaction signature
Agent Enrollment
Agent enrollment uses short-lived tokens. Tokens are shown once, stored only as hashes, and exchanged for runtime credentials. The server generates the agent identity and does not trust a client-supplied agent ID.
mTLS Runtime Channel
Production deployments should use mTLS for the runtime agent channel. Enrollment can happen over the web endpoint, but the long-running agent connection should use the dedicated mTLS-backed channel.
Open Source Posture
Tamandua may gradually publish selected Core EDR components. Those components should prioritize auditable security logic, reproducible builds, transparent detection content, and clear disclosure processes. The mobile analyst app, native mobile endpoint/MTD, and App Guard are outside that open-source intent and remain closed commercial products.
See Open Source Risk for the security tradeoffs of open-sourcing endpoint security software.