We sell attack-surface management, so we expect to be held to the standard we hold others to. If you have found a weakness in our platform, we want to hear about it and we will not treat you as a threat for telling us.
Include enough detail to reproduce: affected URL or endpoint, the steps, and what you observed. Screenshots or a short request/response capture help. Please write in English.
hexasentra.com — this websiteapp.hexasentra.com — the applicationTenant isolation is the one we care about most. If you can read, modify, or infer another organization's data, treat it as critical and tell us immediately.
Create your own account to test with. If you need a trial to do so, ask us at security@hexasentra.com and we will provide one.
No paid bounty yet
We do not currently run a paid bug-bounty programme, and we would rather say so plainly than imply one. We offer public credit, a written advisory, and swag where we can. We would rather receive your report than have you withhold it for want of a payout — if you believe a finding warrants compensation, say so in your report and we will discuss it honestly.
Every tenant table is enforced in the database, and the application connects as a role that cannot bypass it. This is verified by an automated test suite on every change.
Credentials you store for authenticated scanning are encrypted with a key held outside the database, so a database copy alone does not reveal them.
No packet leaves our infrastructure for a target until an authorization for it has been verified. Authorizations expire, and expiry stops scanning without anyone intervening.
Card details go directly to our payment processor. We never receive or hold them.
We only scan what you have demonstrated you control, and we record that authorization against every scan. If you are the owner of a system and believe we are scanning it without your permission, email security@hexasentra.com with the hostname and we will suspend scanning of it while we verify — before asking you for anything else.
This policy is also published at /.well-known/security.txt per RFC 9116.