Added Policy, PGP key and security.txt

.well-known/security.txt

@@ -0,0 +1,5 @@
+Contact: mailto:[email protected]
+Encryption: https://keys.openpgp.org/vks/v1/by-fingerprint/0ECE09253E2394088F47077CC9C4569EB636C3DB
+Encryption: https://kraxnet.com/security/publickey.txt
+Preferred-Languages: en, cs, sk, de
+Policy: https://kraxnet.com/security/policy

_config.yml

@@ -36,6 +36,8 @@ theme: jekyll-theme-minimal
 plugins:
   - jekyll-feed
 
+include: [".well-known"]
+
 # Exclude from processing.
 # The following items will not be processed, by default.
 # Any item listed under the `exclude:` key here will be automatically added to

index.md

@@ -6,7 +6,8 @@ permalink: /
 
 # Contact info
 
-|Email:|[email protected]|
-|Address:|Kamenická 26, 170 00 Praha 7, CZ|
-|Phone:|	+420 220 199 201|
+|Email:   | [email protected] |
+|Address: | Kamenická 26, 170 00 Praha 7, CZ |
+|Phone:   | +420 220 199 201 |
 
+- [Vulnerability Disclosure Policy]({{ site.path }}/security/policy)

security/policy.md

@@ -0,0 +1,83 @@
+## Vulnerability Disclosure Policy
+
+KRAXNET s.r.o.
+
+2024-01-01
+
+### Introduction
+
+KRAXNET is committed to ensuring the security it's customers by protecting their information. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
+
+This policy describes **what systems and types of research** are covered under this policy, **how to send us** vulnerability reports, and **how long** we ask security researchers to wait before publicly disclosing vulnerabilities.
+
+We encourage you to contact us to report potential vulnerabilities in our systems.
+
+### Authorization
+
+**If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized we will work with you to understand and resolve the issue quickly, and KRAXNET will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.**
+
+### Guidelines
+
+Under this policy, "research" means activities in which you:
+
+- Notify us as soon as possible after you discover a real or potential security issue.
+- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
+- Only use exploits to the extent necessary to confirm a vulnerability's presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
+- Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
+- Do not submit a high volume of low-quality reports.
+
+Once you've established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), **you must stop your test, notify us immediately, and not disclose this data to anyone else**.
+
+### Test methods
+
+The following test methods are not authorized:
+
+- Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
+- Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing
+
+### Scope
+
+This policy applies to the following systems, services and hostnames:
+
+- \*.kraxnet.com
+- \*.kraxnet.cz
+- \*.xnet.cz
+- AS51210
+
+All customer applications are excluded from this policy.
+
+**Any service not expressly listed above, such as any connected services, are excluded from scope** and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy's scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren't sure whether a system is in scope or not, contact us at [email protected] before starting your research.
+
+Though we develop and maintain other internet-accessible systems or services, we ask that _active research and testing_ only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.
+
+### Reporting a vulnerability
+
+**We accept vulnerability reports via [email protected]**. To ensure confidentiality, encrypt your findings with our [PGP key](/security/publickey.txt). Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.
+
+#### What we would like to see from you
+
+In order to help us triage and prioritize submissions, we recommend that your reports:
+
+- Describe the location the vulnerability was discovered and the potential impact of exploitation.
+- Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
+- Be in English, if possible.
+
+#### What you can expect from us
+
+When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.
+
+- Within 3 business days, we will acknowledge that your report has been received.
+- To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
+- We will maintain an open dialogue to discuss issues.
+
+### Questions
+
+Questions regarding this policy may be sent to [email protected]. We also invite you to contact us with suggestions for improving this policy.
+
+### Document change history
+
+| Version | Date       | Description     |
+| ------- | ---------- | --------------- |
+| 1.0     | 2024-01-01 | First issuance. |
+
+Based on [Vulnerability Disclosure Policy Template](https://www.cisa.gov/vulnerability-disclosure-policy-template).

security/publickey.txt

@@ -0,0 +1,14 @@
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+
+mFIEAAAAABMIKoZIzj0DAQcCAwTVIu2OExFgC2Wk5opbQ0JqMWQq7IqAaXkhMcko
+ciQDtI9r+UavdptzR4EscvmdKpiok4fZQ53ruvRc/Ae0hsuytCRTZWN1cml0eSBU
+ZWFtIDxzZWN1cml0eUBrcmF4bmV0LmNvbT6IgAQTEwgAHAUCAAAAAAILCQIbAwQV
+CAkKBBYCAwECF4ACHgEAFgkQycRWnrY2w9sLGlRSRVpPUi1HUEdHmQEA04MyAtsD
+N27AbL3Zt2TtuIK0cOxcTYnzb3beGKp+XCwA/0tOg+1SujBx9aHaO81VnlFug6zt
+ECY+QfbPRKpQtnDhuFYEAAAAABIIKoZIzj0DAQcCAwQ5eKLZbRr96WStgsR9LlKI
+C4aaGmxSN5ZG4hiTjCyCOFQ2EBQAelbsrITynE+VIr9ZuslTEOaXk2m1NhRaLFL5
+AwEIB4htBBgTCAAJBQIAAAAAAhsMABYJEMnEVp62NsPbCxpUUkVaT1ItR1BHkIQB
+APWGmV4xxVlhpfFV94RfjU3MURadQwEbz8zKalTv68BFAP4wnFjCocWftWVKHHfo
+N6uoHcpdYv+yCirD9V/Qrbecuw==
+=EeiU
+-----END PGP PUBLIC KEY BLOCK-----