Ellucian Vulnerability Disclosure Policy
We take the security of our systems seriously, and we value the security community. The disclosure of security vulnerabilities to Ellucian helps us keep information secure. We want to thank those of you who have helped so far by honoring you on our Security Researcher "Hall of Fame".
We require that all researchers:
- Make every effort to avoid privacy violations, violation of licensing terms, degradation of user experience, disruption to production systems, and destruction of data during security testing;
- Perform research only within the scope set out below;
- Use the identified communication channels to report vulnerability information to us; and
- Keep information about any vulnerabilities you’ve discovered confidential between yourself and Ellucian until we’ve had 90 days to resolve the issue;
- Allow an appropriate amount of time for customers to deploy updates before releasing any specific details of the issue that could harm those customers.
If you follow these guidelines when reporting an issue to us, we commit to:
- Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission);
- Recognize your contribution on our Security Researcher Hall of Fame, if you are the first to report the issue and we make a code or configuration change based on the issue.
- Customers wishing to perform testing of Ellucian cloud systems must notify Ellucian (via email at [email protected]) and receive confirmation prior to the start of any testing. Such testing must be limited to non-production environments.
- Researchers not affiliated with a licensed Ellucian customer should contact [email protected] for additional information prior to testing.
Out of scope
Any services hosted by 3rd party providers and services are excluded from scope.
In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- UI and UX bugs and spelling mistakes
- Network level Denial of Service (DoS/DDoS) vulnerabilities
- Brute force attacks
Things we do not want to receive:
- Personal information
- Credit card holder data
How to report a security vulnerability?
If you believe you’ve found a security vulnerability in one of our products or platforms please contact us by emailing [email protected]. Please include the following details with your report:
- Description of the location and potential impact of the vulnerability;
- A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us);
- Your name/handle and a link (website, Twitter profile, LinkedIn profile, etc.) for recognition in our Security Researcher Hall of Fame.