Security and responsible disclosure

• 1.1 This policy covers the Reports sites published at therisk.global/nexus-reports/, globalriskforum.com/nexus-reports/, globalriskalliance.com/nexus-reports/, nexustandards.com/nexus-reports/ and risksacademy.com/nexus-reports/ (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.

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

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

• 4.1 GCRI Canada 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.

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

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

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

Prepared for review by legal counsel before adoption.

• EmailGateway GW-ACADEMYSend it from this pageEvidence, 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 depositDeposit it and submit to the communityPublish 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 AcademySee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.

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.