> ## Content Index
> Fetch the complete content index at: https://the-readiness-directive.ghost.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# When Information Becomes Awareness
- URL: https://the-readiness-directive.ghost.io/when-information-becomes-awareness/
- Published: 2026-10-01T06:30:05.000Z
- Updated: 2026-11-02T08:22:52.000Z
- Description: CRA Article 14 defines the reporting clock. But another interval matters first: how long does it take an organisation to recognise that an ordinary operational signal may have become a regulatory question?
- Author: William Corkhill
- Tags: Cyber Resilience Act, Product Goverance, product security, Product Integrity, Regulatory Readiness

The reporting clock is written into law. The recognition clock is not.

Most organisations watching CRA Article 14 are focused on the 24-hour reporting window. There is another interval worth examining: the time consumed before potentially relevant information is recognised as something that may require regulatory assessment. That interval can be difficult to see precisely because nothing necessarily looks broken.

A support ticket records unusual product behaviour. A field technician notices something similar elsewhere. A vulnerability researcher sends a report. Engineering investigates an anomaly. Security has an alert that has not yet become a conclusion. Every process may be functioning as designed, yet every hour in which the significance of those signals remains unrecognised is decision time the organisation does not know it is spending.

That matters beyond cybersecurity. A board may see strong incident-response metrics while knowing very little about how efficiently signals travel between Customer Service, Quality, Engineering, Product Security and the installed product base before something is formally classified.

Article 14 of the Cyber Resilience Act requires manufacturers to submit an early warning without undue delay and, in any event, within 24 hours after becoming aware of an actively exploited vulnerability in a product with digital elements or a severe incident affecting its security. Further notification follows within 72 hours.

That is the reporting clock. The harder organisational question is what happens before the organisation reaches the point where it knows that clock may be relevant.

## Detection is not recognition

Cybersecurity already has mature measures for speed: mean time to detect, dwell time, triage time and response time. Those measures are useful because they tell an organisation how quickly a technical signal is discovered and acted upon once it has entered an environment designed to recognise it.

The problem considered here sits further upstream. A SOC can have an excellent mean time to detect while a significant pattern remains dispersed across Customer Service, Field Service, Warranty, Quality, a distributor network or supplier communications. A PSIRT can triage a vulnerability rapidly once something reaches its queue without knowing that related information has been sitting elsewhere in the organisation for days.

That is not a criticism of the SOC or PSIRT. They may be performing extremely well. The different question is how long it takes a potentially significant signal to reach the organisational pathway capable of recognising its regulatory relevance.

**I use recognition latency to describe that interval.**

This is not CRA terminology and it is not a legal definition of when a manufacturer “becomes aware” under Article 14\. The existence of information somewhere inside a company does not, by itself, establish corporate awareness.

Recognition latency is an operational concept: a way of examining the time between a potentially material signal entering an organisational pathway and its significance being recognised sufficiently to trigger regulatory assessment.

**A reporting clock measures time. Recognition determines how much decision time the organisation actually has.**

## What if nothing appears to be failing?

Customer Service may be closing cases on time. Field Service may be documenting observations correctly. Quality may be recording complaints. Engineering may be investigating anomalies. Security may be meeting its detection targets. Suppliers may be using the channels established for them.

There may be no missed KPI, no red dashboard and no visibly broken procedure. The vulnerability can exist in the space between systems that are individually working exactly as intended.

Imagine three apparently unrelated customer cases entering different service queues. None looks extraordinary on its own. An engineer later observes unusual behaviour in the same product family, while a distributor forwards a customer concern using entirely different terminology.

**Where do those signals meet?**

Perhaps they do not need to. Perhaps the events are genuinely unrelated. But who is capable of recognising when they might not be?

**That is the uncomfortable part of recognition latency: an organisation may have no obvious indicator that it is occurring.**

## The CRA already expects vulnerability information to move

The CRA does not treat vulnerability handling as passive. Annex I, Part II requires manufacturers to put in place and enforce a coordinated vulnerability disclosure policy and to facilitate the sharing of information about potential vulnerabilities, including by providing a contact address for vulnerability reporting.

Those channels matter, but receiving information and recognising its significance are different organisational activities. A researcher can successfully report a vulnerability. A customer complaint can be logged correctly. A field observation can be recorded accurately. A supplier can follow the prescribed communication route.

The unresolved question is whether information can move beyond the process that originally received it when its significance changes. An inbox can work perfectly while the significance of what it contains remains invisible elsewhere.

## Two clocks, two different problems

The reporting clock is regulatory: Article 14 defines the notification periods after manufacturer awareness. The recognition clock is organisational: it represents the interval before potentially relevant information has been recognised as something requiring regulatory assessment.

**Only the first exists in legislation.**

But the second influences how much practical time remains when assessment finally begins. Early recognition creates room for technical investigation, product identification, evidence review and legal assessment. Late recognition compresses that work into a smaller decision window.

That does not mean late recognition is automatically a CRA breach. It means something more operational: the organisation may have been consuming valuable decision time without knowing it.

## Questions worth asking

The answer is not to tell every employee to escalate everything. That would replace blindness with noise. The more revealing questions are structural:

- Would three similar complaints sitting in separate service queues ever meet?
- Would a field observation with possible cybersecurity implications reach someone capable of recognising that significance?
- If a distributor and a vulnerability researcher described different symptoms of the same underlying weakness, where could those signals connect?
- Could the security organisation be monitoring exactly the right environment while the most important clue remains in a system it was never designed to see?
- If that were happening today, how would the organisation know?

Those questions are more useful than another readiness checklist because they test connectivity rather than the existence of procedures.

## The boundary of recognition latency

Once a signal has been recognised as potentially relevant, another set of questions begins: who assesses it, who decides, whether reporting is required and how the organisation responds. Those questions matter, and The Readiness Directive has explored many of them elsewhere through the Product Integrity Case Files and related work on decision-making under incomplete evidence.

Its concern is the moment before formal assessment begins: when apparently ordinary operational information becomes significant enough that a different question must finally be asked.

## The question behind the clock

A reporting deadline is straightforward to put into a procedure. Recognition is harder to engineer.

The complaint may have been logged correctly. Engineering may have documented the anomaly. The researcher may have used the right disclosure channel. Security may be performing exactly as expected. Nothing obvious may have failed, yet the organisation may still be slower than it realises at recognising that separate pieces of information have become part of the same regulatory question.

That is what recognition latency is intended to expose: not that the organisation knew and failed to act, but that organisations need to understand how efficiently they recognise when ordinary information has become something requiring a different level of attention.

**The first regulatory risk may not be missing the 24-hour deadline. It may be failing to recognise soon enough that the clock has become relevant.**

### Primary sources

Regulation (EU) 2024/2847 — Cyber Resilience Act, Article 14 and Annex I, Part II.  
European Commission — CRA reporting guidance and Article 14 implementation material.