research and check for ISO norms #847

Closed
opened 2026-10-06 16:17:25 +00:00 by Cordy · 3 comments
Owner

specifically Iso 27001, 9001 and/or 9002
what does this entail, what does this provide, do we have this potentially already implemented? what would be missing for this?
deep research, competitors, similar cases, our code, through the UI as well.

27001 was implemented via issue 842.
what also would be interesting is to know, are there any more ISO norms which are applicable to us, as well as interesting for public sector customers.

which are implemented at competitors? and also we should document this as it is something the customers from the public sector will be interested about.

specifically Iso 27001, 9001 and/or 9002 what does this entail, what does this provide, do we have this potentially already implemented? what would be missing for this? deep research, competitors, similar cases, our code, through the UI as well. 27001 was implemented via issue 842. what also would be interesting is to know, are there any more ISO norms which are applicable to us, as well as interesting for public sector customers. which are implemented at competitors? and also we should document this as it is something the customers from the public sector will be interested about.
Author
Owner

Research (2026-10-29)

Framing: ISO 9001 and ISO/IEC 27001 certify an organisation's management system, never software. Cairn can support a customer's ISMS (Annex A mapping) and Swisscairn could get its own ISMS certified. #842 supported A.8.15 (logging); it did not "implement 27001". ISO 9002 was withdrawn (merged into ISO 9001:2000); ISO 9001:2026 was published Sept 2026. Nextcloud says the same: "SOC2 or BSI C5 cover operations rather than software in isolation".

Already done: docs/handbook/security-standards.md maps features to nDSG/DSV, BK AR012, IKT-Minimalstandard, BSI IT-Grundschutz, ISO 27001/27002, NIS2, NIST, CIS, CRA, with a "supports, never certified" wording policy. Gap: the ISO table covers only access/logging/TLS; missing rows for A.5.14, A.5.28, A.5.30, A.5.33, A.5.34/8.11, A.8.9, A.8.10 (crypto-erasure), A.8.12, A.8.20/22, A.8.24 (at-rest encryption, custody, PQ). Real gaps buyers notice: classification labels (A.5.12/13), malware (A.8.7, #1022), MFA for local accounts (delegated), alerting by mail (#896), SIEM push.

Other norms worth knowing: ISO/IEC 29147/30111 (vulnerability disclosure/handling → CRA), NIST SSDF 1.1 (cheap self-attestation), ISO 22301 (continuity; vendor continuity is a tender question), 27017/27018/27701 (only if hosting), ISO 15489 (records; don't claim GEVER), ISO/IEC 40500 (= WCAG, see #638), CSPN/BSZ (EN 17640) as the realistic product certification. Swiss/EU: privatim resolution Nov 2025 (warns against international cloud for sensitive data → self-hosted, operator-held keys is Cairn's strongest argument), ISG/ISV (customer's ISDS), BSI C5:2026 (providers), CRA (vulnerability reporting from 11 Sep 2026, full duties 11 Dec 2027).
Competitors: Nextcloud: ANSSI CSPN for Files 31, certified operating partners, reference DPIA, no company ISO claim; OpenCloud GmbH: ISO 27001 badge, Blauer Engel; Proton, Tresorit, Infomaniak (SaaS): ISO 27001 (Infomaniak also 9001/14001/50001).
Vendor gaps: no SECURITY.md / security.txt / disclosure policy; SBOM generated by ko but undocumented; no image signing; govulncheck weekly but not documented; no security-support period policy.

Recommendations: (1) no ISO 9001 now; (2) a buyer-facing compliance-certifications.md (what Cairn is/isn't certified for, shared responsibility, data flows to the vendor, privatim facts, ISDS/DPIA inputs, vendor security practices); (3) extend the ISO table + "do not claim" gaps; (4) CRA basics: SECURITY.md + security.txt (ISO 29147/30111), ENISA reporting readiness, document SBOM, cosign signing, support policy; (5) SSDF self-attestation; (6) mid-term pen test, then BSZ/CSPN, certified Swiss operating partner; (7) later vendor ISO 27001 (scope: development, release, licence server, support), WCAG conformance report, AV and labels as backlog.
Open questions: EU market already (beta, free tier)? → assume yes for the first EU customer, legal check; vendor ISO 27001 → later; BSZ vs CSPN → BSZ if DE/CH first; AV/labels → backlog issues; public release channel → decide before signing/SBOM docs; licence model in tenders → state it plainly.

## Research (2026-10-29) **Framing:** ISO 9001 and ISO/IEC 27001 certify an *organisation's* management system, never software. Cairn can *support* a customer's ISMS (Annex A mapping) and Swisscairn could get its own ISMS certified. #842 supported A.8.15 (logging); it did not "implement 27001". **ISO 9002 was withdrawn** (merged into ISO 9001:2000); ISO 9001:2026 was published Sept 2026. Nextcloud says the same: "SOC2 or BSI C5 cover operations rather than software in isolation". **Already done:** `docs/handbook/security-standards.md` maps features to nDSG/DSV, BK AR012, IKT-Minimalstandard, BSI IT-Grundschutz, ISO 27001/27002, NIS2, NIST, CIS, CRA, with a "supports, never certified" wording policy. Gap: the ISO table covers only access/logging/TLS; missing rows for A.5.14, A.5.28, A.5.30, A.5.33, A.5.34/8.11, A.8.9, A.8.10 (crypto-erasure), A.8.12, A.8.20/22, A.8.24 (at-rest encryption, custody, PQ). Real gaps buyers notice: classification labels (A.5.12/13), malware (A.8.7, #1022), MFA for local accounts (delegated), alerting by mail (#896), SIEM push. **Other norms worth knowing:** ISO/IEC 29147/30111 (vulnerability disclosure/handling → CRA), NIST SSDF 1.1 (cheap self-attestation), ISO 22301 (continuity; vendor continuity is a tender question), 27017/27018/27701 (only if hosting), ISO 15489 (records; don't claim GEVER), ISO/IEC 40500 (= WCAG, see #638), CSPN/BSZ (EN 17640) as the realistic *product* certification. Swiss/EU: privatim resolution Nov 2025 (warns against international cloud for sensitive data → self-hosted, operator-held keys is Cairn's strongest argument), ISG/ISV (customer's ISDS), BSI C5:2026 (providers), CRA (vulnerability reporting from 11 Sep 2026, full duties 11 Dec 2027). **Competitors:** Nextcloud: ANSSI CSPN for Files 31, certified operating partners, reference DPIA, no company ISO claim; OpenCloud GmbH: ISO 27001 badge, Blauer Engel; Proton, Tresorit, Infomaniak (SaaS): ISO 27001 (Infomaniak also 9001/14001/50001). **Vendor gaps:** no SECURITY.md / security.txt / disclosure policy; SBOM generated by ko but undocumented; no image signing; govulncheck weekly but not documented; no security-support period policy. **Recommendations:** (1) no ISO 9001 now; (2) a buyer-facing `compliance-certifications.md` (what Cairn is/isn't certified for, shared responsibility, data flows to the vendor, privatim facts, ISDS/DPIA inputs, vendor security practices); (3) extend the ISO table + "do not claim" gaps; (4) CRA basics: SECURITY.md + security.txt (ISO 29147/30111), ENISA reporting readiness, document SBOM, cosign signing, support policy; (5) SSDF self-attestation; (6) mid-term pen test, then BSZ/CSPN, certified Swiss operating partner; (7) later vendor ISO 27001 (scope: development, release, licence server, support), WCAG conformance report, AV and labels as backlog. **Open questions:** EU market already (beta, free tier)? → assume yes for the first EU customer, legal check; vendor ISO 27001 → later; BSZ vs CSPN → BSZ if DE/CH first; AV/labels → backlog issues; public release channel → decide before signing/SBOM docs; licence model in tenders → state it plainly.
Author
Owner

Reframed (Nikola, 2026-10-29)

This issue is about helping customers (companies and public bodies) meet the standards they are audited against, ISO/IEC 27001 and ISO 9001 among them, through Cairn's features, the way #842 made admin audit events always-on for 27001 A.8.15. It is not about certifying Cairn itself (software can't be certified; only organisations can).

Scope here:

  1. Customer control mapping: extend docs/handbook/security-standards.md so each relevant ISO/IEC 27001:2022 Annex A control and each relevant ISO 9001 clause (notably 7.5 "documented information": control, versions, retention, access, protection) shows which Cairn feature helps and how to configure it, with the "supports, never certified" wording: e.g. A.5.14 sharing policy and reviews, A.5.28 sealed audit + verify, A.5.30 break-glass + restore declaration, A.5.33 retention/holds/locks/versions, A.5.34 audit.ip + DPIA snippet, A.8.9 config, A.8.10 purge log + Destroy key, A.8.12 leak tracing, A.8.15 audit, A.8.24 encryption + custody. Also where Cairn helps with ISO 22301 (continuity), ISO 27701 (privacy) and records management (ISO 15489) without claiming them.
  2. A customer-facing "Compliance support" page: what Cairn helps with, what stays the customer's job (shared responsibility), and inputs for their ISDS concept / DPIA / audits.
  3. Gaps as feature issues: classification labels (A.5.12/5.13), malware scanning (#1022), mail alerts (#896), pushing audit events to a SIEM (A.8.15/8.16).

Split out: certifying Swiss Cairn as a company (vendor ISO 27001, CRA disclosure process, SECURITY.md/security.txt, signed releases, SBOM docs, pen test, BSZ/CSPN product certification) moves to a separate issue.

## Reframed (Nikola, 2026-10-29) This issue is about **helping customers** (companies and public bodies) meet the standards they are audited against, ISO/IEC 27001 and ISO 9001 among them, through Cairn's features, the way #842 made admin audit events always-on for 27001 A.8.15. It is **not** about certifying Cairn itself (software can't be certified; only organisations can). Scope here: 1. **Customer control mapping:** extend `docs/handbook/security-standards.md` so each relevant ISO/IEC 27001:2022 Annex A control and each relevant ISO 9001 clause (notably 7.5 "documented information": control, versions, retention, access, protection) shows which Cairn feature helps and how to configure it, with the "supports, never certified" wording: e.g. A.5.14 sharing policy and reviews, A.5.28 sealed audit + verify, A.5.30 break-glass + restore declaration, A.5.33 retention/holds/locks/versions, A.5.34 audit.ip + DPIA snippet, A.8.9 config, A.8.10 purge log + Destroy key, A.8.12 leak tracing, A.8.15 audit, A.8.24 encryption + custody. Also where Cairn helps with ISO 22301 (continuity), ISO 27701 (privacy) and records management (ISO 15489) without claiming them. 2. **A customer-facing "Compliance support" page:** what Cairn helps with, what stays the customer's job (shared responsibility), and inputs for their ISDS concept / DPIA / audits. 3. **Gaps as feature issues:** classification labels (A.5.12/5.13), malware scanning (#1022), mail alerts (#896), pushing audit events to a SIEM (A.8.15/8.16). **Split out:** certifying Swiss Cairn as a company (vendor ISO 27001, CRA disclosure process, SECURITY.md/security.txt, signed releases, SBOM docs, pen test, BSZ/CSPN product certification) moves to a separate issue.
Author
Owner

Shipped in v0.6.371 (PR #1047).

  • docs/handbook/security-standards.md: ISO/IEC 27001:2022 Annex A rows A.5.14, A.5.15, A.5.18, A.5.28, A.5.30, A.5.33, A.5.34, A.8.9, A.8.10, A.8.11, A.8.12, A.8.13, A.8.15, A.8.16, A.8.20/22, A.8.24, each with where to configure it; ISO 9001 clause 7.5 (7.5.2, 7.5.3) "how Cairn helps"; notes on ISO 22301, ISO/IEC 27701, ISO 15489; a "do not claim" gaps table. Control titles stay marked "Check" (licensed text not read).
  • New page docs/handbook/compliance-support.md: what Cairn helps with, what it is not (software isn't certified), shared responsibility, data flows to the vendor, the privatim resolution, and where to find what an ISDS concept / DPIA / audit asks for.
  • Related doc fixes: purge log needs access logging (code decision in #1045), encryption covers content only, Destroy key vs backups, retention vs versions.

Gaps filed: #1043 classification labels, #1044 SIEM push, #1045 purge log completeness, #1046 document approval / version limits UI / local second factor; already tracked: #1022, #896, #1023. Vendor-side items: #1042.

Shipped in v0.6.371 (PR #1047). - `docs/handbook/security-standards.md`: ISO/IEC 27001:2022 Annex A rows A.5.14, A.5.15, A.5.18, A.5.28, A.5.30, A.5.33, A.5.34, A.8.9, A.8.10, A.8.11, A.8.12, A.8.13, A.8.15, A.8.16, A.8.20/22, A.8.24, each with where to configure it; ISO 9001 clause 7.5 (7.5.2, 7.5.3) "how Cairn helps"; notes on ISO 22301, ISO/IEC 27701, ISO 15489; a "do not claim" gaps table. Control titles stay marked "Check" (licensed text not read). - New page `docs/handbook/compliance-support.md`: what Cairn helps with, what it is not (software isn't certified), shared responsibility, data flows to the vendor, the privatim resolution, and where to find what an ISDS concept / DPIA / audit asks for. - Related doc fixes: purge log needs access logging (code decision in #1045), encryption covers content only, Destroy key vs backups, retention vs versions. Gaps filed: #1043 classification labels, #1044 SIEM push, #1045 purge log completeness, #1046 document approval / version limits UI / local second factor; already tracked: #1022, #896, #1023. Vendor-side items: #1042.
Cordy closed this issue 2026-10-29 00:27:23 +00:00
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#847
No description provided.