Is this product actually in scope?
EU market exposure, manufacturer role, digital elements, connection to devices or networks, and sector-specific exclusions all matter.
Product-level CRA readiness for US manufacturers of industrial, embedded and connected products — from scope and classification to evidence, reporting and remediation planning.
Actively exploited vulnerabilities and severe product-security incidents can trigger 24-hour and 72-hour reporting.
Product cybersecurity, conformity, technical documentation and vulnerability-handling requirements become fully applicable.
For a US manufacturer, the practical questions are usually technical before they are administrative.
EU market exposure, manufacturer role, digital elements, connection to devices or networks, and sector-specific exclusions all matter.
Core functionality matters. A gateway that merely sends its own data is not the same as a product whose core function is routing, VPN or network management.
Risk assessment, SBOM, vulnerability handling, update capability, support period and traceability must form a coherent product evidence base.
About 10–12 short questions. No signup, no source code, no confidential architecture details. The assistant adapts to the product and returns a preliminary readiness snapshot.
Review a fictional assessment excerpt to see the structure, reasoning and level of detail you can expect, plus the field brief used for technical outreach.
Three-page fictional excerpt: readiness snapshot, classification reasoning, gap-matrix excerpt and 90-day remediation plan.
Open sample deliverable →A nine-page field brief for US industrial manufacturers covering Article 14, the 2027 evidence stack, classification, support period and a 90-day readiness sequence.
Download the field brief →Turn the QuickCheck signals into documented scope and classification reasoning, an Annex I evidence-gap matrix, Article 14 readiness review, support-period assessment and a prioritized 90-day remediation plan.
ConformVector is led by Ronald Reisener, Diplom-Informatiker (FH), with more than twenty years of work across embedded systems, technical integration, requirements-based engineering, medical technology and avionics.
From biomedical measurement and embedded development to the A400M Loadmaster Workstation / Loadmaster Control System environment and later independent systems work, the common thread is evidence: requirements, interfaces, failure modes, traceability and technically defensible decisions.
CRA readiness is not primarily a paperwork problem. It is a product-engineering evidence problem.
Add product-level CRA engineering to your existing testing, product-safety or advisory services. Start by discussing one anonymized client situation.
Free preliminary signal. Product-level questions, no signup.
Fixed-scope review of one product family and its evidence base.
Engineering and documentation work to close selected gaps. Typical implementation scopes are roughly $15k–$40k+ depending on product complexity and agreed work.
Yes. A product can be made available on the EU market through distributors, importers, OEM routes or other channels. The actual product and economic-operator roles matter more than who owns the customer relationship.
No. An SBOM is one element of the vulnerability-handling and technical evidence foundation. Risk assessment, vulnerability processes, update/remediation capability, support period and traceability still need to line up.
No. The CRA classification analysis is based on the core functionality of the product as a whole. Integrated functionality does not automatically elevate the entire product; the product-level role must be assessed.
No. The QuickCheck explicitly asks users not to submit source code, credentials, unpublished vulnerabilities or confidential architecture details.
No. ConformVector provides technical product-compliance engineering and readiness assessment. The QuickCheck is preliminary engineering triage, not a legal opinion, certification or conformity decision.
If the QuickCheck surfaces something material, request a 20-minute fit call. Most assessment work is asynchronous and document-based; calls are scheduled as needed across US time zones.