EU Cyber Resilience Act: vendor duties for Cairn (security logging with opt-out, data minimisation): deep research reminder #876

Open
opened 2026-10-12 11:28:47 +00:00 by Cordy · 0 comments
Owner

Parked from the #864 research (2026-10-11). This is a reminder to do a deep research pass before acting. It is not legal advice; get legal review before any customer-facing statement.

What we know so far

  • The EU Cyber Resilience Act (Regulation (EU) 2024/2847) applies to "products with digital elements" placed on the EU market, including self-hosted software sold commercially. Its duties fall on us as the manufacturer, unlike the GDPR/nDSG, where the self-hosting customer is the controller.
  • Timeline: vulnerability and incident reporting from 11 Sep 2026; the main essential requirements from 11 Dec 2027.
  • Annex I(2)(l): the product must provide security-related information by "recording and monitoring relevant internal activity, including the access to or modification of data, services or functions, with an opt-out mechanism for the user".
  • Data minimisation is also an Annex I requirement.
  • Open question: Cairn currently says "administrative changes are always recorded" (#859). Does the opt-out requirement conflict with that, or is a documented justification enough?
  • Planned in #864: the audit.ip: full | truncated | off setting and the operator data-protection page. Both are candidate parts of our Annex I(2)(l) / minimisation story.

To research when this is picked up

  1. Does Cairn fall under the CRA? Look at the commercial-activity test, the treatment of open-source components, and whether a Swiss manufacturer selling into the EU needs an EU authorised representative.
  2. Product class: default vs "important"/"critical" (Annex III/IV). Which conformity assessment route applies?
  3. The full Annex I list (secure by default, update mechanism, vulnerability handling, SBOM, support period) mapped against what Cairn has today.
  4. Annex I(2)(l) in detail: what counts as "relevant internal activity", how the opt-out must work, and how competitors interpret it (Nextcloud, GitLab, Mattermost statements).
  5. Reporting duties from Sep 2026: ENISA single reporting platform, 24h/72h deadlines, and whether they already apply to us.
  6. The harmonised standards status (CEN/CENELEC, ETSI drafts) and what they say about logging.
  7. Interplay with Swiss law: the DSV Art. 4 logging duty and ArGV 3 Art. 26.

Output: a requirements matrix (requirement → Cairn today → gap → issue), posted here, then split into actionable issues.

Parked from the #864 research (2026-10-11). This is a **reminder to do a deep research pass before acting**. It is not legal advice; get legal review before any customer-facing statement. ## What we know so far - The EU Cyber Resilience Act (Regulation (EU) 2024/2847) applies to "products with digital elements" placed on the EU market, including self-hosted software sold commercially. Its duties fall on us as the **manufacturer**, unlike the GDPR/nDSG, where the self-hosting customer is the controller. - **Timeline:** vulnerability and incident reporting from **11 Sep 2026**; the main essential requirements from **11 Dec 2027**. - **Annex I(2)(l):** the product must provide security-related information by "recording and monitoring relevant internal activity, including the access to or modification of data, services or functions, with an opt-out mechanism for the user". - **Data minimisation** is also an Annex I requirement. - **Open question:** Cairn currently says "administrative changes are always recorded" (#859). Does the opt-out requirement conflict with that, or is a documented justification enough? - **Planned in #864:** the `audit.ip: full | truncated | off` setting and the operator data-protection page. Both are candidate parts of our Annex I(2)(l) / minimisation story. ## To research when this is picked up 1. Does Cairn fall under the CRA? Look at the commercial-activity test, the treatment of open-source components, and whether a Swiss manufacturer selling into the EU needs an EU authorised representative. 2. Product class: default vs "important"/"critical" (Annex III/IV). Which conformity assessment route applies? 3. The full Annex I list (secure by default, update mechanism, vulnerability handling, SBOM, support period) mapped against what Cairn has today. 4. Annex I(2)(l) in detail: what counts as "relevant internal activity", how the opt-out must work, and how competitors interpret it (Nextcloud, GitLab, Mattermost statements). 5. Reporting duties from Sep 2026: ENISA single reporting platform, 24h/72h deadlines, and whether they already apply to us. 6. The harmonised standards status (CEN/CENELEC, ETSI drafts) and what they say about logging. 7. Interplay with Swiss law: the DSV Art. 4 logging duty and ArGV 3 Art. 26. Output: a requirements matrix (requirement → Cairn today → gap → issue), posted here, then split into actionable issues.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#876
No description provided.