Skip to content
Distr
Book DemoStart free trialLogin
← Back to Glossary

Support Period (CRA): The 5-Year Floor Explained

The Cyber Resilience Act support period: the minimum 5 years of vulnerability handling, the 10-year update availability rule, and the engineering consequences.

The support period under the Cyber Resilience Act is the time during which a manufacturer must handle vulnerabilities in a product with digital elements, and it must be at least 5 years under Article 13(8), unless the product is expected to be in use for a shorter time. During this period the manufacturer must identify, document, and remediate vulnerabilities without delay and provide security updates through a secure distribution mechanism.

The support period is a product-level decision with engineering consequences: every version line a customer can legitimately run within that window needs a path to receive security fixes. A related but distinct obligation is update availability: under Article 13(9), each security update issued during the support period must remain available for at least 10 years after it was issued, or for the remainder of the support period, whichever is longer. The support period must also be stated transparently so users know how long they can expect security support.

See the full duty list in the CRA guide for software vendors.

Frequently Asked Questions

Is a 5-year support period mandatory under the CRA?

Yes, as a floor. Article 13(8) requires at least 5 years, unless the product is expected to be in use for less time. Products expected to be used longer need correspondingly longer support periods.

What is the 10-year rule in the CRA?

Under Article 13(9), each security update issued during the support period must remain available for at least 10 years after issuance, or for the remainder of the support period, whichever is longer.

Turn self-hosted into a repeatable sales motion

From your first on-prem POC to dozens of enterprise customers, the Distr platform gives you the tooling to deploy, update and manage self-hosted customers, backed by a team that supports you hands-on with the deployment knowledge and implementation help.

Proof from teams shipping self-hosted software

GovCloud deployments without extra overhead

"Distr gives us a clean way to deploy and update our software in GovCloud without breaking security or adding operational overhead."

Corbin Klett

Corbin Klett

Co-Founder, Artifact

Manual operations become one-click workflows

"Our main goal is to simplify the daily operations. No more manual installations, updates, or rollbacks — everything can now be handled with a single click with Distr."

Jefferson Rodrigues

Jefferson Rodrigues

Co-Founder & CTO, Lerian

Read case study

Updates that took days now take minutes

"Distr eliminated nearly all deployment headaches. Updates that used to take days now take minutes."

Ansh Gupta

Ansh Gupta

CTO, Sophris.ai

Read case study

One place for every self-hosted customer

"Having a dedicated space for all our self-hosted customers that can manage authenticated registry access is great."

Derek Reynolds

Derek Reynolds

Product Engineer, Basedash

Read case study

From guided setup to scalable delivery

"We went from hands-on Docker setup calls to an install flow that can be running in minutes."

Daniel Kasen

Daniel Kasen

Chief Engineer for Customer Success, Ozgar AI

Read case study

Self-hosted without the engineering tax

"Weave has a fully self-hosted offering. It's a huge unlock for us, but we almost didn't build it. Distr made such a huge difference in getting us there."

Andrew Churchill

Andrew Churchill

Co-Founder & CTO, Weave

Read case study