The following areas are considered out of scope: • Vulnerabilities that require access to an already compromised account (unless access to an account exposes other accounts) • Policies as opposed to implementations - email verification, password length or reuse, etc. • Ability to upload or download malicious files via vikingpro.net • Ability to upload or download malicious files via vikingpro.net • Spam (unless a specific vulnerability leads to easily sending spam) • Authentication (or lack thereof) on free transfers • Missing security headers or 'best practices' (except if you are able to demonstrate a vulnerability that makes use of their absence) • Vulnerabilities in our open source software (unless you have a proof of concept of how the specific vulnerability can be used on our or related apps). • Distributed Denial of Service attacks (DDoS) • Social engineering attacks • Third party applications we make use of, but do not control, (e.g. a blog hosted on an external service, unless we've configured the blog in such a way as to make our in-scope areas vulnerable) • Integrations and extensions created by third party developers using our public API • Non-production environments across our product line The following areas are considered in scope: • The vikingpro.net web application • The applications listed on our products page • Our developers ’ portal as well as the API it describes
What we ask of you
If you believe you have discovered a security vulnerability in a vikingpro service, please do the following:
• Submit your findings by us by email to email@example.com
• Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data. This is critically important, so let us emphasise: do not interact with the data in question more than is necessary to notify us.
• Do not reveal the problem to others until it has been resolved.
• Do not use attacks on physical security, social engineering, distributed denial of service (or any attack using large volumes of requests), spam or applications of third parties.
• Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.
What we promise
• We thank you for your help in making vikingpro more secure.
• We will respond to an accepted report within 5 business days with our evaluation of the report.
• We will keep you informed of the progress towards resolving the problem.
• In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise).
Recognition and remuneration
For accepted reports we may provide a financial reward. This reward will be based on the quality of the disclosure and nature of the vulnerability. Where possible we may also provide a Pro account (with a value of 120 EUR) and if available some vikingpro swag. Please feel free to submit your report anonymously or under a pseudonym. Rewards are granted entirely at our discretion and may be reduced or declined if there is evidence of abuse
For questions about this NTD Policy, please contact vikingpro by sending an email to firstname.lastname@example.org