# Patch advisory

EU Cyber Resilience Act | Worked example with fictional data

Step: Assemble the technical and conformity file
Owner: Regulatory lead + engineering
When: Before placing a covered product on the market

## Gather first
- Confirmed affected versions
- Vulnerability analysis and released fix
- Customer support channels and disclosure rules

## How to prepare it
1. State which product and versions are affected and what a user could experience. Record workarounds and security impact using confirmed details.
2. Give the fixed version, update steps, prerequisites and a way to verify successful installation. State whether users need to act immediately.
3. Have engineering and product security verify technical claims. Coordinate publication with required reporting and keep the original release and revisions.

## Example

### Affected versions
Example router firmware 3.2.0 through 3.2.2

### Impact
An authenticated operator can reach a restricted diagnostic action.

### Remediation
Install approved firmware 3.2.3 and check the version in the admin console.

### Temporary measure
Restrict management access to trusted networks while the update is scheduled.

### Published and reviewed
Record approval, time and applicable case reference before publishing.

## Review
A customer can identify affected devices and confirm the fix. Claims match reproducible engineering evidence.

## Handoff
Publish through the approved support channel and link the advisory to investigation and release records.

Use the current rules and any prescribed forms for your engagement.
