From a published policy to managed handling

Keep a clear front door.
Add the team behind it.

A vulnerability disclosure policy explains how someone can report a security issue. A working disclosure program also needs people to assess the evidence, answer the researcher and get useful findings to the right engineer.

If those tasks compete with product work or depend on one person's availability, managed support can help. Hackrate's managed vulnerability disclosure service brings report intake, human validation and researcher coordination into an agreed workflow.

Your policy can remain on your website. Review its content, embed the Hackrate reporting form and agree who handles each step after a submission arrives.

Make reporting easier to follow.

Give researchers a defined submission route and useful fields for evidence. Review the policy, form and contact instructions together so they explain the same process.

Explore managed VDP

Add technical review capacity.

Have Hackrate's security team assess incoming findings and seek clarification. Give engineers the evidence and technical context needed to decide their next action.

See how validation works

Give conversations an owner.

Agree who acknowledges reports, follows up and communicates outcomes. Connect researcher updates to your team's remediation decisions and escalation contacts.

Explore disclosure coordination

Start with the VDP transition checklist.

Use the editable worksheet to map your policy, reporting channels, open findings and launch checks. Assign owners and record what needs to be agreed with Hackrate.

Download the VDP migration checklist (CSV)

A practical division of work

What Hackrate handles.
What your team owns.

Moving from a self-managed VDP changes the operating model. It gives your team support for the work around a report while keeping product and risk decisions with the people responsible for your systems.

Use this comparison to define the engagement. Your current setup may already cover some of these tasks well; identify where added support would make the biggest difference.

Activity
Typical internal workflow
Hackrate managed support
Your team's role
Policy and scope
Your team publishes the policy and maintains the list of covered assets.
Support defining the policy and reporting process for the agreed service.
Approve the assets, policy wording and any changes to testing permissions.
Report intake
A security inbox, contact form or self-hosted tool receives submissions.
A Hackrate submission form embedded on your website provides a structured reporting route.
Publish the form and instructions; own any previous channels that remain active.
Technical validation
Internal staff assess evidence, duplicates and technical impact.
Security specialists review incoming reports and request clarification as needed.
Provide product context, access where agreed and decisions that require customer authority.
Researcher communication
Your team acknowledges reports, asks questions and provides updates.
Researcher coordination within the agreed handling workflow.
Approve commitments and provide remediation updates for the reporting conversation.
Engineering handoff
Staff translate reports into engineering tasks and track follow-up.
Validated findings and supporting evidence are available through the Hackrate platform.
Assign technical owners, prioritize work and implement fixes.
Escalation and disclosure
Your team coordinates urgent cases and publication decisions.
Support for the escalation and disclosure coordination defined in the engagement.
Provide reachable contacts, make risk decisions and approve public disclosure.

Confirm service coverage, response commitments, report limits, integrations and any retesting or disclosure support in your proposal.

Six steps to managed disclosure

Build the handover
around your current process.

A policy and an empty inbox need a different transition from a busy program with years of history. Start with what you have and agree the work before setting a launch date.

01 / MAP

Inventory the policy and reporting routes.

List covered assets, policy URLs, security inboxes, forms and internal tracking tools. Identify open reports, unresolved researcher questions and any existing response or disclosure commitments.

Output: a current-state inventory and a named customer owner.

02 / AGREE

Scope the managed service.

Define intake, validation, communication and escalation responsibilities with Hackrate. Discuss expected report volume, coverage, data handling, fees and any backlog work separately.

Output: an agreed proposal and a responsibility map.

03 / PREPARE

Review the policy and configure reporting.

Approve the scope, reporting instructions, testing permissions and communication expectations. Plan the Hackrate form on your existing website and decide how previous channels will be monitored.

Output: an approved policy and a reporting route ready to check.

04 / HAND OVER

Account for open findings.

Agree how relevant records and evidence will be shared or referenced. Keep source IDs, submission dates, decisions and ongoing conversations connected to each finding and its technical owner.

Output: a checked register of continuing cases and next actions.

05 / VERIFY

Walk through a sample report.

With the responsible teams, check form submission, customer access, acknowledgement, escalation and engineering handoff. Use an agreed sample to verify the workflow before directing researchers to it.

Output: a readiness review and owners for any remaining gaps.

06 / SWITCH

Update the channels and review the move.

Publish the approved instructions at the agreed time. Inform researchers with active cases, monitor the previous channels and reconcile late reports. Review the new workflow with Hackrate after launch.

Output: managed handling for new reports and a clear route for legacy cases.

Keep the context that matters

Every open report.
Every reporting route.

Plan the handover around live work. A researcher may still be replying to an email while an engineer is implementing a fix, even after the website shows a new form.

Agree an appropriate transfer method and access permissions before sharing detailed vulnerability evidence. Review a representative record sample to establish what can be transferred, recreated or kept available for reference.

For existing reports, preserve:

  • The source reference, submission date and affected asset.
  • Evidence, reproduction details and validation decisions.
  • Known duplicates and relevant earlier findings.
  • The current status, technical owner and next action.
  • Researcher conversations and promised follow-up dates.
  • Any agreed disclosure, recognition or reward commitments.

Confirm historical-record handling and any backlog assessment as part of the work. Import support depends on the available records and agreed method.

For existing channels, decide:

  • Who monitors the security inbox during the transition.
  • How late reports and replies reach the correct owner.
  • Which policy pages, contact pages and forms need updates.
  • Whether published security.txt reporting references need updates.
  • What researchers are told about the new process.
  • When an old channel can be retired and who approves it.

Confirm any email forwarding or integration before relying on it. Keep an explicit route for urgent reports throughout the agreed handover.

Keep active researchers informed.

Explain the new reporting URL, the effective date and timezone, and where each ongoing conversation should continue. State any policy changes and who to contact with questions. Preserve the original report reference so the researcher and both teams can identify the same case.

Ready for managed handling

Make the first handoff
a checked process.

Before switching the public reporting instructions, verify the full journey from the website to the people who can act on a finding. Resolve ownership questions while the current workflow is still available.

After launch, review late submissions, open legacy cases, researcher questions and the engineering handoff together. Use that review to refine the process.

Before the changeover, confirm:

  • The policy, assets and reporting instructions are approved.
  • The form works on desktop and mobile, and links reach the right page.
  • Customer access and the sample reporting workflow have been checked.
  • Technical owners and escalation backups know their roles.
  • Open reports and previous channels have named owners.
  • Active researchers have clear continuation instructions.

Bring these details to Hackrate.

Share your current policy URL, covered assets, reporting channels, approximate incoming volume and open-report count. Explain the work your team wants help with and any requirements for response coverage or record retention.

Start with a high-level overview. Agree how to share sensitive examples during scoping. Ask the proposal to distinguish setup, transition work, ongoing managed handling and optional services.

Discuss your VDP transition

Still evaluating managed VDP providers?

Use our buyer's guide to compare technical validation, researcher communication, service commitments and the evidence to request in a demo.

Read the managed VDP buyer's guide

Frequently asked questions

The details worth agreeing.

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

What is the difference between a self-hosted VDP and a managed VDP?

A self-hosted VDP often combines a policy on your website with a security inbox, form or internal tracking system. Your team handles incoming reports and researcher communication. Hackrate's managed VDP adds support for intake, technical validation and coordination under an agreed service. The policy can still be published on your website; the main change is who operates the reporting workflow.

Can we keep our existing disclosure policy and website URL?

Yes. Hackrate's submission form can be embedded on your website, so adopting managed handling does not require moving the policy to a new domain. Review the existing policy, covered assets and reporting instructions together, then approve any updates before launch. Your website team controls the page and its URL. Check that the published policy and reporting form describe the same scope and process.

What happens to our existing security inbox?

Agree whether the inbox remains a monitored contact, directs researchers to the new form or supports a defined handover process. Name an owner for late reports and ongoing email threads. Confirm any forwarding or integration method, access controls and handling of attachments before using it. Moving to managed VDP does not establish automatic email ingestion or permission to close an inbox that still receives active reports.

Can we transfer historical reports from email, spreadsheets or a self-hosted tool?

Start with an inventory and a representative record sample. Agree which open reports need active handover and which historical records should be transferred, referenced or retained in your own archive. Preserve source IDs, evidence, submission dates, decisions and researcher conversations where needed. Supported formats, attachments and import work must be confirmed from your records; a complete automatic import is not assumed.

Why move an internally managed VDP to Hackrate?

Hackrate is a fit when your team wants specialist support assessing incoming vulnerability reports and coordinating with researchers. Its managed service combines a website submission form, human validation and a platform for handling findings. Use the move to establish clear ownership, escalation and engineering handoffs, with the operational support defined in your proposal.

Does moving to managed VDP mean launching a bug bounty program?

No. Managed VDP handles incoming vulnerability disclosures. Bug bounty rewards and commissioned security testing are separate choices with their own scope and terms. Review the policy's testing permissions and reward wording during the transition so researchers understand what is offered. Record any commitments already made to reporters and assign an owner to resolve them.

Who fixes vulnerabilities after we move to Hackrate?

Your engineers or technical provider implement fixes. Your organization also approves scope, makes risk decisions and owns public disclosure approvals. Hackrate handles the report validation and researcher coordination agreed for the managed service. Name a customer decision owner, technical contact and escalation backup, and confirm any retesting or disclosure support in the engagement.

How long does the transition take and what does it cost?

Timing and cost depend on your policy changes, website work, open-report volume, record quality and the handling you need. Ask Hackrate to separate setup and transition work from ongoing managed VDP fees, report limits and optional services. Set the changeover date after the reporting channel, responsibilities and handover checks are agreed. A policy-only setup and a program with a large backlog need different plans.

A practical next step

Give your disclosure policy a managed workflow.

Bring your current policy URL, reporting channels and a high-level view of open reports. We will help scope the managed service, plan the handover and agree how findings reach your team.

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