<p>Welcome to the Red Lion Cybersecurity Portal. The company has created a centralized Product Security Incident Response Team (PSIRT) to review, respond and oversee all security-related vulnerabilities surrounding Red Lion products and solutions. The PSIRT is a cross-functional team, comprised of company representatives from several departments including, Product Management, Customer Experience, and Engineering. </p>
<p>The PSIRT’s charter is to </p>
<li> - Receive all Security related issues involving Red Lion Products and Services</li>
<li> - Investigate all reported vulnerabilities</li>
<li> - Coordinate all internal resources</li>
<li> - Publish Red Lion responses to all security reports and vulnerabilities</li>
<p>The PSIRT has full authority to investigate and report on any potential Cybersecurity vulnerabilities raised with the company. Red Lion encourages all customers, channel partners, independent third-party investigation entities, and interested parties to report any and all Cybersecurity related concerns. </p>
<p> Click on the Network or Automation groups below, then the follow button if you would like to receive an email when a new alert is posted. <b>You may also click on the Support button at the bottom of any page to submit your own findings or to contact us for assistance.</b></p>
<p><b>Red Lion Vulnerability Disclosure Policy</b></p>
<p>Red Lion Controls is committed to providing industrial data products and software that enables our customers to connect, access and visualize their data securely. As part of this commitment, we maintain a robust security program to identify and mitigate potential vulnerabilities in our products. We also work with security researchers around the world to help identify and mitigate potential vulnerabilities in our firmware and software that were not already detected thorough our internal controls.</p>
<p>Our Vulnerability Disclosure Program (VDP) is a structured framework for security researchers to identify and submit security 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.</p>
<p>If 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 Red Lion will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.
<p>Under this policy, “research” means activities in which you:
<li>Notify us as soon as possible after you discover a real or potential security issue.</li>
<li>Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.</li>
<li>Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems. </li>
<li>Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.</li>
<li>Do not submit a high volume of low-quality reports.</li>
<p>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 this data to anyone else. It is imperative that a solution be identified, and a coordinated disclosure be developed to minimize impact.
The following test methods are not authorized:
<li>Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data</li>
<li>Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing</li>
<p>This policy applies to the products, systems, and services produced by Red Lion Controls.</p>
<p>Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in 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). If you aren’t sure whether a system is in scope or not, contact us at firstname.lastname@example.org.</p>
<p>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 particular system 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.</p>
<p><b>Reporting a vulnerability</b></p>
<p>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 Red Lion, 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.
<p>We accept vulnerability reports at this form or via email@example.com. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.
<p>We do support PGP-encrypted emails, our public key can be downloaded at <a href="https://support.redlion.net/hc/en-us/articles/20069685670157-Red-Lion-PSIRT-Public-Key">RLC Public Key</a> For particularly sensitive information, submit through our HTTPS web form.
<p>By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against Red Lion related to your submission.
<p>What we would like to see from you</p>
<p>In order to help us triage and prioritize submissions, we recommend that your reports:
<li>Describe the location the vulnerability was discovered and the potential impact of exploitation. </li>
<li>Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).</li>
<li>Suggest mitigation or remediation actions, as appropriate. </li>
<p>What you can expect from us</p>
<p>When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.
<li>Within 3 business days, we will acknowledge that your report has been received. </li>
<li>To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution. </li>
<li>We will maintain an open dialogue to discuss issues. </li>
<p><b>Modification or Termination of this Policy</b></p>
<p>Red Lion may modify the terms of this policy or terminate the policy at any time.</p>
<p><b>Activities Outside the Scope of this Policy</b></p>
<p>Red Lion does not authorize, permit, or otherwise allow (expressly or impliedly) any person, including any individual, group of individuals, consortium, partnership, or any other business or legal entity, to engage in any security research or vulnerability or threat disclosure activity on or affecting Red Lion products that is inconsistent with this policy or the law. If you engage in any activities that are inconsistent with this policy or other applicable law, you may be subject to criminal and/or civil liabilities.</p>
<p>Questions regarding this policy may be sent to firstname.lastname@example.org. We also invite you to contact us with suggestions for improving this policy.</p>