Snapshot 17188
Normalized text
Scripts and page chrome removed; this is what change detection compares.
This site uses cookies to offer you a better browsing experience. Learn more. Summary This policy provides guidelines for security researchers conducting vulnerability discovery. It describes what systems and types of research are covered, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities. This policy also describes CareEvolution’s bug bounty program: what systems are in scope, what sorts of testing are permissible, and the per-impact monetary award ranges for reported vulnerabilities. We encourage you to contact us to report potential vulnerabilities in any of our systems. See Reporting a vulnerability. 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 CareEvolution® 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. 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 and notify us immediately. Do 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 and services: The careevolution.com website *.careevolutionapi.com *.careevolutionapps.com *.symptomshark.org mydatahelps.org (Do not join any projects other than Symptom Shark or test projects that you have created for yourself using https://designer.mydatahelps.org) MyDataHelps and myFHR mobile applications (Do not join any projects other than Symptom Shark or test projects that you have created for yourself using https://designer.mydatahelps.org) api.mydatahelps.org designer.mydatahelps.org api.designer.mydatahelps.org myfhr.careevolution.com rosetta.careevolution.com share.careevolution.com 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 before starting your research. Reporting a vulnerability Complete the following form to report a security issue. You may report the issue anonymously, or include your email so we may follow up with you. Report an issue Please include as much information as you can about the security issue (e.g., proof of concept code), but DO NOT include Protected Health Information (PHI), Personally Identifiable Information (PII), or any other sensitive data, such as (but not limited to): patient name, birth date, medical record number, social security number, address, phone number, or email. If communicating PHI, PII, or sensitive data is required to demonstrate the security issue, contact us for instructions on how to securely share this additional information. If you include your email address in your report, you will receive a response from us within five business days acknowledging receipt of your report. Evaluation We will research the report based on our current backlog. This typically takes between 2-4 weeks. Please do NOT contact us for updates on your report. This will be provided when our review is completed. If you include your email address in your report, we will respond with either our conclusions or a request for further clarification. Disclosure If you intend to publicly disclose the issue, e.g., at a conference demonstration, on a blog, etc., provide us a reasonable amount of time to resolve the issue before you disclose it. We prefer that you coordinate with us to make sure our partners have had the opportunity to deploy a mitigation or fix prior to public disclosure. Do not include PHI, PII, or other sensitive information in any public disclosure. We appreciate your help in keeping everyone’s health information secure. Bug Bounty Program As a part of our validation disclosure program, CareEvolution has established a bug bounty program to incentivize security researchers to identify and report security vulnerabilities or bugs in our systems. Issues can be reported via our Vulnerability Disclosure program, and will be processed based on priority. Report an issue Systems in Scope The following services are expressly designated as in scope for CareEvolution’s bug bounty program: The careevolution.com website *.careevolutionapi.com *.careevolutionapps.com *.symptomshark.org mydatahelps.org (Do not join any projects other than Symptom Shark or test projects that you have created for yourself using https://designer.mydatahelps.org) MyDataHelps and myFHR mobile applications (Do not join any projects other than Symptom Shark or test projects that you have created for yourself using https://designer.mydatahelps.org) api.mydatahelps.org designer.mydatahelps.org api.designer.mydatahelps.org myfhr.careevolution.com rosetta.careevolution.com share.careevolution.com Qualifying Vulnerabilities Any design or implementation issue that significantly impacts the confidentiality or integrity of user or system data is likely to fall within the scope of CareEvolution’s bug bounty program. The program is specifically focused on technical vulnerabilities in applications or infrastructure owned or used by CareEvolution. Non-Qualifying Vulnerabilities Depending on a reported issue’s impact, it may not qualify if it does not represent a considerable amount of risk to CareEvolution’s systems or organization. The following finding types are expressly excluded from the CareEvolution Bug Bounty program: Vulnerabilities that rely on guessing a UUID or identifier of similar entropy without a demonstrated leak vector Disclosure of publicly known files or directories (e.g., robots.txt) Issues only exploitable through clickjacking CSRF vulnerabilities on forms accessible to unauthenticated users CSRF attacks requiring knowledge of CSRF tokens (e.g., involving local machines) Logout CSRF vulnerabilities Content spoofing Brute force attacks on login or password recovery pages without account lockout enforcement OPTIONS HTTP method enabled Username/email enumeration Missing HTTP security headers, e.g. Strict-Transport-Security; X-Frame-Options; X-XSS-Protection; X-Content-Type-Options; Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP; Content-Security-Policy-Report-Only; Cache-Control and Pragma. HTTP/DNS cache poisoning SSL/TLS issues, such as BEAST, BREACH, Renegotiation attack, SSL Forward Secrecy disabled, weak/insecure SSL cipher suites, and lack of DNS attributes such as CAA Self-XSS reports, and any XSS vulnerabilities where local access is required, except if you can demonstrate a working off-path MITM attack that allows the XSS to occur Missing or incorrect records related to SPF, DMARC, MTA-STS or other emerging standards Source code disclosure vulnerabilities Information disclosure of non-confidential information Email bombing/flooding/rate limiting DoS/DDoS attacks Physical intrusion CORS issues or cookie attributes on sites containing only public content Regular expression denial of service (ReDoS) Presence of Exif metadata on images Lack of CAPTCHA or rate limiting Software version disclosure Flaws affecting out-of-date browsers and plugins Javascript execution in locations that are unable to impact the user’s context or obtain confidential information, such as sandboxed/iframed domains or server-side execution sandboxes Exceeding the stated limits of free accounts Rewards CareEvolution’s Bug Bounty rewards generally align with industry standards for bug bounty programs. The exact amount is determined by our reward panel. For especially innovative or critical vulnerabilities, we may offer higher rewards, while vulnerabilities requiring uncommon user actions may receive lower rewards. CareEvolution reserves the right to consider very closely-related reports as a single report, warranting a single reward. We award bug bounties on a first-come, first-served basis, meaning that the first comprehensive report submitted for any given eligible issue will receive the bounty. Current CareEvolution employees are not eligible to participate in our Bug Bounty program. Rewards, if any, are at the sole discretion of the CareEvolution reward panel. Legal Points CareEvolution is prohibited from rewarding individuals residing in nations listed on Federal sanctions lists. Bug bounty hunters are responsible for any tax obligations based on their residency and citizenship. Additional restrictions may apply based on local laws. CareEvolution’s Bug Bounty Program is not a competition, but rather a discretionary rewards initiative. CareEvolution reserves the right to terminate the Bug Bounty Program at any time, and the decision to grant rewards is entirely at the discretion of CareEvolution. It is essential that testing complies with all applicable laws and does not disrupt or compromise any data that does not belong to you. Testing must also be in accordance with the CareEvolution vulnerability disclosure Guidelines. For inquiries, please contact our information security team.