Skip to content

Security: zulh-civo/kubevirt

Security

SECURITY.md

Security Policy

Reporting a Vulnerability

The KubeVirt project treats security vulnerabilities seriously, so we strive to take action quickly when required.

The project requests that security issues be disclosed in a responsible manner to allow adequate time to respond. If a security issue or vulnerability has been found, please disclose the details to our dedicated email address:

[email protected] [PGP](#PGP Encryption)

Please include as much information as possible with the report. The following details assist with analysis efforts:

  • Description of the vulnerability
  • Affected component (version, commit, branch etc)
  • Affected code (file path, line numbers)
  • Exploit code

Any confidential information disclosed to the security team will be handled appropriately to prevent misuse or accidental disclosure.

PGP Encryption

Security issues can often be sensitive in nature, so information can be disclosed with PGP encryption. Our public key can be found on public keyservers and our fingerprint is as follows:

CEF1 66F8 B929 4CDE 3233 5FCF B3D9 0475 26A3 D09E

Please note that the above key will not be used for signing releases. Please refer to your vendors instructions for verifying packages, images or source code.

Security Notices

Security notices will be sent to the [email protected] mailing list and published to the Security Advisories page.

Security Team

The security team consists of key developers, vendor security contacts and project leadership.

Membership of the security team is assessed on a case-by-case basis. If you have cause to join the team, please sent an email to the email address above. Members will need to demonstrate secure information handling practices and procedures before joining.

There aren’t any published security advisories