Vulnerability Disclosure Policy
floragunn GmbH/Search Guard Vulnerability Disclosure Policy
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 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 floragunn GmbH until we’ve had 60 days to resolve the issue.
If you follow these guidelines when reporting an issue to us, we commit to:
• Not pursue or support any legal action related to your research;
• Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission);
• Recognise your contribution on our Security Researcher Hall of Fame, if you are the first to report the issue and we make a code or configuration change based on the issue.
Source code of the following public github repos
Search Guard SSL
Search Guard Enterprise Modules
Search Guard Kibana Plugin
Search Guard Offline TLS Tool
Out of scope
Any services hosted by 3rd party providers and services mentioned below are excluded from scope.
These services include (but are not limited to):
• Github itself
• The Search Guard Website
• The Search Guard Documentation Website
• Private github repos
In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from 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
• Spelling mistakes
• Network level Denial of Service (DoS/DDoS) vulnerabilities
How to report a security vulnerability?
If you believe you’ve found a security vulnerability in one of our products (open source or commercial) please send it to us by emailing email@example.com.
We can accept only security issues at this address. 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.
If you’d like to encrypt the information, please use our [PGP key].