📣 Product updates September 2024. Learn more →
Vero logo

Vulnerability Disclosure Program

Last updated: 12 September 2024

Important: We have migrated our vulnerability disclosure program to Bugcrowd. Unless discussed otherwise, at this time we are no longer offering monetary rewards as part of a bug bounty. We will consider launching a bug bounty in the future.

As of 03:00 UTC 12 September 2024, reports made to dataprivacy@getvero.com will not be responded to. All vulnerability reports must now be made using the form below. Reports made using the form will be responded to.

Vulnerability Disclosure Philosophy

Vero believes effective disclosure of security vulnerabilities requires mutual trust, respect, transparency and common good between Vero and Security Researchers. Together, our vigilant expertise promotes the continued security and privacy of Vero customers, products, and services.

Security Researchers

Vero accepts vulnerability reports from all sources such as independent security researchers, industry partners, vendors, customers and consultants. Vero defines a security vulnerability as an unintended weakness or exposure that could be used to compromise the integrity, availability or confidentiality of our products and services.

Our Commitment to Researchers

  • Trust. We maintain trust and confidentiality in our professional exchanges with security researchers. Respect. We treat all researchers with respect and recognize your contribution for keeping our customers safe and secure.
  • Transparency. We will work with you to validate and remediate reported vulnerabilities in accordance with our commitment to security and privacy.
  • Common Good. We investigate and remediate issues in a manner consistent with protecting the safety and security of those potentially affected by a reported vulnerability.

What We Ask of Researchers

  • Trust. We request that you communicate about potential vulnerabilities in a responsible manner, providing sufficient time and information for our team to validate and address potential issues.
  • Respect. We request that researchers avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing.
  • Transparency. We request that researchers provide the technical details and background necessary for our team to identify and validate reported issues, using the form below.
  • Common Good. We request that researchers act for the common good, protecting user privacy and security by refraining from publicly disclosing unverified vulnerabilities until our team has had time to validate and address reported issues. Vulnerability Reporting

Vero requests that security researchers share the details of any suspected vulnerabilities across any asset owned, controlled, or operated by Vero (or that would reasonably impact the security of Vero and our users) using the web form below. In conjuction with Bugcrowd, Vero will acknowledge receipt of each vulnerability report, conduct an investigation, and take appropriate action for resolution.

In/out-of-scope

Refer to the "Target" dropdown in the submission form below for in-scope entities.

The following are out-of-scope:

  • Developer guide (developers.getvero.com)
  • Help site (help.getvero.com)
  • Changelog and feedback (feedback.getvero.com)
  • Status site (status.getvero.com)
  • Zight (drops.getvero.com)
  • Calendly (calendly.com via www.getvero.com/demo)

Other

When signing up to test Vero accounts please use an email address with one of the following domains. wearehackerone.com, bugcrowdninja.com, maildrop.cc or guerrillamail.com.