Client-controlled runtime
The product retains its own local configuration, audit trail, licence state and operational workflow.
Resource mapping
Cybstyx Phylaxis Topora Resource Mapper
Resource discovery, topology mapping, asset relationships, sensitivity classification, and connector planning. 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.
asset topology, connector planning, sensitivity and readiness
- Resource catalogue
- Native scanner and endpoint collector
- Relationship map
- Risk register and sensitivity labels
- Connector planner, compliance map, deployment readiness, and evidence ledger
Deployment and control model
Roles: Super Admin, Mapper Admin, Network/Infra Operator, Security Admin, Auditor, Service Scanner
Authentication: Local RBAC with MFA; optional Eidon SSO; scanner or collector service authentication.
Linked with: Optional Unified Cyber Security Command Center adapter, Pteron route planning, Phylax device context, Chronyx asset context, Dolion decoy placement, Tekmerion evidence, Eidon, and Nomion.
Boundary: Topora must never scan beyond approved client scope; Unified Cyber Security Command Center receives only approved map exports.
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.