The EU CRA reporting obligation will come into effect in September 2026: What should buyers confirm with suppliers before purchasing connected devices?
Starting September 11, 2026, serious cyber incidents and exploited vulnerabilities must be reported on time; buyers should now include updates, contact persons, and evidence in their RFQs.

Compliance with connected devices is no longer limited to "security at the factory." Buyers also need to confirm: who monitors vulnerabilities after the product is launched, who reports them within 24 hours, who is responsible for fixing them, and how long security updates will last.
The EU's Cyber Resilience Act (CRA) covers "products with digital elements," common examples including connected cameras, industrial gateways, smart appliances, routers, controllers, and machinery with software. The European Commission has confirmed that from September 11, 2026, manufacturers must report vulnerabilities that have been actively exploited and security incidents that have caused serious impact.
Why will reporting obligations change the procurement process?
Short timeframes
Manufacturers typically need to submit an alert within 24 hours and a full notification within 72 hours after discovering a problem. For buyers, the real risk is that suppliers lack a continuous monitoring mechanism, and by the time customers discover the problem, the legal timeline has already begun.
"Being able to make hardware" does not equal "being able to maintain software"
Many equipment suppliers are skilled at manufacturing but outsource firmware development. Buyers should confirm who has control over the source code, signing keys, upgrade servers, and vulnerability handling responsibilities to avoid situations where no one can fix the issues after product delivery.
CRA Procurement Five-Point Checklist
| Checklist | What should the buyer confirm? | Acceptable evidence |
| --- | --- | --- |
| Security Contact | Who responds within 24 hours of an incident? | Dedicated email address, on-call and escalation process |
| Vulnerability Handling | How to receive, assess, and close vulnerabilities? | Vulnerability disclosure policy, ticket example |
| Update Mechanism | Are updates signed and rollback possible? | Update process, test records |
| Support Period | Until what date are security updates provided? | Product support statement, contract terms |
| Software Inventory | Which third-party components does the product use? | SBOM or equivalent component list |
How should RFQs and contracts be written?
RFQ Phase
-
Specify whether the product is connected to the internet and remotely managed;
-
Require a list of major software components and cloud dependencies;
-
Inquire about security update methods and expected support periods;
-
Require a description of the internal upgrade path for critical incidents.
Contract Phase
The contract should clearly specify notification deadlines, fix priorities, patch delivery methods, post-discontinuation support periods, and whether advance notice is required when the supplier replaces critical software components. Do not simply state "the product should comply with CRA," as this statement does not provide concrete work.
Acceptance Phase
In addition to functional testing, verify default passwords, access controls, update signatures, logs, factory reset, and offline upgrades. Issues discovered during testing must be documented and closed; do not simply state "resolved" in emails.
Three Issues Overseas Buyers Often Overlook
-
The product is manufactured in a Chinese factory, but the brand owner in the EU market may be the legal manufacturer.
-
Cloud service outages may render the device unusable; contracts must address service continuity.
-
A vulnerability may originate from a third-party open-source component; the supplier still needs the ability to identify and respond to it.
Applicable Boundaries
Different products may be subject to CRA, wireless equipment, machinery, medical devices, or other industry regulations simultaneously. This document provides a procurement management framework and does not replace product classification, conformity assessment, or EU legal advice.
FAQ
Does the CRA only regulate software companies?
No. Hardware manufacturers, brand owners, and importers may all be affected as long as the physical product contains digital functionality and meets applicable conditions.
Does the Buyer Always Need Complete Source Code?
Not necessarily. Most procurements can begin by requesting an SBOM, updated commitments, vulnerability handling procedures, and necessary hosting arrangements. Whether source code is needed depends on risk and business continuity requirements.
What Should Be Changed First?
First, add four fields to the RFQ: "Security Update Years," "Vulnerability Contact Person," "Incident Notification Deadline," and "Component List."
The procurement goal for networked devices should not only be on-time delivery, but should include sustainable remediation throughout the entire support cycle.
A truly procureable "security product" is one where the supplier can still be found after an issue occurs, can report it promptly, and can deliver patches.