Trust Centre

Security

Visma Responsible Disclosure

The information on this page is intended for security researchers interested in reporting security vulnerabilities to the Visma security team. If you are a customer and have a question about security or a password or account issue, please contact us through the support channels available for your product.

This policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.

Quick links:

Visma Responsible Disclosure program (Intigriti)
Public Bug Bounty Program (Intigriti)
Security Hall of Fame (HoF)
Our PGP key

Expectations

When working with us according to this policy, you can expect us to:

  • Extend Safe Harbor for your vulnerability research that is related to this policy.
  • Work with you to understand and validate your report, including an initial response to the submission within 12 business hours.
  • Work to remediate discovered vulnerabilities in a timely manner.

Safe Harbor

When conducting vulnerability research according to this policy, we consider this research to be authorized, lawful, helpful to the overall security of the Internet, and conducted in good faith.

You are expected, as always, to comply with all applicable laws.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through our official channel (see below)l before going any further.

‍

Ground Rules

To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attacks, we ask that you:

  • Play by the rules. This includes following this policy, as well as any other relevant terms or agreements. If there is any inconsistency between this policy and any other relevant terms, the terms of this policy will prevail.
  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope.
  • Only interact with accounts or devices you own or with explicit permission from the owner.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • If a vulnerability provides unintended access to data, limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept.
  • Cease testing and submit a report immediately if you encounter any user data during testing, such as personal data and sensitive personal data, credit card data, or proprietary information.
  • Do not attempt to execute Denial of Service attacks.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Report any vulnerability you’ve discovered promptly.
  • Do not engage in extortion by demanding a reward before disclosing vulnerability details.
  • Use only the official channels to discuss vulnerability information with us.

‍

Disclosure

You are not allowed to publicly discuss or publish any vulnerability before it has been fixed and you have received explicit permission from us to do so.

How to Contact Us

We offer two options for reporting:

  1. Visma Responsible Disclosure Program is available on the Intigriti platform: https://app.intigriti.com/programs/visma/VismaResponsibleDisclosure/detail
  2. If you do not want to send the report through Intigriti, you can use our official communication channel: security@visma.com. The issues are triaged by a Security Analyst before being escalated to the appropriate team. If you feel that the email should be encrypted, our PGP key is available below.

‍

Rewards

We do not offer monetary rewards for Responsible Disclosure reports, but if you report via our Visma Responsible Disclosure program on Intigriti, for all valid Medium+ reports we do offer swag as a sign of appreciation.

‍

The only monetary reward exceptions are the specific assets listed in our Public Bug Bounty Program on Intigriti. Please note that for the Public Bug Bounty Program, we will only accept reports for those assets that are listed into the program scope and no other variations.

For all other assets and regardless of the option used for reporting, we will offer a place in our Security Hall of Fame (HoF) for all researchers that submit a previously unknown vulnerability that triggers a code or configuration change.

Scope

This policy covers all Visma services, products or web properties.

‍

Please note! Most reports we receive have little or no security impact or are already known. To avoid a disappointing experience when contacting us, please take a moment and consider if the issue you want to report actually has a realistic attack scenario.

‍

More specifically, we ask you to not submit issues regarding:

‍

  • Theoretical vulnerabilities without any proof or demonstration of the real presence of the vulnerability.
  • Findings from automated tools without providing a Proof of Concept.
  • Vulnerabilities requiring MITM, or physical access to a user’s browser, or a smartphone, or email account, as well as issues on rooted or jailbroken smartphones.
  • Missing or weak security-related HTTP headers.
  • Non-Sensitive Data Disclosure, for example server version banners.
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions.
  • Self-XSS.
  • Missing email best practices (invalid, incomplete or missing SPF/DKIM/DMARC records, etc.).
  • Host header injection, unless you have confirmed that it can be exploited in a practical attack.
  • Expired SSL certificates, weak SSL Ciphers, or issues regarding old TLS/SSL versions.
  • Previously known vulnerable software or libraries without a working Proof of Concept.
  • Rate limiting or bruteforce issues on non-authentication endpoints.
  • Denial of Service.
  • CSV/formula injection.
  • Flash based exploits.
  • Clickjacking.
  • Google Maps API key disclosure.

‍

When duplicates occur, we will only accept the first report. A duplicate is a vulnerability that we are already aware of, regardless of how we first became aware of it (it could have also been discovered by us internally).

‍

Our PGP key

-----BEGIN PGP PUBLIC KEY BLOCK-----

Version: Mailvelope v2.0.0

Comment: https://www.mailvelope.com

‍

xsFNBFolcs0BEADhn3g0A+sHKKJLzxhI6oRNAXf+nDNoTiwVA5J+mk88NPhk

vIDA0MfvhvTInHJZSgtwV0QpyCoF2zxnP28pNT+EjxeiZkpbVKjEeXEyV9vG

wH+bocKAnHKtvVD6NPFnzeb9xat2MxbcWCOeYBPVauEOXNdcGqWjkx7CNYU2

YT3NwR0Ytw68nFZyJc8dm7x2UQW7SKIwJdW9jx3Zyu1wDCRmFCzsWuUn/vGw

TjrXhJtrqgvLwIDafDLFgiYWeT1I22LPWKWFPTLySzH1dNx3ZrF6eEQoWLhH

JuRSOgQ7IQ0WASxsGiQU1oEy8vWgiA4ZKT4BLdJH0/E0NeDotZICe+LR3HGq

1w+bYawim1+YBjsQrYcH6MqY5VZ3sCcvknN4xAbA2SZNv8YATrG1gfKUd0M/

yrSDJbF/ZE5xxTcSFC0vN9nF8UyCkTtTLTBIDA2p2ZHkEyVaxmVX9lS0GnAM

X62HmNpUC0cjBxGQUwyEPdduO6IOmrF/uGGFos2svzfveD1bMAyUAf5hcx1N

NsqspUiF3x3xjhT2Qzm12aBuATN5Jmckf4IVNkpZw6Ou1KPfpWej7hIb74oZ

DGYtTgyEhNTfOaEsklh1wcJL6JP07QdMBKOKf+TTjlXdiDSpNUju+W3Ci1Om

cxwzi/jLzSKsEfmgSl6NlW4lK5uxHCqwWMhWKQARAQABzT9WaXNtYSBSZXNw

b25zaWJsZSBEaXNjbG9zdXJlIDxyZXNwb25zaWJsZS1kaXNjbG9zdXJlQHZp

c21hLmNvbT7CwXUEEAEIACkFAlolctAGCwkHCAMCCRACIJNLR31TqAQVCAoC

AxYCAQIZAQIbAwIeAQAA+WcP/jv/n9MSXRhbK1wDZEnicvAnPblh0BYnhVen

H54AHkPHflWuAHHLYlS7Ez1Pjp9sBA7ZhVgW7Gw7GgnvvGSWCcs4/NjJKh1Q

wWIDyu6ikqxewfy160Qd1QbVIMkiBy902ZG0YJivDPGGFscCa5YRODNT5GcY

XI4WNd5Xj3DCf7qDImWTTZvCq5waq5O2pE0d2flzesvDuxta0gj9SbS1Soiq

LAeqzv0Y8nnTkK7HcF/dbnqqw/I3zGlo4Y5zwgEdlRFcMtXiN3pRQx3ZacVV

4YvI2XWNGxABMqqoJU6zXfjGaVZHfkXrCkf0xPC3nYStL1iontCaNAscH6iZ

EcR2l8qOreJdvNwY3L0U1FIJbKyHGo63Cb3k0yw1DITKh6QQnwZCaL2B9BER

eJ59l9ipwO2/G0U5yjsds8xsLpwN3R1Lwx20dY/IOaamsNGeskR2nmmlz3vP

sTRKO6CMKNnLphaXC3l0pvkil4Cilk4X3l0YFocjwSFQLv145l7yIm1yovdV

bHan5kckuShbRiqA4J8JgMAJvEPhStI0ISQ/aUUXSMtWQ+AX7BC6iTGjAbHY

39GJDC3EjxCXXjqmYSb8lx3CbODB02rOXfK5qjuZTc/ppAT6sEv3QNPP/+Ku

N7MVJ968J4Q3CazsnCRLGu5f8yeh7VT00mlzrs4kBW1ZvW0PzsFNBFolcs0B

EADKyvqR/qhZUFixJCOH+ZXcTQfT1IxcPoqUH+ItaPp+6zRU4sbe03G/VI+G

q5BJWlwcesn4qJLn+B8EpFka/+sXozGV144b1qFcQIfetog9b71pLkDNA3hZ

t8FP3nW1iddr1wLQ/qPwlwScOsnZOjo1fJK/s/ATxzDALZkI6YufHZmx5RPV

H6z4d/IKWSaFUDe/boEw78DMHFbiOdgrVMVjAVbhlI5iiG6dnekv4M3tdJd2

qPbeeawd+x7bQVPTCLvUrPhaev2wIHQVUNB6XCAgJcxP8PBnFbKPjvGxeKUf

YrpPlf2BqeQ+08aSNdJYw9szu0PHp2oNPh+mna7XtL9GtpcvoTtKRPVNunFz

eaiOtf8Xo7s51UUML8jkrTu36/RL45qfNIhksY31BOS5Gu0Gi2qpMv9rJ3tB

4AMcteGO24J0KZTZkJrULQMEj083U/r+KwXyuLH6o+R9Pnhq7jpDNu5xNmjo

eGWyPaVGVw+DyTMAn82O3Mo8u/8DFlRXuxvauDFzRumW6rJGf9XXYrnIEb1t

bD34nzp4V+PusAwdwWAwF8ABF5lMMYlhUUfq4o0Y6zqNYMMwW2Au4+0KFtER

STfS9i2w0NHUdS89b+Gh3xn4VxSk5veUnFx/FsXo/Rfr/teGO3xIxnESH9oV

78t7k6roTLV20jtQPfQTqq7XWQARAQABwsFfBBgBCAATBQJaJXLRCRACIJNL

R31TqAIbDAAA0loQANM/XFObeQa/rGlMI6K6j9nt/CISbRDkDzAXY0Vk93Ik

02N1fvkJHBq8zi900UOn9vCJTLeu3VBpR/sBwh16Qtq3mHhCG/2WyniBkgdz

iyknLQ0SGW09AFac3NQHYQ8bGJc/+iAWlCQvYlzIqtZfux3kUoz1uUIpbE7x

rA6O0JJ2s7YZDpAbN+tGCcfEG/JqfRvk5lLNoQWG+KCIsZKWyDVBe+9Uht+d

0HusOm2RBnTJ/JS5Dvs0yDUodtYWnplxjOOkn80/MmYZoD2Ue60vGabrgLmg

pt1Vbo6m6lMWKYPb1GQ+H1C4f0SfHSgu2SfWQIRRpaxStvRKQdp+p8M8ZOYi

nyxA2zSKoM4VJBDkHdfL/IjrgElPIllTAI0se9ZqS0CEq/7d4u+TpEn+mwjz

4t/dMqcYxN2F0JJ7ec1Z0RB/SUgX2CJggmnsZG1vNQV6EFOEuVN6rKFedjgP

AerySOPJ2DHXmdmppSbP5lRzwKyWwGnh7c/ksaku4HTz8/hIjoTmcnWpOuf/

Wl2413InypvPslfs7MwrWrzcvMm83QQz9SK5rq1kjIFAjhke3P+AFENvC6BY

Ulef1fKRZVse//nCDYj5+puI3rIzhbiH2tfox9zrY3U5i4EMTjUD6XI9E1xf

1KR0Aq+5JIiBF15X1wcG5kXQx5W1i7YdmsGHI83h

=O8N3

-----END PGP PUBLIC KEY BLOCK-----

‍