Post-market Surveillance (PMS) is the systematic process by which a manufacturer actively monitors the performance and safety of their products after they have been placed on the EU market. PMS is a legal obligation under virtually all CE marking directives, not an optional quality improvement activity. The EU Cyber Resilience Act (CRA) has raised the bar significantly — transforming PMS from a passive complaint-collection function into an active, continuous cybersecurity monitoring programme.
Legal Basis
Post-market surveillance obligations arise from:
- The General Product Safety Regulation (GPSR, EU 2023/988) — applies to all consumer products; manufacturers must collect and analyse field information, investigate incidents, and take corrective actions
- Sector-specific legislation — the LVD, the RED and the Machinery Regulation (EU) 2023/1230 require manufacturers, where the risks call for it, to sample-test marketed products, investigate complaints and keep a register of them; the EMC Directive has no such clause, but every act obliges the manufacturer to act on a product it has reason to believe is non-compliant
- Medical Device Regulation (EU 2017/745) — the most prescriptive PMS regime; requires a formal PMS plan, PMS reports (PSUR for Class IIa+), field signal analysis, and periodic safety update reports
- EU Cyber Resilience Act (EU 2024/2847) — requires vulnerability handling throughout the support period (at least 5 years, unless the product is expected to be in use for less), and staged reporting of actively exploited vulnerabilities and severe incidents — 24-hour early warning, 72-hour notification and a final report — to the coordinator CSIRT and ENISA
CRA Post-market Obligations in Detail
The CRA’s post-market requirements are the most operationally demanding in EU hardware law:
| Obligation | Timeline | Who must act |
|---|---|---|
| Early warning — actively exploited vulnerability or severe incident | Within 24 hours of becoming aware | Manufacturer → coordinator CSIRT and ENISA (via the single reporting platform) |
| Vulnerability / incident notification | Within 72 hours of becoming aware | Manufacturer → coordinator CSIRT and ENISA |
| Final report | Vulnerability: within 14 days after a corrective or mitigating measure is available; severe incident: within one month of the notification | Manufacturer → coordinator CSIRT and ENISA |
| SBOM maintenance | Kept current in the technical documentation; at least top-level dependencies | Manufacturer |
| Vulnerability handling policy | Must be published and maintained | Manufacturer |
| Security updates | Must be provided free of charge for the support period | Manufacturer → Users |
| End of the support period | End date stated at purchase; where technically feasible, users are notified when the support period has ended | Manufacturer → Users |
PMS Infrastructure for Hardware Products
Effective post-market surveillance for connected hardware requires:
1. Software Bill of Materials (SBOM) Monitoring The SBOM must be cross-referenced continuously against public vulnerability databases (CVE/NVD, OSV.dev, GitHub Advisory Database, vendor security advisories). When a CVE affects a component in the SBOM, the impact on the specific product configuration must be assessed.
2. Vulnerability Assessment and Triage Not every CVE in a dependency is exploitable in a specific product configuration. A proprietary library compiled with specific flags, running in a sandboxed environment, may not be affected by a vulnerability described in the CVE. Triage requires product-specific expertise — generic CVE scanners produce false positives that lack this context.
3. OTA Update Infrastructure Security patches must reach deployed devices reliably. For connected devices this usually means an authenticated OTA infrastructure (SUIT manifest-based firmware updates, or equivalent), a staging/rollback mechanism, and telemetry confirming update uptake across the installed base.
4. Incident Response Process A documented process for receiving, triaging, and responding to externally reported vulnerabilities (coordinated vulnerability disclosure) must exist and be publicly referenced in the product documentation.
5. CRA Reporting Process The 24-hour reporting requirement is operationally demanding. In practice it takes automated alerting from SBOM monitoring tools feeding into a defined escalation path — a manual daily review will rarely meet the deadline.
PMS vs. Quality Management
Post-market surveillance is distinct from, but feeds into, quality management:
| PMS | Quality Management (QMS) | |
|---|---|---|
| Scope | Field performance of specific products | Processes and systems producing those products |
| Regulatory basis | Product directives | ISO 9001, ISO 13485 (medical devices), IEC 62443-4-1 (secure development for industrial products) |
| Trigger | Market data, field incidents, vulnerability disclosures | Nonconformances, audits, management review |
| Output | Corrective actions, CRA notifications, safety alerts | CAPA, process improvements, supplier evaluations |