Third Party Index

Snapshot 28155

Document
Security advisories
URL
https://www.nabla.com/vulnerability-disclosure-policy
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
66598 bytes
SHA-256 (raw)
fa173aaede91e9b81a9c2cfe62484782e8c7a4a52823d2e38aa5a9af20956e1a
SHA-256 (normalized text)
8afc86a1be1838d9ddc8ce9fc00ed4550b22570b1b964dc36a7d96323a480a3c

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Get in touch
We’d love to hear from you! Let us know what you need, and someone from our team will get back to you shortly. If you need any help with the product, please reach out to [email protected]. If you are not a healthcare organization you can reach out to [email protected]
This data is used by Nabla to answer your contact request. Learn more.
This data is used by Nabla to answer your contact request. Learn more.
Vulnerability Disclosure Policy
Updated September 5, 2023
Introduction
Security is essential to Nabla’s mission. We value the input of hackers acting in good faith to help us maintain a high standard for the security and privacy for our users and technology. This includes encouraging responsible vulnerability research and disclosure.
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.
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 Nabla 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 all Nabla products. If you aren't sure whether a system is in scope or not, contact us at [email protected] before starting your research. 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 at this form or via [email protected]. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.
We do not support PGP-encrypted emails. For particularly sensitive information, submit through our HTTPS web form.
Information shared with us in this manner must be shared unconditionally. While we do not operate a bug bounty program, we may occasionally choose to reward reported vulnerabilities.
What we would like to see from you
In order to help us triage and prioritize submissions, please include in your report:
a detailed description of the vulnerability and its potential impact
a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful)
any additional information you think we should be aware of
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.