Skip to content

Compliance program (PROD-14)

SOC 2 / ISO 27001 and the NL eID accreditations are formal, audited processes owned by people and auditors, not code. This document is the starting map: which Helix capabilities provide the technical controls, and what the organisational process still requires. It does not, by itself, confer any certification.

SOC 2 / ISO 27001 — technical control coverage

Control area Helix capability that supports it
Access control (least privilege) Realms, fine-grained admin RBAC, per-client scopes & roles
Strong authentication MFA (TOTP/SMS/Email OTP), WebAuthn passkeys, device push, step-up
Credential protection Argon2id password hashing, AES-GCM encryption at rest (DB_ENCRYPTION), HIBP breach check, password policy + history
Key management Per-realm signing keys (RS256 or ES256; generated, imported with a CA-signed certificate, or CSR-based; encrypted at rest with DB_ENCRYPTION), staged zero-downtime rollover, daily certificate-expiry warnings; no KMS/HSM yet
Audit logging Audit events as JSON lines on stdout for your log collector and audit tool; HelixIAM keeps no audit data itself
Session management Unified SSO sessions, idle/max/remember-me policies, admin revoke, SLO
Account lifecycle SCIM 2.0 in/out, LDAP sync, lockout/brute-force protection
Data subject rights (GDPR) Export/delete user data, consent records
Change management Versioned schema migrations (Flyway), signed releases + SBOM

What the program still requires (organisational, external)

  • Scope definition + system description; risk assessment.
  • Written policies (access, incident response, change management, vendor, BCP/DR).
  • Evidence collection over the audit period (typically 3–12 months for SOC 2 Type II).
  • An independent auditor (SOC 2 / ISO 27001) — engagement, fieldwork, report.

NL eID accreditation (external schemes)

Helix ships eIDAS, eHerkenning and DigiD connectors; live operation against the production schemes requires formal admission, not just code:

  • DigiD — admission via Logius; mandatory annual security assessment (penetration test + ENSIA/assessment per the DigiD norm) before connecting to production.
  • eHerkenning — join as a recognised participant under the Afsprakenstelsel eToegang; conformance
  • audit per the scheme.
  • eIDAS — connect through the national eIDAS node; cross-border notification process.
  • EU Digital Identity Wallet (Beta core verifier; Preview Digital Credentials API and verify-only) — Helix acts as an OpenID4VP verifier but does not register you with any wallet registrar or trust-list operator and does not obtain an access certificate for you. Accepting real wallets needs your own relying-party registration and access certificate. See EU Digital Identity Wallet.

The connectors are implemented and configurable from the console; the accreditations are scheme processes run with Logius / the eToegang scheme / the national node.

Internal penetration test (2026-10-15)

On 2026-10-15 the project ran two internal penetration tests against a build of helix-iam-server: one covering the EUDI Wallet surfaces, one covering the admin API, EU trusted lists and core. No exploitable Critical, High or Medium finding was identified in either report — every finding was Info or Low (documented design limits, operator footguns, or hygiene items), and all were fixed or dispositioned in 1.0.0-rc.11 (the view-identity-providers permission, the wallet-form revocation-off confirmation, and StrictCbor rejecting indefinite-length CBOR, among them).

Assurance roadmap

These tests were run by the HelixIAM team with full source access. An independent third-party penetration test is in preparation.

The full disposition record (internal pentest, 2026-10-15) and the security review are available to licensed customers from KubeDNA B.V. (contact@helixiam.com) on request.

Gathering evidence

An auditor asks for evidence that the controls above actually operate. Your primary sources are the audit events in your audit tool and the realm export, which is readable over the admin API for scripted, repeatable collection (see Authenticating to the API):

  • Audit events — every authentication and administrative action is one JSON line on stdout, which your log collector delivers to your audit tool (SIEM, ELK, Loki, Splunk); you search it there by type, actor, realm or outcome. HelixIAM keeps no copy, so the audit tool is the evidence store. This is your access-control and change-management evidence. See Events & audit.
  • Realm export — GET /admin/realms/{realm}/export produces a point-in-time snapshot of the realm's configured controls (RBAC, client policies, password policy, MFA requirements) suitable for attaching to a control narrative. See Backup & disaster recovery.

Pair these with your written policies and the auditor's period-of-review sampling to build the SOC 2 / ISO 27001 evidence package.

Status

Technical controls: implemented (see the table). Accreditation/audit: external processes — this document is the kickoff map, not a certificate.