Red Hat takes security very seriously, and we aim to take immediate action to address serious security-related problems that involve our products or services.
To report an issue in any Red Hat branded website or online service please contact Red Hat Information Security at firstname.lastname@example.org.
When to Contact Red Hat Product Security
You should contact Red Hat Product Security if:
- You think there might be a security vulnerability in a Red Hat product or service.
- You want to provide feedback about our standards of service and performance. If you feel your security concern is not dealt with in a satisfactory manner, please contact the customer service manager at email@example.com.
In all other cases, you should contact Red Hat Global Support Services.
You should contact Red Hat Global Support Services if:
- You are unsure about how a known vulnerability affects a Red Hat product or service.
- You wish to report an issue in a language other than English.
- You require technical assistance for a security function (for example, "How do I configure my firewall?").
- You need help upgrading packages due to security alerts. (Refer to "How do I apply package updates from the Red Hat Network?" for information on upgrading packages.)
- Your issue is not security related.
In any of these cases, please contact Red Hat Global Support Services instead.
Who Reads Email Sent to firstname.lastname@example.org?
Only members of Red Hat Product Security, a restricted and carefully chosen group of Red Hat employees, will have access to material sent to the email@example.com address. No outside users can subscribe to this list.
What to Send to firstname.lastname@example.org
Please provide as much information about your system and the issue as possible when contacting the list.
How to Contact Us Securely
Red Hat Product Security uses an OpenPGP key to secure our email communications. Mail sent to email@example.com can be encrypted with this public key. We expect to change the key we use from time to time. Should we change the key, the previous keys will be revoked and the rhsa-announce mailing list will be notified of the change.
DCE3823597F5EAC4: Red Hat, Inc. (Product Security)
This key is used for communicating securely with Red Hat Product Security and for signing the security advisories posted to mailing lists.
Download: Red Hat
Fingerprint: 77E7 9ABE 9367 3533 ED09 EBE2 DCE3 8235 97F5 EAC4
Please do not send messages encrypted with this public key to any address other than firstname.lastname@example.org and email@example.com. We are unable to accept any non–security-related email which is encrypted with this public key.
How We Respond
Email sent to firstname.lastname@example.org is read and acknowledged with a non-automated response within three working days. For issues that are complicated and require significant attention, we will open an investigation and will provide you with a mechanism to check the status of our progress at any time.
Any information you share with us about security issues that are not public knowledge is kept confidential within Red Hat. It is not passed on to any third-party without your permission.
Common Criteria Timely Updates
For security issues under embargo, Red Hat does not disclose, discuss, or confirm security issues until an investigation is conducted and the vulnerability is made public. Once an embargoed issue has been made public, Red Hat publishes documentation regarding the flaw including technical details on the issue, a Common Vulnerabilities and Exposures (CVE) identifier, a Common Vulnerabilities Security Score (CVSS), a Red Hat Severity Rating, and the Red Hat products impacted by the vulnerability. Red Hat distributes information about security issues in its products through the Red Hat CVE database and security advisories to active subscription holders. Advisories are provided through the rhsa-announce mailing list.
Resources include the following:
Coordinated Vulnerability Disclosure
Red Hat engages with partners, vendors, researchers, and community coordinators to disclose newly discovered vulnerabilities in hardware, software, and services. Multi-party coordination is a complex process and understanding parties vulnerability disclosure policies, vulnerability handling policies, and contractual agreements opens the way to trusted communication and collaboration. Increasing transparency between parties ensures vendors can understand and manage the risk imposed by the vulnerability, and facilitate engagements with other parties. The aim for coordinated vulnerability disclosure is to provide timely and consistent guidance to parties and customers to help them protect themselves.
For more information on CVD, please review the information provided in the following links: