Security Disclosure

Contact & support

IT & Operations

Give researchers a place to report a vulnerability with severity, product area, and a non-public write-up.

securityvulnerabilitypsirtdisclosure

A security inbox that is also Contact Us is how disclosures leak into Zendesk. This template asks for a product area, a severity guess, and a write-up meant for humans who can patch.

Who it is for

Product security and founders who just published a security@ address.

When to use it

Link it from a security.txt or trust page. Support Request is for customer bugs. Bug Bounty Intake is when you are paying. Do not put working exploits in a public success message.

What this form collects

A handle, contact email, severity guess, product area, write-up, and credit preference.

  • security.txt contact form
  • Private disclosure before a bounty exists
  • Partner-reported issues

Preview mode: This is a live read-only render of the template. Sign up to clone it into your account, or customize it with the guest AI builder first.

Security Disclosure

Give researchers a place to report a vulnerability with severity, product area, and a non-public write-up.

Ready to use this template?

Frequently asked questions

Is this a bug bounty?

Not by itself. Use Bug Bounty Intake if you pay. This form is the mailbox so the report does not land on Twitter first.

Should I publish a PGP key here?

Link it from the page intro. The form fields stay ordinary so researchers can still reach you without encryption if they choose.

Can researchers attach a proof-of-concept file?

Add a file field if you want. Many teams prefer the write-up in text so nothing executable sits in the first inbox.

Related templates

Nearby GRTforms templates for the same job or the next step after this one.

Browse all Contact & support templates

Browse IT & Operations templates