A buyer's evaluation checklist

Eight checks for
your shortlist.

A managed vulnerability disclosure program gives external reporters a defined way to reach your organization and adds operational support for handling their findings. The provider you choose should make the reporting journey clear for researchers and the next action clear for your engineers.

Use these questions to evaluate any provider. The Hackrate column explains our approach, while the final column gives you something concrete to verify during scoping.

What to evaluate
Ask the provider
The Hackrate approach
Evidence to request
Policy and scope
How will you define the covered assets, reporting rules and customer responsibilities?
Hackrate helps establish the disclosure policy and reporting process around the assets and handling you agree.
Review the proposed policy, exclusions and ownership before launch.
Explore mVDP setup
Report intake
Can researchers find the channel and submit enough evidence to assess a report?
Embed Hackrate's submission form on your website to provide a structured route for incoming vulnerability reports.
Ask to see the form and the information requested from a reporter.
See the reporting approach
Technical validation
Who reviews the evidence, checks scope and distinguishes useful findings from invalid or duplicate reports?
Hackrate's security team reviews submissions, assesses technical validity and severity, and seeks clarification where needed.
Walk through an example with evidence, a validation decision and the reasoning behind it.
Explore report validation
Researcher communication
Who follows up with the reporter and explains the outcome?
Hackrate coordinates researcher communication within the agreed service, helping your team maintain a clear reporting conversation.
Agree acknowledgement, follow-up, escalation and closure responsibilities.
Read about coordination
Engineering handoff
Will engineers receive the technical detail they need to investigate and prioritize the issue?
Validated findings are managed through the platform with technical information, severity assessment and supporting evidence.
Ask for a report walkthrough and confirm status tracking and any integration requirements.
See a report example
Service commitments
What happens when a critical report arrives, a contact is unavailable or volume exceeds the plan?
Define the included handling, service levels and customer contacts in your Hackrate proposal.
Get response coverage, escalation routes, report limits and additional-work terms in writing.
Discuss service requirements
Security and control
Who can access vulnerability data, and what are the retention, export and disclosure arrangements?
Use Hackrate's Trust Center and a scoping discussion to review the platform and your organization's requirements.
Request the relevant security documentation and confirm the data-handling terms for your engagement.
Visit the Trust Center
Disclosure and CVE support
Can the provider support coordinated publication when an eligible vulnerability needs a CVE record?
Hackrate is a CVE Numbering Authority and offers optional CVE coordination for eligible findings within its approved scope.
Confirm eligibility, included support, customer approval and publication timing.
Explore Hackrate CNA support

Service inclusions depend on the agreed engagement. Use the proposal to confirm scope, report handling, response commitments, integrations and any optional support.

Why choose Hackrate?

Make disclosure
a process your team can use.

Hackrate is a strong fit for product and security teams that want a clear reporting channel, expert assessment and help coordinating the people behind each finding.

A clear route from your website.

Give researchers a visible place to submit vulnerabilities through Hackrate's embeddable form. We help establish the reporting policy and handling workflow around your organization.

Your website remains the starting point for the disclosure process, with the platform supporting structured intake and follow-up.

Explore the managed VDP service

Human validation and communication.

Hackrate's security specialists assess the evidence and work with reporters when more information is needed. The aim is to help your engineers focus on findings they can investigate and act on.

Validation and communication stay connected, so the report reaches your team with technical context and a reasoned assessment.

See how Hackrate triages reports

A path to coordinated CVE records.

When a finding is eligible and falls within our approved CNA scope, Hackrate can support CVE assignment, record preparation and coordinated publication as an optional service.

This gives teams a way to connect validated evidence with the wider vulnerability disclosure process when a public record is appropriate.

Read the CVE Program announcement

Buying through AWS Marketplace?

Hackrate's managed VDP is listed on AWS Marketplace. If that suits your procurement process, discuss a private offer covering your assets, service scope and commercial terms.

View Hackrate mVDP on AWS Marketplace

Make the demo practical

Follow one report
from intake to action.

Ask the provider to walk through a sanitized or illustrative report. You should be able to see who owns each step, what the reporter hears, and what your engineering team receives.

Bring your own requirements to a Hackrate conversation. A current policy, asset list and example of the reports you receive will help us show where managed support fits.

01 / RECEIVE

Show the reporting journey.

Check how a researcher finds the policy, understands the scope and submits evidence. Ask what happens if a report is incomplete or arrives through an existing security inbox.

Look for: a clear channel, useful submission fields and an agreed acknowledgement process.

02 / ASSESS

Explain the validation decision.

Ask how scope, evidence, severity and duplicates are assessed. See how the team requests clarification and records what it could establish.

Look for: technical reasoning, reproducible evidence where available and a clear distinction between an unconfirmed report and a validated finding.

03 / HAND OVER

Make the next action clear.

Follow the finding into the customer's workflow. Ask how a technical owner receives the details and how a potentially urgent issue reaches the agreed contacts.

Look for: an actionable report, an escalation route and a customer owner who can prioritize remediation.

04 / COORDINATE

Track the outcome.

Discuss researcher updates, customer decisions, remediation status and any agreed retesting or disclosure support. Include CVE coordination if it is relevant to your product.

Look for: a recorded outcome, clear approvals and a shared understanding of any work still open.

Ask about the difficult handoffs.

What if the researcher disputes the severity? What if your technical contact is unavailable? What if a report needs access the provider does not have? Use the answers to agree escalation and decision ownership before the program starts.

Plan your team's involvement

Agree the operating model

Choose the scope.
Know what is included.

Compare proposals against the same assets, reporting needs and contract period. Ask how the provider counts included reports, handles extra work and supports your required communication channels.

Hackrate can support an existing disclosure process or help establish a new one. The scoping conversation should connect your requirements to a concrete service proposal.

Confirm the service and price.

  • Covered applications, APIs and other eligible assets.
  • Included intake, technical validation and researcher communication.
  • Response coverage, escalation contacts and report limits.
  • Setup, integrations, extra reports and additional-work charges.
  • Any retesting, disclosure or CVE coordination support.
  • Contract duration, currency, taxes and renewal terms.
Explore Hackrate solutions and pricing

Prepare the customer side.

  • A decision owner and a backup contact.
  • Authority over the assets covered by the program.
  • A policy and a clear place to publish the reporting channel.
  • Technical contacts who can answer product questions.
  • An engineering team or provider able to implement fixes.
  • An agreed route for disclosure and publication decisions.
See how to prepare your first month

Need active security testing as well?

Hackrate also offers bug bounty programs and penetration testing. A managed VDP handles incoming disclosures; commissioned testing and researcher rewards need their own scope and terms. We can help you choose the combination that fits your goals.

Compare managed VDP, bug bounty and pentesting

Already running your own VDP?

Plan the move from an internal security inbox, reporting form or self-hosted tool. Our migration guide covers policy updates, open reports, researcher communication and the changeover to managed handling.

Move your self-hosted VDP to Hackrate

Frequently asked questions

The details worth agreeing.

Use these answers to prepare the conversation about your own scope and responsibilities.

What should I look for in a managed VDP provider?

Look for a clear disclosure policy and reporting channel, technical validation, researcher communication, actionable reporting and a defined customer handoff. Ask for evidence of the workflow, the people responsible and the service boundaries. Compare response commitments, report limits, data handling and total costs against your requirements.

Why choose Hackrate for managed vulnerability disclosure?

Hackrate is a strong fit for teams that want support across disclosure setup, report intake, human validation and researcher coordination. Its submission form can be embedded on your website, with findings handled through the Hackrate platform. For eligible vulnerabilities, optional CVE coordination can connect validated evidence to a public record within Hackrate's approved CNA scope. Confirm the included work and service levels in your proposal.

Can Hackrate work with our existing disclosure policy or security inbox?

Yes. Hackrate can work with an existing VDP, responsible disclosure policy or coordinated disclosure process. Start by reviewing the current policy, covered assets, reporting channels and open reports. Agree how the Hackrate reporting channel and handling workflow will fit, including ownership of any transition and outstanding communication.

Does managed VDP include a bug bounty program or penetration test?

No, those are separate service choices. Managed VDP focuses on incoming reports and their handling. A bug bounty program has explicit testing and reward rules, while a pentest commissions a scoped assessment. Hackrate offers these services, so you can discuss a broader security program while keeping permissions, deliverables and budgets clear.

Who fixes vulnerabilities and decides when to disclose them?

Your organization owns risk decisions, engineering changes and disclosure approvals. Hackrate supports the agreed assessment and coordination process, including communication with the reporter. Define the technical owner, escalation backup and any retesting or disclosure support before launch so that validated findings have a clear route to action.

Can Hackrate assign a CVE ID to a reported vulnerability?

Hackrate is a CVE Numbering Authority and can support CVE assignment and record preparation for eligible vulnerabilities within its approved scope. Eligibility, duplication, affected products and disclosure timing must be assessed. CVE support is optional and should be agreed; a report submitted through a VDP does not automatically qualify for a CVE ID.

How should we compare managed VDP pricing?

Compare the covered assets, included report handling, validation depth, communication, escalation and contract period. Ask how limits are counted, what additional reports or work cost, and whether setup, integrations, retesting or CVE coordination are included. Use Hackrate's pricing page as a starting point and confirm the scope and commercial terms in a proposal.

What should we prepare for a managed VDP demo?

Bring the assets you control, your current disclosure policy or reporting address, examples of the reports you receive and your technical contacts. Explain your handling needs and any response, data or procurement requirements. Ask Hackrate to walk through intake, validation, researcher communication, escalation and the handoff to your engineering team.

A practical next step

Build your disclosure process with Hackrate.

Bring your current reporting process, proposed assets and handling requirements. We will help define the channel, validation workflow, escalation contacts and commercial scope for your managed VDP.

Hackrate

Our platform helps companies to identify software vulnerabilities in a cost-efficient way. It provides a secure and centralized view of ethical hacking projects for your company.

US Patent Applied for HackGATE #63/645,845

Hackrate Status

Hackrate Ethical Hacking Platform |
2026 ©

CVE Program Numbering Authority