Security

Vulnerability disclosure policy

If you’ve found a security problem in OhAuthCat, we want to hear about it. This page explains what’s in scope, how to report it and what you can expect from us.

Scope

  • Every host under *.ohauthcat.com, including this site, the dashboard and the IT admin portal.
  • Our APIs, including the SSO, SCIM and management endpoints at api.ohauthcat.com.

How to report

Email security@ohauthcat.com. Please include:

  • the affected host, endpoint or feature;
  • the steps to reproduce it, with any requests, payloads or proof of concept;
  • what an attacker could do with it, as you understand it;
  • how you’d like to be credited, if at all.

Use only test accounts you own. If you reach data that isn’t yours, stop, don’t keep or share it, and tell us in your report.

What to expect

We aim to acknowledge your report within 3 business days and to give you a status update within 10 business days. These are targets, not commitments. We’ll keep you informed while we fix the problem and tell you when it’s resolved.

Safe harbour

If you act in good faith and follow this policy, we consider your research authorised. We won’t take legal action against you or ask law enforcement to investigate you for it. Good faith means you avoid privacy violations, data destruction and service disruption, you test only within the scope above, and you give us a reasonable time to fix the problem before you disclose it publicly. If a third party takes action against you for research that followed this policy, we’ll make it known that your work was authorised.

Out of scope

  • Volumetric denial-of-service or load testing.
  • Social engineering or phishing of our staff, customers or their users.
  • Physical attacks on offices, data centres or people.
  • Findings from automated scanners without a demonstrated, exploitable impact.
  • Third-party services we use, such as Cloudflare, AWS and our payment providers; report those to the vendor.

Rewards

We don’t run a bug bounty programme yet, so we can’t pay for reports. With your permission, we’ll gladly thank you by name once the problem is fixed.

Machine-readable contact details are in /.well-known/security.txt. For how the product protects sign-ins, see security and reliability; for sub-processors and policies, see the trust centre.