
Lead analysis
CRA in October: turn 24- and 72-hour reporting into an operation
Manufacturer reporting already applies. The task now is to connect triage, owners and submission evidence without waiting for a perfect investigation.
Read analysisLatest edition
Blog · 267 analyses
Context for better decisions.
Analysis on AI, cybersecurity, regulation, governance and digital systems. With sources, practical consequences and one clear next action.
Showing
1–12 of 54
Current knowledge, organised by topic, date and practical consequence.

Lead analysis
Manufacturer reporting already applies. The task now is to connect triage, owners and submission evidence without waiting for a perfect investigation.
Read analysis
The entity maintaining a project's infrastructure and the entity supplying a market product may differ. How can that distinction be preserved without leaving a vulnerability without a recipient?
Read analysis
After receiving an advisory, can a user determine whether they are affected, choose the measure and verify the result without interpreting a sales statement?
Read analysis
What evidence qualifies a vulnerability as actively exploited in the product? The form comes after distinguishing identification, demonstration and malicious exploitation.
Read analysis
How can you show that a sold release will keep receiving a security response? CRA preparation connects expected use, components and update delivery.
Read analysis
Which product do we supply to the market, and under whose name? CRA classification starts here, not with a count of installed applications.
Read analysis
Cyber Resilience Act reporting duties began to apply before the main obligations stated for 2027.
Read analysis
The European innovation proposal creates a preparation opportunity, but it does not justify treating proposed outcomes as rules already in force.
Read analysis
The European simplification package is a planning signal, but proposals require legislative tracking.
Read analysis
The AI Omnibus entering into force changes Commission-indicated timelines, but does not remove the need for compliance governance.
Read analysis
An obligations inventory is useful only when it separates legal requirements, technical standards, and internal decisions.
Read analysis
The communicated timelines for high-risk systems change planning, but do not remove the need for documented preparation.
Read analysisHow we publish
Every analysis links the official documentation it relies on.
We translate change into decisions, owners and evidence.
We update the analysis when facts or guidance change.
We disclose generated photography and credit documentary photography.
From context to execution
We map the problem, write the scope and build the solution with acceptance criteria.