Vulnerability disclosure program (VDP)

A public channel and a working process for vulnerability reports from outside: policy, security.txt, intake, triage and coordinated disclosure.

Programs and assurance

Sooner or later someone outside the company finds a vulnerability in your product. What happens next depends on whether they can find an address to write to and on whether anyone answers. Where there is no channel, the report goes to a support inbox, to social media or nowhere at all.

A disclosure program is the minimum: a published policy that says how to report and what the reporter may expect, an inbox that is read, and a process that takes a report from receipt to a fix. It pays no rewards and needs no platform. The EU Cyber Resilience Act makes a coordinated disclosure policy mandatory for manufacturers of products with digital elements: reporting of actively exploited vulnerabilities applies from 11 September 2026, the full set of obligations from 11 December 2027.

01Scope

What we test

  • Disclosure policy: scope, rules, safe harbour, disclosure timeline
  • security.txt according to RFC 9116, with monitoring of its expiry date
  • Intake channel: dedicated mailbox or form, encryption key, acknowledgement
  • Triage procedure: reproduction, severity rating, deduplication
  • Internal handling according to ISO/IEC 30111: ownership, deadlines, escalation
  • Communication with reporters and coordinated publication
  • Advisories and CVE identifiers for vulnerabilities in your products
  • Reporting obligations under the Cyber Resilience Act and NIS2, where they apply

02Approach

How the work is done

  1. Policy

    We draft the policy with your legal team. The safe harbour wording follows the text that the research community recognises, adapted to your jurisdiction by your lawyers.

  2. Channel

    The intake channel and security.txt are set up and tested from outside, the way a researcher would find them.

  3. Process

    Roles, deadlines and escalation are written down and rehearsed on a test report before the policy is published.

  4. Operation

    If you wish, we operate the intake: acknowledge, reproduce, rate and hand confirmed reports to your engineers.

Methodology

03

What you receive

  • Disclosure policy ready for publication
  • security.txt and the procedure for renewing it
  • Handling procedure with roles, deadlines and templates for replies
  • Record of a rehearsal with a test report
  • Executive summary for management
  • Technical report: every finding with evidence, CVSS 4.0 vector, CWE class and fix
  • Debrief call with your engineers
  • One retest of every finding within 60 days of the report
  • Attestation letter after the retest

04

What we need from you

  • A decision on which products and systems the policy covers
  • An owner of the process inside the company
  • Legal review of the policy
  • A mailbox or form under your own domain

05Standards

Standards behind the method

06Questions

Questions about this service

Someone has sent us a vulnerability report and asks for money. What do we do?

Do not pay under pressure and do not threaten. Acknowledge receipt, ask for the technical detail and verify the claim. Most unsolicited reports come from researchers acting in good faith, some are automated noise, a few are extortion. We verify the report, assess its severity and help you answer; request it through the form on this site and mention that a report is pending.

What is the difference between a disclosure program and a bug bounty?

A disclosure program receives reports and promises fair treatment. A bug bounty adds payment and thereby invites active searching. The first is a baseline for every company with a product online, the second is a decision about budget and readiness.

Does a safe harbour clause expose us to risk?

It commits you not to pursue people who follow your rules. It does not authorise anything outside those rules and it does not bind third parties or prosecutors. The text is reviewed by your lawyers before publication.

08Request

Tell us what needs testing

  • Website check free of charge
  • Reply within 1 business day
  • NDA before any technical detail
  • Fixed price for paid engagements
  • No obligation

Request an assessment

Describe the systems and the goal. A manager replies within 1 business day with clarifying questions and the next step.

Who to reply to

We reply to this address unless you choose another channel.

A sole proprietor writes their own name.

Preferred channel
What to assess
Services of interest

Choose all that apply.

Free check

We check your website free of charge

If we find no problems, you receive the report free of charge as well. You pay for the report only when we find problems, and its price depends on their number and severity.

Terms of the free website security check

Application security

Infrastructure and cloud

Adversary simulation

AI, Web3 and cryptography

Programs and assurance

Application security

Free website security check

We look at your website from the outside, the way an attacker does, and check whether it can be broken into: weak settings, outdated software, exposed files, unsafe forms. The check is free of charge.

Application security

Web application penetration testing

We try to break into your web application the way a real attacker would: log in to the accounts of other people, read the data of other customers, change prices or orders. You learn what is possible before criminals do.

Application security

API security testing

An API is the channel through which your app, your website and your partners exchange data with your servers. We check that nobody can use it to read or change data that is not theirs.

Application security

Mobile application penetration testing

We examine your iOS or Android app and the servers behind it: what the app keeps on the phone, what can be extracted from it and whether its requests can be tampered with.

Application security

Secure code review

Our specialists read the source code of your product and find the mistakes that lead to a break-in, including those that cannot be seen from the outside.

Infrastructure and cloud

Cloud & Kubernetes security assessment

We check how your cloud is set up (AWS, Azure, Google Cloud, Kubernetes): who has access to what, which data is open to the internet and how far an attacker gets after the first mistake.

Infrastructure and cloud

Infrastructure penetration testing

We test your servers and your office network from the outside and from the inside: can an attacker get in, and once inside, reach the accounting system, the mail or the backups.

Infrastructure and cloud

External attack surface assessment

We find everything your company exposes to the internet, including what has been forgotten: old websites, test servers, leaked passwords. Then we show which of it can be attacked.

Infrastructure and cloud

CI/CD & supply chain security

We check the path your code takes from the developer to the customer: build servers, third-party libraries, access keys. Whoever controls that path controls your product.

Adversary simulation

Red team operations

A full-scale exercise. Our team plays a real attacker with a goal, for example to reach customer data, and you see whether your defence notices and stops it.

Adversary simulation

Purple team exercises

Our attackers and your defenders work side by side: we show an attack technique, your team checks whether it sees it, and the gaps in monitoring are closed on the spot.

Adversary simulation

Social engineering assessment

We test people, not machines: the phishing emails, calls and messages that attackers use to obtain passwords. You learn how many employees would be deceived and what to train.

AI, Web3 and cryptography

AI & LLM security testing

If your product has a chatbot or another AI model, we check whether it can be talked into revealing confidential data, breaking its own rules or acting on behalf of someone else.

AI, Web3 and cryptography

Smart contract audit

Before a smart contract holds money, we look for mistakes in its code that would let someone withdraw or freeze the funds. After deployment such mistakes cannot be corrected.

AI, Web3 and cryptography

Cryptography review

We check how your product encrypts data and protects keys: whether the right algorithms are chosen and whether they are applied correctly. A mistake here makes the encryption useless.

Programs and assurance

Bug bounty program management

A bug bounty is a program in which independent researchers look for vulnerabilities in your product and are paid for each one they find. We launch and run such a program for you.

Programs and assurance

Vulnerability disclosure program (VDP)

A public page and a procedure that tell researchers how to report a vulnerability to you safely. Without them reports get lost or arrive as threats. We set the process up and handle incoming reports.

Programs and assurance

Continuous penetration testing

Instead of one test a year, we test every significant change of your product throughout the year, so that a new vulnerability does not wait for months to be found.

Programs and assurance

Compliance-driven penetration testing

A penetration test arranged so that an auditor, a regulator or a large customer accepts its report: PCI DSS, DORA, NIS2, ISO/IEC 27001, SOC 2.

Services of interest

Not sure yet

Choose this if you do not know which service you need. Describe the task in your own words, and a specialist will suggest the service in the reply.

Domain or URL of the website or of the main system to test, for example app.example.com.

What needs testing, why now, and any deadline or compliance requirement. No passwords, keys or vulnerability details.

Confirmations

Do not send credentials, keys or details of a vulnerability through this form. A secure channel is agreed after the first reply.

Automated abuse check