Risk Academy, led by the Nexus Consortium · Legal
Security and responsible disclosure · Version 1.0, effective 20 October 2026
Security and responsible disclosure
How to report a security vulnerability in risksacademy.com and its faculty sites, the rules for good-faith research, the commitment not to pursue researchers who follow them, and what reporters can expect.
توضیحی: لورینز اٹریکٹر پر نشانات، ایک معیاری مربوط غیر خطی نظام
01دستاویز
Security and responsible disclosure
- Version
- 1.0
- Effective date
- 20 October 2026
- Last updated
- 20 October 2026
- ناشر
- The publisher of record named in the Legal Notice
- رابطہ
- رابطہ فارم
Risk Academy، جس کی قیادت Nexus Consortium کرتا ہے
02Summary
Summary, with 6 related topics
Summary
The document in brief
- Report vulnerabilities privately to the contact address.
- Good-faith research that follows the rules is not pursued.
- Coordinated disclosure; no reward is offered.
ریکارڈ
Version 1.0, effective 20 October 2026
| ریکارڈ | قدر |
|---|---|
| Document | Security and responsible disclosure |
| Version | 1.0 |
| Effective date | 20 October 2026 |
| Last updated | 20 October 2026 |
| ناشر | The publisher of record named in the Legal Notice |
| رابطہ | رابطہ فارم |
Section 1
دائرہ کار
- 1.1 This policy covers risksacademy.com and the faculty sites published at addresses beginning with risksacademy.com/ (together, the Site), the forms and interfaces they offer and the public repositories from which they are built. Third-party services that the pages request, listed in the cookie and storage notice, are covered by their own providers' policies.
Section 2
How to report
- 2.1 Send a report to the contact form. Describe the vulnerability, the address or component affected, the steps to reproduce it and its likely impact.
- 2.2 Do not include exploit code, personal information, passwords or access keys in a first message. An encrypted channel is arranged on request.
Section 3
Rules for good-faith research
- 3.1 Access, keep or disclose no more data than is needed to show the vulnerability, and stop and report at once if personal information is reached.
- 3.2 Do not modify or delete data, degrade a Service, run denial-of-service or volumetric tests, use social engineering or phishing, attempt physical access, or test the systems of third parties.
- 3.3 Give the publisher reasonable time to fix the vulnerability before any public disclosure, and agree the date of disclosure with it. Disclosure is coordinated, and the reporter is credited if the reporter wishes.
Section 4
Safe harbour
- 4.1 The publisher will not bring legal action against, or refer to law enforcement, a person who reports a vulnerability in good faith and follows this policy, and will treat that research as authorised for the purposes of its own terms. This commitment cannot bind third parties or authorities, and does not cover activity that breaches the law in a way this policy does not contemplate.
Section 5
What reporters can expect
- 5.1 An acknowledgement with a reference, an assessment of the report, updates while the fix is made and notice when it is complete. Reports are handled confidentially and the reporter's details are used only for the report.
- 5.2 No payment or reward is offered for reports.
03Section 6
Section 6, section 7 and document
Section 6
Out of scope
- 6.1 Findings of automated scanners without a demonstrated impact, the absence of a best-practice setting without a demonstrated risk, reports about third-party services, and vulnerabilities that require a compromised device or an outdated browser.
Section 7
Incidents involving personal information
- 7.1 An incident that affects personal information is handled, recorded and notified to the people affected and to the competent authorities as the privacy documents and the applicable law require.
Document
Status of this document
Prepared for review by legal counsel before adoption.
رپورٹیںتعاون کریں
اس صفحے سے شواہد فراہم کریں۔
Reports is the Consortium's quarterly publication, written by six desks. This page sits with the Academy Capability desk. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work. Sent to the wrong desk, it is forwarded, not refused.
Academy Capability desk
- EmailGateway GW-ACADEMY Send it from this page Evidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen deposit Deposit it and submit to the community Publish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsRisk Academy See which desk takes what you have The routing table opens the contribution page: what you have, the desk that takes it, how each contribution is reviewed and credited, and the licence.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Questions about this document
Questions and requests go to the contact form.