Halcyon Tech takes the security and integrity of our software systems, client platforms, and open-source contributions with the utmost seriousness. This document outlines our vulnerability reporting policy, response protocols, and security practices across the HalcyonTech-LTDA organization.
If you believe you have discovered a security vulnerability or weakness in any repository, application, or service maintained by Halcyon Tech, please report it to us privately.
Caution
Do not open public GitHub issues, discussions, or pull requests for suspected security vulnerabilities.
To submit a confidential vulnerability report, please send an encrypted or direct email to:
- Primary Security Contact:
developers@halcyontech.com.br - Subject Line:
[SECURITY] Potential Vulnerability in <repository-or-service>
To assist our security engineers in triaging and resolving the issue promptly, please include:
- Target: The specific repository, URL, service, or component affected.
- Vulnerability Type: An overview of the vulnerability (e.g., SQL Injection, Remote Code Execution, Privilege Escalation, Information Disclosure).
- Step-by-step Reproduction: Clear, actionable steps, commands, or proof-of-concept (PoC) scripts necessary to reproduce the issue.
- Impact Assessment: Your estimate of the potential impact on affected users, systems, or data.
- Mitigation Suggestions: Any remediation ideas, patches, or configuration changes you believe would resolve the issue (optional).
When you submit a vulnerability report through our designated channels, Halcyon Tech commits to:
| Stage | Target Response Time | Action |
|---|---|---|
| Initial Acknowledgment | Within 48 hours | Confirmation of report receipt and assignment to a security engineer. |
| Initial Triage & Assessment | Within 5 business days | Technical validation of the vulnerability and determination of severity score (CVSS). |
| Status Updates | Every 5 business days | Regular updates on investigation, reproduction, and remediation status. |
| Remediation & Patching | Timeline based on severity | Deployment of fixes to affected production services or release of patched packages. |
| Public Disclosure | Mutually agreed timeline | Coordinated public disclosure after fixes have been deployed and verified. |
Halcyon Tech supports responsible, ethical vulnerability research. We consider security research conducted under this policy to be authorized. We commit not to pursue legal action against researchers who:
- Act in good faith to avoid privacy violations, data destruction, service degradation, or interruption of production services.
- Keep details of vulnerabilities strictly confidential until a fix has been validated and deployed.
- Do not exploit a vulnerability beyond the minimal proof required to demonstrate its existence.
- Do not exfiltrate, alter, or expose sensitive customer or operational data.
All software developed by Halcyon Tech adheres to strict shift-left security principles:
- Zero Secrets in Code: Automated pre-commit hooks and CI scans prevent credentials or API tokens from entering version control.
- Least-Privilege RBAC: Access control and cloud IAM permissions follow least-privilege principles by default.
- Dependency Auditing: Automated continuous monitoring for vulnerable dependencies and supply chain attacks.
- Encrypted State & In-Transit Data: State storage, databases, and network communications mandate strong encryption (TLS 1.3 / AES-GCM / KMS).