Check Out My LLC (“COMC”) and our affiliated companies are committed to ensuring the security of our customers by protecting their information from unwarranted disclosure. This policy is intended to give security researchers (AKA “ethical hackers” or “white-hat hackers”) clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
This policy describes what systems and types of research are covered under this policy, 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 that we can fix them and keep our customers 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.
If, in our sole discretion, you make a good-faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and COMC will not recommend or pursue legal action related to your research.
Under this policy, “research” means activities in which you:
- notify us as soon as possible after you discover a real or potential security issue.
- make every effort to avoid privacy violations, degradation of customer 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 (as defined in the Disclosure section below) to resolve the issue before you disclose it publicly.
- do not intentionally compromise the privacy or safety of COMC employees, customers, or any third parties.
- do not intentionally compromise the intellectual property or other commercial or financial interests of any COMC personnel or entities, or any third parties.
Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose that data to anyone else.
This policy applies to the following systems and services within the Check Out My, LLC organization:
Systems and services directly associated with domains and sub-domains listed above are in scope. Additionally, any website published with a link to this policy shall be considered in scope. Websites not explicitly listed here or published with a link to this policy are considered out of scope for this policy. Vulnerabilities found in non-COMC systems from our vendors fall outside of 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 there is a system not in scope that you think merits testing, please contact us at firstname.lastname@example.org to discuss it first. We reserve the right to increase or decrease the scope of this policy over time.
Rules of Engagement
Security researchers must not:
- test any system other than the systems 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 COMC facilities or resources,
- engage in “social engineering” with COMC employees, vendors, and/or customers,
- send unsolicited electronic mail to COMC employees, vendors, and/or customers, including “phishing” messages,
- execute or attempt to execute “Denial of Service” or “Resource Exhaustion” attacks,
- introduce or attempt to introduce malicious software,
- test in a manner which could degrade the operation of COMC systems, or intentionally impair, disrupt, or disable COMC systems,
- test third-party applications, websites, or services that integrate with or link to or from COMC systems,
- delete, alter, share, retain, or destroy COMC data, or render COMC data inaccessible, or
- use an exploit to exfiltrate data, establish command-line access, establish a persistent presence on COMC systems, or “pivot” to other COMC systems.
Security researchers may:
- view or store COMC 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 an exposure of nonpublic data, and
- purge any stored COMC nonpublic data upon reporting a vulnerability.
Reporting a Vulnerability
We accept vulnerability reports at https://comc.responsibledisclosure.com . Reports may be submitted anonymously. We do not support PGP-encrypted emails at this time.
Information submitted under this policy will be used for defensive purposes only: to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely COMC, we may share your report with the United States Cybersecurity and Infrastructure Security Agency (CISA). We will not share your name or contact information without express permission (unless compelled to do so by a court of law).
By clicking Submit Report, 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 COMC information systems, and consent to having the contents of the communication and follow-up communications stored on a COMC information system.
In order to help us triage and prioritize submissions, we recommend that your reports:
- 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/video clips are helpful).
COMC is committed to timely correction of vulnerabilities. However, we recognize that public disclosure of a vulnerability in absence of 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 acknowledgement (which will be sent to you via email) confirming 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), local law enforcement, as well as any affected vendors. We will not share names or contact data of security researchers unless given explicit permission by the researcher or unless compelled by a court of law.
Acknowledgments & Bug Bounties
While COMC does not currently offer a “Bug Bounty” program (i.e., we do not pay “bounties” or other forms of financial compensation for security vulnerabilities that are reported to us via this policy), we nonetheless appreciate the help of the security researcher community in finding and making us aware of potential vulnerabilities. In recognition of those efforts, we are happy to, at our sole discretion, publicly acknowledge individual security researchers who, acting in good faith, find and ethically disclose any potential vulnerabilities to us and wish to be added to our list of acknowledgements. For COMC Vulnerability Disclosure Policy Program acknowledgments, please visit our Acknowledgements page here.
Questions regarding this policy may be sent to email@example.com. We also invite you to contact us with suggestions for improving this policy.