Log in
Talk to us
ProductsIdentity Verification PlatformAML & KYC ComplianceID Verification SoftwareFace MatchAssisted Image CaptureVerification ToolingProof of AddressAll productsIndustriesFintechMobilityCryptoGamingMetaverseEducationUse casesAge verificationDriver validationNew account onboardingCustomer Identity and Access Management
Developers documentationSupportService status
ResourcesBlogProduct updatesCase studiesOur people
ReportsWebinarsKeeping up with KYCEngineering blogAll resources

Responsible Disclosure

We take the security of our systems seriously, and we value the security community. The disclosure of security vulnerabilities helps us ensure the security and privacy of our users. We ask all researchers to follow the guidelines below.

We require that all researchers:

  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
  • Perform research only within the scope set out below;
  • Use the identified communication channels to report vulnerability information to us; and
  • Keep information about any vulnerabilities you’ve discovered confidential between yourself and Veriff until we have resolved the issue.

If you follow these guidelines when reporting an issue to us, we commit to:

  • Not pursuing or supporting any legal action related to your research;
  • Working with you to understand and resolve the issue quickly (including an initial confirmation of your report within 5 (five) working days of your submission);

Scope

  • www.veriff.me
  • developers.veriff.me
  • api.veriff.me
  • magic.veriff.me
  • station.veriff.com
  • alchemy.veriff.com
  • hub.veriff.com
  • louvre.veriff.me
  • stationapi.veriff.com

Out of Scope

  • Findings from physical testing such as office access (e.g. open doors, tailgating)
  • Findings derived primarily from social engineering (e.g. phishing, vishing)
  • Findings from applications or systems not listed in the ‘Scope’ section
  • UI and UX bugs and spelling mistakes

The following potential issues are not considered in scope:

  • Lack of rate limiting on any resources
  • Password policy issues, including lack of upper limit on passwords
  • HTTP 404 or other error codes and pages
  • Banner or version disclosure of any kind
  • Presence of common public files, such as robots.txt or files in the .well-known directory
  • CSRF on anonymous resources, or any CSRF issue which does not include an exploit showing control over sensitive actions
  • Clickjacking issues, unless an exploit showing account takeover or disclosure of sensitive resources is provided
  • Self-XSS issues
  • SPF/DKIM/DMARC configuration issues

Forbidden

  • DoS and overloading server with many requests or large requests
  • Accessing and copying our customer data
  • Conducting research against our partners and customers
  • Abusing our services to conduct fraud
  • Spamming
  • Use of automated scanning tools

Reporting

If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing security@veriff.net. Please include the following details with your report:

  • Description of the location and potential impact of the vulnerability;
  • A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us); and
  • Your name/handle and a link for recognition in our Hall of Fame: https://www.veriff.com/hall-of-fame
    Note: We do not currently offer bounties or other rewards for submitted vulnerability reports.
  • If you’d like to encrypt the information, please use our PGP Key
  • Please note that we register your data in connection with your report and our internal further processes. If you want to know more about how we process your personal data, please read more on: https://veriff.com/privacy-policy. If you wish to report the issue anonymously, please state this in your communication, and we will not contact you or retain your personal information.

  • Valid from: November 28, 2020
  • Last update: February 10, 2021