ASEC greatly appreciates investigative work into security vulnerabilities which is carried out by well-intentioned, ethical security researchers. We are committed to thoroughly investigating and resolving security issues in our platform and services in collaboration with the security community. This document aims to define a method by which ASEC can work with the security research community to improve our online security.
Vulnerabilities in ASEC products and services are only within scope of the Bug Bounty Program when they meet the following conditions:
Below is a list of in-scope and out-of-scope assets. Please note that this list is not exhaustive and may be updated at any time.
The following security issues are currently not in scope (please don’t report them):
Unfortunately, ASEC is not currently offering a paid bug bounty program. We would like to offer a token of our appreciation to security researchers who take the time and effort to investigate and report security vulnerabilities to us according to this policy. Reporters of qualifying vulnerabilities will be offered a unique ASEC reward. Please note: swag rewards are only available for shipment within North America, and no monetary bounties are offered.
If you have discovered an issue which you believe is an in-scope security vulnerability (please see the section above for more details on scope), please email [email protected]. Provide as much information as possible about the potential issue you have discovered. The more information you provide, the quicker ASEC will be able to validate the issue.
The following should be included in your report:
ASEC does not require your submission to be encrypted, however if you want to send us a vulnerability using PGP we still want you to have this option.
Please realize that using PGP will likely slow down our response to your submission. Under normal circumstances, a member of our team can view security reports and respond immediately. If you PGP encrypt your message, only core members of the security team will be able to triage your submission. Please be aware that if we receive an encrypted submission, unless your submission has a significant impact, we will likely not reply utilizing PGP.
Still, if you feel your vulnerability submission requires the use of PGP, then you can find our public key here.
In response to your initial email to [email protected] you will receive an acknowledgement reply email from the ASEC Security Team, this is usually within 24 hours of your report being received. Following the initial contact, our Security Team will work to triage the reported vulnerability and will respond to you as soon as possible to confirm whether further information is required and/or whether the vulnerability qualifies as per the above scope, or is a duplicate report. Next, necessary remediation work will be assigned to the appropriate ASEC teams and/or supplier(s). Priority for bug fixes and/or mitigations will be assigned based on the severity of impact and complexity of exploitation. Vulnerability reports may take some time to triage and/or remediate, you’re welcome to enquire on the status of the process but please limit this to no more than once every 14 days, this helps our Security team focus on the reports as much as possible.
Our Security Team will notify you when the reported vulnerability is resolved (or remediation work is scheduled) and will ask you to confirm that the solution covers the vulnerability adequately. We will offer you the opportunity to provide us with feedback on the process. This information will be used in strict confidence to help us improve the way in which we handle reports and/or develop services and resolve vulnerabilities on our acknowledgements page and we’ll ask for the details you wish to be included.
Security researchers must not:
We request that any and all data retried during research is securely deleted as soon as it is no longer required and at most, 1 month after the vulnerability is resolved, whichever occurs soonest.
If you are unsure at any stage whether the actions you are thinking of taking are acceptable, please contact our security team for guidance (please do not include any sensitive information in the initial communications): [email protected].
The policy is designed to be compatible with common good practices among well-intentioned security researchers. It does not give you permission to act in any manner that is inconsistent with the law or cause ASEC to be in breach of any of its legal obligations. ASEC will not seek prosecution of any security researcher who reports, in good faith and in accordance with this policy, any security vulnerability on an in-scope ASEC service.
If you wish to provide feedback or suggestions on this policy, please contact our security team: [email protected]. This policy will evolve over time and your input will be valued to ensure that it is clear, complete and remains relevant.