As an AI governance platform trusted by enterprise security teams, we hold ourselves to the highest security standards. Security isn't a feature - it's our foundation.
Security is built into every layer of Areebi. From infrastructure to application, we follow industry best practices and exceed compliance requirements.
AES-256 encryption at rest and TLS 1.3 in transit. All data is encrypted by default with customer-managed keys available on Enterprise plans.
Every request is authenticated and authorized. No implicit trust, network-level isolation, and least-privilege access controls throughout the platform.
Regular third-party penetration testing and red team exercises. Findings are remediated on strict SLAs and results are available to customers under NDA.
Continuous vulnerability scanning, automated dependency updates, and a structured patch management process with severity-based SLAs.
For a comprehensive overview of our security posture, certifications, and compliance status, visit our Trust Center.
We value the security research community and welcome responsible disclosure of vulnerabilities. If you've found a security issue, we want to hear from you.
Send your report to security@areebi.com. Please encrypt sensitive details using our PGP key (available at /.well-known/security.txt).
We will confirm receipt of your report and assign a tracking ID.
Our security team will assess the severity and impact of the reported vulnerability.
Critical: 7 days. High: 14 days. Medium: 30 days. Low: 90 days. We will keep you updated on progress.
Areebi will not pursue legal action against security researchers who report vulnerabilities in good faith and in accordance with this policy. We consider security research conducted under this policy to be authorized and will not initiate legal claims against you for circumventing technological measures we have employed to protect the applications in scope.
We ask that you make a good faith effort to avoid privacy violations, data destruction, and interruption or degradation of our services during your research.
Our /.well-known/security.txt file follows the RFC 9116 standard and contains our security contact information, PGP key, and disclosure policy reference.
For more details, visit our Trust Center, review our Privacy Policy, read our Terms of Service, explore our platform security features, or check our compliance certifications. Have questions? Get in touch.
Our security team is available to answer questions, provide documentation, or discuss our practices in detail.