Introduction 

Illumio is committed to ensuring the security of our customers by protecting their information. This policy is intended to give security researchers 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 encourage you to contact us to report potential vulnerabilities in our systems. 

Authorization 

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 Illumio 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. 

Guidelines 

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 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 persistent command line access, or use the exploit to pivot to other systems. 
• Provide us with a reasonable amount of time to resolve the issue before you disclose it publicly. 
• Do not submit a high volume of low-quality reports. 

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. 

Test Methods 

Rules regarding authorized test methods:

• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data are not authorized
• Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or     any other non-technical vulnerability testing are not authorized
• No testing of Third-party Services
• No uploading of any vulnerability or client-related content to third-party sites (e.g. Github, DropBox,     YouTube)
• All attack payload data must use professional language
• If able to gain access to a system, accounts, users, or user data, stop at the point of recognition and report. Do not dive deeper to determine how much more is accessible.
• When documenting a vulnerability, if a vulnerability is public, please make sure it is discreet and doesn't identify the company.

Scope 

This policy applies to the following systems and services: 

• *.illumio.com
• *.illum.io
• *.ilabs.io

Out of Scope - Low Impact Vulnerabilities

• Account/e-mail enumeration using brute-force attacks
• Any low-impact issues related to session management (i.e. concurrent sessions, session expiration, password reset/change log out, etc.)
• Bypassing content restrictions in uploading a file without proving the file was received
• Client-side application/browser autocomplete or saved password/credentials
• Descriptive or verbose error pages without proof of exploitability or obtaining sensitive information
• Incomplete or missing SPF/DMARC/DKIM records
• SSH Username Enumeration
• SSL Weak Ciphers/ POODLE / Heartbleed
• CSV Injection
• Server-Status if it does not reveal sensitive information
• Snoop Info Disclosure Issues related to password/credential strength, length, lockouts, or lack of     brute-force/rate-limiting protections
• Low impact Information disclosures (including Software version disclosure)
• Missing Cookie flags
• Missing/Enabled HTTP Headers/Methods which do not lead directly to a security vulnerability
• Reflected file download attacks (RFD)
• Self-exploitation (i.e. password reset links or cookie reuse)
• SSL/TLS best practices that do not contain a fully functional proof of concept
• URL/Open Redirection
• Use of a known-vulnerable library that leads to a low-impact vulnerability (i.e. jQuery outdated version leads to low impact XSS)
• Valid bugs or best practice issues that are not directly related to the security posture of the company
• Vulnerabilities affecting users of outdated browsers, plugins, or platforms
• Vulnerabilities that allow for the injection of arbitrary text without allowing for hyperlinks, HTML, or     JavaScript code to be injected
• Vulnerabilities that require the user/victim to perform extremely unlikely actions (i.e. Self-XSS)

Any service not expressly listed above, such as any connected services, is excluded from the scope and is 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 are not sure whether a system is in scope or not, contact us at security[at]illumio[dot]com before starting your research(or at the security contact for the system's domain name listed in the .com WHOIS). 

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 overtime. 

Reporting a Vulnerability 

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 Illumio, we may share your report with other security firms, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission. 

We accept vulnerability reports via security[at]illumio[dot]com. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report. 

We do support PGP-encrypted emails. For secure e-mail, you can find the Illumio pgp/gpg key details at security.txt. By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against Illumio related to your submission.

What we would like to see from you

To help us triage and prioritize submissions, were commend that your reports: 

• Describe the location where the vulnerability 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). 
• Be in English, if possible. 

What You Can Expect From Us  

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible. 

• We will acknowledge that your report has been received. 
• 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. 
• We will maintain an open dialogue to discuss issues. 

Questions 

Questions regarding this policy may be sent to security[at]illumio[dot]com.