EU Cyber Resilience Act Stewardship Guidelines for Red Hat Supported Open Source Projects

PDF download - EU Cyber Resilience Act Stewardship Guidelines for Red Hat Supported Open Source Projects.

Last updated: June 12, 2026

Introduction to the CRA Stewardship

The enactment of the European Union's Cyber Resilience Act (CRA) marks a definitive turning point in the governance of the global software supply chain. For decades, the open source ecosystem has operated on a foundation of voluntary collaboration, best-effort security practices, and a distinct lack of warranty or liability. The CRA fundamentally alters this landscape by introducing statutory cybersecurity requirements for products with digital elements (PDEs) placed on the European market. While the regulation primarily targets commercial manufacturers who monetize software, the interconnected nature of modern software development means that upstream open source projects—specifically those that serve as the foundation for commercial enterprise products—can no longer operate in a regulatory vacuum.

The legislation introduces a new legal actor: the Open Source Software Steward. Read more in the Red Hat blog. This role was specifically architected by EU legislators to recognize the critical infrastructure provided by open source foundations and corporate sponsors, while simultaneously shielding individual contributors and non-commercial projects from the weight of full manufacturer compliance. For the 15 projects within the scope of this guidance - Ansible, Fedora, CentOS Stream, Konflux, Quay, StackRox, OKD, crun, hermeto, IIB, Maistra, OSbuild, Pulp, RamaLama, sssd - Red Hat has formally identified itself as an Open Source Software Steward. This designation is not merely a label; it is an acknowledgment of Red Hat's systematic, sustained support for these communities and its intent to ensure their viability.

By assuming the role of Steward, Red Hat absorbs the bulk of the administrative burden associated with the CRA. However, this protection is heavily dependent on the projects adopting technical governance and security hygiene practices. The guidelines in this document are not meant as legal guidance, but as a practical handbook for maintainers, providing guidance on actionable workflows and incident response protocols that aim to improve security and ensure the continued success of these critical projects.

Open source contributors and maintainers in the EU CRA context

Individual contributors to Open Source projects are out of scope of the CRA. Maintainers of Open Source projects are generally out of scope of the CRA if they don’t monetize their projects. The formal “FOSS Guidance,” the March 2026 Draft CRA Guidance, is under development by the EU Commission to clarify some aspects, expected to be released in 2026.
CRA Software Supply Chain Relationships
*This is the current understanding of the community of experts. Not legal advice. We should expect more official details on the CRA specifics in future.*

The distinction between Manufacturer and Steward

Under the CRA, a Manufacturer is any natural or legal person who develops a product with digital elements and makes it available on the market in the course of a commercial activity. Manufacturers bear the full weight of compliance, including conformity assessments, CE marking, and financial penalties for non-compliance that can reach €15 million or 2.5% of global annual turnover, whichever is higher. Red Hat acts as the Manufacturer for its commercial products, such as Red Hat Enterprise Linux (RHEL), OpenShift Container Platform, and Ansible Automation Platform.

In contrast, the Open Source Software Steward is a legal entity that provides support for the development of open source software. The obligations of a Steward are less burdensome compared to a Manufacturer but are nonetheless statutory. They focus primarily on process, documentation, and cooperation rather than product conformance. The formal definition of a Steward in the CRA is given in Article 3 (14) - in practice it falls short of capturing the reality of Red Hat's role in the Open Source Community as an "upstream first" company. Instead of setting a target that Red Hat must try to attain, it sets a target far lower than our usual engagement but one that applies more broadly. The CRA sets the floor, but Red Hat is committed to go above and beyond, helping projects in implementing bar-raising security practices for communities we support.

Fedora Project Organization Structure

This picture illustrates relationships in the SW supply chain under the CRA as an example.

How we identified projects for stewardship

FOSS maintainers generally have no obligations under the CRA if they don’t monetize or place their projects on the EU market. Moreover, some projects do not qualify as "Products with Digital Elements" and as such are not covered by the CRA. Most importantly, not all FOSS communities and projects are not obligated by the CRA to have a Steward, and not all will have one.

Even if the project itself holds no legal CRA obligations, accepting a Steward bridges the gap between open source freedom and the strict compliance needed by downstream users and enterprise adopters. By partnering with a Steward, the project may unlock dedicated resources, security tooling, infrastructure support among other help to elevate the project's security posture. This ensures the software remains universally trusted and adoptable, while allowing maintainers to continue doing a great job of advancing a project.

Under the CRA, "Stewardship" isn't a choice. If an entity provides "sustained support" to an open source project, they are legally considered a Steward. We understand that all communities are different and recognize there might be misunderstanding or a push back at the start of the CRA journey. This is why Red Hat aims to provide "Champion Level" support to certain projects - we can prove that formal collaboration is a win for both parties without impeding efforts in other areas. This also helps us to encourage other organizations actively supporting the same open source projects to even enhance their support, specifically in security.

The provision of sustained support can include but is not limited to:

  • The hosting and managing of software development collaboration platforms.
  • Hosting source code or software.
  • Governing or managing products qualifying as free and open source software.
  • Steering the development of such products.

Additional guidance,currently in draft form as of March 2026, expands on these activities to include:

  • Non-technical support, such as managing the branding of projects, laying down governance rules, organizing community events or collecting donations.
  • Providing underlying IT infrastructure necessary to run the project, such as hosting source code repositories, providing version control systems, or generating signing keys.
  • Actively contributing engineering resources to the project, including handling vulnerability reports and security patches.

We have captured this in our identification of levels:

  • The "Light Stewardship" is the CRA minimum. Our engagement with projects with Light Stewardship will focus on policy, process and governance, to share best practices and help set the projects up for success with more formal working arrangements.
  • For "Champion Stewardship" we take the CRA as a foundation and expand on it to promote "best in class" processes. All of these additional activities are offered to the projects business critical to Red Hat as a means to collaborate to achieve greater security. However, these additional activities are not a strict requirement by the CRA.

We analyzed 800+ open source projects that potentially may fall under the CRA Steward legal definition for Red Hat.

As a result of the assessment, 15 projects were selected that Red Hat would be considered a Steward for:

  • Champion Steward: Ansible, Fedora, CentOS Stream, Konflux, Quay, Stackrox, OKD.
  • Light Steward: crun, hermeto, IIB, Maistra, OSbuild, Pulp, RamaLama, sssd.

NOTE: This identification is based on the current understanding of the Steward definition. CRA is one of the most complicated tech regulations ever and there are a lot of questions yet to be answered by the EU officials. Therefore, we anticipate this list will be re-assessed in the future as our understanding changes.

What is in scope for each project

The CRA doesn’t regulate individual hardware, software, binaries or code repositories, it instead regulates a specific category identified as being "Products with Digital Elements" also known as PDE. Hence, approaching Stewardship, it’s important to understand what’s in scope for each open source project to qualify as a “PDE.”

Each open source project may contain many repos, sub-projects, supporting tools, as well as rely on underlying infrastructure provided by different platforms or services.

Fedora Project Organization Structure
This is an example of how the Fedora Project is organized. https://docs.fedoraproject.org/en-US/project/orgchart/

The CRA defines software as 'the part of an electronic information system, which consists of computer code ' (Article 3(4)). Whether computer code is uncompiled, compiled or interpreted is not relevant to determining whether such software is within the scope of the CRA when it constitutes or forms part of a PDE.

In scope

  • Machine code, which is the set of instructions directly executed by a computer's processor, written in binary format.
  • Source code, namely, the set of instructions and statements written in a programming language, which must be compiled or interpreted to be executed by a computer.
  • Software development collaboration platforms (if managed by project and/or by Steward).
  • Source code or software hosting platform (if managed by Steward).
  • Build system, release system, CI/CD system (if managed by Steward).
  • Any other infrastructure or supporting managed toolset that is critical for project’s development or normal operations (if managed by Steward).

Out of scope

  • Unfinished code shared during a product's design and development phase, such as, for testing or review.
  • Sample or demo code provided as part of tutorials or training materials.
  • Unfinished software, such as alpha versions, beta versions or release candidates, provided that the unfinished software is made available only for the time necessary to test it and gather feedback.
  • Pure documentation
  • Abandoned repos

Additional questions to consider

  • Is this repo a PDE? See In Scope/Out of Scope above.
  • Is this repo a commercial product, for example, is it the exact same name and trademark, developed and shipped by a Manufacturer?
  • Is there a better Steward for this repo, either right now or in the future? For example, any mid-term plans to donate it?
  • Do I still need this repo up and running or can we archive it?

Although this is primarily for manufacturers, we recommend open source projects to align with these expectations and ask the above questions for each of the repos to properly scope them.

The key 6 principles of Red Hat Stewardship

Red Hat strongly believes in its role of Responsible CRA Steward (read more in Red Hat blog https://www.redhat.com/en/blog/eu-cyber-resilience-acts-impact-open-source-security). As CRA reshapes responsibilities within the open source ecosystem, now is a defining moment for Red Hat to lead by example, reinforcing our leadership as an open source advocate and protector.

We approach CRA compliance with the following core principles:

  • Listen First, Act Second. We start by learning your existing community practices, governance, processes, and tools. We do not assume we know better than the maintainers who built the project. We meet you where you are, not where a regulation says you should be.
  • Minimal Disruption Compliance efforts must be workflow-native. We aim to integrate seamlessly into your existing development pipelines and governance structures. If a requirement breaks a developer's flow, it is the wrong requirement and we are committed to partnering with the project to satisfy the intent without breakage.
  • Security First, Compliance Follows We prioritize genuine security improvements over box-checking. By focusing on overall security hygiene and engineering excellence (as per the spirit of the CRA), we ensure that compliance becomes a natural consequence of doing the right thing for the software and its users.
  • Gap-Filling Support (Only Where Needed). We are here to collaborate, not to take over. We will provide resources, tooling, or part-time personnel only to fill specific compliance gaps that the community cannot handle. If you are already doing it, let’s simply document it.
  • Pragmatic & Developer-Centric. All compliance requirements must make technical sense. We filter out bureaucratic noise and focus on actions that genuinely improve security and quality without burdening the contributor.
  • Diversity and there is no "one-size-fits-all." We recognize the diversity of each community. Once we reach an agreement, we’re happy to help with a CRA readiness roadmap individually tailored for projects. This roadmap will be largely based on your current practices, acknowledging the work you have already done.

In addition to the above, Red Hat is eager to go further. By taking the core CRA Requirements ("Light Stewardship") as the foundation, for our most critical open source projects we will continue to go above and beyond any minimum legal obligations to collaborate together and promote top-tier practices of quality and security, treating compliance as a byproduct of engineering excellence. This is our "Champion Stewardship" - above and beyond what the CRA requires for the benefit of all.

To amplify these principles, we’re leading CRA efforts in Open Source Communities (like OpenSSF and Eclipse) and EU Official Standardization bodies to make sure the entire open source ecosystem can support CRA compliance in a healthy and sustainable manner.

The strategic value of stewardship

The Cyber Resilience Act introduces a layer of regulatory friction but for the projects under Red Hat's stewardship it also creates a significant competitive advantage. In a market where compliance is becoming a prerequisite for adoption, Ansible, Fedora, CentOS, Konflux, Quay, StackRox, and OKD will distinguish themselves as "enterprise-ready" upstreams.

For the maintainer, the message is clear: You are not alone. Red Hat, as the OSS Steward, assumes the applicable CRA obligations and manages the regulatory interface. Your responsibility is to manage the security of your product – and the Steward can help by collaborating in areas such as well documented policies, secure builds, and responsive vulnerability handling. By embedding these practices now, we ensure that these open source projects remain the default choice for innovation in a regulated global economy. The transition to CRA compliance is not just about following the law; it is about maturing the processes that underpin the trust placed in open source software by the world.

The core obligations of the Steward

The regulatory core of the Steward's responsibility is encapsulated in Article 24 of the Cyber Resilience Act. This article outlines four primary duties: the establishment of a cybersecurity policy, the fostering of secure development, the effective handling of vulnerabilities, and cooperation with market surveillance authorities. While Red Hat is the legal entity responsible for these duties, their fulfillment is made possible through the collaboration of project maintainers to implement the necessary changes.

Reporting obligations under the CRA

The reporting obligations, Article 14, are one of the most challenging under the CRA. As a way to bridge a gap between a Manufacturer, for example, building commercial software like Red Hat Enterprise Linux - RHEL, and an Open Source Software Steward, like supporting a community project like Fedora, these reporting requirements are applicable to both, but with a lighter touch for stewards.

Two key "Modifiers", derived from the Steward’s operational involvement, help manage expectations for what can be reportable:

  • The development modifier: This modifier applies when the Steward employees actively contribute code to these projects, sometimes to the extent of the project’s viability. Thus the Steward may become aware of vulnerabilities in the code, and as such becomes able to report on it.
  • The hosting modifier: This modifier applies when Steward maintains or hosts the networks and systems used for the development of these projects (e.g., the Koji build system for Fedora, the CI infrastructure for OKD). Because of this contribution, the Steward may become aware of incidents in the hosting environment, and as such becomes able to report on them.

As a Manufacturer, you are expected to proactively monitor for and report actively exploited vulnerabilities and incidents as a matter of course. However, as a Steward, your reporting obligation is based purely on awareness: you are only required to report severe incidents or actively exploited vulnerabilities if you become aware of them through your development or hosting activities (i.e., the Modifiers above). You don't need to force the open source community to adopt strict corporate incident-response processes or demand they share all their security data with you, unless it’s aligned with their security strategy and they accept your help to improve it.

The bottom line: A Steward only has to report what they see to the extent of their involvement. An understanding of this helps set the stage for the collaboration between Steward and each of the open source projects.

Vulnerability management guidance

Phase 1: Identification and initial reporting - immediate action

The moment an OSS project is notified about an known exploited vulnerability (KEV) or severe incident (for example, significant availability issues or critical CVE found in the build system or CI/CD infrastructure), the OSS Developer must verify and immediately take the following steps.

  • Steward notification: Immediately notify Red Hat Product Security (secalert@redhat.com).

  • Initiate remediation: Start the standard remediation (fix) process without delay.

  • Vulnerability information: Inform project users through official communication channels. This could be a forum, blog, email, or changelog entry.

Phase 2: Remediation - focusing on the fix

The remediation phase is the project's core focus, leading to the development and deployment of the security fix.

  • Dedicate full attention: Focus solely on the technical solution and vulnerability remediation. Red Hat, as the Steward, can facilitate access to relevant project data and enablement resources as needed, subject to availability and resource capacity.

  • Continuous information gathering: During development, continuously gather and document:

    • The technical details of the vulnerability.
    • The mechanism of the exploit.
    • Any available intelligence regarding the malicious actor.
  • Status updates: Continuously inform project stakeholders and Red Hat as a Steward about the status of the fix development through the agreed communication channel.

  • Steward assistance: Engage with Red Hat Product Security for additional guidance if needed,via cra-steward@redhat.com as a default or other agreed channels.

Phase 3: Finalization and reporting - the compliance trigger

This phase is critical for the final regulatory and public reporting to make sure users are aware and can plan their own actions as soon as possible.

  • Immediate notification of fix availability: Once the corrective or mitigating measure, the fix, is completed and ready for users, the OSS Developer must publish the fix availability on the agreed communication channel.

    • This notification is the key trigger for the final compliance deadline.
  • Security advisory publishing: Agree with Red Hat Product Security on the final update and publication of the security advisory in a VEX statement.

  • Steward assistance: Engage with Red Hat Product Security for additional guidance if needed, via cra-steward@redhat.com as a default or other agreed channels.

Reporting guidelines for projects

As a Manufacturer, Red Hat is responsible for the entire vulnerability management for its commercial products, including reporting to relevant CSIRT and ENISA via the ENISA SRP in accordance with CRA requirements.

As a Steward for open source projects, Red Hat is responsible for reporting known actively exploited vulnerabilities and severe incidents (such as critical CVE found in the build system or CI/CD infrastructure) for certain projects. The responsibility for vulnerability management stays with the open source project, except where already arranged with Red Hat for it to be taken on. Therefore, we offer two distinct processes on how to ensure we can report to ENISA SRP on behalf of the open source project we are a Steward for:

Red Hat is doing full vulnerability management

  • Individual projects to agree on terms with Red Hat Product Security about the specifics on a case-by-case basis.
  • We recommend utilising or updating the security.md based on the provided SECURITY.md template.

Red Hat as a Steward is doing reporting to SRP only

  • We recommend utilising or updating the security.md based on the provided SECURITY.md template.

  • Projects are expected to follow their own established process for full vulnerability management. If you need any help to review, adjust or improve your processes, request assistance from Red Hat.

  • You must follow notification requirements from the Vulnerability Management Guidance (above) to coordinate the mandatory reporting process with the Steward - Red Hat.

  • Red Hat will coordinate the SRP notification process on behalf of the open source project.

Establishing a verifiable cybersecurity policy

Article 24(1) mandates "putting in place and document in a verifiable manner a cybersecurity policy." This requirement moves security from an implicit cultural norm to an explicit, documented standard. For technical projects, this documentation must be accessible, version-controlled, and integrated into the repository structure. It is no longer sufficient to assume that security is being taken care of; the project must demonstrate as much through the existence of policy that governs its security practices.

The cybersecurity policy serves three distinct audiences. First, it informs the user community and downstream adopters of the security processes and issues remediation expectations. Second, it provides clear guidance for researchers and external contributors on how to responsibly report potential vulnerabilities and security incidents. Third, it serves as clear evidence to verify CRA compliance as needed, for example, by the Market Surveillance Authorities (MSAs).

Critically, a cybersecurity policy must cover the handling of vulnerabilities and incidents. This encompasses the entire lifecycle of a security issue, from the moment of discovery to the release of a patch and the subsequent public disclosure. The CRA places a heavy emphasis on Coordinated Vulnerability Disclosure (CVD), a process that balances the need for transparency with the need to protect users during the remediation window. Effective handling means having a defined, predictable process. It requires a dedicated channel for receiving reports that is distinct from public bug trackers, a triage process to assess severity, and a mechanism for embargoed communication with other stakeholders, such as other distributions or downstream vendors. The policy must also promote the sharing of information concerning discovered vulnerabilities, as appropriate, within the open source community, ensuring that the broader ecosystem can protect itself.

In practice, “Verifiable Cybersecurity Policy” might be named differently and consist of several documents such as Vulnerability and Incident Handling Policy, Secure Development Practices, Security Guidelines, etc. While having these full documents in the central location (e.g, website, docs page) is the right expectation, it’s highly recommended to have a dedicated SECURITY.md or SECURITY.txt file in each repo with the minimal information. It’s essential for ease of discoverability and allows for automated checks by downstream users.

The needs for each project will be different to others. As Steward, Red Hat works with each team to adjust security policies as is needed. It is important to note that the responsibility for vulnerability management stays with the open source project, except where already arranged with Red Hat for it to be taken on.

Fostering secure development

The mandate to "foster the development of a secure product" implies an active, ongoing effort to improve the security posture of the software. This goes beyond fixing bugs; it requires the implementation of preventative measures and security-by-design principles. However, the baseline of the CRA today does not make demands on actual secure product development for open source projects.

For an "upstream first" company like Red Hat supporting open source projects and making sure the best quality and security is part of our DNA. We have been working together with OpenSSF to release CRA Readiness Guide for Maintainers and Developers that are voluntary good security practices aiming to improve the quality and robustness of the projects that are aligned with the EU Cyber Resilience Act (CRA).

For our Champion projects, Red Hat will proactively collaborate and help to adopt these recognized industry standards such as the OpenSSF Open Source Project Security (OSPS) Baseline, SBOM generation or SLSA attestations.

Cooperation with Market Surveillance Authorities

Article 24(2) establishes the duty to cooperate with Market Surveillance Authorities. These are the national bodies in each EU Member State responsible for enforcing the regulation, like BSI in Germany. If an MSA identifies a risk associated with a project - for instance, a critical vulnerability in a widely used Fedora package - they may issue a "reasoned request" to the Steward for information or action.

While the primary interface for these requests is Red Hat’s legal and product security teams, maintainers play a crucial role in providing the technical context required to respond. This might involve explaining architectural decisions, providing build logs, or detailing the timeline of a specific patch. The CRA requires that this documentation be provided in a language easily understood by the authority, emphasizing the need for clear, professional technical documentation within the project.

The timeline

Red Hat aims to implement and test the mandatory Light Stewardship requirements for all 15 projects - Ansible, Fedora, CentOS Stream, Konflux, Quay, StackRox, OKD, crun, hermeto, IIB, Maistra, OSbuild, Pulp, RamaLama, sssd - by the end of CY2026. This might be adjusted as the new implementation guidance is released by the EU Commission and other authorities. To achieve that, we are actively reviewing the current CRA readiness together with open source projects and helping to define the individual roadmaps.

One critical milestone comes in September 2026 when the ENISA’s Single Reporting Platform (SRP) will be available, and the Steward's responsibility begins for certain projects to report on actively exploited vulnerabilities and severe incidents it becomes aware of. As Steward, Red Hat will have a process in place to submit information for reporting, where required by the CRA. Cooperation by open source project maintainers is crucial to achieve this.

Implementation guide for open source projects

It’s expected that open source projects implement appropriate security practices (most of them do it already!) to match the CRA expectations. Recognizing the diverse nature of different communities, the OSS Steward's role is not to interrupt or dictate, instead to act as a trusted advisor and provide help if and where needed.

There is no official list of requirements for open source projects and their Stewards yet, besides those codified in the CRA itself. We’re actively contributing to the CRA efforts in Open Source Communities, like OpenSSF and Eclipse, and EU Official Standardization bodies to make sure the open source ecosystem can support CRA compliance in a healthy and sustainable manner aligned with the project’s governance.

Based on industry alignment, working with the groups above and on what we know today, the Red Hat CRA Working Group put together this Stewardship Implementation Guide for Open Source Projects. This work was started internally but then resulted in the joint collaboration with OpenSSF - CRA Readiness Guide for Maintainers and Developers.

Items for Light Stewardship, are the [MUST baseline] for all projects under Red Hat Stewardship as per the CRA legal requirements.

Item Description Notes and examples Modifier applicability (D-Developer; H-Hosting) Stewardship type (L-Light; C-Champion)
Reporting Actively Exploited Vulnerabilities and Severe Incidents to national CSIRTs and ENISA Stewards are required to report severe incidents and actively exploited vulnerabilities they became aware of. Projects are requested to collaborate with the Steward (Red Hat) to enable this reporting. The Steward (Red Hat Product Security team) will develop, communicate and help implement it for each project, depending on technology used and services provided. See “Reporting Guidelines For Projects” section in this document above. D, H L, C, MUST baseline
Cybersecurity, Vulnerability Management and Incident Response Policy A published policy must, at a minimum, address: 1) Secure development practices 2) Contact information for security questions, vulnerabilities and incidents reporting 3) Contact information of the project’s Steward (cra-steward@redhat.com) 4) The processes for vulnerability reporting, identification, remediation, patching, and coordinated disclosure (CVD). 5) The process for handling incidents for underlying infrastructure and tooling used 6) Intended support period for addressing vulnerabilities and the end-of-life process. Publish a SECURITY.md file in each repo, containing minimum information (see above) for easy discoverability. A publicly and clearly accessible document. Can be published at the project’s website, as part of documentation. See the “Vulnerability Management Guidelines” section in this document above. It’s highly recommended to have a security.md file in each repo. It’s essential for discoverability and to allow automated checks for users. SECURITY.md or SECURITY.txt must contain the minimum information, but can link to the detailed policy in a central location. A minimal recommended template of SECURITY.md could be found here. Other good examples: Example 1, Example 2, Example 3, Example 4, Example 5, Example 6. D L, C, MUST baseline
SBOMs Generate and store SBOMs as easily discoverable artefacts for each release or tag. If building binaries, build-time SBOMs are recommended. Start with the tools available on your platform (e.g, enable Dependabot on GitHub). Request consultation/help as needed from Red Hat. Consider using trusted software factories such as open source Konflux to enable native SBOMs generation. D C
Security Self-Assesment This document reflects how the project designs its software securely, describes security features, compliance (if applicable). It might be part of the Cybersecurity Policy. But the best practice is to document it as a separate .md file. A self-assessment template can be found here. D C
Contributing Guidance Contributing guidance (or how to join) should include explicit links to secure development practices CONTRIBUTING.md file is commonly used for this purpose, but it could be on the website or documentation page. Examples: Example 1, Example 2. D C
Release Documentation If you do releases or tags, ensure corresponding documentation describing new functionality or user guides. It should include Security fixes, if any. This documentation could be CHANGELOG.md, release notes, documentation pages, version history. Examples: Example 1, Example 2, Example 3. D C
Defect Reporting Guide Document process for reporting issues/bugs/defects. This should be clearly distinguished from security reporting. Can be in the same file as the contributing guide or included to the release process description. Examples: Example 1 (part of CONTRIBUTING.md), Example 2 (part of ISSUES.md). D C
MFA Enforcement If your project platform supports it, enable Multi-Factor Authentication (MFA) for all contributors. This is a MUST for high-privileged roles such as admins. Enabling MFA reduces the risk of unauthorized changes. Examples: How to enable MFA in GitHub, Two-factor authentication in GitLab. D, H C
Branch Protection If your project platform supports it, enable branch protection in org or repo settings. Branch protection mechanisms help demonstrate that changes to the codebase are reviewed and controlled. Examples: Branch Protection in GitHub, Branch Protection in GitLab D, H C
License File Repository should contain a clear LICENSE or COPYING file. Projects originating from Red Hat should follow the guidelines in Licensing information in open source projects. If a project originated from Red Hat, follow internal License Selection Guidelines. Otherwise - pick up one of the commonly used open source licences. D C
OSPS Achieve Open Source Project Security Baseline (OSPS) Level 1, at minimum. Achieving (at least) OSPS Level 1 demonstrates implementation of basic security and governance practices that are reviewed by downstream users. More details at baseline.openssf.org. D, H C
SLSA Achieve (Supply-chain Levels for Software Artifacts) SLSA Level 1 for Builds, at minimum. More details at slsa.dev. Request consultation/help as needed from Red Hat. Consider using trusted software factories such as open source Konflux to enable native SLSA provenance generation. D C
OpenSSF Best Practices Badge Obtain OpenSSF Best Practices Badge at Passing Level, at minimum. Go to bestpractices.coreinfrastructure.org to learn details. D, H C
Signing Commits Require signing Git commits when contributing to your project. Signing Git commits provides cryptographic proof of a commit's author and integrity. Examples: GitHub guide to sign commits, GitLab signed commits. D C

References

Red Hat CRA

Official CRA implementation guide and FAQ by the EU Commission:

Red Hat blog posts about CRA

Free CRA educational & community materials