Authorization comes from the asset owner.
A program listing does not grant permission to test every system an organization owns. Always follow the specific program’s published scope and rules.
Purpose and coverage
This policy sets the baseline rules for submitting and handling vulnerability reports through KSVRI, whether you are participating in an organization-hosted Vulnerability Disclosure Program (VDP) or reporting independent research.
Each VDP is managed by its participating organization. Its published scope, testing conditions, and disclosure requirements apply in addition to these platform-wide rules. Where a program allows less testing than this policy describes, follow the program's narrower limits.
Authorization and scope
A listing on KSVRI is not permission to test every asset belonging to an organization. Only test systems that a program expressly identifies as in scope and only in ways its rules permit. Do not infer authorization from a company name, domain, logo, or public profile.
Third-party systems, customer environments, vendors, employee devices, and linked services remain out of scope unless the responsible owner expressly authorizes testing. If the scope or ownership is unclear, ask the organization before proceeding.
Independent research submission is a reporting channel, not a grant of testing authorization. Researchers remain responsible for obtaining any permissions required for their activities.
Responsible testing
Use the least intrusive method sufficient to verify a suspected issue. Keep requests proportionate, avoid service degradation, and stop as soon as the finding is adequately demonstrated.
- Use test accounts or your own data wherever possible.
- Limit collection and access to the minimum necessary to establish impact.
- Follow rate limits and any additional boundaries in the program.
- Stop testing and notify the relevant program if you encounter unexpected access to sensitive data or risk of disruption.
Prohibited activity
Unless expressly authorized by the asset owner for a defined test, the following activities are prohibited through KSVRI programs:
- Denial-of-service, destructive testing, resource exhaustion, or disruption of production systems.
- Social engineering, phishing, physical intrusion, or targeting employees and customers.
- Exfiltrating, altering, or deleting third-party data; harvesting credentials or secrets.
- Installing persistence, malware, ransomware, or unauthorized backdoors.
- Pivoting to other systems, broad internet-scale scanning, or testing assets outside scope.
- Using a vulnerability for extortion, personal benefit, or public exposure of private information.
If a technique is not clearly permitted, do not assume it is allowed.
Evidence and sensitive information
Submit enough evidence to support verification without creating unnecessary security or privacy risks. Redact personal data, access tokens, passwords, session cookies, and other sensitive material from screenshots, logs, payloads, and reproduction steps where possible.
Use the private report and attachment features rather than public file-sharing links for confidential evidence. Do not upload information that you obtained through activity beyond the authorization you had. If sensitive material has already been exposed, promptly notify the report recipient and avoid further access.
What a useful report includes
Provide an accurate title, affected asset and version if known, a concise explanation of the vulnerability and impact, reproducible steps, and appropriately redacted proof of concept. State any conditions needed to reproduce the behavior.
Disclose whether a finding was previously reported or publicly discussed when that context is relevant. Do not deliberately inflate impact, fabricate evidence, or submit the same issue repeatedly to bypass limits or duplicate handling.
Review and communication
Organizations manage their own VDPs, review reports, and decide how to investigate and remediate findings. KSVRI provides the reporting and coordination workflow; participation does not guarantee a particular response time, outcome, severity classification, or acceptance decision.
Keep communications professional and use the report's authorized conversation channels for clarifications. A request for additional evidence is not permission to expand testing beyond the original scope.
Coordinated disclosure
Keep non-public technical details and privately submitted evidence confidential while coordinating with the affected organization and relevant reviewers. Follow any disclosure date or process expressly agreed with the parties involved, subject to applicable law.
Do not publish private report conversations, customer data, credentials, or unremediated exploit details simply because you submitted a report. If coordination stalls or a serious public-safety concern arises, raise it through the existing report channel before taking further steps.
CVE coordination
Eligible findings may be referred for CVE coordination through Knight Squad Academy, the CVE Numbering Authority (CNA) supporting the KSVRI initiative. KSVRI itself is not a separate CNA.
Submitting a report or requesting a CVE does not guarantee an identifier, a publication date, or researcher credit. Eligibility, assignment, and publication are subject to CNA and CVE Program requirements, including the information needed for a useful public record.
See CVE Coordination and the Knight Squad Academy CVE policy.
Recognition and rewards
A VDP is not automatically a bug bounty program. Financial rewards are available only if an organization separately and expressly offers them under its own terms. KSVRI does not promise payment or reimbursement for research.
Non-monetary recognition, KXP, and achievements—if enabled—are governed by the platform's applicable rules. Duplicate, out-of-scope, unverified, or policy-violating findings may not qualify.
No blanket safe harbor
This policy is intended to encourage responsible, authorized security research. It does not itself grant legal immunity, override local law, or bind a third-party organization to a safe-harbor commitment.
If an organization offers a safe-harbor statement, read that statement together with its exact scope and conditions before testing. KSVRI may restrict reports or accounts involving harmful or unauthorized activity.
Policy questions and changes
We may update this policy to reflect changes in platform functionality, operational practice, or applicable requirements. The date above identifies the current published version.
For questions about a particular program's authorization or disclosure rules, contact that program through its published reporting channel. For platform-specific concerns, use the relevant account or report support channel.
Continue reading