Bug Bounty
Keeping user information safe and secure is a top priority for us at Syfe, and we welcome the contribution of external security researchers.
Introducing Bug Bounty
Syfe 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, and what you can expect from us.
How it works
Please report security issues via mail to: [email protected], providing all relevant information. Your submission will be reviewed and validated by a member of our security team. The more details you provide, the easier it will be for us to triage and fix the issue.
This policy applies to the assets listed below. If you believe you have found a security issue in any of them, we encourage you to notify us.
To perform testing on these test environments, please email us at [email protected] with the subject line “Test Credentials: Bug Bounty” for access to the credentials.
- https://uat-bugbounty.nonprod.syfe.com/ - Primary Test Environment
- api-uat-bugbounty.nonprod.syfe.com
- www.syfe.com
- alfred.syfe.com
- mark8.syfe.com
- api.syfe.com
- Assets or other equipment not owned by parties participating in this policy.
- Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.
- Please provide detailed reports with reproducible steps and a clearly defined impact.
- Submit one vulnerability per report.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
The Syfe promise
When working with us, according to this policy, you can expect us to
- Respond to your report promptly, and work with you to understand and validate your report;
- Strive to keep you informed about the progress of a vulnerability as it is processed;
- Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
- Extend Safe Harbor for your vulnerability research that is related to this policy.
Provided you abide with the following when conducting vulnerability research under this policy, we consider this research conducted under this policy to be entitled to the safe harbour protections mentioned here under:
- Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
- Report any vulnerability you’ve discovered promptly;
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
- Use only the Official Channels to discuss vulnerability information with us;
- Provide us a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly;
- Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
- If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
- You should only interact with test accounts you own or with explicit permission from the account holder; and
- Do not engage in extortion.
In participating in our vulnerability disclosure programme in good faith, we ask that you:
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services.
- Only interact with accounts you own or with explicit permission of the account holder. If you do encounter Personally Identifiable Information (PII) contact us immediately, do not proceed with access, and immediately purge any local information.
- Authorised concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
- Authorised concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
- Exempt from restrictions in our Terms of Service (TOS) and/or Acceptable Usage Policy (AUP) that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
- Provide us with a reasonable amount of time to resolve vulnerabilities.
- Consult us prior to any disclosure to the public or a third-party.
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 harbour applies only to legal claims under the control of Syfe, and that the policy does not bind independent third parties.
In recognition of your service
Syfe will provide a reward for qualifying vulnerabilities that are discovered by you. A “qualifying vulnerability” is one that is determined by Syfe, at its sole and absolute discretion:
- to meet the requirements of this policy;
- as not being excluded under this policy; and
- as not having been discovered or informed to Syfe by any other person.
Participation in our vulnerability disclosure programme does not constitute a contract between Syfe and you. Syfe will determine any eligibility for a reward under this programme at its sole and absolute discretion. You are not entitled to, and Syfe is not obliged to and does not undertake to provide, any legal or equitable remedy for any participation in this programme.
Attacks that can completely compromise the integrity, the authenticity, and potentially the availability of our services are our biggest priority.
Issues that affect a large portion of the platform and would require immediate action to prevent from spreading.
Medium-severity issues tend to require user-interaction and the scope of the attack is usually narrowed down to a single user.
The issues marked as Low Severity include information leakage, configuration errors and a lack of some security measures.
Exclusions
- Reports of vulnerabilities in applications or systems not listed in the "Scope" section, unless you've found a high-severity issue that directly affects us. Issues in third-party services should be reported to the respective team.
- Vulnerability reports with video-only Proofs of Concept.
- Reports that state that software is out of date or vulnerable without a proof of concept.
- Highly speculative reports about theoretical damage. Be concrete.
- Vulnerabilities as reported by automated tools without additional analysis as to how they’re an issue.
ISSUES
Excluded from scope
