Skip to content

Jisc

Vulnerability disclosure program on Self-hosted jisc.ac.uk

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
3
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]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 7 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 7 days Respond and acknowledge your report within seven calendar days
Safe harbor
Full Promise not to take legal action against you for accessing (or attempting to access) our systems as long as this policy is followed and you do not cause foreseeable harm
Hall of fame
Yes If you wish, acknowledge your assistance to Jisc in our hall of fame (below)

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

3 assets you may test.

Domains 1

  • jisc.ac.uk

Products and areas 2

  • All systems owned by Jisc and its subsidiaries
  • Any system managed or operated by Jisc

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Jisc's policy. "We" in these lines means the program, not this site.

While testing

  • Respect our members’ privacy . Contact us immediately if you access anyone else’s data, personal or otherwise.
  • Act in good faith . You should report the vulnerability to us with no conditions attached
  • Work with us . Promptly report any findings to us, stopping after you find the first vulnerability and requesting permission to continue testing.
  • Exfiltrate data. Instead use a proof of concept to demonstrate a vulnerability
  • Use a vulnerability to disable further security controls
  • Perform social engineering
  • Perform any testing of physical security
  • Break the law, or any agreements you may have with Jisc or third parties
  • Only test systems that are in scope of this policy.
  • Use a test, or other non-production, environment if it is available to you

Not accepted

  • Missing security headers that may be best-practice but do not impact on the security of the system in this instance
  • Support for older, but non-exploitable, protocols and cipher suites such as TLS 1.1.
  • Fingerprinting/version detection
  • Out of date software, with no exploitable vulnerability

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

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.