Client-controlled runtime
The product retains its own local configuration, audit trail, licence state and operational workflow.
Where Trust Begins
Data protection
DLP, sensitive data classification, export approval, and data movement guardrails. The product is positioned as a client-controlled security engine with professional deployment, audit and integration boundaries.

Core responsibility
DLP, classification, export approval and movement controls
Roles: Super Admin, DLP Admin, Data Owner, Reviewer, Auditor, Service Agent
Authentication: Local RBAC with MFA; optional Eidon SSO; scanner or agent service authentication.
Linked with: Optional Unified Cyber Security Command Center adapter, Eidon identity, Nomion, Tekmerion evidence, Chronyx timeline, Keraunix response, and Kleidion secrets.
Boundary: Data guard policy works locally; Unified Cyber Security Command Center is only central visibility and command.
Cybstyx model
The product should be strong alone first. Integration improves visibility and coordination, but it must not become an uncontrolled dependency.
The product retains its own local configuration, audit trail, licence state and operational workflow.
SecOwl can receive approved events and show posture or evidence if the client enables the adapter.
Products may connect to identity, evidence, licence, secrets or timeline services when policy allows.
Administrative changes, service events and proof exports should remain auditable.