---
title: "Responsible Disclosure Policy"
url: "https://grc.plus/policy/responsible-disclosure/"
type: "Policy"
updated: "2026-11-12"
publisher: "GRC+"
---

# Responsible Disclosure Policy

How to report a security vulnerability in GRC+ systems, what we need from you and what you can expect from us. We do not run a bug bounty.

In effect from 12 November 2026 · Version 3.0 · [Download PDF](https://grc.plus/policy/responsible-disclosure/pdf/?v=0e60ac50)

In short

- Thank you for looking: we fix real vulnerabilities in our systems quickly.
- We do not run a bug bounty, so reports are not paid, whatever the severity.
- A report needs steps to reproduce and a working proof of concept.
- Scanner output and the low-risk findings listed below do not qualify on their own.
- If you act in good faith within this policy, we will not take legal action against you.

Thank you for taking the time to look at our security. We work in security ourselves, so we take every real vulnerability in our systems seriously and fix it quickly. This page explains what we need from you, what you can expect from us, and which findings do not need a report. It follows the Dutch National Cyber Security Centre’s guideline for coordinated vulnerability disclosure. Our contact details are also in [security.txt](/.well-known/security.txt).

## We do not run a bug bounty

GRC+ does not pay for vulnerability reports, whatever the severity. That means no reward, no gift and no paid “hall of fame” entry. We say this up front so you can decide how to spend your time before you start.

A report that asks for payment, or that makes disclosure depend on payment, is not something we can take forward. If you are looking for paid research work, a bug bounty platform is a better place for it.

We are glad to say thank you in public: with your permission, we name you on this page once a serious issue you reported has been fixed.

## What we want to hear about

Vulnerabilities that you can show have a real impact on the confidentiality, integrity or availability of GRC+ systems or of the data we hold. For example:

- remote code execution, SQL injection or other injection that reaches data or the server;
- a way around login or permissions, including access to another user’s data (IDOR);
- cross-site scripting that works against other users without unusual interaction;
- exposure of personal data, credentials, keys or confidential documents;
- server-side request forgery or path traversal that reaches internal resources;
- payment or subscription logic that gives access to paid services without paying.

## Systems in scope

Systems run by GRC+: grc.plus and its subdomains, and GRC+ apps and integrations. Systems of our clients and of our providers, such as HubSpot, Microsoft, Stripe, Google or our hosting company, are not ours to fix: please report those to the provider. A third-party service on one of our subdomains stays the provider’s responsibility.

## Findings that do not need a report

Automated scanners flag many things that are not a risk for a site like ours, or that we have already decided to accept. To save you the effort, these findings do not qualify on their own. We do read every report, but we do not reply individually when a report only contains one of them:

- scanner or tool output without manual checking and a working proof of concept;
- missing or “weak” HTTP security headers, cookie flags, CSP or HSTS settings;
- SPF, DKIM, DMARC, BIMI or other e-mail configuration advice;
- clickjacking on pages without a sensitive action, and tabnabbing;
- software or version disclosure, banner grabbing, directory listings without sensitive content, descriptive error messages;
- CSRF on forms without a sensitive action, such as login, logout, contact or newsletter forms;
- self-XSS, and content or text injection without script execution;
- missing rate limits on public forms, or being able to send many form submissions;
- user enumeration through the login or password reset pages;
- public files and pages such as robots.txt, sitemap.xml, llms.txt, wp-json routes that list public content, or the reachable WordPress login page;
- SSL or TLS settings such as cipher suite order, without a practical attack;
- broken links, typos, and social media accounts or domains we do not own;
- attacks that need physical access, a compromised device or an outdated browser;
- denial of service, load testing, social engineering, phishing and spam.

If you believe one of these does have a real impact in our case, you are welcome to report it: show the impact with a working proof of concept and we will look at it properly.

## How to report

The quickest way is the security report form on this page. It asks for what we need to reproduce the problem: the affected address or system, the type of vulnerability, the impact, the steps and a proof of concept. You can also e-mail [security@grc.plus](mailto:security@grc.plus); those reports go through the same review.

Please leave out any personal data you came across. You can write in English or Dutch, and you may report anonymously.

## Encrypting your report

The report form on this page is sent over an encrypted connection, so most reports need nothing more. If you prefer to e-mail us, or your report contains sensitive details, you can encrypt it with our PGP key:

Key

GRC+ Security <security@grc.plus>

Fingerprint

`B516 C076 76A0 4F3B 9487 D5FE 5746 A8DB 9AE6 BDAC`

Valid until

12 November 2029

Download

[/.well-known/pgp-key.asc](https://grc.plus/.well-known/pgp-key.asc) · [keys.openpgp.org](https://keys.openpgp.org/search?q=B516C07676A04F3B9487D5FE5746A8DB9AE6BDAC)

Please send your own public key with an encrypted report, so we can reply in the same way.

## Testing with care

- Do only what is needed to show the vulnerability. Please do not copy, change or delete data; if you reach personal or confidential data, stop and let us know.
- Keep automated tools at a gentle pace that does not affect the site, and do not run denial-of-service tests.
- Do not install anything, keep access open, or move on to other systems.
- Keep the details confidential until the issue is fixed, and agree the timing of any publication with us. We aim to fix serious issues within 90 days.
- Stay within the law: this policy cannot authorise anything that is illegal.

## What you can expect from us

- We confirm receipt of an in-scope report within 3 business days and give a first assessment within 10 business days.
- We keep you informed until the issue is fixed, and tell you when it is.
- If you act in good faith and follow this policy, we will not take legal action against you or report you to the police for your report.
- We treat your report and your personal details confidentially and do not share them without your permission, unless the law requires it.

## Change history

| Version | Date | Change |
| --- | --- | --- |
| 3.0 | 12 November 2026 | Text revised; section on encrypting your report with our PGP key added. |
| 2.2 | 5 May 2026 | Security report form added. |

## More in Security and AI

- [Information Security Statement](https://grc.plus/policy/information-security/)
- [Responsible AI Statement](https://grc.plus/policy/responsible-ai/)
- [All policies](https://grc.plus/legal/)
