Bug Bounty Program
Saasu values and appreciates the contributions from the cybersecurity community in improving and maintaining our systems to meet cybersecurity standards. We review and accept reports by the community submitted by following the criteria listed below. Saasu will not respond to any vulnerability reports from the exclusions list or vulnerabilities that have been reported previously.
Please do not publish any reported vulnerabilities for Saasu domains.
Reports submitted to Saasu for https://secure.saasu.com are in scope and will be accepted for evaluation.
Saasu retains the right to determine whether to accept a report submitted as a vulnerability disclosure.
Saasu will reject reports where you:
- Create multiple free trial accounts programatically or otherwise. We do this because you in turn trigger volumes of email, sms’s, marketing activities, sales actions and service team followups off the back of that. If you cannot assess our system with a limit of a few trial files we ask that you not seek bounties from Saasu.
- Perform rate limit tests where you have not been considerate in approach. i.e. test small in tight time frames (10 events in <200ms) to reduce volume and cost impacts on our services like email, sms, account creation and related sales and marketing activities.
- Harass our support staff for updates. We have an internal process for the support team to raise a ticket for the development team to review and qualify submissions. This can take some time and is often prioritised after their scheduled workload. The support team is unable to provide you with any further information until the development team completes their review, and sending multiple emails asking for updates creates greater strain on our support team whose first priority is our paying customers.
- Harass our accounting staff for payment, request updates on payment, fail to invoice as requested or any other unprofessional behaviour. even though, at times, they may be paid within days.
- Identify minimal security impact or low exploit-ability, vulnerabilities beyond Saasu’s control, vulnerabilities discoverable through automated scans which have not been verified manually, vulnerabilities already reported or vulnerabilities related to a violation of the program requirements.
Out of scope vulnerabilities
- Vulnerabilities demonstrated where the attacker has direct access to the victim’s device for demonstration purposes eg: direct access to cookies
- Click-jacking on pages with no sensitive actions;
- CSRF without a demonstrated vulnerability;
- Password and account recovery policies, such as reset link expiration or password complexity;
- Presence of autocomplete attribute on web forms;
- Username/user id enumeration;
- Vulnerabilities only affecting outdated or unpatched browsers;
- SSL/TLS configurations without a demonstrated vulnerability;
- Content spoofing/text injection that cannot be leveraged for XSS or sensitive data disclosure;
- Denial of service or resource exhaustion;
- Missing HTTP-only or secure cookie flags unrelated to a vulnerability;
- Missing security headers unrelated to a vulnerability;
- Attacks against network and security infrastructure; and
- Email spoofing issues (e.g., absence or misconfiguration of SPF, DKIM, DMARC).
Saasu would not pursue legal action against participants who:
- Submit in-scope reports and engage in testing/research of systems without harming Saasu, its customers, employees, or third parties.
- Do not compromise the privacy of Saasu’s customers, employees, or other individuals by accessing personal information as an example.
- Do not conduct social engineering, spam, or phishing attacks.
- Do not test the physical security of any property of Saasu or third parties.
- Do not conduct denial-of-service or resource-exhaustion attacks.
- Comply with applicable criminal laws.
- Adhere to other applicable laws.
You agree that Saasu may disclose the information in a report you submit through this website. Saasu will consider any request from a researcher to make a disclosure but reserves the right to deny such requests.
How to Submit a Report
To submit a report to Saasu, please email the report to firstname.lastname@example.org accepting the disclousure guidelines in this policy by including the sentence “I have read and agree to the vulnerability disclosure policy and terms outlined by Saasu.”
Expectations for Researchers:
- Well-written reports in English will have a higher chance of faster response and resolution;
- Reports that include proof-of-concept code enable Saasu to better understand and triage the submitted information;
- Reports that include only output from programs may receive lower priority;
- Participating in this program does not give you any right to intellectual property owned by Saasu or a third party;
- Do not report the same vulnerability more than once (e.g. same vulnerability for different entities, fields, interfaces) for Saasu domains.
- Please include how you found the vulnerability; if possible include any potential remediation(s); and
- Please do not include any personal information.
- Account takeovers requiring a victim to be social engineered or an attacker to gain access to their mobile or email are not considered account takeovers.
How Saasu pays a bounty
We pay bounties in AUD via PayPal.
- Invoice Saasu Pty Ltd for the amount notified in the legal name that is to be paid.
- Include your PayPal payment email address in the invoice.
- Do not charge fees or an amount that differs to the exact bounty as accounts will not process the request.
- We send payment via PayPal within 5 business days.