# Fedora Security SIG drafts new Incident Response Policy for improved disclosures

> **Key takeaway:** Fedora is establishing a formal framework for handling security incidents and embargoed information to improve communication and regulatory compliance.

**Published:** 2026-11-20T14:47:51+00:00 
**Source:** Phoronix Benchmarks &amp; Drivers 
**Category:** kernel-os 
**Canonical URL:** https://fosswire.org/news/fedora-security-sig-drafts-new-incident-response-policy-for-.html 

## Summary
The Fedora Security Special Interest Group (SIG) has released a draft for a new Incident Response Policy. This initiative aims to formalize how the Fedora project identifies, declares, and manages security incidents. The move follows communication challenges observed during the XZ Utils security incident.

Because Fedora relies heavily on volunteer contributors, the policy is designed as a best-effort framework rather than a rigid corporate mandate. The draft also seeks to align the project's security practices with the requirements of the EU Cyber Resilience Act.

## Framework and regulatory alignment
- **Incident Definition:** The policy establishes specific criteria for what qualifies as a security incident within the Fedora ecosystem.
- **Communication Protocols:** It outlines formal procedures for declaring incidents and managing the flow of information during a crisis.
- **Embargo Management:** The draft includes specific guidelines for handling embargoed security information to prevent premature disclosure.
- **Regulatory Compliance:** The framework is being developed to meet the standards set by the EU Cyber Resilience Act.

## Why it matters
This policy provides much-needed structure for downstream distributions and users who rely on Fedora's security posture. By formalizing disclosure workflows, Fedora aims to prevent the communication breakdowns seen in previous high-profile supply chain attacks.