Client-controlled runtime
The product retains its own local configuration, audit trail, licence state and operational workflow.
Identity security
Cybstyx Phylaxis Eidon Identity Mesh
Identity mesh, local IAM, SSO-ready federation, SCIM/LDAP/OIDC/SAML connector governance, and role claims. The product is positioned as a client-controlled security engine with professional deployment, audit and integration boundaries.
Core responsibility
What this product is built to handle.
local IAM, MFA, SSO bridge, roles and service identities
- Identity directory
- Groups, roles, and access requests
- MFA and session control
- Access reviews and break-glass
- Service tokens, connector hub, and audit evidence
Deployment and control model
Roles: Super Admin, Identity Admin, Access Reviewer, Auditor, User, Service Account, Break-glass Admin
Authentication: Primary product for local identity, MFA, SSO federation, and service identity tokens.
Linked with: Optional identity backbone for Unified Cyber Security Command Center and all Phylaxis products, plus Nomion, Tekmerion evidence, and Kleidion secrets.
Boundary: If Eidon is offline, standalone products use local admin auth and cached identity only if policy allows.
Cybstyx model
Standalone product, optional ecosystem connection
The product should be strong alone first. Integration improves visibility and coordination, but it must not become an uncontrolled dependency.
Command-center option
SecOwl can receive approved events and show posture or evidence if the client enables the adapter.
Bounded integration
Products may connect to identity, evidence, licence, secrets or timeline services when policy allows.
Every action has context
Administrative changes, service events and proof exports should remain auditable.