Skip to content
CORVASEC — Knowledge Defends
TRUST & LEGAL

Responsible Disclosure

Report suspected security vulnerabilities affecting CORVASEC privately, safely and with enough detail for the issue to be investigated and reproduced.

Before you report

  • Confirm that the issue affects a CORVASEC-owned website, application, API, account workflow or other service that is clearly operated by CORVASEC.
  • Use the private Security contact channel below. Do not post exploitable details, credentials, personal data or proof-of-concept material in the public forum or another public area.
  • If the issue belongs to a third-party product, service or provider, report it to that organization through its own vulnerability disclosure process.

Research expectations

  • Use the minimum testing necessary to demonstrate the issue and stop if you encounter another person’s private information, credentials or sensitive records.
  • Do not intentionally disrupt availability, degrade service, send high-volume automated traffic, perform denial-of-service testing or damage or alter data.
  • Do not use social engineering, phishing, impersonation, physical intrusion or attempts to obtain credentials from CORVASEC users or staff.
  • Do not establish persistence, pivot into unrelated systems or expand testing beyond the specific CORVASEC service necessary to validate the finding.
  • This page does not grant permission to test third-party infrastructure or any system that is not clearly operated by CORVASEC.

What to include

  • The affected URL, endpoint, feature or component and the date and time you observed the issue.
  • A concise description of the vulnerability, the expected behavior and the security impact you believe it creates.
  • Clear reproduction steps using the smallest practical proof necessary to validate the issue.
  • Relevant request/response details, screenshots or logs with secrets and unrelated personal information removed.
  • Your preferred contact method and any coordination request for future disclosure.

How reports are handled

Security reports are reviewed based on reproducibility, impact and the affected CORVASEC component. The team may request additional information, coordinate remediation or determine that a report does not affect a CORVASEC-controlled service. Response and remediation timing can vary with severity, complexity and available evidence.

Coordinated disclosure

Please allow CORVASEC a reasonable opportunity to investigate and address a validated issue before publishing technical details that could increase risk to users. If public disclosure is appropriate, coordinate timing through the private Security channel. Unless CORVASEC separately announces a reward or bounty program, submitting a report does not create a promise of payment or compensation.

Sensitive data and credentials

If testing unexpectedly exposes credentials, authentication tokens, private messages, personal information or other sensitive data, stop testing, do not retain or redistribute the material, and report only the minimum information needed to identify the exposure.

CORVASEC CONTACT

Get in touch

Continue to the CORVASEC Contact Us page with Security already selected.

Contact topic: Security
Compose email