RookDuel | Security
Vulnerability Disclosure Policy
- Published by
- RookDuel
- Last updated:
- October 17, 2026
- Document sections
- 10
RookDuel maintains this Vulnerability Disclosure Policy to provide an official channel for reporting suspected security vulnerabilities affecting its digital assets and maintained software.
This policy defines reporting procedures, security testing restrictions, disclosure expectations, and the boundaries of any authorization granted by RookDuel.
The existence of this policy does not constitute authorization to conduct security testing, vulnerability scanning, penetration testing, or exploitation against RookDuel systems.
In this document10 sections
Reporting Security Vulnerabilities
Suspected vulnerabilities must be submitted through an official, designated reporting channel.
Security contact: security@rookduel.tech
Reports should include:
- A description of the suspected vulnerability.
- The affected asset, endpoint, product, or software version.
- Relevant reproduction details, where obtained through authorized activity.
- A technical assessment of the potential impact.
- Supporting evidence that does not unnecessarily expose sensitive data.
Do not include passwords, authentication tokens, confidential third-party information, or personal data that is not necessary for evaluating the report.
Submitting a report does not establish a contractual relationship or confer authorization for further investigation.
Security Testing Restrictions
Unless explicitly authorized in writing, the following activities are not permitted under this policy:
- Penetration testing, exploit attempts, or deliberate vulnerability probing.
- Automated vulnerability scanning or security enumeration targeting deployed systems.
- Attempts to bypass authentication, authorization, rate limits, or other security controls.
- Accessing, collecting, modifying, or deleting information belonging to other users or third parties.
- Denial-of-service attacks, resource exhaustion, or activities that disrupt system availability.
- Social engineering, phishing, impersonation, or attempts to obtain credentials.
- Uploading malware, establishing persistence, or attempting unauthorized remote execution.
- Testing third-party infrastructure or externally hosted services without authorization from their respective owners.
- Continuing intrusive investigation after discovering an apparent vulnerability without appropriate authorization.
These restrictions define activities that RookDuel does not authorize through this policy. They do not independently determine whether particular conduct is unlawful.
Publicly available documentation, ordinary authorized use of services, and reporting information already lawfully obtained are not prohibited by this policy.
Handling Sensitive Information
Vulnerability reports must be submitted privately through the designated reporting channel.
Reporters must not use this policy as authorization to obtain, retain, distribute, or disclose confidential information or personal data.
If sensitive information is encountered unexpectedly, cease the activity that exposed it. Do not attempt to access additional information, and notify RookDuel through the designated reporting channel.
Do not include unnecessary sensitive information in the report.
Vulnerability Assessment and Response
RookDuel may review submitted reports to determine their relevance, reproducibility, security impact, and appropriate handling.
Reports may be classified, prioritized, referred to an appropriate maintainer, or closed based on their technical findings.
RookDuel does not guarantee:
- Individual acknowledgment of every submission.
- A fixed investigation or remediation timeframe.
- Acceptance of every reported issue as a security vulnerability.
- Implementation of a particular mitigation or remediation.
- Public disclosure of every reported issue.
RookDuel may request additional technical information where necessary.
Coordinated Disclosure
Reporters are requested to coordinate with RookDuel before publishing technical details that could facilitate exploitation of an unresolved vulnerability.
Disclosure timing should consider the vulnerability's severity, the availability of mitigations, affected users, and applicable legal obligations.
RookDuel may publish advisories or remediation information when appropriate.
This policy does not itself establish a confidentiality agreement, prohibit lawful independent publication, or waive rights available under applicable law.
Compensation and Recognition
RookDuel does not operate a public bug bounty program under this policy.
Submitting a vulnerability report does not entitle the reporter to compensation, rewards, employment, or other benefits.
Researcher acknowledgment may be considered for valid reports, subject to the reporter's consent and RookDuel's publication decisions.
Product-Specific Security Policies
Certain RookDuel projects maintain their own security reporting policies.
RookDuel Avikal
Security issues affecting Avikal should be reported using its designated reporting process.
Any explicit authorization or disclosure arrangements established by a product-specific policy apply to that product within their stated scope.
Policy Administration
RookDuel may update this policy as its projects, infrastructure, and security procedures evolve.
The published policy identifies RookDuel's current general reporting procedures. Material changes do not automatically alter permissions or agreements already granted separately.
Policy owner: RookDuel
Last updated: October 17, 2026
Official website: https://rookduel.tech