Skip to content

Latest commit

 

History

History
78 lines (51 loc) · 3.05 KB

index.md

File metadata and controls

78 lines (51 loc) · 3.05 KB
Raw
layout
default

Responsible Disclosure Policy

{% if site.announcement and site.announcement != "" %}

Announcement

{{ site.announcement }}

{% endif %}

Introduction

Kitabisa.com welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.

Systems in Scope

{% for in-scope in site.scopes.in %}

  • {{ in-scope.value }}

{% endfor %}

Out of Scopes

{% for out-scope in site.scopes.out %}

  • {{ out-scope }}

{% endfor %}

  • Assets and/or other equipment not owned by parties participating in this policy.

Testing is only authorized on the targets listed as in scope. Any domain/property of Kitabisa not listed in the targets section is out of scope. This includes any/all subdomains not listed above. Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority. If you think it demonstrably belongs to Kitabisa, use Official Channels to discuss with us.

Our Commitments

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

{% for commit in site.commitments %}

  • {{ commit }}

{% endfor %}

Our Expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

{% for expect in site.expectations %}

  • {{ expect }}

{% endfor %}

Official Channels

Please report security issues via {{ site.email }}, providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.

The Kitabisa security team recommends to use this PGP key to sign all security notifications and encourages others to use this key when sending sensitive information to us.

PGP fingerprint: {{ site.pgp_fingerprint }} 
{% include_relative pgp.txt %}

Safe Harbor

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

{% for harbor in site.harbors %}

  • {{ harbor }}

{% endfor %}

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.

Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.