- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 0
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Response
-
Within 3 days
including an initial confirmation of your report within 72 hours of submission
- Safe harbor
-
Partial
If you follow these guidelines when reporting an issue to us, we commit to:
- Hall of fame
-
Yes
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.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
0 assets you may test, 7 excluded.
Self-hosted does not list the scope of this program publicly. Check its policy.
Out of scope (7)
- Any services hosted by 3rd party providers and services
- Brute force attacks
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Network level Denial of Service (DoS/DDoS) vulnerabilities
- UI and UX bugs and spelling mistakes
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Ellucian's policy. "We" in these lines means the program, not this site.
While testing
-
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.
-
Customers wishing to perform testing of Ellucian cloud systems must notify Ellucian (via email at the address on the policy page ) 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 the address on the policy page for additional information prior to testing.
Not accepted
-
UI and UX bugs and spelling mistakes
-
Network level Denial of Service (DoS/DDoS) vulnerabilities
-
Brute force attacks
-
Personal information
-
Credit card holder data
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 6 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.