Responsible Disclosure
Last Updated:
May 14, 2024
At OctoAI, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.
If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.
This policy applies only to the domains octo.ai
, *.octo.ai
, octoai.cloud
, and api.octoai.cloud
. Any other services such as any connected services, are excluded from scope and are not authorized for testing.
Please do the following:
E-mail your findings to security@octo.ai. Optionally, encrypt your findings using our PGP key (see below) to prevent this critical information from falling into the wrong hands,
Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data,
Do not reveal the problem to others until it has been resolved,
Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties, and Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation,
Do not submit a high volume of low-quality reports.
What we promise:
If you have followed the instructions above, we will not take any legal action against you in regard to the report,
We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,
We will keep you informed of the progress towards resolving the problem,
In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise), and
As a token of our gratitude for your assistance, we offer a bug bounty for every report of a significant security problem that was not yet known to us.
We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved.
The following is a partial list of issues that we ask for you not to report, unless you believe there is an actual vulnerability:
Publicly accessible Jenkins servers
CSRF on forms that are available to anonymous users
Disclosure of known public files or directories (e.g. robots.txt)
Domain Name System Security Extensions (DNSSEC) configuration suggestions
Banner disclosure on common/public services
HTTP/HTTPS/SSL/TLS security header configuration suggestions
Lack of Secure/HTTPOnly flags on non-sensitive cookies
Logout Cross-Site Request Forgery (logout CSRF)
Phishing or Social Engineering Techniques
Presence of application or web browser 'autocomplete' or 'save password' functionality
Frontegg rate limits and Open Authentication Link
Sender Policy Framework (SPF) configuration suggestions
Please include the string
27949f5bddb688d6da7788642ff8a741
in your email body to qualify for review