Responsible disclosure policy
Version 0.1.0, November 18, 2026.
Responsible disclosure policy
Do you think you have found a security vulnerability in AttackScout? Thank you for writing to us. This page explains how to do so, what you may test and what we commit to doing.
1. How to report
- Email: [email protected], or [email protected] as a second contact.
security.txtfile:https://attackscout.com/.well-known/security.txt(RFC 9116).- Languages: French, English, Spanish.
- Encryption: we do not publish a PGP key at this time. Do not send third parties' personal data in your report; if a sensitive detail is needed, first ask us for a suitable way to exchange it.
Describe the vulnerability, the address concerned, the steps to reproduce it, its possible impact and, if you wish, how you would like to be credited.
2. What is in scope
attackscout.comand its subdomains operated by AttackScout.- AttackScout's APIs and customer account.
- The
AttackScout-Probeprobe: behavior contrary to our "Our probe" page (pace, paths, unannounced requests) is also a welcome report.
3. What is out of scope
- Our providers' services (Google Cloud, Cloudflare, Brevo, Mollie, Invopop, Anthropic, Discord): report to them directly.
- Denial-of-service attacks, load testing, spam.
- Social engineering, phishing, physical attacks.
- Findings without demonstrated impact (for example a missing header without an exploitation scenario, software versions without an exploitable flaw, enumeration of public email addresses).
4. Rules to follow
For your research to remain in good faith: a) only use accounts you created for your tests; never access another user's data; b) if you accidentally access data that is not yours, stop, do not keep it, do not share it, and report it to us; c) do not modify or delete any data; do not degrade the service; d) do not use AttackScout to audit a domain without the right to do so (terms of use, Art. 5); e) do not use high-volume automated tools; f) give us reasonable time to fix before any publication: we suggest 90 days, to be adjusted together; g) do not ask for money in exchange for your report.
5. Our commitments
- Acknowledge receipt within 5 business days.
- Give you an initial assessment within 15 business days, then updates at least every 30 days.
- Fix according to severity, and let you know when it is fixed.
- Credit you, if you wish, on an acknowledgments page.
- Not take legal action or file a complaint against anyone who has followed this policy in good faith. This commitment binds AttackScout only: it does not bind the authorities or third parties, such as our providers.
AttackScout does not offer a financial reward (bug bounty) at this time.
6. Personal data
Reports are handled under the privacy policy (§3.10). We keep your email and our exchanges for 3 years after the last exchange.
7. Content of the security.txt file
The file published on our website contains:
Contact: mailto:[email protected], thenContact: mailto:[email protected](in order of preference);Expires:a validity date, renewed for less than a year, as recommended by RFC 9116;Preferred-Languages: fr, en, es;Canonical: https://attackscout.com/.well-known/security.txt;Policy:the address of this page.