Cyber Resilience Act: What US Vendors Need to Know

The EU Cyber Resilience Act sets security evidence, vulnerability reporting and support rules for hardware and software sold in Europe. Here is what a US vendor should document first and when each requirement applies.

By the Total 360 Security team6 min read
Product engineering team whiteboard in a North Texas office with a hand-drawn release pipeline and colored markers

The Cyber Resilience Act is an EU product law requiring evidence that hardware and software sold in the EU are secure and remain supported. A US address does not put your products outside its scope. Start with a named product-security owner and a written secure-development statement, not a promise to complete a questionnaire later.

For a vendor facing a European distributor’s document request, the real question is who owns the evidence and the reporting clock. Have qualified counsel confirm your product’s scope and legal obligations in writing.

What does the Cyber Resilience Act ask a product to prove?

Regulation (EU) 2024/2847 entered into force on December 10, 2024. Full requirements apply to products placed on the EU market from December 11, 2027. Reporting obligations for actively exploited vulnerabilities and severe incidents apply from September 11, 2026, with an early warning within 24 hours and a fuller notification within 72 hours.

The manufacturer is responsible for product security across its life, including third-party components and maintenance. Products cannot enter the EU market with known exploitable vulnerabilities. Secure-by-default configurations and security capabilities such as strong authentication also form part of the requirements.

A certificate alone does not establish that work. Your documentation must explain the security measures applied during development and maintenance, with the reasons for those choices. Treating the Act as a one-time certification project misses the continuing obligation.

Which US vendors are most likely to be affected?

Scope follows the product, not your headquarters. A Texas equipment manufacturer or software supplier can be affected when its products reach the EU market. One product line can be in scope while another is not.

Some products covered by sector-specific EU rules may fall outside the Act. Review your actual product list with counsel rather than assuming your entire industry is included or exempt.

A European buyer’s questionnaire is a reason to check scope, not proof that the law applies. Ask what requirement drives the request and what evidence the buyer will accept. Commercial requirements and legal obligations need separate answers.

Which documents should a vendor start this quarter?

Which documents should a vendor start this quarter?, Total 360 Security

Give each document an owner. Start with a secure-development statement you can defend, then build the supporting records. The statement explains your practices; the records establish that you followed them.

DocumentWhat it holdsSuggested owner
Secure-development statementSecurity practices across development and maintenance, with the reason for each measureHead of engineering, with a named security lead
Software bill of materialsA machine-readable inventory of product components, including third-party and open-source itemsEngineering lead for each product line
Technical fileCybersecurity risk assessment, implemented measures, referenced standards, vulnerability test results and user instructionsProduct lead, with security review
Vulnerability handling recordHow reports are assessed and resolved, including who makes the reporting decisionSecurity lead
Support-period statementThe update commitment and justification for a different support lifetime where applicableProduct lead and commercial owner

For manufacturers, this work crosses engineering and executive governance. Our virtual CSO program for manufacturers addresses security program leadership rather than leaving ownership with a questionnaire recipient.

The secure-development statement comes first

Describe how your team addresses security from design through maintenance. Explain why each measure exists. A tool inventory does not tell a distributor how you decide whether a release is ready.

Date the statement and name its owner. Review it against each release cycle. If a practice is planned but not operating, label it as planned and give a delivery date rather than presenting it as an existing control.

The SBOM is kept current, not produced once

The software bill of materials, or SBOM, must inventory product components in a machine-readable format. That includes third-party and open-source dependencies.

Generate and check it as part of each release. An inventory from an earlier build does not establish what your customer is running now. Assign ownership by product line and verify the inventory against the released build.

The technical file is built as the product is

Article 31 addresses technical documentation. The file should contain the cybersecurity risk assessment, implemented security measures, referenced standards, vulnerability assessment results and user instructions.

Write those records while the decisions are fresh. Keep earlier versions so you can connect a release to its assessment and test results. Reconstructing the rationale after engineers move to another product adds avoidable work.

How do vulnerability handling and updates fit the requirements?

Security updates create a continuing obligation. The default support period is at least five years for most products unless the manufacturer justifies a different lifetime. Set the commitment deliberately before it appears in a customer contract.

Reporting deadlines require a separate process from patch delivery. An early warning within 24 hours does not mean every fix must be ready within 24 hours. It means someone must recognize a reportable event and act before the deadline.

Who makes the 24-hour call

Name a decision-maker and a backup. Give them authority to escalate a suspected reportable vulnerability without waiting for an executive meeting.

Document who assesses the evidence and who submits the notification. Test that process against an incident arriving during November holiday absences in Texas. A reporting procedure that depends on one available employee has a coverage gap.

Setting the support period on purpose

Decide the support period before signing the first contract. Record the rationale for any departure from the default and have counsel review it. If you promise longer support, budget for the engineering work that follows.

Check supplier dependencies against that commitment. Your customer-facing update obligation does not disappear because a component supplier ends support.

How can a small security team support development without slowing it?

How can a small security team support development without slowing it?, Total 360 Security

Use one documented security gate per release rather than creating a separate approval process outside engineering. The gate should check the current SBOM, unresolved vulnerability decisions and supporting evidence. A named reviewer records the outcome with the release.

That gate does not replace security work during development. Reserve specialist time for risky design decisions, particularly features handling credentials or sensitive data. Define how outside vulnerability reports reach the team and who decides patch priority.

Article 33 provides support measures for microenterprises, small and medium-sized enterprises, including start-ups. Check which measures apply to your organization. For executive ownership of framework selection and compliance work, our virtual CISO services provide cybersecurity program leadership.

Where should a vendor confirm scope and conformity before committing a launch date?

The official regulation sets out conformity assessment, the EU declaration of conformity and CE marking. Certain product categories involve a notified body. Confirm your product’s route before committing to an EU launch date.

Engineering builds the evidence. Qualified counsel confirms the scope and legal obligations in writing. Do not ask a technical lead to resolve a legal classification through a buyer questionnaire.

Ask the buyer which version of the requirements its questionnaire follows and what evidence it accepts. If a requested document is missing, state that plainly. Provide a dated delivery plan and a draft that accurately describes current practices.

Total 360 Security runs security programs across 13 risk domains and reports directly to the board. To assign executive ownership and sequence the work, book a 30-minute risk discussion. For the governance responsibilities behind the evidence, see our guide to GRC cyber security in Texas.

Frequently asked questions

What is the EU Cyber Resilience Act?

The Cyber Resilience Act is Regulation (EU) 2024/2847, a binding EU law setting cybersecurity requirements for hardware and software products with digital elements sold on the EU market. It covers product security and continuing responsibilities such as vulnerability handling and documentation. It is not a one-time security assessment.

When do the Cyber Resilience Act requirements apply?

The regulation entered into force on December 10, 2024. Reporting obligations for actively exploited vulnerabilities and severe incidents apply from September 11, 2026, with a 24-hour early warning and a fuller notification within 72 hours. Full requirements apply to products placed on the EU market from December 11, 2027.

Does the Cyber Resilience Act apply to a US manufacturer?

A US manufacturer can fall within scope when its products with digital elements are placed on the EU market. Scope is assessed product by product, with some exclusions for products covered by sector-specific EU rules. Have qualified counsel confirm the classification and resulting obligations in writing.

Is a Software Bill of Materials required?

Yes. The CRA requires a machine-readable software bill of materials identifying product components, including third-party and open-source components. Keep it current with each release and check it against the actual build.

Does every product need a notified body?

No. The conformity assessment route depends on the product category, and the official regulation specifies where a notified body is involved. Confirm that route before setting your EU launch date.

Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.

Serving Texas, California, Nevada, New Mexico.