Vulnerability Disclosure Policy

Introduction

Security is core to our values, and 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. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.

Expectations

When working with us according to this policy, you can expect us to:

• Extend Safe Harbor for your vulnerability research that is related to this policy
• Work with you to understand and validate your report, including a timely initial response to the submissio
• Work to remediate discovered vulnerabilities in a timely manner
• Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.

Scope

Assets hosted on the following domains:

• *.ampol.com.au
• *.ampol.com.sg
• *.ampolusa.com

Assets hosted on the following IPv4 ranges:

• 203.0.32.0/24
• 203.0.33.0/24
• 203.0.34.0/24
• 203.0.35.0/2

Assets that are directly attributable to Ampol Australia usingopen-source intelligence(OSINT) techniques

Out of Scope

• Research that requires physical access to Ampol Australia’s sites (including but not limited to, retail stores, terminals, refinery sites and offices) 
• Social Engineering of any kind 
• Reporting of bulk personal data. If you think you have found a bulk data breach containing personal information, please report a proof of concept not a dump of sensitive information.  Importantly, you must ensure that you continue to comply with the Privacy Act 1998 (Cth) or any other applicable privacy legislation. 
• Denial of Service attacks that interfere with the normal operation of systems. If you have found an issue that could result in a Denial of Service attack it is enough to demonstrate via a proof of concept 
• Generic issues with SaaS applications used by Ampol Australia. If you find an issue with Ampol Australia’s specific configuration of a SaaS tool please report it, but generic issues impacting SaaS platforms should be reported to the platform vendor 
• Output from automated tools will not be accepted without impact analysis and proof of concept 

Ratings and Rewards

This program uses the Bugcrowd Vulnerability Rating Taxonomy. Points will be awarded for successful submissions

Disclosure Policy

• The Official Channel for reporting vulnerabilities is the BugCrowdsubmission form on this page
• You must gain explicit permission from Ampol Australia before disclosing any issues identified. Please manage any such requests for permission through the BugCrowd platform
• Rewards will not be given for issues that are publicly disclosed without permission and you will be excluded from future programs

Ground Rules

• To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attack, we ask that you: 
• Play by the rules. This includes following this policy, as well as any other relevant Ampol's guidelines or policies. If there is any inconsistency between this policy and any other relevant terms, the terms of this policy will prevail 
• Report any vulnerability you have discovered promptly 
• Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience 
• Use the tools provided by BugCrowd to discuss vulnerability information with us 
• Keep the details of any discovered vulnerabilities confidential until they are fixed, according to the Disclosure Policy 
• 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. 

Safe Harbour

When conducting vulnerability research according to this policy, we consider this research conducted under this policy to be:

• Authorized in view of any applicable anti-hacking law 
• Authorized in view of relevant anti-circumvention laws 
• Exempt from restrictions in our Acceptable Usage Policy 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 

You are expected, as always, to comply with all applicable laws and must not cost any parties including us to suffer losses or damages as a result of your conduct. 

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.