Aeros

Vulnerability Disclosure Policy

Overview

 

Aeros is committed to ensuring the security of our customers by protecting their information from unwarranted disclosure. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and convey our preferences in submitting discovered vulnerabilities to us.

This policy 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.

We want security researchers to feel comfortable reporting vulnerabilities they’ve discovered – as set out in this policy – so we can fix them and keep our users safe. We have developed this policy to reflect our values and uphold our sense of responsibility to security researchers who share their expertise with us in good faith.

 

Authorization

 

If you make a good faith effort to comply with this policy during your security research, we will consider your research authorized, we will work with you to understand and resolve the issue quickly, and Aeros will not recommend or pursue legal action related to your research. However, we do not offer monetary rewards for vulnerability disclosures.

 

Guidelines

 

Under this policy, “research” means activities in which you:

  • Notify us as soon as possible after you discover an actual 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 command line access and/or persistence, 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.
  • You do not intentionally compromise the privacy or safety of Aeros personnel, customers, or any third parties.
  • You do not intentionally compromise the intellectual property or other commercial or financial interests of any Aeros personnel or entities, customers, or third parties.

Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, proprietary information, or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

 

Scope

 

All systems and services associated with the domains listed below are in scope.  Likewise, unless explicitly excluded, subdomains of each listing are always in scope.  Additionally, any website published with a link to this policy shall be considered in scope.  Vulnerabilities found in non-Aeros systems from our vendors fall outside this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any).

Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If a system is not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.

 

Product Domains
Aeros getaeros.com

Rules of Engagement

 

Security researchers must not:

  • Test any system other than those set forth in the ‘Scope’ section above.
  • Disclose vulnerability information except as set forth in the ‘Reporting a Vulnerability’ and ‘Disclosure’ sections below.
  • Engage in physical testing of facilities or resources.
  • Engage in social engineering.
  • Send unsolicited electronic mail to Aeros personnel or customers, including “phishing” messages.
  • Execute or attempt to execute “Denial of Service” or “Resource Exhaustion” attacks.
  • Introducing malicious software.
  • Test in a manner that could degrade the operation of Aeros systems or intentionally impair, disrupt, or disable Aeros systems.
  • Test third-party applications, websites, or services that integrate with or link to or from Aeros systems.
  • Delete, alter, share, retain, or destroy Aeros data or render Aeros data inaccessible.
  • Or use an exploit to exfiltrate data, establish command line access, establish a persistent presence on Aeros systems, or “pivot” to other Aeros systems.

Security researchers may:

  • View or store Aeros’ nonpublic data only to the extent necessary to document the presence of a potential vulnerability.

Security researchers must:

  • Cease testing and notify us immediately upon discovery of a vulnerability.
  • Cease testing and notify us immediately upon discovery of exposure of nonpublic data.
  • Purge any stored Aeros nonpublic data upon reporting a vulnerability.

Reporting a Vulnerability

 

We accept vulnerability reports at getaeros.com on our Contact Us page.

Information submitted under this policy will only be used for defensive purposes – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely Aeros, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.

By submitting a vulnerability, you are indicating that you have read, understand, and agree to the guidelines described in this policy for the conduct of security research and disclosure of vulnerabilities or indicators of vulnerabilities related to Aeros information systems and consent to having the contents of the communication and follow-up communications stored on a Aeros system.

To help us triage and prioritize submissions, we recommend that your reports:

  • Adhere to all legal terms and conditions.
  • Describe the vulnerability, where it was discovered, and the potential impact of exploitation.
  • Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).

 

Disclosure

 

Aeros is committed to the timely correction of vulnerabilities. However, we recognize that public disclosure of a vulnerability without a readily available corrective action likely increases versus decreases risk. Accordingly, we require that you refrain from sharing information about discovered vulnerabilities for 90 calendar days after you have received our acknowledgment of receipt of your report. If you believe others should be informed of the vulnerability prior to our implementation of corrective actions, we require that you coordinate in advance with us.

We may share vulnerability reports with the Cybersecurity and Infrastructure Security Agency (CISA) and any affected vendors. We will not share security researchers’ names or contact data unless given explicit permission.

 

Verification and Remediation

The General Manager will be responsible for keeping an ongoing list of public reports, verifications, and remediations. Validation and remediation will be assigned to the appropriate Mgmt. Team members, according to the source of the vulnerability (i.e., if from the website, will be assigned to sales and marketing).

Verification and Remediation Procedures

1.  Upon receipt of an email, the Aeros General Manager is responsible for calling a Management Team meeting and deciding who should respond and the level of response.

a. Level of response includes verifying the threat and communicating with the source.

2.  The General Manager will also be responsible for determining the severity of the threat and may raise a security incident with Aeros IT to involve the legal and/or Volaris Data Security Team.

 

Review and Revision

This policy will be reviewed as deemed appropriate, but no less frequently than every 12 months.

Aeros Management will undertake a policy review.