Client-controlled runtime
The product retains its own local configuration, audit trail, licence state and operational workflow.
Private access
Cybstyx Phylaxis Pteron Private Access
Private access and ZTNA gateway for identity-aware, resource-scoped access without exposing the whole network. 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.
identity-aware private routes, micro-access and gateway sessions
- Private gateway and connector
- Access request and route policy
- Vendor and temporary access controls
- Session gate and tunnel health
- DNS or resource routing with audit evidence
Deployment and control model
Roles: Super Admin, Access Admin, Gateway Operator, Security Admin, Auditor, Service Connector
Authentication: Local RBAC with MFA for users and admins; optional Eidon SSO; signed connector authentication.
Linked with: Optional Unified Cyber Security Command Center adapter, Eidon identity, Nomion licence, Topora resource map, Kleidion secrets, Tekmerion evidence, and Chronyx session timeline.
Boundary: Private access continues within local policy when Unified Cyber Security Command Center is offline; cached identity fallback depends on client policy.
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.