Security policy

In short:

• Report a security issue in blaeu.com to rob@blaeu.com.
• Encrypt sensitive details with our PGP key.
• We respond within three business days and take no legal action against you if you follow this policy.
• We pay no rewards for reports.
• Vulnerabilities we find in third-party systems are reported privately first and published only after the fix.

Coordinated vulnerability disclosure

This is our coordinated vulnerability disclosure (CVD) policy, also known as a responsible disclosure policy.

At Blaeu, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.

If you discover a vulnerability in blaeu.com, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.

Please do the following:

• Email your findings to rob@blaeu.com. Encrypt your findings using our PGP key to prevent this critical information from falling into the wrong hands.
• 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 viewing, deleting, or modifying other people's data.
• Do not reveal the problem to others until we have fixed it, and delete any confidential data obtained through the vulnerability as soon as we have fixed it.
• Do not use attacks on physical security, social engineering, distributed denial of service, spam, or applications of third parties.
• Provide enough information to reproduce the problem, so we can 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 enough, but complex vulnerabilities may require further explanation.

What we promise:

• We will respond to your report within three business days with our evaluation of the report and an expected resolution date.
• If you have followed the instructions above, we will not take any legal action against you about the report.
• We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission, unless this is necessary to comply with a legal obligation. Reporting under a pseudonym is possible.
• We will keep you informed of the progress towards resolving the problem.

We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved.

We pay no rewards, and we do not list reporters on this website.

Security contact: Rob van Eijk, director, Blaeu Privacy Response Team B.V.

Based on the example CVD policy by Floor Terra, licensed under CC BY 4.0.

Vulnerabilities in third-party systems and code

Our work includes analysing software, websites, and data flows for research and for expert-witness work for clients. If that work reveals a vulnerability in someone else's system, we handle it as follows:

1. Report it first to the vendor or the responsible CSIRT, privately.
2. Allow a reasonable time to fix it, agreed case by case.
3. Publish only after the fix.

For client engagements this happens within the confidentiality terms of the engagement and applicable law.

PGP key and security.txt

Fingerprint: 6E9C 7952 DA11 3DB1 1F1A 9411 9B91 7133 4B4F 58DE

Public key on the SURFnet keyserver

Machine-readable contact details: security.txt

Languages: English, Dutch.