1. Responsible Disclosure Philosophy
ENCLAVE is dedicated to delivering resilient, zero-knowledge cryptographic communication tools. We deeply appreciate the security research community's contributions to finding and responsibly reporting vulnerabilities. We commit to working with researchers collaboratively and transparently.
2. Safe Harbor for Security Researchers
If you conduct research in good faith and in compliance with this policy:
- • We consider your security research activities authorized and lawful.
- • We will not initiate legal action against you under anti-hacking statutes (such as the IT Act, 2000, or CFAA).
- • We will work with you to understand, validate, and remediate the issue promptly.
3. In-Scope & Out-of-Scope Targets
In-Scope Research Targets
- Cryptographic engine (
packages/crypto) - Protocol framing & sequence validation (
packages/protocol) - Room relay and presence APIs (
/api/rooms/*) - Client Web application and authentication stores
Out-of-Scope & Prohibited
- Denial of Service (DoS/DDoS) and network packet flooding
- Social engineering, phishing, or physical intrusion
- Accessing, modifying, or retaining other users' communication data
- Automated volume scanning causing service degradation
4. How to Submit a Vulnerability Report
Please submit detailed vulnerability findings to enclave.support.legal@gmail.com including:
- Vulnerability Summary: Description of the issue, root cause, and potential security impact.
- Step-by-Step Reproduction: Clear steps or minimal proof-of-concept (PoC) code to reproduce the issue.
- Affected Versions/Files: Specific code paths or endpoints involved.
- Suggested Remediation: Any technical recommendations for resolving the vulnerability.
5. Assessment & Remediation Targets
| Phase | Target Timeline | Action Description |
|---|---|---|
| Initial Acknowledgement | Within 24 to 48 hours | Confirm receipt and assign security tracking ticket. |
| Technical Triage | Within 3 to 5 business days | Validate vulnerability and assign CVSS severity rating. |
| Patch & Deployment | Within 14 to 30 calendar days | Engineer fix, execute test suites, and deploy to production. |
6. Coordinated Public Disclosure
We request that researchers allow a minimum 60-day coordinated disclosure window from the date of submission before publishing advisories or technical write-ups, giving our team sufficient time to deploy verified patches to all users.
7. Security Desk Contact
For formal data rights requests, security disclosures, or regulatory inquiries concerning this policy, submit a verified request through our official channels.