Aegis SafeForge helps teams assess CRA applicability, classify products, map obligations to existing engineering evidence, and monitor gaps without treating compliance as a one-time checklist.
CRA vulnerability and incident reporting obligations begin on 11 September 2026. Full product obligations apply from 11 December 2027.
The cockpit is designed to connect product intake, classification, obligations, evidence expectations, and reviewer state in one traceable workflow.
Compliance state should change when your product, SBOM, vulnerability posture, or evidence changes. Aegis SafeForge is being shaped around that living loop.
Aegis SafeForge keeps compliance work grounded in human review, source evidence, and traceability rather than unsupported automation claims.
Cockpit loop
01
Connect sources
02
Classify product
03
Map obligations
04
Score evidence coverage
05
Track gaps
06
Escalate remediation
CRA self-check
This deterministic self-check uses simple scope rules. The full Aegis SafeForge CRA Cockpit analysis then connects product data, SBOM, evidence, and obligations.
CRA timetable
Your role
01
Is the product software, hardware with digital elements, or a connected product?
02
Is it placed on the EU market, supplied to EU customers, or planned for EU release?
03
Is it offered commercially or as part of a business activity?
04
Is it clearly covered by a specific excluded sector regime or purely non-commercial open source?
05
Does it provide security, identity, network, update, access-control, or vulnerability-management functions?
06
Does the product depend on remote processing, cloud services, APIs, or continuous updates?
CRA scorecard
91
Likely CRA-relevant
Check Default or Important Class I
Self-check only, not legal advice and not a conformity guarantee.
Dedicated CRA workflow
The Aegis SafeForge CRA Cockpit performs the detailed analysis with product context, SBOM, evidence, obligations, reporting cases, and ASF handoff.
No. Aegis SafeForge supports assessment, evidence mapping, traceability, and review workflows. Final conformity decisions remain with qualified teams, legal advisors, assessors, and notified bodies where required.
The cockpit direction is to keep classification and obligation results tied to versioned content packages and reassessment history, so teams can see when a change affects the gap picture.
A checklist records answers. Aegis SafeForge aims to connect answers to product context, evidence, SBOM state, reviewer decisions, and ongoing monitoring.
Aegis SafeForge