← Back to knowledge center

Receiving vulnerability reports: VDP and security.txt

A security.txt file helps a researcher find the right contact, but it does not create an operating process. An organisation needs a clear VDP that defines authorised testing, evidence handling and ownership through remediation.

V
Virtek Cybersecurity TeamInfrastructure and data protection

1. Define the scope

  • List covered domains, applications, APIs and products.
  • Exclude customer systems, physical action, social engineering, denial of service and unsafe handling of live data where appropriate.
  • Explain permitted testing and the requirement to stop when sensitive information appears.
  • Assign a policy owner and technical triage team.

2. Publish security.txt correctly

RFC 9116 uses HTTPS and the /.well-known/security.txt location. Provide at least one Contact and exactly one Expires field; Canonical, Policy, Preferred-Languages and Encryption are useful additions. Every contact must reach a monitored channel.

Test the MIME type, UTF-8 encoding, redirects, expiry and external availability. Do not assume inheritance across domains: the file applies to the domain from which it is retrieved.

3. Provide a safe evidence channel

Email can start the conversation, but evidence may contain personal data, tokens or sensitive technical detail. Offer a protected form, PGP key or agreed secure exchange. Explicitly tell reporters not to send passwords and secrets in clear text.

An acknowledgement should provide a reference, expected initial response time and a way to add evidence. Do not promise a reward unless a bounty programme actually exists.

4. Operate triage and response targets

  • Confirm receipt and scope.
  • Deduplicate, reproduce and assess impact and existing mitigations.
  • Assign a product owner, next-update date and critical escalation path.
  • Coordinate disclosure and keep the researcher informed.

Connect the VDP to incident response without treating every report as a confirmed compromise.

5. Close with evidence

Independently verify the fix, run regression tests and inspect similar components. Record affected versions, release date, temporary mitigations, customer notice and the decision on public disclosure or CVE handling.

Quarterly, check contacts and Expires, acknowledgement time, useful-report ratio and unresolved cases. A functioning programme gives each report an owner, visible progress and a verified outcome.

Need an architecture
for your workload?

We will review inputs, risks and constraints, then propose a reasoned solution.

Talk to an engineer↗︎