Security overview

Security spans the complete product interaction: the integrity of ModuLix content, the authorization of IO execution, the management and consumer boundaries of Wunderbox, and the confidentiality and integrity of Atlas observations.

This public documentation explains objectives and review methods. It does not publish control implementations, internal topology, incident procedures, risk acceptance, customer requirements, or audit evidence.

Cross-product security objectives

• Authenticate human, workload, source, and target identities.
• Authorize the smallest action, scope, privilege, and lifetime needed.
• Resolve every deployed artifact to an immutable reviewed source.
• Validate inputs before they cross a trust boundary.
• Keep credentials and sensitive values out of source, logs, evidence exports, and public documentation.
• Separate management, workload, observation, and evidence access.
• Observe security-relevant failure without collecting unnecessary sensitive data.
• Define backup, recovery, retention, and secure retirement for protected state.
• Verify actual outcomes instead of inferring implementation from code or configuration presence.

Responsibility by product boundary

Product	Primary public security lens
ModuLix	Content provenance, dependencies, input safety, privilege, and convergence
IO	Request authorization, runtime identity, secret exposure, execution isolation, and evidence
Wunderbox	Management access, consumer isolation, artifact integrity, data lifecycle, and recovery
Atlas	Source trust, data minimization, observation integrity, access scope, export, and retention

An environment's shared-responsibility record must assign the concrete owner for each control and dependency. Product names alone do not assign operational accountability.

Security review cycle

Review after a material architecture, dependency, identity, data, deployment, or recovery change; after a relevant incident or finding; and at the approved periodic cadence. Keep deviations, compensating controls, residual-risk decisions, and verification evidence in their protected registers.

Continue

• Publication boundary
• Backup and recovery
• BSI mapping approach
• Product-specific security: ModuLix, IO, Wunderbox, and Atlas