Open Source Risk

Open-sourcing endpoint security software creates both trust and risk.

Tamandua's approach is to open the project gradually, starting with documentation, detection content, APIs, reproducible deployment paths, and non-sensitive integration logic. Components that need additional hardening can be released after review.

Benefits

• Operators can audit what the agent collects.
• Researchers can improve detection rules.
• The community can verify privacy guarantees.
• Self-hosted teams avoid vendor lock-in.
• Web3 operators can build integrations around optional signed attestations.

Risks

• Attackers can study detection logic.
• Poorly configured self-hosted deployments may expose sensitive telemetry.
• Fake bounty submissions can attempt to exploit weak validation.
• Unsafe response actions can cause operational disruption.
• Unsigned or unofficial builds can create supply-chain risk.

Mitigations

• Signed releases and documented build provenance.
• Clear separation between public rules and sensitive internal detections.
• Bounty validation through benchmarks, reviewer approval, and reputation.
• Short-lived enrollment tokens and server-generated agent identities.
• mTLS for long-running agent channels.
• Security disclosure process before broad public release.

Open Source Plan

Tamandua should publish code in stages:

1. Public website, documentation, and whitepaper.
2. Detection rules, sample integrations, and API clients.
3. Server and dashboard components after multi-tenant and auth review.
4. Agent code after enrollment, update signing, mTLS, and response safety review.
5. Driver and low-level components after independent security review.

This phased model gives the community transparency without rushing sensitive code before the security model is ready.