Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Company

Responsible Disclosure.

How to report a security vulnerability in Brandefense systems, and what to expect when you do.

Our Commitment

Security researchers help keep our customers safe. If you find a vulnerability in a Brandefense system, we want to hear about it. This page says what you may test, how to report and what to expect from us. Please read it before you start testing.

01Scope

Scope.

This policy covers systems that Brandefense owns and runs.

In scope03
  • The brandefense.io website and the subdomains that Brandefense owns and operates
  • The Brandefense platform web application and its API
  • Other applications and services that Brandefense owns and runs
Out of scope07
  • Systems owned by customers, partners or other third parties, even if they link to us
  • Third-party services that we use but do not operate
  • Denial-of-service and load testing
  • Social engineering, phishing or physical attacks against staff, customers or partners
  • Spam, and reports from automated scanners with no demonstrated impact
  • Missing security headers or best-practice settings with no proven security impact
  • Reports that depend on outdated or unsupported browsers
02Testing Rules

Testing Rules. Keep your testing small and safe.

Please+
  1. +01Test only with accounts and data that you own or have permission to use
  2. +02Use the least access needed to show the problem
  3. +03Stop testing and report as soon as you confirm a vulnerability
  4. +04Keep the details private until we have agreed on disclosure
Please do not×
  1. ×01Access, change, copy or delete data that is not yours, beyond the minimum needed as proof
  2. ×02Run denial-of-service tests
  3. ×03Use social engineering against our staff, customers or partners
  4. ×04Move on to other systems after you gain access
  5. ×05Install malware or leave persistent access behind
  6. ×06Share what you find publicly before we have had time to fix it
03How To Report

How To Report.

  1. Step 01 Write to us Email info@brandefense.io. Put "Security report" in the subject line.
  2. Step 02 We acknowledge it We aim to acknowledge your report promptly. We may ask you for more detail.
  3. Step 03 We investigate and fix We confirm the issue, work on a fix and keep you updated where we can.
  4. Step 04 We agree on disclosure Once the issue is fixed, we agree with you when and how details can be shared.
04What To Include

What To Include And What To Expect.

What to include 0 / 6 ready
What you can expect from us
  1. 01We aim to acknowledge your report promptly.
  2. 02We read the report and look at what you describe.
  3. 03We treat your report and your contact details as confidential.
  4. 04We keep you updated on progress where we can.
  5. 05This policy does not promise payment or a reward.
05Principles
Good-Faith Research

We appreciate good-faith research and will work with you.Please follow the rules on this page, stay within the scope, and ask us first if you are unsure whether an action is allowed. This page does not cover third-party systems, and it does not offer payment or a bug bounty.

Coordinated Disclosure

We ask you to give us reasonable time to fix a problem before you share details with anyone else.We will work with you to agree a date for public disclosure. We may publish an advisory when a fix is released. We credit reporters by name if they ask us to, and we do not name you without your consent.

06Send

Where To Send A Report.

Email info@brandefense.io with the subject line "Security report". Include the details listed above. Please send only the data needed to show the problem.

Send A Report →
To info@brandefense.io
Subject Security report
Brandefense logo

Know What Is Exposed. Before Attackers Do.

Book a demo of the platform.

4.8Gartner Peer Insights
24hEarly warning time
190+Countries covered
What You See In The Demo
01 Your exposure Assets and services seen from the outside, starting from your own domain.
02 Threats aimed at you Leaked credentials, look-alike domains and brand abuse in one view.
03 From alert to action How findings reach your team and what to do next.