Software & SaaS | Modelled case study
Connect a product cryptography incident to the CRA reporting clock
Does an exploited vulnerability or severe incident meet reporting criteria, and what is known at each deadline?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the PSIRT · Legal · Product Operations functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A software provider ships frequent releases through source, build, package, deployment, dependency, and customer-assurance systems.
What is at stake
Customers and regulators need to distinguish an authorized release and evidenced control from a claim assembled after an incident.
Situation
Engineering severity, active exploitation, affected versions, signing-key exposure, and customer impact evolve faster than manual reporting documents.
Event that forces action
Confirmed exploitation, compromised release infrastructure, or a severe product incident.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
product vulnerability intake
affected crypto components
incident decision timeline
CRA notification evidence
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Engineering severity, active exploitation, affected versions, signing-key exposure, and customer impact evolve faster than manual reporting documents.
Frame the decision the owners must make
Does an exploited vulnerability or severe incident meet reporting criteria, and what is known at each deadline?
Apply QNSI to the controlled boundary
Link QNSI asset, algorithm, key, version, and audit evidence to early-warning, notification, and final-report checkpoints.
Leave the team with a concrete result
A CRA reporting packet with version scope, cryptographic impact, mitigation chronology, confidence, and unresolved facts.
Prove the result in the organisation's environment
The manufacturer and counsel decide reportability, recipients, deadlines, confidentiality, and corrective action.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A CRA reporting packet with version scope, cryptographic impact, mitigation chronology, confidence, and unresolved facts.
Independent validation boundary
The manufacturer and counsel decide reportability, recipients, deadlines, confidentiality, and corrective action.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.