Annex III, Class I (7)
Security information and event management (SIEM) systems
SIEM are important product, class i under Regulation (EU) 2024/2847 when the listed function is the product's core functionality. A SIEM ingests hostile data from every system and is trusted by the security team; a compromised SIEM blinds detection and can be used to pivot.
Updated 2026-09-12 · Operational guidance, not legal advice.
- Classification
- Important product — Class I
- Conformity route
- Self-assessment only with fully applied standards
- Reference
- Annex III, Class I (7) · Art. 32(2)
What the annex says
Security information and event management (SIEM) systems.
Paraphrase of Annex III, Class I (7); the Official Journal text governs.
Typical products in this category
- Log collection, correlation and alerting platforms
- Security data lakes marketed as SIEM
- SOAR platforms with a SIEM core
Where the boundary runs
A logging library or a generic observability platform without a security-analytics purpose is a default product; the category targets products marketed and used for security event management.
The test is core functionality (Article 7). Record the reasoning and the approver: the category determines the conformity assessment route and market surveillance authorities can challenge it.
Conformity assessment
Self-assessment only with fully applied standards. Module A is permitted only where harmonised standards, common specifications or a European cybersecurity certification scheme are applied in full; otherwise EU-type examination (Module B) followed by conformity to type (Module C), or full quality assurance (Module H). (Art. 32(2))
What to prepare operationally
- Track parsers and ingestion connectors in the SBOM; log parsing is a frequent injection surface.
- Document data segregation for multi-tenant deployments.
- Plan the coordinated disclosure policy with the MSSP channel in mind — customers often run your product on your behalf.
- Maintain an SBOM per released version, match it continuously against vulnerability intelligence, and keep the Article 14 runbook rehearsed — these apply to every product with digital elements, listed or not.
Frequently asked
- Is every siem product an important product — class i?
- Only where the listed function is the product's core functionality (Article 7). A logging library or a generic observability platform without a security-analytics purpose is a default product; the category targets products marketed and used for security event management.
- What changes compared with a default product?
- Module A is permitted only where harmonised standards, common specifications or a European cybersecurity certification scheme are applied in full; otherwise EU-type examination (Module B) followed by conformity to type (Module C), or full quality assurance (Module H). The essential requirements of Annex I, the vulnerability-handling duties and Article 14 reporting apply to every product with digital elements regardless of category.
- From when?
- Article 14 reporting obligations have applied to all manufacturers since 11 September 2026. Conformity assessment and CE marking under the CRA apply from 11 December 2027; products placed on the market before that date are not required to be re-assessed unless substantially modified.